deCONZ - Official thread

Configuration Zigbee
2044

My sd card failed recently. I moved to hassOS 5.2 on a ssd drive restoring a snapshot of system. Now my deconz with conbee II won’t connect to anything. In the logs it just keeps repeating:
18:26:40:680 channel 15 does not match channel mask 0x00100000 (TODO)
18:26:40:680 channel is 15 but should be 20, start channel change
18:26:40:680 Skip automatic channel change, TODO warn user
18:26:48:690 don’t close database yet, keep open for 900 seconds

If I try manually setting a channel it reverts back. Any solutions?

2045

This is the log from last evening when lights and sensors started to get unavailable for 10 seconds and repeating that a few times.

21:40:16:298 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:298 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:464 don't close database yet, keep open for 900 seconds
21:40:16:467 delay sending request 243 dt 1 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:467 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:467 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:491 delay sending request 243 dt 1 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:491 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:491 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:555 delay sending request 243 dt 1 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:555 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:555 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:655 delay sending request 243 dt 1 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:655 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:655 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:755 delay sending request 243 dt 1 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:755 delay sending request 247 dt 1 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:755 delay sending request 43 dt 1 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:855 delay sending request 243 dt 2 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:855 delay sending request 247 dt 2 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:855 delay sending request 43 dt 2 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:961 delay sending request 243 dt 2 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:16:961 delay sending request 247 dt 2 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:16:961 delay sending request 43 dt 2 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:029 send move to color temperature 500 to 0x00178801043E793B
21:40:17:029 delay sending request 243 dt 2 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:029 delay sending request 247 dt 2 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:17:029 delay sending request 43 dt 2 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:034 send move to color temperature 500 to 0x00178801044BECEF
21:40:17:035 delay sending request 243 dt 2 ms to 0x0017880104A78379, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:035 delay sending request 247 dt 2 ms to 0x0017880103C7C675, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:17:035 delay sending request 43 dt 2 ms to 0x0017880106320C99, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:035 delay sending request 78 dt 0 ms to 0x00178801043E793B, ep: 0x0B cluster: 0x0008 onAir: 1
21:40:17:035 delay sending request 79 dt 0 ms to 0x00178801043E793B, ep: 0x0B cluster: 0x0300 onAir: 1
21:40:17:051 send move to color temperature 500 to 0x001788010842A14C
21:40:17:051 5 running tasks, wait
21:40:17:054 5 running tasks, wait
21:40:17:077 send move to color temperature 500 to 0x0017880106A20C0D
21:40:17:077 5 running tasks, wait
21:40:17:093 5 running tasks, wait
21:40:17:094 send move to color temperature 500 to 0xD0CF5EFFFE6D2652
21:40:17:094 5 running tasks, wait
21:40:17:095 5 running tasks, wait
21:40:17:095 failed to add task 301971 type: 14, too many tasks
21:40:17:095 failed to add task 301972 type: 11, too many tasks
21:40:17:095 5 running tasks, wait
21:40:17:102 failed to add task 301974 type: 14, too many tasks
21:40:17:102 failed to add task 301975 type: 11, too many tasks
21:40:17:102 send move to color temperature 500 to 0x001788010457159C
21:40:17:102 failed to add task 301976 type: 6, too many tasks
21:40:17:102 5 running tasks, wait
21:40:17:114 failed to add task 301978 type: 14, too many tasks
21:40:17:114 failed to add task 301979 type: 11, too many tasks
21:40:17:114 send move to color temperature 500 to 0x001788010838F156
21:40:17:114 failed to add task 301980 type: 6, too many tasks
21:40:17:114 5 running tasks, wait
21:40:17:125 failed to add task 301982 type: 14, too many tasks
21:40:17:125 failed to add task 301983 type: 11, too many tasks
21:40:17:125 send move to color temperature 500 to 0x00178801064FC54B
21:40:17:125 failed to add task 301984 type: 6, too many tasks
21:40:17:125 5 running tasks, wait
21:40:17:155 5 running tasks, wait
21:40:17:254 5 running tasks, wait
21:40:17:363 5 running tasks, wait
21:40:17:497 5 running tasks, wait
21:40:17:555 5 running tasks, wait
21:40:17:655 5 running tasks, wait
21:40:17:755 5 running tasks, wait
21:40:17:855 5 running tasks, wait
21:40:17:955 5 running tasks, wait
21:40:18:055 5 running tasks, wait
21:40:18:154 5 running tasks, wait
21:40:18:255 5 running tasks, wait
21:40:18:370 5 running tasks, wait
21:40:18:454 5 running tasks, wait
21:40:18:554 5 running tasks, wait
21:40:18:655 5 running tasks, wait
21:40:18:755 5 running tasks, wait
21:40:18:857 5 running tasks, wait
21:40:18:955 5 running tasks, wait
21:40:19:055 5 running tasks, wait
21:40:19:155 5 running tasks, wait
21:40:19:255 5 running tasks, wait
21:40:19:355 5 running tasks, wait
21:40:19:454 5 running tasks, wait
21:40:19:555 5 running tasks, wait
21:40:19:655 5 running tasks, wait
21:40:19:755 5 running tasks, wait
21:40:19:855 5 running tasks, wait
21:40:19:956 5 running tasks, wait
21:40:20:055 5 running tasks, wait
21:40:20:155 5 running tasks, wait
21:40:20:255 5 running tasks, wait
21:40:20:355 5 running tasks, wait
21:40:20:455 5 running tasks, wait
21:40:20:554 5 running tasks, wait
21:40:20:655 5 running tasks, wait
21:40:20:755 5 running tasks, wait
21:40:20:855 5 running tasks, wait
21:40:20:955 5 running tasks, wait
2046

Is anyone else having problems with states in deconz not reflecting reality? I added all my lights (around 45 bulbs) yesterday afternoon and I’ve already had this problem twice, that suddenly 80% of my lights gets in the “on” state while they are actually off… Why is that ?

2047

How do you disable VNC? I already removed all the ports but it’s still available via ingress. The logs show that it always stops the add on after randomly opening the vnc server when I don’t even use it.

2048

I was not able to find it

2049

Have you seen this new Blog entry
https://community.home-assistant.io/t/the-supervisor-joins-the-party/

Just Look for “Improve add-on availability with the new watchdog feature”

2050

Yes, but that’s a workaround, not a fix …:wink:
Should be fixed

1 Like
2051

Hello everyone!

I was wondering, how do you people with deCONZ and ConBee 2 handle situations caused by power outages? There was a big storm yesterday which caused some power loss problems (only 7 minutes without power, but during that time, power came back for 0,5 seconds or so and then off again quite a few times). After the power came back, ALL my Ikea Tradfri lights and one Ikea remote as well were unresponsive. Lights were all on but I couldn’t control them anymore via Home Assistant or PhosCon interface (I later noticed that I didn’t have updated my HASS plugin for a while, nowadays it’s possible to use either PhosCon or DeConz).

All light entities and that one zigbee remote were grey, and the only way I could get my lights back working was to delete all entities and then do the discovery and pairing again.

So, if power outage resets all zigbee lights, is there some reliable way to easily restore them without adding them again one by one?

2052

There must be something wrong. Never happened with my own system when there is a powerloss or I unplug my RBPi for any reason.

2053

It doesn’t happen if I switch power off from my Raspberry, or, if someone accidentally switches lamp off from wall switch (normally they are always on so that automation can work). And so, normal power outage where power goes off and then returns after X minutes/hours, it doesn’t break the system. But this power loss, although only lasted for 7 minutes, was such as power flickered on and off every now and then during that time, so maybe that resetted something. At least it resetted all my Sonoffs as well, but that’s different system and I found a way to prevent that in the future, but I wonder if I can prevent it somehow on PhosCon / DeConz side as well? :slight_smile:

2054

