Hi all,
The issue is sorted out- kinda…
-
The most important rule: do not connect the new switch with Deconz version older than 2.9.3 (recognized by having Deconz version 6.7.0 in Home Assistant). If you do not update first, it corrupts something (a database?) pretty badly in Deconz if you start connecting your switch. Simply removing the device from Deconz is not recovering this situation. The way i dealt with this situation, is to do a full gateway reset of my Conbee II, and than reconnecting all my devices again, and restore my automations in Home Assistant again (an 8 hour job). Another user had a more elegant solution to recover from this, you can find more details here, but is not very easy either: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4287#issuecomment-781503704
I hope this warning helps. -
Update Deconz to version 2.9.3/6.7.0 or newer first
-
Use Phoscon to add the device. This can be really difficult, multiple attempts are usually needed. After adding, it will most likely not pop up in Phoson, but you will see it in the Deconz overview.
-
The switch is now visible in Home Assisant. However, it is now time to reboot Home Assistant. If you don’t reboot, the change is very high that only the battery of the remote will be recognized, but not the buttons.
-
Automations can now be created in Home Assistant.
Something is clearly very wrong with the current implementation of the new switch in Deconz/Phoscon, but the above procedure worked for me. I’ve repeated the procedure with a second hue switch, and it’s all working by following the steps above.