jdejaegh / irm-kmi-ha Goto Github PK

Would it be possible to expose the hourly weather data via attributes? More specifically I'm interested to retrieve the rain in the upcoming hours to see if I will let out my mowing robot or not.

The default weather integration does it like below.

I can retrieve the rain data for the coming hours like:
{{ (state_attr(''weather.forecast_home'',''forecast'')[0].precipitation | float(0) + state_attr(''weather.forecast_home'',''forecast'')[1].precipitation | float(0) + state_attr(''weather.forecast_home'',''forecast'')[2].precipitation | float(0) ) < 5 }}

I suppose you have the data because i see it in the lovelace, but I don't see any state attributes I could retrieve.

hi,

I was installing the integration and ran into an error : "Could not get data from the API"

Wondering if the API target is still correct (https://app.meteo.be/services/appv4/) or anything else that could be related?

Get the debug logs: go to Settings > Devices & services > IRM KMI integration > Disable debug logging.
Download the file and attach it here.
home-assistant_irm_kmi_2024-03-24T12-32-13.602Z.log

Describe the bug
FileNotFoundError: [Errno 2] No such file or directory: 'custom_components/irm_kmi/resources/roboto_medium.ttf'

Version

• Home Assistant: [2024.3.3]
• IRM KMI integration 0.2.3

Since one of the most recent versions the uv-index attribute seems to be missing:

I think the last IRM KMI version to have this was version 0.2.4 but I could be wrong here.
Currently I'm on version 0.2.8.
Is it possible to include this attribute again?

Is it possible to get the KMI data for active pollen and the current Uv-index as seperate attributes?
These values are the only ones missing to complete my custom weather card so I would greatly appreciate it if these became available!

Right now, there is a storm warning for Brussels. I can't find it anywhere. Maybe the warning sensor could be used.

Hi

Great integration to have as a Belgian!

Would it be possible to improve the labelling during the night, so weather Lovelace integrations would show a moon instead of a sun in case it is 'partly cloudy' during the night?

I'm not sure if this is accessible through the KMI data you pull, although the KMI website does properly show a moon during 'partly cloudy' at night. If not available, perhaps sunrise and sundown hours are available so one could write a workaround to have a 'partly cloudy night' condition.

I also asked if perhaps the Lovelace integration I use can add this particular label, or if it can make an override during the night.decompil3d/lovelace-hourly-weather#662

As you see below, it is a bit odd that during the night we see this 'partly cloudy' condition with a sun.

Thanks for considering this improvement.

For example

Thank you for this integration!

Right now, there weather is characterised as exceptional. True is not really the case.

Screenshot with Clock Weather Card:

When I set the 'live' option on the camera of the radar, the bottom graph is not shown any more. Not sure if this is an issue with HA or this integration.

P.S. thanks for this repo, it's awesome already!

On the following screenshot, met.no data above and IRM below:

Sunday temperature should go to 6°C instead of zero. And Thursday is missing.

While reporting this, Sunday got fixed but Wednesday vanished. This all happened between midnight and 1.00.

For reference:

Have they inverted the tonight and Sunday values?

Also of interest: Wednesday's night value is higher the during the day. This might have wrecked havoc in your logic.

hi,
I am on the latest version, I am in Belgium, in Liège, where, for the moment, there is a yellow alert in the wind, but the alert sensor always tells me "secure"
Is there anything to change or modify or is it a bug?

there is indeed alert, so why tell me “secure”??

Currently, when the API times out, Home Assistant shows all the sensors as 'unavailable' until the next successful refresh. As the polling interval is 7 minutes, it means that the sensors are 'unavailable' a multiple of 7 minutes.

Things to investigate to improve that:

• Keep the existing data and do not make the sensor become unavailable immediately (wait 2 or 3 failed updates before doing so)
• Increase the timeout limit on the client side
• Retry sooner than the default polling interval if the last request timed out (may not be nice to the API)

Linked to #21