For the RaspB, it is good to use a UPS. There are small solutions available, which keeps the raspi up for at least 30 minutes. Enough time to shut it regularly down.
This one for example: https://www.amazon.de/dp/B082TGLD2Q/?coliid=I2KBGK7ZQA923&colid=3098H133FSQ3A&psc=1&ref_=lv_ov_lig_dp_it

The bulbs have no problem with power lost.

2055

Sure, and I have UPS with my raspberry. It kept the power whole time. The problem was with light bulbs. Not sure if it’s Ikea Trådfri spesific but then again, I don’t have any other manufacturers light bulbs so cannot compare…

2056

Note after a power-loss nothing gets reset or is lost, albeit many people falsely believe that and start to reset their devices.

In case that after a power-loss or a new firmware update the network appears to be not responsive:

  1. Check that deCONZ is actually connected to RaspBee / ConBee, that is if the firmware version is shown in Phoscon App > Settings > Gateway. If not restarting the integration / container should bring it back.
  2. If connected but devices aren’t responsive yet… wait. Give if a few minutes. Likely the firmware Zigbee Frame Counter needs to catch up to get the value it had before the power-loss.

#2 Wasn’t a problem with older ZLL devices (which ignore the frame counter as per spec) but has become now with newer devices which ignore commands from the coordinator with an lower frame counter to prevent replay attacks. Recent firmware versions improved the frame counter handling but it isn’t optimal yet and can cause a delay after hard power-loss, which will be solved finally in upcoming versions.

Very important: In 99.999% of all cases there is no reason to reset all devices. The Zigbee configuration is stored in NVRAM of ConBee/RaspBee as well as each device.

1 Like
2057

Only thing i can think of is that your lights (tradfri devices) have all been reset to default

As the way to reset the Tradfri devices is by disconnecting and connecting the power 6 times.
And like you said the power switched on and of a couple of times very fast.

An easy way to keep your Pi powered is with and USB Power bank between the pi and charger but i don’t think your problem lies in there.

2058

Ah ok, I do not have Tadfri. My hue, Tint and Innr bulbs have no problem with power lost.
Happend two times last month due to uncarful electricians :slight_smile:

2059

Nothing was lost in sense that I still saw all my devices in Phoscon software, but they all were just grey (couldn’t do anything to those). And I waited for several hours and things didn’t change. Restarting Home Assistant did not help either, I even unplugged ConBee from USB port and then plugged it back, but it didn’t help.

Well, I think I hit that 0.001% chance then :slight_smile: as I couldn’t connect them.

Yes, I think that as well. Except I don’t think power switched off and on six times in a row, but few times yes. But I think I will have to buy another zigbee bulb, maybe from Philips etc, just to see if this happens again, if my Philips behaves differently than Trådfri.

2060

I have two big ups cases in my home. Providing enough power to my whole network, zigbee 2x and my z-wave. In case of power loss the system turns off most of the lights and non critical hardware. The rest can stay on for a couple of hours.

2061

Does anyone have the Xiaomi lumi.relay.c2acn01 energy meter working. It used to work when I just got it before the summer. I guess after an update it stopped working but I’m not so sure.

2062

I have found that to get my zigbee network functional after a power loss I must restart the host, let everything boot, and then restart the server.

2063

I have seen this in a few rare cases
I run deCONZ on bare metal on same machine as I run Home Assistant Supervised.
If HA comes up and tried to connect to deCONZ before deCONZ is fully up running, then I have to restart Home Assistant to make it pick up deCONZ. I wonder if there is a command way to retrigger that, which could be made in an automation.
Another solution that I considered was to change the systemctl file for docker so it does not start until the deCONZ service has stared
I actually had to manually change the deCONZ systemctl file to wait for the network because in rare cases I saw a race condition between the two.

I do not think this is a deCONZ rest issue. It is the deCONZ integration that seems to lack a feature to wait and try again when failing to start. Or maybe it does but we are just too impatient to wait???