Your comments


The streaming URL was copied from ONVIF Device Manager. Exact message can bee seen in the log prompt in the bottom of the screenshot below

When I press Configure I get "camera does not support ONVIF"

I get this message even if the camera is disconnected

Netatmo log message:

Monitor : 03.03.2020 12:17:36 : General\Users\User : LastServerMessage : Devices : 03/03/2020 12:17:35 : Error : Devices\Netatmo : NotFound (404) GET: /api/getstationsdata?access_token=%0

I tried to download the example again and configure it. For some reason this gives me a "403" error. Not the 404 as above.

When trying to connect to's API I get a "error connecting to device" message.

I have tried now with the alpha version. No change in the behaviour. Netatmo, tibber, is not working.

Did you try to delete and reinstall the app? Worth trying

Which server version are you running, Håvard?

Thanks for the tip, but I still get the 403 error.

Didn't solve my issue :( I have updated the Netatmo specific thread with details.

Hi Guys,

I'm currently having problems with the Netatmo Template that has been working pretty much flawless on my system for a while. Some weeks ago it stopped working after an update of bOS. I have double checked the client id, secret, username and password. I even tried to use the fresh template without success. I updated to the latest beta 4.6.26 tonight and it seems it's getting a different message than I got on the previous releases.

If i disable and enable the device it states "connected"

If I then use the send function on "weather stations" I get this message:

Devices : 10.12.2019 21:07:04 : Error : Devices\Netatmo : Forbidden (403) GET: /api/getstationsdata?access_token=%0

I guess the 403 is some access denied message or similar...

If I press the send function on "oAuth" I get this message:

Devices : 10.12.2019 21:11:13 : Error : Devices\Netatmo : Error connecting to device.

On previous releases I got this message:

Devices : 07.11.2019 12:35:50 : Error : Devices\Netatmo : Error connecting to device. Content-type   at System.Net.Http.Headers.HttpHeaders.CheckName (System.String name) <0x707728a0 + 0x000fc> in :0 
at System.Net.Http.Headers.HttpHeaders.Add (System.String name, IEnumerable`1 values) <0x707727d0 + 0x0002f> in :0
at System.Net.Http.Headers.HttpHeaders.Add (System.String name, System.String value) <0x70772740 + 0x00053> in :0
at ComfortClick.Http.Driver.HttpDriver+d__10.MoveNext () <0x7073aef0 + 0x00297> in :0

Is it working for you?

I have now updated to the latest beta 2 or 3 times past couple of weeks. Still not working. It's a bit annoying not having the outside temp visible on my KNX switches. Do i have to issue a ticket to get response from the developers? Seems it's a bit random what they read on the forum regarding bugs.