LTW001 Light shows „on“ after vew seconds in deconz API but the real state is „off“

[Olli]

Only one Lamp shows the unreal state „on“ (API Version 2.25.0)
When i switch off the state by deconz API, after vew seconds the state switch back in the API to „on“, but in reality the lamp is off.

"20:23:36:311": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "11",
        "lastannounced": "2023-12-29T12:29:01Z",
        "lastseen": "2023-12-29T19:23Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "KU_Silberlampe",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
    },
    "e": "changed",
    "id": "11",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},
"20:24:01:732": {
    "e": "changed",
    "id": "11",
    "r": "lights",
    "state": {
        "alert": "none",
        "bri": 254,
        "colormode": "ct",
        "ct": 454,
        "on": false,
        "reachable": true
    },
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},
"20:24:22:267": {
    "e": "changed",
    "id": "11",
    "r": "lights",
    "state": {
        "alert": "none",
        "bri": 254,
        "colormode": "ct",
        "ct": 454,
        "on": true,
        "reachable": true
    },
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},
"20:24:45:305": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "11",
        "lastannounced": "2023-12-29T12:29:01Z",
        "lastseen": "2023-12-29T19:24Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "KU_Silberlampe",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
    },
    "e": "changed",
    "id": "11",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},
"20:25:54:325": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "11",
        "lastannounced": "2023-12-29T12:29:01Z",
        "lastseen": "2023-12-29T19:25Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "KU_Silberlampe",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
    },
    "e": "changed",
    "id": "11",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},
"20:27:03:235": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "11",
        "lastannounced": "2023-12-29T12:29:01Z",
        "lastseen": "2023-12-29T19:27Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "KU_Silberlampe",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
    },
    "e": "changed",
    "id": "11",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:a0-0b"
},

[Olli]

Today the second light with the same bug.

Both lamps with the incorrect status are LTW001 models.
It looks like the LTA011 models work perfectly.

//Edit
To check this, I have now registered my reserve LTW001. The problem is always the same

{
"16:06:22:460": {
    "e": "changed",
    "id": "6",
    "r": "lights",
    "state": {
        "alert": "none",
        "bri": 76,
        "colormode": "ct",
        "ct": 0,
        "on": false,
        "reachable": true
    },
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
},
"16:06:25:842": {
    "e": "changed",
    "id": "6",
    "r": "lights",
    "state": {
        "alert": "none",
        "bri": 76,
        "colormode": "ct",
        "ct": 0,
        "on": true,
        "reachable": true
    },
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
},
"16:07:11:716": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "6",
        "lastannounced": null,
        "lastseen": "2023-12-30T15:07Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "WZ_Schranklicht",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
    },
    "e": "changed",
    "id": "6",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
}

}

//Edit colorcapabilities=16?

"20:54:41:757": {
    "attr": {
        "colorcapabilities": 16,
        "ctmax": 454,
        "ctmin": 153,
        "id": "6",
        "lastannounced": null,
        "lastseen": "2023-12-30T19:54Z",
        "manufacturername": "Signify Netherlands B.V.",
        "modelid": "LTW001",
        "name": "WZ_Schranklicht",
        "productid": null,
        "swconfigid": null,
        "swversion": "67.88.1",
        "type": "Color temperature light",
        "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
    },
    "e": "changed",
    "id": "6",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:17:88:01:02:de:ec:4e-0b"
}

}

[Helox]

Got the exact same problem with my LTW001 lamps, also the LTW010 (also A19) lamps are showing the same behaviour but the LTW013 (GU10) are reported correctly.

Removing the lamps from zigbee network and readding them does not resolve the problem.

Note: seems to be related to the 2.25.0 release, running 2.24.2 resolved the problem, guess the latest docker tags includes the betas too, so I’m running the stable tag now.

[Olli]

Has anyone addressed the problem or has it even been recognized as a bug?
I’m back to version 2.24.2 so everything works fine again.

[Mimiix]

@Olli

has it even been recognized as a bug?

Bugs are collected and reported on GitHub