Bug Report — Philips Hue Wizard not working in 2.2.0

[Entara07]

• I confirm that this is an issue rather than a question.

Bug report

Environment

Hyperion version: 2.2.0
Docker image: sirfragalot/hyperion.ng:latest (digest: 490b34eca77a, linux/amd64)
Host: Synology DS920+ (Intel Celeron J4125, x86_64)
Browsers tested: Firefox, Edge (no extensions)

Steps to reproduce

Run the container sirfragalot/hyperion.ng:2.2.0
Open Hyperion web UI at http://IP:8090
Go to LED Instances → LED Output
Set Controller type to philipshue
Click Philips Hue Wizard button

What is expected?

The wizard opens and guides through Philips Hue bridge configuration.

What is actually happening?

Nothing happens. The following errors appear in the browser console (F12):
Loading module from "http://IP:8090/js/wizards/LedDevice_philipshue.js"
was blocked because of a disallowed MIME type ("").

Loading failed for the module with source
"http://IP:8090/js/wizards/LedDevice_philipshue.js"

Uncaught (in promise) TypeError: error loading dynamically imported module:
http://IP:8090/js/wizards/LedDevice_philipshue.js

System

Root cause
The file LedDevice_philipshue.js seems to be missing from the image. Confirmed via:
bashdocker exec -it hyperion-ng find / -name "LedDevice_philipshue.js"
Returns no result.

Additional notes :
The same wizard works correctly in sirfragalot/hyperion.ng:2.0.16
Manually configuring the Philips Hue controller without the wizard is possible but the Hardware LED count field is greyed out and cannot be set to the correct value (6), causing the device to fail with error: Number of hardware LEDs configured [1] do not match the Entertainment lights' channel number [6]

[Lord-Grey]

@Entara07 How do you access the docker container?

I installed the latest and nightly container and both work with the wizard (using FireFox)

And the js is also accessible:

I am running the container on a Synology DS720+ and access it via a bridged local network address.

And even going via a Reverse Proxy works.
Maybe for your reference, if should be configured as

I would suggest you have another look at your setup or pin-point to the main difference of your setup.

Manually configuring the Philips Hue controller without the wizard is possible but the Hardware LED count field is greyed out and cannot be set to the correct value (6), causing the device to fail with error: Number of hardware LEDs configured [1] do not match the Entertainment lights' channel number [6]

You are right the LED number is not resolved when the respective IDs are provided.
As an immediate workaround you can export the configuration, update the LED count and import it again.

[Entara07]

@Lord-Grey , thank you very much for you quick investigation and answer!

I realized also that I'm using an image that you may have no control over : sirfragalot/hyperion.ng:2.2.0
It is the most used one on Synology, but it may not be the official one as on this Github.
It's my first time creating a request on Github, so I may be talking nonsense, if so please excuse me.

So far, I've downgraded Hyperion and I'm using the 2.0.16 version again. But I'll try next week-end the latest and your workaround.

I'll let you know.

Thanks again.

[Lord-Grey]

@Entara07 Please note that I tested with the docker image sirfragalot/hyperion.ng:latest and sirfragalot/hyperion.ng:nightly

Maybe you retest with those too

[Lord-Grey]

Closing as no further feedback

[Entara07]

Hello @Lord-Grey ,

I apologize for the very late reply.
I have been putting this aside for while.

Regarding your question "how do I access Hyperion".
Here is the answer :
I access the Hyperion web UI directly via IP address: http://192.168.1.22:8090
The container runs with network_mode: host on a Synology DS920+.
The error in browser console (Firefox and Edge) when clicking the Philips Hue Wizard button:
Loading module from "http://192.168.1.22:8090/js/wizards/LedDevice_philipshue.js"
was blocked because of a disallowed MIME type ("").

Uncaught (in promise) TypeError: error loading dynamically imported module:
http://192.168.1.22:8090/js/wizards/LedDevice_philipshue.js
Confirmed the file is missing inside the container:
bashdocker exec -it hyperion-ng-test find / -name "LedDevice_philipshue.js"

Returns no result

