search

zigpy / zha-device-handlers

ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices.
Apache License 2.0
749 stars 685 forks source link

[BUG] Warning about "Min mireds is 0, setting to 153" #3086

Open EPinci opened 7 months ago

EPinci commented 7 months ago

Bug description

Reporting bug per HA log:

2024-04-04 00:12:15.724 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x766B:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-04 00:12:15.731 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x766B:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected

Steps to reproduce

Appears in HA logs

Expected behavior

Not sure what to report in here, I created the bug as instructed by the log entry. How do I trace it back to the offending device?

Screenshots/Video

Screenshots/Video [Paste/upload your media here]

Device signature

Device signature ```json [Paste the device signature here] ```

Diagnostic information

Diagnostic information ```json [Paste the diagnostic information here] ```

Logs

Logs ```python [Paste the logs here] ```

Additional information

No response

MattWestb commented 6 months ago

Pleas provide device signature and / or diagnostic.

This is not one HA error, its one not well done device firmware (very likely not Zigbee certified device) that is reporting its color propitiates outside the allowed range so shall being reported to the device manufacture so they can fixing ther device firmware.

EPinci commented 6 months ago

Those lines on the log are all I have. Can you tell me how to trace them back to a device?

TheJulianJES commented 6 months ago

Search 0x766B on the ZHA network visualization map to find the device that's in a broken state. Then, go to the device page of that and download diagnostics information and upload that info. (It might be a device such as a ZBDongle-E router.)

EPinci commented 6 months ago

You are spot on, it's a ZBDongle-E router. Info attached. zha-3630fb3d98a51a5a4bfab9d7b1d2741a-SONOFF DONGLE-E_R-a33f3faaf7988ab11c31c5d4082cb77d.json

AlexW75 commented 6 months ago

Have the same issue also using Sonoff ZBDongle_E.

gdrapp commented 5 months ago

Seeing the same with my Sonoff ZBDongle-E running router firmware Z3RouterUSBDonlge_EZNet6.10.3_V1.0.0.gbl.

StingRayZA commented 3 months ago

In case it helps, Similar issue here with the same. here's a json.

Error happens twice, I suppose because the device reports two lights 🤷‍♂️ 

homeassistant  | 2024-07-06 12:01:45.387 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x2965:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
homeassistant  | 2024-07-06 12:01:45.401 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x2965:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected

zha-ed8218d35d87057379ed64de725e603b-SONOFF DONGLE-E_R-859c4730571388a83952e6347d3f7554.json

brackishwaters commented 2 months ago

Same issue here in logbook.
Logger: zha.zigbee.cluster_handlers Source: components/zha/init.py:151 First occurred: 6:56:57 AM (2 occurrences) Last logged: 6:56:57 AM

[0xE1CA:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected

Im starting to feel like I need a quirk for this due to how ZHA is seeing its configuration: image

semaf commented 1 month ago

Same issue here..