Open andrew01144 opened 3 months ago
I found the original PR that added support for this device, and my feeling is that the author wanted to add the E3-ZR
instead.
I will try to add the device as an alias to the Miboxer FUT035
which is older Dual-white controller of the same manufacturer instead, let's see if that works.
@pvyleta thanks for taking a look. I have an E2-ZR in front of me. Note that it can be configured as "Single Color" or "Dual White" by pressing the button on the unit. Let me know if it needs to be in a particular config, and let me know if you would like me to try anything.
@andrew01144 That should be fine, since the FUT035+ has the same feature. I mean it is basically identical device feature-wise, just in newer box.
So I tried editing the code on my instance, and now it works. It claims it failed the interview for whatever reason, but I can control the color etc anyway. I will create a PR soon.
@pvyleta I think I understand what you have done, so I tried the same. It now identifies as MiBoxer FUT035Z+ and, as far as I can tell, works correctly. Thanks for the inspiration.
Link
https://www.zigbee2mqtt.io/devices/E2-ZR.html
Model
E2-ZR
Description
LED controller
Vendor
MiBoxer
Picture (link)
https://www.zigbee2mqtt.io/images/devices/E2-ZR.png
Database entry
{"id":24,"type":"Router","ieeeAddr":"0xa4c138f5a21a2354","nwkAddr":4867,"manufId":4417,"manufName":"_TZB210_ayx58ft5","powerSource":"Mains (single phase)","modelId":"TS0502B","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":268,"inClusterList":[3,4,5,6,4096,8,768,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65534":0,"stackVersion":0,"dateCode":"","manufacturerName":"_TZB210_ayx58ft5","zclVersion":3,"appVersion":64,"modelId":"TS0502B","powerSource":1}},"lightingColorCtrl":{"attributes":{"colorCapabilities":16,"colorTempPhysicalMin":153,"colorTempPhysicalMax":500,"colorTemperature":0}},"genOnOff":{"attributes":{"onOff":1}},"genLevelCtrl":{"attributes":{"currentLevel":254}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x00124b002e1e9f4e","endpointID":1},{"cluster":8,"type":"endpoint","deviceIeeeAddress":"0x00124b002e1e9f4e","endpointID":1},{"cluster":768,"type":"endpoint","deviceIeeeAddress":"0x00124b002e1e9f4e","endpointID":1}],"configuredReportings":[{"cluster":6,"attrId":0,"minRepIntval":0,"maxRepIntval":65000,"repChange":1,"manufacturerCode":null},{"cluster":8,"attrId":0,"minRepIntval":10,"maxRepIntval":65000,"repChange":1,"manufacturerCode":null},{"cluster":768,"attrId":7,"minRepIntval":10,"maxRepIntval":65000,"repChange":1,"manufacturerCode":null}],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":64,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":332242049},"lastSeen":1721467873839}
Notes
Hi, This is a re-open of [Wrong device]: Miboxer E2-ZR shown as TuYa TS0502B https://github.com/Koenkk/zigbee2mqtt/issues/21185
I have the same problem, but have not succeeded in fixing it.
Starting with Z2M from around 01-Jun, that's before the fix. I my E2-ZR successfully joined Z2M, but it appeared as Tuya TS0502B. I upgraded Z2M; herdsman now shows as 19.62.0. I removed the device. Re-joined the device, but it still appears as Tuya TS0502B. Am I missing a step?
I tried bringing up a new instance of Z2M with a different adapter. Still appears as Tuya TS0502B. I tried commenting the E2-ZR line in devices/tuya.js. Still appears as Tuya TS0502B.
Many thanks for any help!
Also - setting 'transition' seems to have no affect on the actual transition.