Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Météo-France setup in non French cities (because of failed next rain sensor) #134782

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

Quentame
Copy link
Member

@Quentame Quentame commented Jan 5, 2025

Proposed change

Test if the next rain is available for a configured location/city before adding it.

Only warn if no available, no error.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link

home-assistant bot commented Jan 5, 2025

Hey there @hacf-fr, @oncleben31, mind taking a look at this pull request as it has been labeled with an integration (meteo_france) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of meteo_france can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign meteo_france Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@Quentame
Copy link
Member Author

Quentame commented Jan 5, 2025

Tested with following cities:

City rain_product_available rain API response Special thanks
Annecy - Rhône-Alpes (74) - FR 0 @Quentame
Awans - Wallonia - BE None #132478 @vegetrunks69
Barrancoueu - Midi-Pyrénées (65) - FR 0 #90397 @faizpuru
Brussels - Brussels Capital - BE None
Lyon - Rhône-Alpes (69) - FR 1 @Quentame
New York City - New York - US None
Québec - Quebec - CA None
Turin - Piedmont - IT None #132478 @parabag

@Quentame
Copy link
Member Author

Quentame commented Jan 5, 2025

Pipe only fail because of coverage diff

@@ -83,7 +84,13 @@ async def _async_update_data_alert() -> CurrentPhenomenons:
update_method=_async_update_data_rain,
update_interval=SCAN_INTERVAL_RAIN,
)
await coordinator_rain.async_config_entry_first_refresh()
try:
await coordinator_rain._async_refresh(log_failures=False) # noqa: SLF001
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we use _async_refresh? And not a public function?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As written in the description: to only warn but not raise an error.

Otherwise the user will both have an error and a warn.

Because async_refresh log_failures=True !

@home-assistant home-assistant bot marked this pull request as draft January 6, 2025 14:32
@home-assistant
Copy link

home-assistant bot commented Jan 6, 2025

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@frenck frenck modified the milestones: 2025.1.1, 2025.1.2 Jan 6, 2025
@Quentame Quentame marked this pull request as ready for review January 7, 2025 13:54
@home-assistant home-assistant bot requested a review from joostlek January 7, 2025 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants