You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
Im trying to run deconz v2.13.01 in an LXC ubuntu 20.04 LTS container in proxmox, deconz starts and i can access it from browser but i cant seem to establish connection to my ConBee II.
I have passed my ConBee through to the cointainer and tried every solution i could find on the web, i've also tried installing docker in LXC and then deconz in that(because thats what was working on my Pi) also with no luck.
Steps to reproduce the behavior
Expected behavior
Screenshots
passthrough (from inside the LXC container)
deconz.service
.conf from proxmox server.
udev.rules from proxmox server.
Environment
Host system: (PC running Proxmox)
Running method: ( ubuntu 20.04 LTS running in LXC ccontainer)
Firmware version: (can't connect so cant see firmware version)
deCONZ version: (2.13.01)
Device: (ConBee II)
Do you use an USB extension cable: (yes)
Is there any other USB or serial devices connected to the host system? no
deCONZ Logs
systemctl status deconz
here is some of the log, let me know if i should be looking for something specific.
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Hi.
Im trying to run deconz v2.13.01 in an LXC ubuntu 20.04 LTS container in proxmox, deconz starts and i can access it from browser but i cant seem to establish connection to my ConBee II.
I have passed my ConBee through to the cointainer and tried every solution i could find on the web, i've also tried installing docker in LXC and then deconz in that(because thats what was working on my Pi) also with no luck.
Steps to reproduce the behavior
Expected behavior
Screenshots
passthrough (from inside the LXC container)
deconz.service
.conf from proxmox server.
udev.rules from proxmox server.
Environment
deCONZ Logs
systemctl status deconz
here is some of the log, let me know if i should be looking for something specific.
Additional context
The text was updated successfully, but these errors were encountered: