You’re right, I’ve been looking at the website of Météo France unfortunately the paca region is not concerned. thanks for your reply
I can’t get it work; could someone post a complete yaml configuration please ?
Thank you in advance.
You can try with the GUI in “configurations / integrations / +” and search meteofrance.
Thanks!
Below a basic YAML config for those interested:
- type: custom:meteo-france-weather-card
entity: weather.paris_01e_arrondissementt
Hello
Thanks for this great component and lot of work done.
Unfortunately, I have my data refreshed rarely with a lot of messages below in the log.
Consequently, ‘next rain’ sensor show data from previous day.
Any clue to fix it ?
2020-05-13 09:40:28 WARNING (MainThread) [homeassistant.helpers.entity] Update of weather.mycity is taking over 10 seconds
2020-05-13 09:40:49 WARNING (MainThread) [homeassistant.components.weather] Updating meteo_france weather took longer than the scheduled update interval 0:00:30
Thanks a lot
Hello,
Since yesterday, my meteo france sensor doesn’t work. Everything is with unavailable status.
Is the same for you ?
Edit : Certainly due to new web site…
Same here since yesterday too.
Same here not working since 03/08.
For your information : https://github.com/home-assistant/core/issues/38592
Fix in 0.114 version
Hello all,
since 0.114 meteo france working fine again but some changes appears
for the next rain, we have now
sensor.*******_next_rain
1_hour_forecast:
- ‘11:15’: Temps sec
- ‘11:20’: Temps sec
- ‘11:25’: Temps sec
- ‘11:30’: Temps sec
- ‘11:35’: Temps sec
- ‘11:40’: Temps sec
- ‘11:50’: Temps sec
- ‘12:00’: Temps sec
- ‘12:10’: Temps sec
I used until now the code of @weado to have the rain forecast but it is not possible any more since now it is the schedule which appears and not the number of minutes. do you have any idea to correct this
I’m looking for a good solution, but it isn’t easy with the time informations.
Hello @weado did you found a solution ?
The next rain display was amazing before I really want to fix that display
So, it isn’t easy because the attributs change every 5 minutes and I don’t find the solution to get value in function of the random attribute…
If you have some ideas to help me …
You should wait ben31 is working on his integration to select the best value to publish.
So it might change again in next or nextest version.
Can I suggest something ?
Is it possible to have 9 boolean entities NextRain5, NextRain10 etc ?
I’m using Météo France for a city in Belgium. The integration (temperature) only updates every 3 hours for me. Can I change this? Is this normal behavior?
Hey guys. OK the attribute for next rain have a bad design and I’m responsible for it. Sorry. I working on a fix.
It will be a dictionary with fix keys like “0 min”, “5 min”, “10 min”, etc. and the status in text returned by Météo France.
You should be able to construct your card or automation with this modification.
@cyrilphoenix71 we won’t create an entity by delay. But you will be able to create it with template sensors.
@aocaoc can you open an issue on GitHub and provide some logs ?
Hello,
have you succeed to update the lovelace yaml with the 1.115 update ?
Thanks a lot !
I don’t use this card.
You have to update the attributes names like rain_level_0min
by in_0_min
And you have to update the tests like ... == 2
with the possible value in text. The list of possible value are in the doc
If you succeed can you share the final code here?
I will try
Thanks