Best path is to use the deCONZ community forums
or the deCONZ discord
Thank you both. I will post to the forum as suggested to see if any additional support for these specific devices can be added. Appreciate the comments and suggestions.
May it be the same issue I’m seeing here?
I have these zigbee GLEDOPTO led strip controllers and they do not have power-on behaviour setting, so they are always ON after a powercut. Also, deconz does not read the status of these controllers after the power comes back on. In home assistant the GLEDOPTO switches are grayed out and does not show they are ON.
If i go to deconz desktop and go to Cluster info of that node and “Read” On/Off Attributes, then Home Assistant gets the status and enables the grayed out switches, so everything works again.
So, as a summary, is there a way to trigger deconz read/update status of a node from within Home Assistant??
AFAIK it’s not exposed over the rest api.
I noticed that the latest Beta supposedly comes with a DDF for IKEA STARKVIND AirPurifier.
So I installed V2.24.1 Beta and expected to see the SATARKVIND magically pop up in Home Assistant, but nothing happend.
Do need to do anything specifically to activate or enable DDF’s in general or this one in particular?
Hello all!
"Better late than never"… and another release of Home Assistant so here comes another release log on Phoscon forum for the HA deCONZ integration
Got pinged some time ago “what about Lidl Christmas light effects?” so whipped it up last night so you have loads of time to prepare for Christmas 
Here are the changes coming with Home Assistant 2023.11.0
Cheers!
/Robban
For feature requests of the integration post an issue at pydeconz github
I’m on Github Sponsors if you appreciate my work.
Hello everyone, before I open an issue on Github wanted to check if anybody had this issue:
My Zigbee network is rock stable, there is no problem with stability. Occasionally (once every 1 or 2 weeks) out of nothing all my Hue Dimmer switches stop working.
All other devices work just fine, I can control all lights, all Hue motion sensors still work, all plugs can be controlled. Literally ONLY Hue Dimmer switches stop doing anything.
Interestingly the fix is has nothing to do with deCONZ or the Zigbee network: to bring them back I have to restart HA core, no need to touch anything on the ZIgbee/deCONZ side.
It just seems that the events around these switches are not passed from the deCONZ to HA anymore or HA does not accept them. I did not see any errors in logs so far.
Did anybody experience such situation? Any hints?
Thanks in advance
Hi,
here everything is rock solid.
Have you tried only to restart the Addon?
Yes - restarting the add-on does not help, everything comes back except the dimmer switches.
As far as I know when restarting core the addon keeps running so I assume deCONZ is healthy and it is something in the communication between the two containers.
It’s really weird as the code base (of the integration) hasn’t changed much the last year. Observed to be really stable so it’s unfortunate you experience this.
Yep - I’m using it for a long time and this behavior is really new.
I will try to listen to events next time to see what is going on there and eventually collect logs.
How do you get the key presses?
Do you use device triggers or events?
I use events exclusively. I hate device triggers as they are cryptic random hex numbers and you cannot easily replace a broken device as the hex number follows the physical item. Events are named from the name used in deconz so you just name the new device the same as old and all automations work like they always did.
If you use events, have you checked if you receive anything in HA?
I have 15 or so Hue 4 button switches and I have never seen all of them stop working. It happens that one does not react at first press but then it works after a couple of presses. Rarely you have to force a remote to reconnect to a new peer by pressing all 4 buttons for several seconds till it flashes red green.
Also make sure you do not have a bad router device that they all connect via. And never have bulbs that you turn off on an old mains switch. Battery devices do not often change peer. Rebooting HA should not cause any activity on deconz so it is still a strange thing you have.
I just use normal triggers via automations based on entity ID that is generated by deCONZ device name.
As I mentioned earlier, I have to see if any events are coming, last time it happened I was under time pressure so had not chance to troubleshoot.
I have around 10 of those switches for over 2 years and also never had a single problem with them till now. Also it never missed a single press. Speaking about network - I am quite sure this is not about network routing because all my routers are always powered (never turned off) and to bring it back I do not have to touch ANYTHING on the Zigbee side (network and deCONZ) - I bring it back by core restart which does not do anything with ZB. Also it is not that some of these switches stop working but ALL OF THEM at the same time (there is no chance they would use same router).
I will wait until it occurs again and try too capture events and collect logs - this is really strange…
So at the moment you don’t get any device support in HA?
Can we consolidate information to this thread and we might get some progress 
Well, that issue is locked - with no activity for over a year.
It’s not locked and last comment was from me in august
Hi guys,
so now I had the situation again (deCONZ - Official thread - #3553 by jnc).
Pressing the button on the dimmer switch does not trigger anything in HA core but when listening to deconz_event in developer tools it indeed comes from the Add-On
de_conz log shows no errors and also in core there is just nothing de_conz related. Restarting HA core fixes the issue.
Worth mentioning is that this time (unlike before) it happened after power outage to the HA so my wild guess is that when HA started de_conz was not ready or the other way round. On the other hand if this was a fundamental communication issue between the containers we would not see the events fired and other de_conz devices would also not work.
Any ideas?
You were not clear in your answer to me when I asked if your automations uses device id or classic events. I hate the device id way with a passion. I know the event trigger is reliable and names predictable
Here is a complete automation for handling a 4 button Philips dimmer in my HA
- id: 'Bedroom_Dimmer'
alias: 'Bedroom Dimmer'
initial_state: 'on'
mode: queued
max_exceeded: silent
trigger:
platform: event
event_type: deconz_event
event_data:
id: bedroom_switch
action:
- choose:
# Normal ON dimmed
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 1002 }}"
sequence:
- service: light.turn_on
data:
entity_id:
- light.bedroom
brightness_pct: 50
# Long press full brightness
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 1001 }}"
sequence:
- service: light.turn_on
data:
entity_id:
- light.bedroom
- light.bedroom_desk
- light.background
brightness_pct: 100
# Increase
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 2001 }}"
sequence:
- service: deconz.configure
data:
entity: light.bedroom
field: "/action"
data: {"bri_inc":254, "transitiontime":50}
# Decrease
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 3001 }}"
sequence:
- service: deconz.configure
data:
entity: light.bedroom
field: "/action"
data: {"bri_inc":-254, "transitiontime":50}
# Stop increase/decrease
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event in ( 2003, 3003 ) }}"
sequence:
- service: deconz.configure
data:
entity: light.bedroom
field: "/action"
data: {"bri_inc":0}
# Off
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 4002 }}"
sequence:
- service: light.turn_off
data:
entity_id:
- light.bedroom
# Off long press
- conditions:
- condition: template
value_template: "{{ trigger.event.data.event == 4001 }}"
sequence:
- service: light.turn_off
data:
entity_id:
- light.bedroom
- light.bedroom_desk
- light.background
#default:
Note that the service call like this assumes deconz GROUP. Syntax differs for single lights for increase and decrease and stop