Forum

Hi,  I have successfully paired (linked) some lights with my Legrand GW using the H+C App. Some of these lights are controlled via a Legrand Micromodule dimmerSwitch, others are Philips HUE bulbs.

These lights shows up automatically in my Home Assistance (2024.7.8) via the Netatmo Integration. So far, so good. However, what is not so good is that the Netatmo Integration isn’t properly showing the state of these lights. That is, if I change the brightness or turn a light off/on using H+C , there is a significant delay before the state and brightness values for that light is updated in HA.  The delay varies significantly from almost instant up to 5 minutes. I get a feeling that the Netatmo integration uses a fixed update cycle of perhaps 5 minutes for all its entities. So, if i.e. the brightness is changed in the H+C near the time of the next scheduled state update cycle, then the report appears quick and responsive. But if the last update has just passed, then one have to wait 5 minutes before the reported values are updated.
Is this by design? Can the update cycle be changed? Do others experience the same as I do?

(I’ve tried running the service Home Assistant Core Integration: Update entity to see if I could force an update of the state, but it does nothing.)

On the other hand – the other way around – if I change the brightness in HA, the change is almost instantly reflected in the H+C app, but the numeric brightness value is completely off. I have to set the brightness to 7% in HA in order to get a 50% actual dimming level in H+C.  Then, after the above mentioned delay, when the state value in HA is finally updated, it changes to 50% even though I did set it to 7%

Any comments, advises or clarifications are highly welcome.

Hello Oyvind,

“However, what is not so good is that the Netatmo Integration isn’t properly showing the state of these lights. That is, if I change the brightness or turn a light off/on using H+C”

It’s normal. The native Home + Control app uses webhooks to display in real-time the ON/OFF/dimming light state. Webhooks are not available for third-party integrations like HA, so in many cases they regularly perform a call to the API to retrieve an update of the status (surely every 5 minutes as you noticed). That’s why there is a delay

This interval between 2 calls is managed by the integration. It’s maybe manageable in your .yaml file but I can’t tell you more about this. The status can be retrieved via a call to /homestatus endpoint : https://dev.netatmo.com/apidocumentation/control#homestatus (pay attention to the number of calls limits : https://dev.netatmo.com/guideline#rate-limits)

“On the other hand – the other way around – if I change the brightness in HA, the change is almost instantly reflected in the H+C app, but the numeric brightness value is completely off. I have to set the brightness to 7% in HA in order to get a 50% actual dimming level in H+C.  Then, after the above mentioned delay, when the state value in HA is finally updated, it changes to 50% even though I did set it to 7%”

I didn’t see any other similar feedback. The brightness value is done with a call to the /setstate endpoint and is retrieved in the same /homestatus call as previously. In my opinion it could be :

• a problem with the HA slider to set the brightness. Could be confirmed by setting a 50% brightness value in Home + Control app and see if it works or if the behavior is the same
• with some bulb brands the dimming behaviour can vary (but in this case the variation is huge, which is strange)

In any case, if it correctly works with the H+C app, the problem is on HA side

Have a good day,

Leslie – Community Manager

Hi Leslie – and many thanks for your comprehensive reply.

I do use webhooks in Home Assistant to interact with the Netatmo cameras, so technically, there shouldn’t be any reason why H+C could also be monitored through webhooks.

Having said that, I must admit that for some reason, the camera webhook API hasn’t been very cooperative lately. It used to be 100% stable and reliable, but sometime around the update to HA 2024.7.x  it began failing. Now it sometimes suddenly begin reporting events, often in the middle of the night, and then just “dies” and remains totally silent for a day or two. While the H+S app reports events all the time.

Back to the LED’s. It isn’t possible to set exactly 50% dimming in the H+C app as the scale is just an analogue bar from left to right. There are no accurate position data presented. But when I adjusted the brightness bar to approximately 50%, it was never reflected in HA at all (I waited almost 20 min).
But turning the LED fully on/off in H+C, isn’t reflected i HA either.

If I turn the LED fully on/off in HA, it is immediately reflected in H+C

I hope you can make something useful of it.

Rgds
Oyvind

Hi Oyvind,

“I do use webhooks in Home Assistant to interact with the Netatmo cameras, so technically, there shouldn’t be any reason why H+C could also be monitored through webhooks.”

Webhooks are only available for Security devices (list here : https://dev.netatmo.com/apidocumentation/security#Products). We don’t allow webhooks for 3rd party services accessing Home + Control products

“Having said that, I must admit that for some reason, the camera webhook API hasn’t been very cooperative lately.”

We had some problems on our side the 2 last weeks with notifications (a strong delay or notifications not sent). As far as I know Netatmo teams fixed that last Saturday

“Back to the LED’s. It isn’t possible to set exactly 50% dimming in the H+C app as the scale is just an analogue bar from left to right. There are no accurate position data presented. But when I adjusted the brightness bar to approximately 50%, it was never reflected in HA at all (I waited almost 20 min). But turning the LED fully on/off in H+C, isn’t reflected i HA either.”

Yes, the dimming bar is not really precise in H+C app. To correctly check you could use the Try-It out tool from the public API : https://dev.netatmo.com/apidocumentation/control#homesdata

The feedback for the “brightness” value in HA can only be done with a call to /homestatus endpoint. The API is not impacted by the problems of the webhooks. I don’t know if HA managed to check the changes of the “brightness” value after a call to the endpoint, so unfortunately we can’t act on it on our side

Have a good day,

Leslie – Community Manager