-
-
Notifications
You must be signed in to change notification settings - Fork 30k
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
New meteo_france sensor not working #18375
Comments
Thank you for opening this issue. 1. Some postal codes are indeed shared for several cities. This would need a new configuration entry needing insee_code, slug and postal code of the town which is quite annoying. (The search results doesn't return anything with the insee code as the query...) 2. no forecast for the query 3. About the weather card for lovelace |
You're welcome, you did a great job. I was also thinking about create one for meteo france (like i also have an idea for a "SNCF" components)...
We can maybe imagine a simple solution like
Not at all, mine was exactly
Awesome ! |
I found out what causes the issue It's easy to fix it with quotes : - platform: meteo_france
postal_code: '01700'
monitored_conditions:
- temperature
- weather
- wind_speed
- next_rain I will edit the documentation with a default value using quotes About the way to select the correct city, this is indeed a solution. |
Some postal codes have a leading zero which would be interpreted as an octal int. Adding quotes on the documentation to be avoid confusion with those postal codes. Fixes home-assistant/core#18375
Docs merged: home-assistant/home-assistant.io@657d1e5 |
Hello, First of all, thank you for your component! Do you know how to use it with another countries? (By example Luxembourg (Luxembourg Ville)). If I search '06590' (via id in http://www.meteofrance.com/previsions-meteo-monde/luxembourg/06590) -> Théoule sur mer If I search 'Luxembourg' (http://www.meteofrance.com/mf3-rpc-portlet/rest/lieu/facet/previsions/search/luxembourg), it takes the second value Best regards, |
@victorcerutti The sensor name should stay the same even if the city name is different, no ? (to be aligned with others weathers sensors) |
@anthosz It currently only work with cities from France |
@adamotte I don't know if there is a standard for this. |
Some updates ? I was going to post a bug report when realised it was already on the task list ! Thanks ;) |
@victorcerutti i also observed a strange case, in fact, some postal codes can be used for multiple cities/places (like mine : 33160). can you please add an extra option ( like city_name for example) or may be liste all the available cities as sensors ? |
Hi everyone. So, what's coming with this update:
Caveats:This is going to be a breaking change as the configuration will move from a sensor one to a whole |
Thanks for the great news and work on it, impatient to get that new version to use with my voice assistant 👍 |
Just so you know, it's live since wednesday |
sensor stopped working ... even after multiple restart.
i'm using HA 0.93.2 :( |
Hi, I confirm, I have the same issue but but city outside France works... Only France city are impacted. Best regards, |
Same here, component broken again :( very unstable component... |
cpython issue is python/cpython#83065 |
Home Assistant release with the issue:
Home Assistant 0.82.0
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io / DietPi
Component/platform:
New Sensor Meteo France
New merge
Description of problem:
If a postal_code is shared by several cities (it's possible in France, eg : 01700), sensor not work and return error.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
By the way if the weather component could be created to be use with Lovelace Weather Card it will be awesome.
cc @victorcerutti
The text was updated successfully, but these errors were encountered: