Hi guys. I have a problem. after updating home-assistant to 0.113.2 and deconz firmware to 2.05.79. The usb stick began to lose connection with all zigbee devices very often. below I attach a log and a screen. Tell me how to fix
18:56:20:644 delay sending request 212 dt 1 ms to 0x00158D0002237EBC, ep: 0x02 cluster: 0x0000 onAir: 1
18:57:03:176 don't close database yet, keep open for 900 seconds
18:57:03:230 Remove websocket 172.30.32.1:46374 after error Unknown error
18:57:03:231 New websocket 172.30.32.1:46546 (state: 3)
18:57:03:248 Current channel 15
18:57:03:258 Device TTL 6774 s flags: 0x7
18:57:05:244 delay sending request 246 dt 0 ms to 0x00158D0002237EBC, ep: 0x03 cluster: 0x0000 onAir: 1
Hey, i got the exact same problem since the update of deconz and hassio. After reboot it seems to work for 1 or 2 hours. but after that it disconnects every couple of minutes. the devices are all unavailable. i have no clue what to try exept for a rollback.
Hi All, has anyone had issues accessing deconz via VNC viewer since updating?
I have just gone from v6.1.1 to v6.2.3 and seem to be getting stuck on the connecting screen.
Same for me. Connecting using regular VNC client (I use Tiger on OSX) works perfectly fine. Frankly speaking I’d prefere not to have choice at start and go directly to deconz (old way) or at least have option in add-on configuration to set default startu behaviour.
For me the update doesn’t go well. If I update the update via the phoscon page, it says update succesfull, after a reboot of home assistant, it’s on the previous version again. Running Home Assistant in a VMware on virtual box.
If I check the log file off the dezonz app, it tries to continiously update the gateway. But it fails to succeed.
09:56:33:091 GW firmware version: 0x264a0700
09:56:33:091 GW firmware version shall be updated to: 0x26580700
09:56:37:097 Current channel 15
09:56:37:106 Device TTL 4857 s flags: 0x7
09:56:37:157 don't close database yet, keep open for 900 seconds
09:56:42:085 don't close database yet, keep open for 900 seconds
09:56:52:059 don't close database yet, keep open for 900 seconds
09:56:58:081 remove outdated neighbor 0x85E8
09:57:01:162 don't close database yet, keep open for 900 seconds
09:57:06:085 don't close database yet, keep open for 900 seconds
09:57:16:058 don't close database yet, keep open for 900 seconds
09:57:25:161 don't close database yet, keep open for 900 seconds
09:57:30:083 don't close database yet, keep open for 900 seconds
09:57:37:096 Current channel 15
09:57:37:104 Device TTL 4797 s flags: 0x7
09:57:40:062 don't close database yet, keep open for 900 seconds
09:57:49:156 don't close database yet, keep open for 900 seconds
09:57:54:082 don't close database yet, keep open for 900 seconds
09:58:04:059 don't close database yet, keep open for 900 seconds
09:58:13:163 don't close database yet, keep open for 900 seconds
09:58:18:085 don't close database yet, keep open for 900 seconds
09:58:28:060 don't close database yet, keep open for 900 seconds
09:58:37:099 Current channel 15
09:58:37:111 Device TTL 4737 s flags: 0x7
09:58:37:157 don't close database yet, keep open for 900 seconds
09:58:37:348 Announced to internet https://phoscon.de/discover
09:58:42:087 don't close database yet, keep open for 900 seconds
09:58:43:089 GW firmware version: 0x264a0700
09:58:43:089 GW firmware version shall be updated to: 0x26580700
09:58:52:062 don't close database yet, keep open for 900 seconds
09:59:01:157 don't close database yet, keep open for 900 seconds
09:59:06:083 don't close database yet, keep open for 900 seconds
09:59:16:061 don't close database yet, keep open for 900 seconds
09:59:25:162 don't close database yet, keep open for 900 seconds
09:59:30:083 don't close database yet, keep open for 900 seconds
09:59:37:100 Current channel 15
09:59:37:110 Device TTL 4677 s flags: 0x7
09:59:40:060 don't close database yet, keep open for 900 seconds
09:59:49:168 don't close database yet, keep open for 900 seconds
09:59:54:089 don't close database yet, keep open for 900 seconds
09:59:58:080 remove outdated neighbor 0x342E
10:00:04:062 don't close database yet, keep open for 900 seconds
10:00:13:166 don't close database yet, keep open for 900 seconds
10:00:18:083 don't close database yet, keep open for 900 seconds
10:00:28:065 don't close database yet, keep open for 900 seconds
10:00:30:718 no button map for: lumi.sensor_magnet.aq2 ep: 0x01 cl: 0x0006 cmd: 0x0A pl[0]: 000
10:00:30:718 ZCL attribute report 0x00158D00042D195A for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
10:00:37:097 Current channel 15
10:00:37:105 Device TTL 4617 s flags: 0x7
10:00:37:177 don't close database yet, keep open for 900 seconds
10:00:42:084 don't close database yet, keep open for 900 seconds
10:00:52:058 don't close database yet, keep open for 900 seconds
Any solution for this issue? Running Home assistant in virtualbox.
I’m sure this has been covered a thousand times before…but I can’t seem to find how to resolve it…
I have an aqara switch WXKG11LM 2016. that has somehow lost it’s way on my network. It’s been fine for months…the battery is fine but has been replaced, so I deleted it from phoscon but it was still in homeassistant…unable to remove it from homeassistant, I deleted the integration and added it again and that has removed it from homeassistant. It is no where to be seen in phoscon and there are no orphans within TigerVNC but for the love of god it will not allow me to add back into the sensors into phoscon. I press the add switch within the phosocon app and then the tiny little button on the switch, it blinks for about 14seconds as I have always done with all my other sensors and lights…but nothing…Has anybody got any bright ideas…
HomeAssistant Version 0.113.3
DeConz Version 6.1.1
RaspBee firmware 26350500
Thanks
Interesting, my case is the opposite.
I can access the phoscon and deconz from within the add-on but cannot access is from the built in VNC client on my MAC.
I made the horrible descission to move all my lights to deconz. The idea was to have all my lights, which is mixed ikea, hue and other brands on one platform. What a bad experience. Ever since i did that nothing has been working properly. Switches only work half the time. Automations only turning on/off half the lights it should.
Just look at this example. My usual automation that turns off the lights outside at night only turned off some of the lights, yet it seems that Home Assistant thinks the light IS actually off, while deconz rightly thinks its on, which it is.
In Philips Hue and Ikea Hubs you normally define rooms (groups) and put the lights in these rooms. And then you associate the switches with the groups. In Zigbee world this means that when you turn a room on, one group message is sent.
Maybe you have som scenes with individual settings and then more messages are sent. But overall the number of zigbee messages queued up at the same time is reduced. And remember in a mesh network these messages are relayed by routers so that doubles or triples the traffic.
Home assistant groups are just logical groups and you can mix zigbee, zwave, RF etc devices into same group. But Home Assistant does not know which zigbee groups devices belong to so all it can do is send an individual message to each device.
By defining groups in deconz, these are presented as a single entity in Home Assistant. You can put these deconz groups in a Home Assistant group so you can turn on e.g. 10 zigbee lights in a zigbee group and 2 Tasmota switches in a single action. The result is that one message is sent to Deconz which sends a single turn on message on the network.
There are two things that makes this more robust. I already noted the huge reduction in virtually simultaneous traffic on the Zigbee network. The other is that even if there is a temporary poor mesh route to a single device, the probability that the individual device hears the group messages is high. I have occationally seen a light bulb that did not respond to on off but it worked when I turn the entire room on and off.
And in normal life 90 % of what we do is turning rooms or groups on and off
And finally for dimming, use this method… Never step increase or decrease a large number of zigbee devices.
Yes, I can confirm, controlling devices via deconz groups helps a lot. Especially the scenes are much more reliable than via HA.
But anyway. I’m every day facing the problem, that one or another bulb or switch is unavailable. Sometimes it’s more annoying, i.e. when the stairs bulb doesn’t switch on during the night or the ventilator switch doesn’t react, but we might have to live with it. Last but not least we’re talking about 2.4Ghz. WLAN, mobiles, microwaves and maybe the neighbours wlan and devices disturbing the mesh and we have no chance to handle that. The interesting thing is, that the hue hub was more reliable. But maybe we just haven’t noticed the interruptions.
One weak link I eliminated were smart plugs from Osram
I had 7 of them. On Philips hue they always appeared offline. And on Deconz I noticed that devices routed via them would not always work. I replaced them all 7 with Philips smartplugs and that improved the stability of the mesh.
I still suspect some older Ikea 1000 lumen bulbs are not as good at routing but Ikea finally released an update for them.
The four button Philips remote were often unstable in the beginning. They were even worse on Philips’ own hub than on Deconz. I gave Philips hell about it. After a year they finally released a firmware that made them stable.
So check out for weak links. Not all devices have good firmware.
