I switched from a RaspBee II (on a Raspberry Pi 2) to a ConBee III stick with deCONZ as a Home Assistant addon, running in a VM of a Synology Diskstation. The new network seems to be ok, and I can control lights with an Osram Lightify 4-buttons switch just like before.
Now to the (Android) Phoscon app:
Before, I had the IP of my Raspberry Pi entered in the Phoscon app.
For the switch to the ConBee III, I cleaned all data from the Phoscon app.
When I now start the Phoscon app, its start page shows the new gateway (ConBee III) with the IP 172.30.33.6, which obviously is an internal/private IP of the docker container of the Home Assistant deCONZ addon (as every HA addon has its own docker container, AFAIK).
Is it not possible to provide such an IP in the Phoscon app?
I assume that my problem/ question is not related to the switch from RaspBee II to ConBee III, but rather to the fact that I now have deCONZ running in a docker container with a private IP and subnet that differs from the rest of my private subnet at home.
How do other users get it working in connection with deCONZ running as a Home Assistant addon?
I looked into the HA addon’s configuration possibilities but still have no clue how and what to configure there in order to be able to open phoscon via its Android app.
Currently, the HA deCONZ addon config in yaml code only contains one row (ID partially redacted):
Sorry, I should have paid more attention.
It’s a typical German saying - along the lines:
As soon as one (myself in this case) does it right, it works.