I didn’t say it wasn’t an issue with the integration. I said that it was a different issue from the onw mentioned above. Please create a new github issue and post debug logs
Don’t agree with that. Had one innr SP120 and the two Xiaomi motion sensors connected always dropped out after a day or two.
Unplugged the innr switch, reconnected the sensors (now connected to a Feibit switch), the motion sensors are working reliable since weeks (again).
My experience regarding Xiaomi sensors and battery powered rocker switches: it is crucial to find the “correct” node. This might be a node even two floors above or below the end point device. If your Xiaomi end point devices drop out on a regular basis, look up to which end point device they are connected and show this behaviour. Turn off this device and reconnect your Xiaomi device. Iterate until you find the best end point device.
It’s so weird. I have the Conbee II stick with DeconZ in Home Assistant for a year now without 1 single issue, dropout or whatsoever.
I have 20+ Philips Hue Lights, 6 Ikea lights, 7 door sensors, 4 pirs and a couple of buttons from Xiaomi and also a couple of Philips Hue dimmer switches and a couple of Pirs.
I think that interference is a really big thing also. Zigbee works on the same frequency spectrum as your WiFi. Always move your Wifi router away from the Conbee stick, use a USB extension cord for the stick, even a powered USB hub would be a good idea.
i never had issues with wifi interference, no mather what channel i choose… the only thing i struggled for a long time were my xiaomi sensors, seems xiaomo, once they are paired to a repeater/router, they dont change anymore … so if you reallocate some smart switches, make sure, you unpair/pair again the xiaomi stuff , so they choose another router then
Hi, anyone knows if a rain sensor exists? I have a xiaomi water sensor, but offcourse not the same effect for rain
for some reason my add-on was suddenly stopped? i have no idea why? this was from log :
what could be cause?
2020-08-14 12:08:54 ERROR (MainThread) [pydeconz.websocket] Client connection error
12:07:48:277 don't close database yet, keep open for 900 seconds
12:07:51:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:52:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:53:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:54:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:55:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:56:232 don't close database yet, keep open for 900 seconds
12:07:59:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:07:59:286 GW firmware version: 0x26330500
12:07:59:286 GW firmware version shall be updated to: 0x26350500
12:08:00:275 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:08:01:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:08:01:464 don't close database yet, keep open for 900 seconds
12:08:02:274 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:08:03:275 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
12:08:03:341 Current channel 11
12:08:03:373 Device TTL 2400 s flags: 0x7
12:08:04:275 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
[12:08:04] WARNING: Your direct VNC access is not protected!
[12:08:04] INFO: Starting VNC server (local/no)...
2020/08/14 10:08:04 [notice] 323#323: signal 15 (SIGTERM) received from 313, exiting
In exit
Closing socket listening at 127.0.0.1:5901
2020/08/14 10:08:04 [notice] 1851#1851: exiting
2020/08/14 10:08:04 [notice] 1851#1851: exit
2020/08/14 10:08:04 [notice] 323#323: signal 17 (SIGCHLD) received from 1851
2020/08/14 10:08:04 [notice] 323#323: worker process 1851 exited with code 0
2020/08/14 10:08:04 [notice] 323#323: exit
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
same here, we got the same logs before it stopped:
[18:38:42] INFO: Starting VNC server (local/yes)…
2020/08/14 10:38:42 [notice] 323#323: signal 15 (SIGTERM) received from 314, exiting
2020/08/14 10:38:42 [notice] 1001#1001: exiting
2020/08/14 10:38:42 [notice] 1001#1001: exit
2020/08/14 10:38:42 [notice] 323#323: signal 17 (SIGCHLD) received from 1001
2020/08/14 10:38:42 [notice] 323#323: worker process 1001 exited with code 0
In exit
Closing socket listening at 127.0.0.1:5901
2020/08/14 10:38:42 [notice] 323#323: exit
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
1 Like
Verry strange, some issue in the container?
I’m not sure. This is the first time, it’s been a week since I updated the addon. I was idle for 30 mins after checking both phoscon and deconz gui,
i hope its a one time only, but clearly an issue with container…
i am running Hassos 4.12 , add-on 6.2.3
Same here, had it once a few weeks ago, and has happened 3 times this morning.
I’ve restarted my VM and seems to be OK so far
Hassos 4.12 , add-on 6.1.1
no coincidence then , maybe an easter bug in container
Same here.
Coincided with some 500 errors in appdaemon. Not sure if that was because it couldn’t find deconz to turn on the lights?
I’ve also had issues the last week or 2 with the add on randomly stopping by itself. I hit start and everything is back to normal for a day or 2 then stops again.
I’ve just disabled vnc in the settings to run everything via ingress to see if it helps. Next time it stops I’ll try and get the logs for you guys to have a look.
1 Like
I just had this happen last night. The addon randomly stopped itself at 5am last night. The logs show that it was a normal stop, without any errors or warning; it just stopped like I pushed the button or something.
It started again without any problems, but I’m eager to see how long it lasts before stopping itself again.
New ConBee, but old HA user here. Despite reading through this monster thread, I can’t connect any sensor or light to my ConBee II stick. The gateway is shown, the HA integration is authenticated and everything seems to be ok but no matter what I do, no sensor/light is found in Phoscon. Any hints what I should be checking? (Setup is Pi4, USB hub with Conbee and Aeotec, latest releases.)
Guys, can we check with HA if an addon is running? if not => start the container? is that possible without dockermon ?
that would resolve/workaround for now if container is stopped for no reason
There is something called docker_monitor, but that doesn’t work with Supervised. Glances can achieve this also I think…
Perhaps describe the pairing process that you are taking, in a step-by-step basis?
I do remember with the Xiaomi door sensors, you need to activate them with a magnet in order for Phoscon to pair them.
1 Like