deCONZ - Official thread

You can enable debug in hass for the deConz integration and then view the logs

When I look in the integration page, there is no debug option for Deconz.
In the Supervisor page, there are some in the Deconz setup page, like dbg_apps=1, dbg_info=1, dbg_zcl=0 and dbg_zdp=0. Should I change all the values to 1 ?
I suppose the log are in Deconz plugin logs, not in Hass log ?
I don’t see somthing interesting in Deconz plugin logs

I found that and add it to my configuration file:

logger:
  default: info
  logs:
    pydeconz: debug
    homeassistant.components.deconz: debug

Somehow my DeCONZ application add-on stopped rebooting itself some hours after my post last saturday. Well… this evening it decided to start rebootlooping again… Is there any way to FIX THIS?!

Best recommended action here would be to post an issue on hass addon githun

I have the same issue as mentioned in another thread (I loose my lights in deconz - #2 by flotteemse), but I thought this might be the best thread to post in.

So I am running HA OS on a Pi 4 with a Conbee II stick and using Deconz. Whenever there is an update to HA (or my Pi loses power by accident) I lose the connection to everything under “Lights” in Phoscon (my lightbulbs and smart plugs). Then I have to search for them again, and add the names for each device again, which is quite annoying. The strange thing is that everything else in Phoscon is still connected - all sensors immediately show up and with the correct names and all. So it is only the devices under “Lights”. I have tried waiting for a couple of hours to see if they would reconnect by themselves, but that didn’t work.

I do not have any logs for it at the moment, but I will of course try to get them when I experience the issue the next time.
But has anyone seen any fix posted for this issue anywhere?
Oh, and by the way the firmware is of course updated :slight_smile:

Iirc this is that when both hass and deconz restart lights take longer to load for deconz and hass requests data before loading is complete. I haven’t noticed this for a long time and I think deconz improved the loading as well. When this happens first thing to try is to see if a reload of the deConz integration solves the issue. Then you can report back

Since the newest Hassio-Update (12.21 / .1) most of my zigbee devices are deactivated. Reloading deconz did not work.
Any ideas?

Too little information to make any asumptions. You need to share more details.

Most of Zigbee devices deactivated; does that mean that some work?
You’re running hassio does that mean that you utilise the Deconz add-on?

What does your log look like?

Yes some work, like the Xiaomi Magic Cube, but none of the Xioami Sensors.
Hue lights do work too.

I’m using the deconz integration in hassio. Nothing (errors or warnings) in the logs.

Ok. Do you have your conbee on an extension cord? That’s typically the most common issue with devices behaving badly is when you don’t have an extension cord

No extension cord but before the update it worked like a charm!

What kind of device do you use for HA? Does it have a wifi adapter build in?

Let us summarize
Your hue devices work. A cube works. Xiaomi sensors do not.

Xiaomi sensors have a reputation for having an issue with connecting to any other router than it originally connected to. A proper device will attempt to connect to a different router (like a lightbulb) or directly to the coordinator. It is most likely that all you need is to repair then. You do not need to remove then and add then again. Just ask Phoscon to add new device and go to the sensor and click the pairing button. Not factory reset. Just click the button. They will normally reconnect and become available again. You can also remove the battery and put it in again. That may also force then to reconnect.

I personally have the sensors branded Aqara and they do not seem to have an issue. It probably depends on firmware. Problem is in the sensors and it is also a problem on other systems than Deconz

One problem can be that you carry the sensors to your computer with the Conbee, pair then, and then carry then to a remote location. Because they refuse to reconnect to a light bulb in near then they may insist on being connected to the Conbee with a poor link. So always pair Xiaomi sensors where they are placed so they connect to a nearby router

And get 1 m USB extender cable for your Conbee. There is too much RF noise near any computer.

Does anyone know when this fix will be implemented ?? I have quite a lot of devices that’s not working right now, and it looks like it fixed here:

If you’re running standalone deconz @manup manup added this to the v2.13.3-beta milestone 14 days ago

I’m using the odroid as a system. The Xiaomisensors are Aqaradevices, so these are the same as yours.
I do not think RF noise is a problem at all, because everything worked before updating to 21.12.

In Phoscon all sensors are available.

Best regards,

Stefan

Please start with adding an extension cord.

The manufacturer recommends a USB extension
https://phoscon.de/en/conbee2/install#connection

I will give it a try but why should that happen just after upgrading and working for almost a year before?

Additionally i do have some hue bulb that act as repeater.