Hi, after upgrade to v2.29.5 I figure out that mobile app Hue Essentials is unable to authenticate anymore. After rollback to 2.28.1 the app work again. I can make deeper tests next week. Is anyone else able to use the app with latest deconz app ?
Hello,
I can confirm that Hue Essential authenticate with the current release of deCONS and as that is app specific, I would dare to suggest that needs to be address by the Hue Essential developers and a quick search has revealed that is has been raised in their forum but does not appear to be getting support.
Interesting I don’t recall we changed authentification handling. I’ll make a test before the upcoming release to see what’s going on.
@manup
I think it was around late Mar/early Apr 2024 which would align to 2.26.03 release or thereabouts.
@lakehawk
I don’t know if you remember during testing that we encountered the json problem?
I did a small test now and connected latest version of Hue Essential with my local instance. Here it worked without issues 
The deCONZ instance was shown, I selected it and in the Browser via Phoscon App → Menu → Gateway → Advanced Settings, clicked on connect 3rd party apps. Then Hue Essentials was connected.
Looking closer at the error message above I don’t think this has anything to do with authentication but that Hue Essentials likely expects the on property to only contain true or false but not null.
Not sure why there is a null in first place (same for bri), will check with the devs.
1 Like
@manup you were correct, this error is indication that there is a lights json and not an authentication error and this case or the error I suspect that light 4 is corrupt.
As per the attached screenshot, the error I received was light 63 and deleting the light should allow Hue Essential to authenticate and process the json. However, they may need to look at the error handling in their app.
"63": {
"capabilities": {
"alerts": [
"none",
"select",
"lselect",
"blink",
"breathe",
"okay",
"channelchange",
"finish",
"stop"
],
"bri": {
"min_dim_level": 0
},
"color": {
"ct": {
"computes_xy": true,
"max": 65279,
"min": 0
},
"effects": [
"none"
],
"gamut_type": null,
"modes": [
"effect"
],
"xy": {
"blue": [
0,
0
],
"green": [
0,
0
],
"red": [
0,
0
]
}
},
"otau": {
"file_version": null,
"image_type": null,
"manufacturer_code": null
},
"sleeper": false
},
"colorcapabilities": 0,
"config": {
"bri": {
"startup": "previous"
},
"color": {
"ct": {
"startup": 336
},
"xy": {
"startup": [
0,
0
]
}
},
"groups": [
"0",
"13"
],
"on": {
"startup": "previous"
}
},
"ctmax": 65279,
"ctmin": 0,
"ddf_hash": null,
"ddf_policy": "latest_prefer_stable",
"etag": "33f80538bceeab8465edb44b086e19ef",
"hascolor": true,
"lastannounced": null,
"lastseen": "2025-04-27T11:47Z",
"manufacturername": "Philips",
"modelid": "LCT024",
"name": "Extended color light 63",
"nwkaddress": 54254,
"productid": null,
"state": {
"alert": "none",
"bri": null,
"colormode": "hs",
"ct": null,
"effect": "none",
"hue": null,
"on": null,
"reachable": false,
"sat": null,
"xy": [
0,
0
]
},
"swconfigid": null,
"swversion": null,
"type": "Extended color light",
"uniqueid": "00:17:88:01:04:f9:5d:89-0b"
}
That might make sense with my setup, I have two light that are offline, and probably expose value that hue essential don’t support. I will validate this next week.
Thanks for reporting this. With the latest deCONZ version v2.30.0-beta it should work again, thanks to this PR: Fix missing default/init values for DDF items by manup · Pull Request #8198 · dresden-elektronik/deconz-rest-plugin · GitHub
It will also be fixed in the next Hue Essentials update, but that will take some more time. Apologies for the inconvenience.
1 Like