Closed talkout closed 9 months ago
Amazing! Thanks for this!
I had to change the manufacturer to _TZ3000_zjtxnoft, but otherwise works perfectly for on/off. Setting the transition time doesnt work, but definitely progress :)
Could you check if the issue is fixed with the following external converter:
configuration.yaml
as ext_converter.js
configuration.yaml
:
external_converters:
- ext_converter.js
This fix some problems, but min/max brightness, switch-type and power_on behavior are not exposed here
Here is my working modified version:
https://gist.github.com/KipK/249f6275105140ca998e1452c71cabf4
@Koenkk I found out today that I had the same 2% issue when turning it off. Tested the external converter and solved the issue for me
Integrated the fix, thanks @KipK
Changes will be available in the dev branch in a few hours from now.
I have the FS-05R dimmer and it's not working 100% in the current version of zigbee2mqtt. I have several problems.
Below is a pic of my Exposes page.
@Koenkk I found out today that I had the same 2% issue when turning it off. Tested the external converter and solved the issue for me
Did you enable a transition time in the Settings (specific) tab under the device? If yes, try to delete the value. In my case it enabled the light to switch off.
I have the same problem with this hardware in home assistant Zigbee2mqtt integration (but on/off work !) and it is recognized as a Tuya TS0052 and not FS-05R
Zigbee2MQTT Version [1.38.0] Zigbee-herdsman-converters Version 19.47.1 Zigbee-herdsman Version 0.49.2
@strati64
What exactly is your problem, many different problems has been on the table for this product.
I have the same problem, when configured by default the ON/OFF button does not turn to OFF but stays at 2%. If i change the transition to '0', the ON/OFF button is OK, the dimming either, but the bulb still slightly ON.
I can see in mqtt explorer, for the first case that a set = brightness : "2" is send a couple seconds after the setstate : OFF causing the command to not shutoff but the bulb is OFF contrary the second case.
I attempted to modify the toZigbee.js but it does not save modification after HA reboot.
I have two FS-05R, the first works flawlessy, the second one has the issues listed in my previous post.
This is an extraction from zigbee2mqtt/database.db, id18 is the working one, id23 has with issue. Something may lead to manu specificbosch missing in the second.
Link
https://www.aliexpress.com/item/1005005824579031.html
Database entry
{"id":11,"type":"Router","ieeeAddr":"0xa4c1388aa502fbec","nwkAddr":56498,"manufId":4417,"manufName":"_TZ3000_mgusv51k","powerSource":"Mains (single phase)","modelId":"TS0052","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":256,"inClusterList":[3,4,5,6,57344,57345,8,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"^��,\u0012ч�,\u0012@��,\u0012У�,\u0012\u0005\u0000\u0000\u0000\u0012\u0005\u0000\u0000\u0000\u0012\u0005\u0000\u0000\u0000\u0012�\u000b\u0000\u0000\u0012","65506":54,"65508":0,"65534":0,"modelId":"TS0052","manufacturerName":"_TZ3000_mgusv51k","powerSource":1,"zclVersion":3,"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":""}},"manuSpecificBosch":{"attributes":{"53251":"AAAA"}},"genOnOff":{"attributes":{"onOff":1,"onTime":0,"offWaitTime":0,"moesStartUpOnOff":2}},"manuSpecificTuya_3":{"attributes":{"switchType":2}},"genLevelCtrl":{"attributes":{"currentLevel":2,"minLevel":2,"maxLevel":254,"onOffTransitionTime":0}}},"binds":[],"configuredReportings":[],"meta":{"onLevelSupported":false}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":-1440156621},"lastSeen":1700818080387,"defaultSendRequestWhen":"immediate"}
Comments
By default this pairs as "TS0052", but the functionalities and controls are not working correctly.
I added an external converter and fixed this for myself and it work.
Not sure if this needs to be a new device or something that already exists, but pairs incorrectly.
External converter
Supported color modes
No response
Color temperature range
No response