Regarding the test I just made :
Created a dedicated Docker project for testing with the following docker-compose.yml:

yamlversion: '3.3'
services:
hyperion:
image: sirfragalot/hyperion.ng:2.2.0
container_name: hyperion-ng-test
restart: unless-stopped
volumes:
- /volume1/docker/Projects/Hyperion-test/config:/root/.hyperion
network_mode: host

The Philips Hue Wizard still does not open (same MIME type error as reported initially).
I used your workaround instead: manually filled in Hostname, Username, Clientkey and Group (UUID format) in the Specific Settings.
The Hardware LED count field was greyed out and stuck at 1. I fixed it by exporting the config JSON, editing both occurrences of "hardwareLedCount": 1 to "hardwareLedCount": 6, and re-importing. This worked.
After saving, the LED Output switches ON briefly but then turns OFF again. Checking the logs reveals a systematic SSL handshake failure:

mbedtls_ssl_handshake attempt 1/5 FAILED.
Reason: code = -30592: SSL - A fatal alert message was received from our peer
mbedtls_ssl_handshake attempt 2-5/5 FAILED.
Reason: code = -26624: SSL - The operation timed out
mbedtls_ssl_handshake FAILED
Failed switching device philipshue ON
Device disabled. Maximum number of 6 attempts enabling the device reached.

Questions :

• Is there a way to disable SSL certificate verification in 2.2.0, or to specify a custom certificate path? The Hue bridge uses a self-signed certificate.

• Is the Philips Hue Wizard MIME type issue known and planned to be fixed in a future release of the sirfragalot Docker image?

Thank you again for your support.
Have a nice day.

[Lord-Grey]

mbedtls_ssl_handshake attempt 1/5 FAILED.

This error is not related to the hue box's certificate, but that the UDP streaming for entertainment cannot establish a secure streaming connection.
If you would run in bridged mode that could indicate that you missing to export 2100:2100 UDP.
As you are running in host mode, could it be that your hue and/or browser sit in a different network segment and not all traffic is passed forward and backward? VLANs?

Is the Philips Hue Wizard MIME type issue known and planned to be fixed in a future release of the sirfragalot Docker image?

The docker image is not provided by the Hyperion project. Therefore, you would need reaching out to the maintainer.
Nevertheless, I am still under the assumption that it is related to your Synology and/or Network setup.

I am running DSM 7.3.2 and the latest Container Manager app on a DS720.
There Host and Bridge mode just runs fine with the image provided by sirfragalot.

Note: As I was not able to load your docker_compose into Container Manager, I assume that you are running in an "old" Synology Docker environment... Maybe worth updating ;)

Confirmed the file is missing inside the container:
bashdocker exec -it hyperion-ng-test find / -name "LedDevice_philipshue.js"

You will not find the file on disk, as it is shipped within the Hyperion executable.
Nevertheless, if the you do a
http://192.168.1.22:8090/js/wizards/LedDevice_philipshue.js
you should get the js code displayed in the browser. Hyperion must be running of course.

[Entara07]

Hi @Lord-Grey,
Here is an update after additional testing today.
Environment

DSM: 7.3.2-86009 Update 3
Container Manager/Docker : 24.0.2-1606
Docker image: sirfragalot/hyperion.ng:2.2.0
network_mode: host
Single VLAN, cascaded switches

Test results

JS file accessible ✅
http://192.168.1.22:8090/js/wizards/LedDevice_philipshue.js returns the JavaScript code correctly. The file is served by Hyperion.
Hue bridge reachable from Synology ✅

From my Synology through SSH connexion : bashcurl -sk https://192.168.1.10/api/config

Returns bridge info correctly

Philips Hue Wizard still not opening ❌
Tested on both HTTP (port 8090) and HTTPS (port 8092). Same MIME type error in browser console (Firefox and Edge):

LED Output fails with SSL handshake error ❌

Question
Since the JS file is accessible but the wizard still won't open, could this be a Container Manager version issue? Is there a specific version of Container Manager required?
Also, is there any way to bypass or debug the SSL handshake failure for the Entertainment API streaming?

Thank you!