Hello. It’s really difficult to debug without a hub, indeed. There was an open-source project that allowed mocking the bridge, but I can no longer get it to work.
I’ll see if I can find a cheap one or borrow one.
The situation has changed a bit since the last messages — I now have a Philips Hue setup at home (with a bridge), so I could debug this error.
However, I’m not at home right now; the earliest I can look is next Thursday 
@cicoub13 if you want I can buy you a bridge, on Leboncoin it’s 30€ — but if you don’t use it afterwards, is it really practical for debugging?
Thank you both for the replies 
@cicoub13 : if needed, I’ll give it to you, no problem, if it can help other people.
1 Like
It’s necessary for debugging, but not convenient indeed. My Philips bulbs are connected via Zigbee today, so I have to unpair them to route them through the bridge each time.
I had helped/developed the Philips Hue integration, so it seems normal for me to maintain it. But I think the fixes aren’t huge to make (the analysis
Ok, I’ll try to take a look next week.
I set myself a reminder so I don’t forget 
Small off-topic question:
Can you confirm that in your case the Philips Hue app is no longer of any use? No more « Sync » function with music, use of their pre-configured colors, etc…?
Is it either the Philips Hue Bridge or Zigbee2MQTT? Is it impossible to use both in parallel?
Indeed, if you pair your Philips Hue lamps with Zigbee2MQTT, you can no longer use the full richness of the Philips ecosystem.
At my place, despite a full Zigbee setup in the rest of the apartment, I kept my living room as native Philips Hue to have access to the nice scenes in particular (fireplace mode under my TV cabinet, etc
2 Likes
Thanks for your reply, that was a bit what I feared.
I have to admit that the Philips Hue ecosystem is really well made (that’s a personal opinion of course). But I would have liked to use them with Zigbee2MQTT to get
1 Like
I had started a branch here Comparing GladysAssistant:master...cicoub13:fix-1690 · GladysAssistant/Gladys · GitHub
And the version of node-hue-api is the latest (version 5 is in beta)
1 Like
As promised I looked at this this morning at home
@cicoub13 there were a couple of things missing in your PR but we were really close to the goal 
Basically:
- A setInterval was missing for the 15-second polling; otherwise the polling is never initialized, so in the tests above the polling was simply never called again ^^
- For colors, handling the « ct » is mandatory — it’s used when the user changes the color using the « Color Temperature » selector in the app, and according to my tests using the x,y value also works perfectly
- For brightness, Philips Hue sends 0-254 and we want 0-100 so a normalization was missing
- A few small bugs in the tests
The fixed PR:
No need to test, I’ve run all the tests on my machine and it works very well!
I’m going to merge this and it will be included in the next Gladys release
2 Likes
Thanks for the correction
And thanks also to « cicoub13 » for everything that was done before.
Great!
2 Likes
Hi,
Sorry to come back again with this … I received the new Gladys version 4.41.0 and I rushed to test it but it doesn’t work for me 
Is there any action to take for already connected lamps? Do I need to remove and re-add them?
The only test performed is: turn on the lamp and change the color → it turns on in Gladys (> 15 seconds) and for the color, nothing happens.
Any idea?
For logs, which command do you use? If it can help to understand.
I installed Dozzle to make things easier and I keep getting these lines:
15/05/2024
09:39:06
2024-05-15T09:39:06+0200 \u003cerror\u003e device.poll.js:23 (DeviceManager.poll) There was an error while polling device philips-hue-light-ecb5faa8e079-14
15/05/2024
09:39:06
2024-05-15T09:39:06+0200 \u003cerror\u003e device.poll.js:24 (DeviceManager.poll) TypeError: Cannot read properties of undefined (reading '0')
15/05/2024
09:39:06
at PhilipsHueLightHandler.poll (/src/server/services/philips-hue/lib/light/light.poll.js:41:43)
15/05/2024
09:39:06
2024-05-15T09:39:06+0200 \u003cerror\u003e device.poll.js:23 (DeviceManager.poll) There was an error while polling device philips-hue-light-ecb5faa8e079-13
15/05/2024
09:39:06
2024-05-15T09:39:06+0200 \u003cerror\u003e device.poll.js:24 (DeviceManager.poll) TypeError: Cannot read properties of undefined (reading '0')
15/05/2024
09:39:06
at PhilipsHueLightHandler.poll (/src/server/services/philips-hue/lib/light/light.poll.js:41:43)
I don’t know if this will help.
For the 15-second polling you do indeed need to remove the bulbs and re-add them.
Ah great, thanks for going to check I see what it is — out of curiosity, on what type of Philips Hue bulbs do you get these errors? They’re white-only ones, I think, right?
Can you create a GitHub issue on our Gladys repo with these logs? I’ll look at it on my next Gladys day
Ok for polling.
Regarding your other question, no, they’re colors. A « Go table Lamp » and a « Hue bulb » (name retrieved from the app).
I just tried with a « Hue color spot » and indeed, it works!
However, between the bulb and the color spot, I don’t see any difference. I removed the bulbs and compared them physically. Apart from the S/N, it’s the same ^^.
Should I open an issue anyway?
That’s odd, I’ll investigate!
I created the GitHub issue:
Thanks for the feedback and the logs @Kevin, it’s fixed in this PR:
I tested it locally and it should fix your issue
I’ll keep you posted when it’s live in Gladys
1 Like
Ok perfect, I’ll test it as soon as it’s available at my place
1 Like
It’s available in Gladys Assistant 4.42:
1 Like