Cannot connect to Bridge: Invalid JSON after adding Hue Go

Devices
,
1

Hi,

I am using a Conbee II Stick with Deconz / Phoscon Version 2.20.01 / 19.9.2022; Firmware Version 26720700.

Everything works fine with Hue Essentials (connection, steering, …) until I add one specific Device to the Network. Its a Hue Go Smartlight. As soon as I connect this lamp to the Bridge, I cannot connect anymore through Hue Essentials.

The device works fine in Phoscon or other apps.

The error message is: Invalid JSON at 11183: Expected string or non-null literal.

Link to the device: Hue White & Color Ambiance Go tragbare Leuchte (neuestes Modell) | Philips Hue DE

I use Hue Essentials version 2.0.1 from Apple Appstore on an iPhone 12 Pro.
Is there anything I can do?
Thank you for your help!

IMG_3133.PNG
IMG_3133.PNG1170×2532 72.4 KB

2

Adding a bit more information, this is the entry within /api/<KEY>/lights which is affected:

"14": {
        "capabilities": {
            "alerts": [
                "none",
                "select",
                "lselect",
                "blink",
                "breathe",
                "okay",
                "channelchange",
                "finish",
                "stop"
            ],
            "bri": {
                "min_dim_level": 0.04
            },
            "color": {
                "ct": {
                    "computes_xy": true,
                    "max": 65279,
                    "min": 153
                },
                "effects": [
                    "none",
                    "colorloop"
                ],
                "gamut_type": "C",
                "modes": [
                    "ct",
                    "effect",
                    "hs",
                    "xy"
                ],
                "xy": {
                    "blue": [
                        0.1532,
                        0.0475
                    ],
                    "green": [
                        0.17,
                        0.7
                    ],
                    "red": [
                        0.6915,
                        0.3083
                    ]
                }
            }
        },
        "colorcapabilities": 31,
        "config": {
            "bri": {
                "startup": "previous"
            },
            "color": {
                "ct": {
                    "startup": 336
                },
                "xy": {
                    "startup": [
                        0,
                        0
                    ]
                }
            },
            "groups": [
                "6"
            ],
            "on": {
                "startup": "previous"
            }
        },
        "ctmax": 65279,
        "ctmin": 153,
        "etag": "4b5b8127c8ddaa02d6097456f12c6412",
        "hascolor": true,
        "lastannounced": null,
        "lastseen": "2023-01-28T13:10Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LLC020",
        "name": "Wand",
        "productid": null,
        "state": {
            "alert": "none",
            "bri": 102,
            "colormode": "ct",
            "ct": 366,
            "effect": "none",
            "hue": 8417,
            "on": false,
            "reachable": true,
            "sat": 140,
            "xy": [
                0.4573,
                0.41
            ]
        },
        "swconfigid": null,
        "swversion": "67.101.2",
        "type": "Extended color light",
        "uniqueid": "00:17:88:01:01:17:5a:8e-0b"
    },
3

The problem seems to be connected to deCONZ REST-API plugin version v 2.20.1 in which the attribute was added. This commit in deCONZ REST-API plugin introduced the new behavior:

4

Hi @ulilicht, thanks a lot for the detailed feedback. It seems the error is happening due to the swconfigid field in the response being null. Hue Essentials does not expect a null value for this key. I will fix it in the next version of Hue Essentials which should be available within a few days.

I am not sure why this value is null, nobody else has reported this issue before. But the next update will just ignore a null value which will fix the app for you.

5

Thanks a lot Thomas! Let me know if you need any test feedback.

Best
Uli

6

Hello,
I’m having a similar (or the same) issue on Android.

Screenshot_20230129_210623_Hue Essentials
Screenshot_20230129_210623_Hue Essentials921×604 73.8 KB

Using deCONZ 6.18.0 on Home Assistant 2023.1.7.

I’m glad to hear that you already know how to fix it.
Is there also a new Android version coming soon?

7

Hi,
I just ran in the same issue. Since @ulilicht tracked it down to a hue go, I checked mine in the phoscon pwa and recognized that the go is missing there, too.

Rolling back to another image worked, so I went over the last options and these are the results:
deconzcommunity/deconz:2.18.01 :white_check_mark:
deconzcommunity/deconz:2.18.02 :white_check_mark:
deconzcommunity/deconz:2.18.00 :x: (rebuild 3 months ago?)
deconzcommunity/deconz:2.19.00 :white_check_mark:
deconzcommunity/deconz:2.19.01 :white_check_mark:
deconzcommunity/deconz:2.19.02 :white_check_mark:
deconzcommunity/deconz:2.19.03 :white_check_mark:
deconzcommunity/deconz:2.20.00 :x:
deconzcommunity/deconz:beta :x:
deconzcommunity/deconz:2.20.01 :x:
deconzcommunity/deconz:stable :x:
deconzcommunity/deconz:latest :x:

edit: I filed an issue at github, but I guess technically the JSON is valid, so it probably won’t get fixed in the API.

8

An update for Hue Essentials is now available for Android, iOS, macOS, and Windows, with a bug fix where this null value is ignored. Please update the app and let me know whether this resolved the connection error. Thanks for providing all the details.

9

Yep, it’s working fine. :+1:

10

IMG_0480.PNG
IMG_0480.PNG1179×2556 236 KB