Philips Hue Bridge required with Signum IOT module

Hi @MDAR : I got it worked out:
127.0.0.1:6000 as connection string did the trick. It now loaded the modules in HA.
Thanks for your help!

1 Like

Thatā€™s interesting.

I thought HA was in a container that prevented it accessing the loopback port.

Useful to know, thanks.

Iā€™m glad youā€™ve got it working.

1 Like

Actually, I think the Philips Hue Bridge might not be required. Iā€™m using the Sonoff zigbee USB dongle and in theory it is possible to connect all your Philips Hue lamps to that dongle. I havenā€™t tested that though.

Think Iā€™ll get myself a Hue Bridge though. I will now finish up on the velbus integrations and document my configuration.
Afther that Iā€™ll start with the Philips Hue integration.
I think the Velbus integration will have been the hardest. Time will tell! :slight_smile:

1 Like

Would you care to share your documentation? Iā€™m particularly interest in the coupling of the glass panel modules (VMBGP4) with the Philips Hue lamps as I currently do this through Home Assistant automations which is not ideal IMO.

Did you use a signum IOT module or a raspberry pi to connect your Sonoff zigbee USB dongle?

I would love to use the dongle in combination with the signum IOT module and de HA (lite) on it.

I used to have a containerized version of HA spinning on my Raspberry Pi. I then bridged my Sonoff zigbee USB dongle in this container. Now, I run HAOS on a dedicated server inside a VM using Proxmox.

So, small update after 6 months or so:

velbus-tcp has been running solid after itā€™s installation in june. I now can control the lights through my smartphone. Have yet to buy a Hue bridge. Been postponing that because I donā€™t really need it as of yet.

But here is the thing:

This whole project been running on a bare metal Home Assistant ā€œcoreā€ version on my NUC. I would like to install proxmox and install HAOS as a VM in it. Will give me a lot more flexibility for a future project.

Wil velbus-tcp work if I set it up this way? Will I have to use USB-passthrough on Proxmox so the HAOS will ā€œdetectā€ the USB connection?

I donā€™t know much about proxmox, but if you must have velbus-tcp running inside a VM for any reason then you must figure out how to make the USB device available to the VM. Generally USB devices are one of the most straightforward types of devices to make available to a VM, and once thatā€™s done, software canā€™t tell the difference for most intents and purposes and will run without batting an eye. That includes velbus-tcp.

But. You could also run velbus-tcp outside of the VM and access it from H-A via network. These two components do not require to be collocated. OR you could isolate further and run velbus-tcp in its own container (proxmox appears to support LXC containers?) or even another VM if you wanted to. Options.

1 Like

Hi @csoete

So Iā€™m looking into running velbus-tcp module on HAOS. I have HAOS installed as a VM on proxmox. Proxmos is installed on an Intel Nuc.
How did you get it working? Obviously the velbus-tcp.sh script is not working in HAOS. Nor can I find it as an add-on in HAOS itself.
Can you point me into the right direction?