ebaauw / homebridge-deconz

Homebridge plugin for deCONZ
Apache License 2.0
135 stars 7 forks source link

warning: 00212EFFFF06E9EB-S35: /sensors/35: CLIPDaylightOffset: ignoring unknown sensors type #225

Closed BEskandari closed 3 weeks ago

BEskandari commented 3 weeks ago

Hello Erik, thank you for your great work. Since the upgrade to version 1.0.13 I got 4 warnings when I start Homebridge:

[21/08/2024, 20:24:22] [deCONZ] Phoscon-GW: warning: 00212EFFFF06E9EB-S35: /sensors/35: CLIPDaylightOffset: ignoring unknown sensors type
[21/08/2024, 20:24:22] [deCONZ] Phoscon-GW: warning: 00212EFFFF06E9EB-S36: /sensors/36: CLIPDaylightOffset: ignoring unknown sensors type
[21/08/2024, 20:24:22] [deCONZ] Phoscon-GW: warning: 00212EFFFF06E9EB-S37: /sensors/37: CLIPDaylightOffset: ignoring unknown sensors type
[21/08/2024, 20:24:22] [deCONZ] Phoscon-GW: warning: 00212EFFFF06E9EB-S38: /sensors/38: CLIPDaylightOffset: ignoring unknown sensors type

The reason is that by mistake I have activated the daily schedule in the Phoscon App, that creates 4 sensors such as:

"35":{
"config":{"mode": "sunset", "offset": 0, "on": true, "reachable": true},
"etag": "e600a0d94b2e3cb15c88c245b4465d2c",
"manufacturername": "Phoscon",
"modelid": "DLOFFSET10011",
"name": "Offset Ref P-SS",
"state":{
"lastupdated": "2024-08-21T18:23:42.857",
"localtime": "2024-08-21T20:32:23"
},
"swversion": "1.0",
"type": "CLIPDaylightOffset",
"uniqueid": "2E:F1:37:A5-D177-5E57-B656-2F:20:94:7D:1D:47"
},

The version 1.0.12 was apparently not sensitive to this. Actually I don't know if those sensors could be useful for the future for supporting the schedule in Homebridge.

ebaauw commented 3 weeks ago

I think previous versions would issue the same warnings?

I could change the message to “ignoring unsupported sensors type”, but I wouldn’t know how to expose these to HomeKit.

ebaauw commented 3 weeks ago

In v1.0.14.