Netatmo Welcome: binding leaves live image NULL

Add-ons Bindings
1

Hi
on my Openhab 4.2.0 the netatmo binding delivers the channel “live#picture” for my Presence cameras (outdoor) as expected. However my Welcome camera (indoor) remains NULL

Screenshot 2024-04-19 082540

If this helps, the last-event#snapshot is also NULL for all cameras.

Any thoughts? Is this an error in my config? A binding issue?

Thanks
Thomas

2

This can happen if you setup your system not to record you and the known persons. Could it be the case ?

3

No, this doesn’t help or yes I do save them.

Perhaps I have a misconception? Is there any kind of documentation I can read? More than the binding documentation.
I would expect the “Live Monitoring” channels to be filled all the time when the APP (Home + Control & Security | Legrand - Netatmo - Bticino) also shows that live content is available.
And the same with “Last Event” channels. They should be all filled with data for the last event and replaced as soon as there is a new (last) event.

But my Welcome Live never gets filled and the “Last Event” snapshots get filled but go back to NULL aber some time.

4

Hi all,

I have a similar issue. I am using a Netatmo Presence together with the Netatmo Binding. So far, it works in general. When there is a new event, the “:last-event#typ” and “:last-event#time” channels both get updated. Also the url “:last-event#local-video-url” gets updated, however this is updated to null.

Once that happened, no further update appears. Waiting or a restart of openhanded also does not help. However, when I uninstall the add-on and reinstall it again, the value is correctly loaded. The bug is fully reproducible. Nothing special in the logs:

2025-05-20 23:21:45.653 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - executeUri GET  https://api.netatmo.com/api/getevents?home_id=XXXXXXXX
2025-05-20 23:21:45.771 [DEBUG] [l.handler.capability.CacheCapability] - HomeCapability requesting fresh data for netatmo:home:XXXXXXXX:netatmo_home
2025-05-20 23:21:45.771 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - executeUri GET  https://api.netatmo.com/api/homesdata?home_id=XXXXXXXX 
2025-05-20 23:21:45.834 [DEBUG] [mo.internal.handler.ApiBridgeHandler] - executeUri GET  https://api.netatmo.com/api/homestatus?home_id=XXXXXXXX 
2025-05-20 23:21:46.016 [DEBUG] [handler.capability.RefreshCapability] - 'netatmo:home:XXXXXXXXXX:netatmo_home' next refresh in PT2M30S

Could that have the same reason and did you, @Thomas_Hartung, find a final solution?

Best, Lui

5

Could that have the same reason and did you, @Thomas_Hartung, find a final solution?

I wouldn’t say I solved it. It was more a trial and error thing until it worked … somehow.

From memory, it was a combination of

  • Update OpenHab (think it was from 3.3 to 3.4 at that time)
  • Create a new account (MyApps) at dev.netatmo.com
  • Using Image with refresh and not the “live” channel.
Image		itemNetatmoFloorSnap		"Bild Flur"				<Camera> (gNetatmo)		{ channel = "netatmo:welcome:xyz:myhome:cam_eg:last-event#snapshot" }

Image item=itemNetatmoFloorLive  refresh=2000 visibility=[itemHomeMaticMotion_EG_20m==ON]

As you can see, I use a motion sensor to change visibility of the netatmo. And of course the refresh doesn’t make total sense. But like this I get the latest snapshot from the camera.

Not perfect at all. But it works.