Hello! I recommend you to ask those low level questions on the deconz forum https://forum.phoscon.de
This may help you
Source Routing · dresden-elektronik/deconz-rest-plugin Wiki (github.com)
Adding source route to your router TZ3000_u5u4cakc may give better result as native zigbee network seems not doing what you want.
Hi,
This problem is still valid, now on version 6.20.0:
I have a problem with the deconz 6.19.0 update: All my IKEA Praktlysning shades stops responding and have disappeared from Phoscon. I’m not sure if other components are affected, but IKEA Tredansen still working.
After reverting to version 6.18.0 everything is working, but it takes a few minutes before the Praktlysning shades are back in business.
I still have [pydeconz.models.light.light] Unexpected light effect type 0 in my log.
Hi there, I am running the following setup on a Raspberry Pi 4 + Phoscon RaspBee II:
Home Assistant 2023.9.1
Supervisor 2023.09.0
Operating System 10.5
Frontend 20230908.0 - latest
deCONZ Add-on version 6.20.0 (Phoscon firmware version 2.22.02)
I have 2 SONOFF ZBMINIL2 smart switches that I want to connect to HA. After a few tests with the first one (let’s call it switch1) without success I got it finally connected after moving it bit closer to the RPi (moved less than 2 meters from original location which is 6-7 meters away from RPi but on a 3rd room). Once connected if I move it back I can see signal is lost from deCONZ application through VNC.
So I though to take advantage of the mesh network installing the second ZBMINIL2 (let’s call it switch2) in the middle room (1st room RPi, 2nd room switch2, 3rd room switch1). switch2 is connected and works correctly but it looks like switch1 doesn’t want to route through switch2 to reach Raspbee II. How can I force that?
I enabled LQI and increased minimum value hoping to push switch1 to change its route. Also toggled “Fast neighbor discovery”. What else should I do?
Alright a few pages later and a few terms learned it seems that SONOFF ZBMINIL2 is an “end device” and not a “router” so it cannot do what I was hoping for. RaspBee II is the coordinator and end devices will just connect to that or to a router node.
This is also confirmed by the “node type” I can see from the node info in deCONZ application. Hope this helps someone else starting the journey of home automation like me.
Hello everyone. How can I install the current beta of deconz in HA?
The addon only runs latest stable. If you want to try the beta you need to run deconz in a different way.
1 Like
But the last stable is the deconz-2.23.01 from 16.09.2023, but you can only install the old stable deconz-2.22.02 from 31.07.2023. When will this be updated?
I don’t use the addon myself but I know Frenck who I think typically manage bumping the addon has been on vacation recently so it might be on his backlog to do. Otherwise you can create an issue here GitHub - home-assistant/addons: ➕ Docker add-ons for Home Assistant and make them aware that a new version is available.
Hi,
This problem is still valid, now on version 6.22.0:
I have a problem with the deconz 6.19.0 update: All my IKEA Praktlysning shades stops responding and have disappeared from Phoscon. I’m not sure if other components are affected, but IKEA Tredansen still working.
After reverting to version 6.18.0 everything is working, but it takes a few minutes before the Praktlysning shades are back in business.
Any takers?
Hi,
I have deCONZ working well with a conbee 2 device but I’m at the stage now where I need to act on device actions (physical light switch press) as soon as possible.
Within HA, virtual events work almost immediately, however physical events (switch press) take ~30 seconds until they are reflected in the HA.
Is this a per device/manufacture setting or some polling interval in deCONZ that is causing this delay? If so, where can it be changed? Devices in question are wiser (schneider) dimmer switches.
There is something very wrong if a button press from a zigbee switch takes 30 seconds to be seen by Home Assistant. It takes a fraction of a second. Otherwise noone could use Deconz/HA to do even simple automations like press a button to turn on light
Aa Kenneth writes it’s expected to be near instant. This was the primary reason I wrote the integration in the first place. I wanted to get a good user experience with using zigbee remotes.
Thanks both. Thats what I figured. I assume when I use a HA entity to toggle a light on/off that it is going through deCONZ to my conbee2 device to action this. That in itself works instantly. Its only if I tap the physical button that it can take up to 30 seconds before the HA entity will reflect the change.
Any tips on how I could better troubleshoot this? Is there anything in the deCONZ app which shows the connected graph of all the devices that I could look for?
So it seems that this is only to do with the lights I have. In HA and the DeCONZ app, sensors (door and motion sensors) update immediately in the both UI’s , however when I physically press the button (switch or dimmer switch) it can take 5-30 seconds to update in both HA and the deCONZ Phoscon app.
The USB device is now close by the devices (lights) and the motion sensors turn them on instantly as directed by them. Could it be the lights are more prone to signal interference/strength than the other devices? (Schneider Electric - CH/DIMMER/1 and CH2AX/SWITCH/1)
I’m not following. Is it a physical switch that cuts off the power to smart lights?
Yes, it a physical button (switch) that powers a light . The switch is connected via deCONZ / Conbee2.
When I press the physical button, it will turn toggle the light on/off, but that change will not reflect within HA for 10-30 seconds (i.e. entity card on a dashboard or entity in home kit)
The wiser sensors/ and other door/window sensors reflect changes in HA immediately, and within the deCONZ app, it is just these switches for some reason have a delay from the physical press.
You could have been more clear with your question. I think we all assumed you had smart light bulbs that you control with a smart switch. The detail matters
So you have a zigbee switch from Wizer which is mains powered which again powers a dumb light bukb?
And yout problem is only with that model of switch? And it is the reporting of the state of the switch that comes late when you press the physical button on the switch. Which exact model of switch is this?
Correct, zignee switch, mains powered that powers LED (dumb) lights. It occurs across 2 of their devices. 1 is a switch, the other dimmer (on/off/brightness adjust on hold) I have about 20 of these switches installed.
Exact devices are
Schneider Electric Wiser 40/300-Series Module Dimmer](Schneider Electric Wiser 40/300-Series Module Dimmer 41EPBDWCLMZ/354PBDMBTZ Zigbee compatibility) → 41EPBDWCLMZ/354PBDMBTZ
Schneider Electric Wiser 40/300-Series Module Switch](Schneider Electric Wiser 40/300-Series Module Switch 41E2PBSWMZ/356PB2MBTZ Zigbee compatibility) → 41E2PBSWMZ_356PB2MBTZ
Both of these devices emit events with a on average, 15s second delay, but can be up to 30 seconds.
Some of their other devices like the motion sensor and temp/humidity sensors are near instant.