A Hassio VM instance running on proxmox, on a separate machine.
A local development environment of home assistant
On Hassio I have deConz addon setup and running - using Conbee 2
I want to use the deConz addon to connect to my zigbee devices on my local environment. In order to run supervisor locally, I installed Remote API proxy addon on my Hassio instance and followed the steps as described here.
I have access to supervisor on my local environment now with all the addons installed, but deConz is not working as it’s working on Hassio instance. I cannot connect to the gateway and have access to my zigbee devices entities on my local.
The gateway is found on the local environment, but with the local IP: ( the gateway is attached to the Hassio machine )
Once I click it, it ask me to enter the username, password and repeat password, to get “Login failed” message.
What is a “local development environment”?
How did you try to access deconz IP-of-Proxmox-VM:8080? I’m not sure if you can share the deconz stick from Home Assistant VM.
It’s a home assistant instance running straight from the code repository, as described here. I went through the manual setup, installed the packages needed on my linux ( actually WSL ) and cloned the repository.
I can access supervisor on my local environment by installing “Remote API proxy” addon on my VM (on another machine running on the same local network ) running Hassio ( which includes supervisor ), as explained here.
So with this way, I am accessing supervisor running on Hassio on VM, remotely from my local development environment, allowing my to use the addons installed even locally and not only on the VM.
I would like to connect to my zigbee devices on my local. The way I do this on my VM is by using deCONZ and a usb dongle attached to the machine ( the gateway ).
Unfortunately deCONZ app takes the current machine IP to sign in to the gateway. So even though I’m accessing supervisor remotely from my local development, deCONZ is submitting my local environment IP to the gateway ( or something that is not making it work! ) so I cannot login to the gateway from my local environment.
I’m not sure I fully understand. I don’t think you’ll get the add-on running on the local dev environment, because the physical device is not attached to it. Do you just want to control zigbee devices from your local dev instance? If so you should be able to use the deconz integration on your local instance and configure it with the IP of the proxmox VM.
I don’t think I can configure IP for deConz, or if so I don’t no how, but yeah ultimately what I would like to have is to be able to control zigbee devices from my local dev instance.
On your local dev instance, login to the web interface, go to Configuration -> Integrations -> Choose deconz. Choose “Manually defined gateway” and press “Submit”. Enter thr IP of the Proxmox VM and the pirt you configured in the deconz addon on the Proxmox VM and then press “Submit” again.
