Phillips Hue: No usable lights found

[AndreasPetersen]

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

Bug report

Hyperion reports "No usable lights found!" when connected to Phillips Hue with 6 lights.

Steps to reproduce

1. Do not have an entertainment group in Phillips Hue
2. Use the Philips Hue Wizard
3. See that there are no lights

What is expected?

Lights should be found. Specifically I want to control this lamp:

What is actually happening?

2024-05-19T21:07:19.025Z [LEDDEVICE|First LED Hardware instance] (ERROR) No usable lights found!

Despite the fact that Hyperiod reports that 6 lights were found.

I've included some of the log here:

2024-05-19T21:14:13.314Z [HYPERION-INSTMGR] (INFO) Hyperion instance 'First LED Hardware instance' has been started
2024-05-19T21:14:13.314Z [JSONSERVER] (DEBUG) (JsonServer.cpp:32:JsonServer::JsonServer()) Created instance
2024-05-19T21:14:12.855Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:422:PriorityMuxer::updatePriorities()) Set visible priority to 1
2024-05-19T21:14:12.855Z [IMAGETOLED|First LED Hardware instance] (DEBUG) (ImageToLedsMap.cpp:113:hyperion::ImageToLedsMap::ImageToLedsMap()) Total index number is: 36 (memory: 36). Reduced pixel set factor: 0, Accuracy level: 0, Image size: 64 x 64, LED areas: 1
2024-05-19T21:14:12.855Z [IMAGETOLED|First LED Hardware instance] (DEBUG) (ImageToLedsMap.cpp:113:hyperion::ImageToLedsMap::ImageToLedsMap()) Previous line repeats 1 times
2024-05-19T21:14:12.855Z [HYPERION|First LED Hardware instance] (DEBUG) (Hyperion.cpp:654:Hyperion::handleSourceAvailability()) new source available -> Resume output processing and switch LED-Device on
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:273:ProviderRestApi::executeOperation()) GET took 16ms, HTTP 200: [http://192.168.0.105/api/config] []
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:743:LedDevicePhilipsHueBridge::isApiEntertainmentReady()) API version [1.64.0] is Entertainment API ready
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:754:LedDevicePhilipsHueBridge::isAPIv2Ready()) Firmware version [1964061010] is API v2 ready
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Bridge Name                   : Hue Bridge
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Bridge-ID                     : xxx
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Model                         : BSB002
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Firmware version              : 1964061010
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) API-Version                   : 1.64.0
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) API v2 ready                  : Yes
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Entertainment ready           : Yes
2024-05-19T21:14:12.860Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) DIYHue                        : No
2024-05-19T21:14:12.958Z [FLATBUFSERVER] (INFO) Started on port 19400
2024-05-19T21:14:12.958Z [PROTOSERVER] (INFO) Started on port 19445
2024-05-19T21:14:12.988Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:479:ProviderRestApi::matchesPinnedCertificate()) First used certificate loaded successfully
2024-05-19T21:14:12.988Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:534:ProviderRestApi::onSslErrors()) 'Trust on first use' - Certificate received matches pinned certificate
2024-05-19T21:14:12.993Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:273:ProviderRestApi::executeOperation()) GET took 109ms, HTTP 200: [https://192.168.0.105/auth/v1] []
2024-05-19T21:14:13.021Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:273:ProviderRestApi::executeOperation()) GET took 28ms, HTTP 200: [https://192.168.0.105/clip/v2/resource/light] []
2024-05-19T21:14:13.021Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:617:LedDevicePhilipsHueBridge::log()) Lights at Bridge found        : 6
2024-05-19T21:14:13.064Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:273:ProviderRestApi::executeOperation()) GET took 43ms, HTTP 200: [https://192.168.0.105/clip/v2/resource/device] []
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (ProviderRestApi.cpp:273:ProviderRestApi::executeOperation()) GET took 14ms, HTTP 200: [https://192.168.0.105/clip/v2/resource/entertainment] []
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (DEBUG) (LedDevicePhilipsHue.cpp:1864:LedDevicePhilipsHue::setLights()) Lights configured: 1
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (WARNING) Configured light-ID  is not available at this bridge
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (ERROR) No usable lights found!
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device philipshue ON
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (INFO) Device philipshue is ON
2024-05-19T21:14:13.078Z [LEDDEVICE|First LED Hardware instance] (INFO) LedDevice 'philipshue' enabled

I'm unsure if it's safe to include the whole log. Are there any keys or IDs that should not be shared publicaly?

System

Hyperion Server:
- Build:             (HEAD detached at 2.0.16) (Paulchen-Panther-cb85d2d/a93d79b-1705568419)
- Build time:        Jan 18 2024 09:18:44
- Git Remote:        https://github.com/hyperion-project/hyperion.ng
- Version:           2.0.16
- UI Lang:           en (BrowserLang: en)
- UI Access:         default
- Avail Screen Cap.: qt,dx
- Avail Video  Cap.: v4l2
- Avail Audio  Cap.: audio
- Avail Services:    boblight,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection
- Config path:       C:/Users/AndreasPetersen/.hyperion
- Database:          read/write
- Mode:              GUI

Hyperion Server OS:
- Distribution:      Windows 10 Version 2009
- Architecture:      x86_64
- Kernel:            winnt (10.0.22631 (WS: 64))
- Root/Admin:        true
- Qt Version:        5.15.2
- Python Version:    3.12.1
- Browser:           Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36

[Lord-Grey]

@AndreasPetersen Could you test, if the PR #1743 fixes the issue, pleaee?
You can download a Windows test build/artifact here.

[AndreasPetersen]

Hi @Lord-Grey . I just tested it out, and it works perfectly. Clicking "Let it light up" button blinks the light.

Thanks for the quick fix!

[Lord-Grey]

Hi
Great that it is working now and thanks for testing!

Nevertheless, I would recommend that you run your lights via an Entertainment group. That is far more performant. Via entertainment up to 10 devices can be updated in one go while in classic mode the lights are updates in sequence.

Note: I removed the image, as it contained the bringe's access keys.
Just in case you wondered why the image is gone 😀

[AndreasPetersen]

Thanks @Lord-Grey .

Unfortunately I cannot use an entertainment group, since it is apparently a requirement to have a least one color light, which I do not have.

[Lord-Grey]

Ahh, I see :)