Diyhue and homeassistant

I am a bit (mentally) stuck in the setup.

I have a raspi with homassistant os and conbee2 module installed. I want to expose some of my devices to amazon alexa with diyhue.
so deconz is running locally and is accessible via homeassistant…

I now installed the diyhue addon and configured it as i thought it might be…

config_path: /config/diyhue
mac: DC:A6:32:29:60:29
debug: true
deconz_ip: 192.168.178.49
no_serve_https: true

MAC is the mac-address of the primary interface of the pi, deconz ip is the primary ip of it…

IIf i have a look at the protokoll it looks like this…


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: diyHue
 Philips Hue Bridge Emulator
-----------------------------------------------------------
 Add-on version: 1.5.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 7.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.12.8
 Home Assistant Supervisor: 2021.12.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
/config/diyhue exists.
Your Architecture is = aarch64
No serve HTTPS
2022-01-07 11:22:30,088 - root - INFO - Using Host 192.168.178.49:80
Host MAC given as DCA632296029
2022-01-07 11:22:30,089 - root - INFO - DCA632296029
Docker Setup Initiated
SSL certificate found
Config file found
Docker Setup Complete
2022-01-07 11:22:30,089 - root - INFO - IP range for light discovery: 0-255
Deconz IP given as 192.168.178.49
2022-01-07 11:22:30,090 - root - INFO - 192.168.178.49
2022-01-07 11:22:30,090 - root - INFO - Online Discovery/Remote API Enabled!
2022-01-07 11:22:30,092 - root - INFO - Config loaded
2022-01-07 11:22:30,097 - root - DEBUG - start ssdp broadcast
2022-01-07 11:22:30,098 - root - DEBUG - starting ssdp...
2022-01-07 11:22:30,100 - root - INFO - sync with lights
2022-01-07 11:22:30,107 - root - INFO - Starting httpd...
2022-01-07 11:22:30,122 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443
2022-01-07 11:22:30,326 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6
{"ok"}
2022-01-07 11:22:33,305 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:34,711 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:36,114 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:37,517 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:38,420 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:39,222 - root - DEBUG - Sending M-Search response to 192.168.178.34
2022-01-07 11:22:40,119 - root - INFO - gracefully exit

nothing about deconz etc. but:
2022-01-07 11:23:00,377 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443
2022-01-07 11:23:00,587 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 “POST / HTTP/1.1” 200 6

that’s what i do not want… Communication to something external…

any hints on my config would be much appreciated…

pings to discovery.diyhue.org can be disabled, but Hue Essentials that support diyHue will not be able to automatically discover the diyhue instance. I cannot figure if you use recent beta release of the official master release, how did you setup Deconz?

i am using the official Master.
Regarding deconz, i am using the “standard” Homeassistant add-on with
device: /dev/ttyAMA0
and:

Container Host Description
40850/tcp deCONZ API backend (Not required for Ingress)
5900/tcp deCONZ via VNC (Not required for Ingress. Not secure!)
8081/tcp deCONZ WebSocket (Not required for Ingress)

If Deconz is connected directly to Home Assistant and not to DIYHue, then you will not be able to set up your light to connect to Alexa through DIYHue. You would have to first connect Deconz to DIYHue then to Alexa. You can’t connect them to DIYHue through HA.

@ryan780 That explains the problem, thanks for you answer!