You’re extremely right!
I was shocked at the effect USB 3.0 storage devices had on other connected items like BT adapters, 2.4GHz wireless input device adapters, etc.
I don’t understand why this is not a more well-known issue…maybe because less and less people have desktop PCs nowadays, but it’s definitely a problem to take into consideration.
I’m not sure is this on deconz or HA side, but let’s put it on the table
After restarts (not every time) Ikea zigbee buttons seem to be unresponsive. Log is fille with these, 2 for each button:
Got error 'No deconz_event tied to device "My_button_name" found' when setting up triggers for My_automation
23:26:38 – (ERROR) Automation
When clicking the log entry, it reveals:
Logger: homeassistant.components.automation.my_automation
Source: components/automation/__init__.py:563
Integration: Automation (documentation, issues)
First occurred: 23:26:38 (1 occurrences)
Last logged: 23:26:38
Got error 'No deconz_event tied to device "My_button_name" found' when setting up triggers for My_automation
In general, this seems to happen to some others as well: Deconz event error with buttons and it has been going on for some time.
No real solution offered and looks like it happens only with zigbee buttons (Ikea and Aqara reported) and typically after restarts.
In my case I’m running Raspberry Pi 4 4GB with SSD and conbee II dongle + deconz addon.
This is a common issue. When investigating Deconz button press triggers malfunction · Issue #71033 · home-assistant/core · GitHub, I talked to other core devs and this is a generic issue in Home Assistant related to start up time of integrations and automations, there is no solution planned ATM.
OK, I did not notice that issue discussion.
Seems to be that bot closed the issue when nobody managed to comment in time, but the problem itself has, as you also say, gone nowhere.
Are there any (automatic) workarounds for this, because it really is not a possibility to leave a house in the condition that buttons do not work and there might not be anyone available, that can fix it?
It is a horrible that so many Home Assistant bugs are closed by an aggresive bot. I can understand the concept but people need time to react to the emails.
It is setup way too aggresive. You miss one day and the bug is closed. And the devs never open then again. You have to open a new duplicate bugs. I have mostly stopped reporting bugs because I am insulted by seeing plain logic easy to reproduce bugs ignorred up to a year having to reset the bot maybe 10 times.
That was the rant. Now to end user advice.
I have never seen this issue but I also 100 % use native events. When the device triggers were introduced with their cryptic long random hex numbers I dismissed that feature as impossible to use when you make automations in yaml. And devices get replaced because the hardware breaks or you get something better. With the events the name follows the name you give the device in Phoscon. So when you replace a device you just give it the same name and all automations work as they used to. If you use the device trigger the ID change and you have to repair all the automations that use it. I really do not like that concept. So I recommend using plain events. And they seems to work perfectly.
Just an update, when checked the issue discussions, seems to be that reloading automations helps.
I restart my HAs and routers (4 routers in a mesh) automatically every morning to avoid stability issues typical for consumer grade stuff.
I just added an automation which calls service automation.reload soon after the restart.
Correct me if I’m wrong but if a device is in gold status and listed under supported devices, I should be able to add said device in the phoscon app, right?
I have a sensor that will not add for the life of me. Does the HA Addon need to be bumped to a newer version or is it supposed to get the device’s information from the REST API?
https://dresden-elektronik.github.io/deconz-rest-doc/devices/tuya/_TZ3000_n2egfsli_door_sensor/
Looking at github it seems to be added in the last few days so the addon usually updates once deconz stable is released so you will have to wait for that. Which should be shortly
That’s pretty much what I had assumed by bumping the version. That makes sense, thanks!
- A cry for help with zigbee mini switch
Could someone more competent than me please help me out with a question in this thread here?
If you are in deconz, try to press the read button and see if reading occur.
In deCONZ, I have pressed the “read” button everywhere, and it looks like it updates. But sadly it does not seem to report power consumption.
Thanks anyway 
Use the device, put some load on it and read again.
Use debug in deconz and RTFM 
My aqaras like deconz, no issue at all but it’s good to test z2m as alternative ( with deconz dongle, it works too).
My experience is different, everything was fine till I need to move the dongle to the upper floor and starting to have issues. … now I don’t have anymore issues because the network learn the weakness points. Also I use 3 repeaters and some electrified endpoints acting also as repeater.
Hi, my hue dimmer switches doresn’t work anymore as usual.
I have this weird picture in phoscon:
I only can add specific lights here:
What’s wrong?
PS: unfortunately I cannot catch the events (1000, 1001 etc.) as well.
Bad luck
PS: ok found it. It’s a bug and should be solved in 6.16.1
Hi there,
Any update how to solve this issue? I do have same troubles with my system. Access through HA App works but not directly on the PC, thanks
Recently I’ve noticed very strange behavior of my Zigbee network:
I made some investigations over past days with no real success… whatever I did it was fixing problem for short period of time (few hours max). But then I checked stus of OTA in deconz… and voila! there was package of firmware updates from 22 and 24 of September from IKEA that was loaded to devices by deconz. As I have 40+ blulbs +10 switches and sensors from IKEA, that was putting huge workload on my Zigbee network making it unstable/unresponsive. Most of actions I took to stabilize situation was disrupting update process, but after a while it started again. So mistery was sort of resolved.
But then I noticed something that is worrying me. Updates seems to run in endless loop on some devices. For example I see now one E27 1000 lm Opal bulb and 1 GU 10 W 400 lm bulb having firmware uploaded over and over again… Since the morning probably something like 10 times already. For some devices it finally ended with success (no more retries), but for others I’ve seen similar situation. What is causing this? Now I have only these 2 bulbs yet to be updated and network seems to be relatively responsive. When mentioned instabilities occured something between 7 and 10 devices were updated simultanously. Any idea how to make this process more reliable/disruptive?
I have the same issue 
Same issue, any info?
Same issue awaiting resolution,
