enkama

+1 on this one. Also getting something similar like that in my logs. ``` 2022-01-26 12:10:14 ERROR (MainThread) [custom_components.reolink_dev] Timeout fetching reolink.Balkon Kamera.motion_states data 2022-01-26 12:11:14 ERROR (MainThread) [custom_components.reolink_dev.binary_sensor] Motion...

The similarity I saw was both times its trying to query the motion state from the api and both time its File "/config/custom_components/reolink_dev/binary_sensor.py", line 122, in handle_event and after that...

+1 on that motion event error. Getting `Motion states could not be queried from API`.

Yea please fix this or at least dont let it appear. Its spamming my log and its coming over homeassistant so I cant even suppress the log. @fwestenberg

Removing the camera from the generic camera configuration seems to fix it for me.

There is a firmware update. Having similar problems. Maybe that helps. https://reolink.com/download-center/?firmware-product=e1-zoom

Same exact stuff for me.

I mean the connection issues happen pretty often ngl. The question is if its coming from nuki_ng or from nuki itself. Also this comes up in the console. ``` 2022-08-02...

https://github.com/Wibias/hass-variables Fixed in my active fork.

That would be neat! But not sure how everyone else using thermal_comfort thinks about that.