After 1 1/2 days still no Problems with the ARM version on my Raspberry 4 model B - loaded the backup of my setup with all the same devices and the conbee II with same firmware as used in my unraid docker of deconz. Just the architecture changed
@manup @Mimiix @ChrisHae @helipus
Wondering what happens if you do a full reinstall on the other machine 
Other than that, afaik there is no difference in builds.
what do you mean when you say full reinstall? new docker with backup or new docker with pair all devices from start?
Maybe this is the problem and the amd64 version need to be different in some way because of the changes that where made since 2.23.02 i dont have any knowledge about that whole thing with running programs on different architectures but there has to be something otherwise it would work if i just rebuild everything loading my backup. I did that about 3 times i tried to upgrade to conbee III and i dont think that the conbee 3 stick is the problem. The only thing else that could be is that later versions got more requirements to the system and @helipus and my systems are to weak to handle multiple dockers plus deconz versions above 2.23.02.
I did the full fresh new install and had the same problems afterwards. Lost todays trying it and had a very angry wife. Now Iā back on 2.23.02. I ordered a new adapter and plan to start switch to zigbee2mqtt with the SMLIGHT SLZB-06. 
You installed a clean deconz on the RPI and did a recover of the backup, instead of an update between versions.
yes thats right, but what is the difference between that and when i tried to get the conbeeIII working. i installed a new version and then i had to load my backup cause its part of the process upgrading to conbee III it lead to the same issues i got when i just update and just tried to used the new version with my conbee II the issues are similar.
and like Helipus mentioned, the fresh install at his system didnāt change a thing:
So maybe it seems that weāre the only two persons running into that problems - but i think its too easy to put it aside like that. I think the people that are fed up with issues and switched are way more than these who invest much time and try to get a solution.
As i wrote in the other thread i bought a conbee III at release and i can not use it because of that issues itās a 40ā¬ paperweight and also iām stuck with the devices implemented in 2.23.02 or is there a easy way to add new devices?
i posted comparison clips and logs, i switched to a raspberry setup where i got no problems, i did around 10 trys to update with conbee II and also with conbee IIIā¦nothing changed, i spent so much time trying to get droped off devices like motion sensors back to life after reverting from the lagging versions, and it feels like we just have to live with it - even if there are two people atm facing the same problems that also put alot of effort in to get this solved. its not like we made up the problemā¦
1 Like
For the issues regarding the install, I really canāt be of more help. @de_employees need to chip in.
This I can answer, you can simply put DDF in the devices folder and add support.
Sorry for hijacking this thread but for me, it doesnāt seem to be AMD64 (or evrn CPU-)related. Iām on RPi4 and see almost no load on the system but since a few firmware releases, events to external systems (like iobroker) are delayed up to 4sec.
Group actions or internal actions (switches bound to lights) are working flawlessly.
Anything in the logs?
After 1 year of unsuccessfully searching for a solution and no longer being able to update deconz without losing the stability of the system, I have now finally switched.
Since Christmas I now have 115 devices in Zigbee2Mqtt together with the SMLIGHT SLZB-06 Coordinator.
This has been running stably since Christmas.
I have also come to really appreciate the fact that I can easily decide which repeater I want to register my battery-powered endpoints with, as well as the easy operation of the mesh card in the WebGUI.
What I missed at the beginning was the functionality of lighting control with groups and scenes in Phoscon, which was really excellent.
However, after a short period of familiarization, this was also quickly achieved in Home Assistant and also offers me more flexibility.
I am therefore currently in the process of moving my automations from OpenHab to Home Assistant piece by piece.
I have been using deconz since at least 2020 and thank alle developers an maintainers for the entry into the Zigbee world. I can no longer participate in the further debugging of the errors described here, as deconz is now switched off and the conbee stick is retired.
@Mimiix: Should I mark this as the solution as it was my solution and I started this topic?
2 Likes
Happy to hear you made it work out for you !
Feel free to do this.
1 Like