Encore un grand site du service public…
1 « J'aime »
Doit y avoir un souci car meme l’appli officielle meteofrance pour iphone ne fonctionne plus non plus
mael
Juin 18, 2023, 9:49
7
Pareil par ici. pas la première fois, la dernière ils avaient pétés leurs DNS et étaient passés en cata chez cloudflare Intégration Météo France "Unknown error occurred" - #4 par Neuvidor
Ca va ils ont remis en ligne après 5h offline.
2 « J'aime »
Le site Météo France fonctionne de nouveau bien, mais l’intégration ne fonctionne plus pour moi
1 « J'aime »
Pareil plus rien qui remonte sur HA
1 « J'aime »
Pareil, j’ai désactiver météo france car ca gonfle les logs. Le site fonctionne, mais pas l’intégration …
qq vu que c’est pas 100% inaccessible ?
EDIT, et encore plus intéressant c’est que le line qui est bloqué (404) me donne un json si j’utilise curl de la même machine. et… son résultat donne forecast par jour et (!) heure en même temps…ce qui peut donner un option d’avoir les deux pour la même ville (si les devs de cette intégration ont d’envie)
1 « J'aime »
idem pour moi l’integration ne fonctionne plus !!
1 « J'aime »
Idem pour moi depuis hier (18h36 précisément …) l’intégration ne fonctionne plus. Les services web de l’API Météo France ne sont pas opérationnels au moins pour certains clients
On va patienter, car le site OK mais sur HA HS.
Exact,https://webservice.meteofrance.com
2 « J'aime »
opened 05:52AM - 19 Jun 23 UTC
closed 01:59PM - 22 Jun 23 UTC
integration: meteo_france
### The problem
Météo France integration have been failing to initialize for at… least one day. It has been working before that. No change in HA version
### What version of Home Assistant Core has the issue?
2023.3.0
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Météo France
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/meteo_france
### Diagnostics information
I have been restarting HA. Here are various log events after startup
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.config_entries
Source: config_entries.py:1244
First occurred: 07:24:59 (1 occurrences)
Last logged: 07:24:59
Config entry 'Saint-Pierre-de-Jards - Centre (36) - FR' for meteo_france integration not ready yet: None; Retrying in background
Logger: homeassistant.components.meteo_france
Source: helpers/update_coordinator.py:215
Integration: Météo-France (documentation, issues)
First occurred: 07:21:11 (15 occurrences)
Last logged: 07:37:52
Error requesting Météo-France alert for department 36 data: 502 Server Error: Bad Gateway for url: https://webservice.meteofrance.com/warning/currentphenomenons?token=__Wj7dVSTjV9YGu1guveLyDq0g7S7TfTjaHBTPTpO0kj8__&domain=36&depth=0
```
### Additional information
_No response_
Citation
opened 04:51PM - 28 Apr 23 UTC
closed 08:18AM - 07 Dec 23 UTC
integration: meteo_france
### The problem
Hello,
I noticed that the integrations keeps reporting "Jaun… e" for "Orages" in the 13, while no clouds in the horizon.
I dug a little bit and that's what the API (https://webservice.meteofrance.com/warning/currentphenomenons?token=...&domain=13&depth=0) returns:
```json
{
"update_time": 1680595200,
"end_validity_time": 1680667200,
"domain_id": "13",
"phenomenons_max_colors": [
{
"phenomenon_id": 1,
"phenomenon_max_color_id": 1
},
{
"phenomenon_id": 4,
"phenomenon_max_color_id": 1
},
{
"phenomenon_id": 3,
"phenomenon_max_color_id": 2
},
{
"phenomenon_id": 2,
"phenomenon_max_color_id": 1
},
{
"phenomenon_id": 5,
"phenomenon_max_color_id": 1
}
]
}
```
So I guess that's make sense if 3 is Orages and 2 is yellow. Problem is: today is April 28, and `end_validity_time` is April 5. And no clouds since then (of course, the sun is the only option in the south 😁).
I'm not an expert of this API, so just guessing: I think that if `end_validity_time` is in the past (maybe with a little margin?) we should take it as "all green".
What do you think? I could go for a PR in that sense if it makes sense to you.
### What version of Home Assistant Core has the issue?
core-2023.4.6
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Météo-France
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/meteo_france/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Quentame
3 « J'aime »
La correction partielle (pour que le reste des sensors continuent de fonctionner) est là:
home-assistant:dev ← hacf-fr:meteo_france/fix_alert_catch
opened 11:05AM - 20 Jun 23 UTC
## Proposed change
<!--
Describe the big picture of your changes here to com… municate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Fixes #94839: allow Météo-France config entry to continue even if the alert API fails.
2 reasons to investigate:
- API server error: which is temporary
- API changes: which needs an integration rework
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] 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
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #94839
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] 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.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
3 « J'aime »
mack
Juin 20, 2023, 12:38
20
Merci pour le lien .
2 « J'aime »
