Hue Essentials Error when connecting

Support
21

can you add the ip and mac of you host?

this is my docker compose:

services:

diyHue:
  container_name: diyHue

  image: diyhue/core:latest

  volumes:

    - /opt/hue-emulator/config:/opt/hue-emulator/config

  restart: always

  network_mode: host

  privileged: true

  environment:

    - DEBUG=true

    - MAC=XX:XX:XX:XX:XX:XX

    - TZ=Europe/Amsterdam

    - IP=192.168.1.25

    - BIND_IP=192.168.1.25
22

Hi,

I have some great news: everything is now working perfectly, including iCUE and Hue Sync!

Here is a summary of the steps that fixed the issue for anyone else facing this:

  1. Environment Variables: I added the IP, BIND_IP, and MAC variables to my docker-compose.yml as you suggested.

  2. Config.yaml Update: I noticed that in my config.yaml, the port section was set to enabled: false. I changed it to enabled: true and explicitly added ports 80 and 443 to the list.

  3. Certificate Regeneration: I deleted the existing cert.pem and bridge.pem files in the config folder.

  4. Restart: After restarting the container, DiyHue successfully regenerated the certificates using the correct MAC/IP and finally started listening on port 443.

Regarding Corsair iCUE: I can confirm that it works perfectly with DiyHue on Windows. Once the port 443 was open and the ā€œEntertainment Areaā€ was created in the official Hue app, iCUE detected the bridge immediately. After clicking the ā€˜Link Buttonā€™ in the DiyHue WebUI, all my Zigbee lights (connected via deCONZ/ConBee III) appeared in iCUE and are syncing beautifully with my Corsair setup.

Thank you very much for your help

23

UrekašŸ„³

Thank you for the feedback and have fun with diyhue.

The port section is for light search, in webui>diyhue>settings>Add extra port for searching

24

Hi everyone,
I encountered a similar problem with Hue Essentials, but it was slightly different. At first, everything worked flawlessly, and the app ran smoothly. Then, I read about setting up the MAC address, so I set it up and deleted the access granted to the app. Now, the Hue Essentials app still ā€œseesā€ the server, but is unable to connect, as described in this thread. Maybe this is due to some port issue? Interestingly, I cannot retrieve the status of the first attempt. I can delete everything on the mobile app and Home Assistant, but the settings are still there.
Any ideas?

Update: The solution is simple. Go to Bridge > Advanced Options and perform a complete sweep. Now I can connect to the bridge again.

25

The issue was probably the certificate, it was first generated and now you entered a mac address and that did not match the cert, now you removed the cert and config and generated a new cert

26

Iā€™ve tried setting this up on a fresh Raspberry Pi 4B, as well as again on a Raspberry Pi 3b+, both times, I can get the app installed fine, but when I connect with hue essentials, I have to always go into the bridges tab and click ā€œconnectā€. Then, when I add my Homeassistant lights, if I pair another phone to the app, it will just crash hue essentials. Iā€™m using the exact docker compose from mark above (with Mac and IP changed of course), but worse, Iā€™m not getting anything in my debug logs that shows any errors.