i’ve been able to sort it and the conbee2 is now detected by phoscon and devcom.
still can not get the zigbee home app inside HA to see the conbee.
anyway, installing the drivers like stated above and also this script gets the conbee detected as dev/ttyACM0 each boot or reboot.
Again… how did you install HA docker…do you have cli or the docker-compose?
If it cannot see the stick then possibly (!) it is because it is external to the container and you have not provided the means to reach it. Mine ran on net=host with high privileges but that was dsm6`
Here I am assuming that phoscon/deconz is on another container, not?
=== sidebar, I suppose ===
NAS boxes used to be with ARM chips with Linux-like OS, so docker install for HA has been the go-to approach. But then, DS220+ has an intel CPU and can run VM. So…
Have you ever considered doing HAOS as a VM guest under VMM of the NAS box? I have seen examples in the forum before, and recalled the CPU taxing is minimal…
I understand running HAOS under VMM is one thing… but…
Would it be easier to do some USB passthrough from metal box to the HAOS VM? I suppose VMM supports USB passthrough?
(Does the USB passthrough feature survive VM reboot or snapshot or DSM reboot?)
the HA docker is installed using the “docker” application inside dsm7.
the deconz inside the HA software can connect with the deconz/phoscon software (also installed via docker container) and the conbee2 appears to be detected this way.
stopped the docker HA container, checked the settings, restarted with root access, and the conbee2 is now detected! i either did not know root was required or simply missed it when i first installed the container.