question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Overwrite max_mireds to 370 for ZS1000204-IN-DE-V1A02

See original GitHub issue

I bought a Linkind bulb with the model name ZS1000204-IN-DE-V1A02 and registered it via z2m, which was recognized as Linkind ZL1000100-CCT-US-V1A02: https://www.zigbee2mqtt.io/devices/ZL1000100-CCT-US-V1A02.html

The main problem is that max_mireds should be 370 rather than 500, because at 370 the lamp has already reached the warmest level. In addition, but less important, the various effects do not differ, they all only flash at the same rate.

I have installed Home Assistant Supervised (2021.1.4), Mosquitto broker (5.1) and Zigbee2mqtt (1.17.1) are retrofitted as add-ons, the bulbs was integrated via MQTT Discovery.

The color-temp slider of the bulb has it max at 500 but only upto 370 has an effect (and jumps back to it in hassio (sometimes in z2m-tab expose), if I slide above it) and the developer-tools of hassio show me a max_mireds of 500.

Now I’ve tried to integrate the bulbs in hassio manually with the additions: min_mireds: 153 max_mireds: 370 If the bulbs was still integrated, the settings were ineffective even after a restart. If I removed the devices from the integration and switched off auto-discorery, the bulbs did not appear even after a restart. But that’s an other issue, which I ignore for now.

I then reversed that and took a closer look at the options of z2m (https://www.zigbee2mqtt.io/information/configuration.html). ‘device_options:’ was ineffective, especially since I don’t know how to bind the parameter to a model, it did not work anyway. ‘external_converters:’ despite the examples I did not understand at all how I could overwrite the max_mireds value with these. I even tried to modify the /zigbee2mqtt-1.17.1/node_modules/zigbee-herdsman-converters/devices.js within the container: extend: preset.hue.light_onoff_brightness_colortemp_color([153, 370]) But as soon I restarted the add-on, the setting was back to default.

What amazes me that /share/zigbee2mqtt/database.db apparently recognized the max value correctly (colorTempPhysicalMax":370):

{"id":7,"type":"Router","ieeeAddr":"0xec1bbdfffeb588bf","nwkAddr":6913,"manufId":4456,"manufName":"lk","powerSource":"Mains (single phase)","modelId":"ZBT-CCTLight-D0106","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":268,"inClusterList":[0,3,4,5,6,8,768,2821,4096,64642],"outClusterList":[10,25],"clusters":{"genBasic":{"attributes":{"modelId":"ZBT-CCTLight-D0106","manufacturerName":"lk","powerSource":1,"zclVersion":3,"appVersion":1,"stackVersion":1,"hwVersion":1,"dateCode":"20190509-346","swBuildId":"2.2"}},"lightingColorCtrl":{"attributes":{"colorCapabilities":16,"colorTempPhysicalMin":153,"colorTempPhysicalMax":370,"startUpColorTemperature":65535,"colorTemperature":370}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":1,"stackVersion":1,"hwVersion":1,"dateCode":"20190509-346","swBuildId":"2.2","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2},"lastSeen":1612722264454}

Is there a simple solution here?

Thanks and regards

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:27 (14 by maintainers)

github_iconTop GitHub Comments

2reactions
sjorgecommented, Feb 12, 2021

That would make syncing up different brands difficult.

setting 370 (neutral) preset on Hue, Innr, Ikea all produce mostly the same color to the eye. 250/370/454 are what the ikea puck remote sets, and what they call cool / neutral / warm, which is in range of a lot of bulbs. (At least with my mix of tested Hue E14, Tradfri GU10 WS, Tradfri E27 CWS, Innr E14, Inner E27, Osram E27, and Tint E27)

coolest and warmest are mapped to whatever the bulbs min/max is, those perhaps should be renamed to min and max.

0reactions
geigervibecommented, Mar 4, 2021

thanks, I was not sure, these bulbs are offline now, could not check, if the range was correct. Thanks you confirmed it and thanks for the fix for the other bulb…

Read more comments on GitHub >

github_iconTop Results From Across the Web

No results found

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found