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
Sorry for not being clear -
I am using device id. I understand your point with them being random hex number but unless the device changes (which pretty much does not happen in years) they stay so I don’t care.
device_id: fd2cda60688bbce3d1e7c009b616bb2a
domain: deconz
platform: device
type: remote_button_short_press
subtype: turn_on
id: "on"
I had the same issue. After a reboot of the machine where HA is on, the Philips switch using device_id (generated by the visual editor) did not work. Only after restarting HA core the switch was working as expected. Now I changed to deconz_event (and pyscript) and that is working much better. My event handler:
@event_trigger("deconz_event", "id==soverom")
def sw_sytse_handler(event=None, **kwargs):
# log.warning(f"sw soverom: {event}")
if event == 1000:
light.turn_on(entity_id=Lampen.sytse, transition=switch_on_time)
if event == 2000: # up
light.turn_on(entity_id=Lampen.sytse, brightness_step=10)
if event == 3000: # down
light.turn_on(entity_id=Lampen.sytse, brightness_step=-10)
if event == 4000:
light.turn_off(entity_id=Lampen.sytse, transition=switch_off_time)
I use the x000 event, as I assume that is the press button, and x002 is the release?
Hello all!
Another release of Home Assistant so here comes another release log on Phoscon forum for the HA deCONZ integration
Just a small PR that fixes a change in deCONZ API, Air quality sensor PM reporting was broken out to its own type.
Here are the changes coming with
Home Assistant 2023.12.1
Home Assistant 2023.12.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.
It is very nice to have these updates, but why does not my deCONZ update? I still have 2.22.02 with my Conbee II and my Home Assistant is 2023.12.0. I ordered Conbee III, because the migration should be easy. Unfortunately, the easy migration process requires 2.24, which I do not have. How can I update my deCONZ?
3 Likes
Dear Community!
After the need to set up the deconz integration new, I wondered why it only found 5 devices on the first attempt (there are much more).
Then I clicked again to add a hub, kept the phoscon device’s IP (a Raspberry Pi 2 with ConBee 2 HAT) and was happy to see that more devices were found. However, these now appear under a separate hub (despite it is the same device/IP). Well, I added the same hub again - and guess what? Yet some further devices were found; however, of course again under a separate (but actually the same) hub.
Maybe I did something wrong, but shouldn’t the integration find all devices all together in one attempt?
You cannot see this, but the 5 devices (5 Geräte) are all the same. Why the last shows 1 entity (1 Entität) but the previous last three do not, I have no clue. Some of the 5 devices are among the 15 devices (15 Geräte) shown in the second row, none of them are among the 42 devices (42 Geräte) in the first row.
Is there a way to merge these? If yes, how?
Or is merging in the end not necessary at all? Well, I would like to have it “clean” but if it is just “cosmetics”, maybe I should not bother.
Anyway, thanks a lot for sharing your thoughts on this. 
.
when does deconz update to the new version, where we can use conbee3?
1 Like
Not sure what you mean with setting up deconz new. If you just removed the integration from HA then all the devices you see in Phoscon also show up in HA
So I assume you started all over with factory reset Conbee or Rasbee
You should only add the hub once in HA. What happens is that you keep on creating a new hub connection with a new key. Delete them all and only add it once inside Home Assistant. Make sure to restart home assistant after you removed the last hub before you add it again.
To pair devices you need to Add New Lights or Add New Plug etc from the Phoscon app. Devices need to be in pairing mode. You need to find out how as the procedure is very different. If you did not unpair the device before then they need to be factory reset to pair again. Usually by long presssing the button. Philips Hue bulbs are reset by using a Philips 4 button remote and holding it really close to the light bulb and press on and off simultaneously for a long time until the bulb flashes.
If for some reason not all devices in Phoscon are loaded into HA try to restart HA. That often solves things.
2 Likes
see this post :
It is very nice to have these updates, but why does not my deCONZ update? I still have 2.22.02 with my Conbee II and my Home Assistant is 2023.12.0. I ordered Conbee III, because the migration should be easy. Unfortunately, the easy migration process requires 2.24, which I do not have. How can I update my deCONZ?
1 Like