stvred
commented
4 months ago I found a similar problem, but it was solved by abandoning Binding and switching to z2m link
Open stvred opened 4 months ago
stvred
commented
4 months ago I found a similar problem, but it was solved by abandoning Binding and switching to z2m link
cdjackson
commented
4 months ago If I look at the log you provided, it looks like the binding sends a single command to the device on endpoint 1, and the device turns on all switches -:
This seems not normal from the device, so I am not sure why it is doing that.
stvred
commented
4 months ago Yes, at first time it also look to me that the problem was in the device, change it and you will be happy. But as it turned out, this is not actually the problem. I put together a circuit link to which I published above (OH-mqttBinding-mosquitto-zidbee2mqtt-coordinator-device), and the device works correctly, all channels switch independently and everything works correctly. So, as it turned out, the problem is not in the device, but in the fact that in the circuit (OH-zigbeeBinging-coordinator-device) it sends a command to the coordinator for the device, and the device activates all channels at the same time. Also, I looked for similar problems in similar projects and found them in HA and zigbee2mqtt and judging by the messages, an update was released that solved problem.
cdjackson
commented
4 months ago Maybe there's a config setting in the device to change it's functionality - I don't know. To me, what the binding is doing by sending a single command to a single endpoint should result in a single switch coming on. This all looks fine. If the device has special, or non-standard functions, then unfortunately I'm not aware of this. You'd need to find out what the non-standard feature is before anything can be done here.
stvred
commented
4 months ago Unfortunately, I don’t have an additional device to sniff the transfer from the coordinator to the device, I only see logs. The logs that I see are the debug log between the binding and the coordinator. If I can get some additional data in this connection, then tell me how to do it. In conjunction with Z2M at the mqtt level, i see that depending on the channel, a different command is transmitted, here is an example:
payload{"indicator_mode":null,"linkquality":152,"power_on_behavior":null,"state_l1":"ON","state_l2":"OFF","state_l3":"OFF","state_l4":"OFF","switch_type":"toggle"}' payload{"indicator_mode":null,"linkquality":152,"power_on_behavior":null,"state_l1":"OFF","state_l2":"OFF","state_l3":"OFF","state_l4":"OFF","switch_type":"toggle"}' payload{"indicator_mode":null,"linkquality":152,"power_on_behavior":null,"state_l1":"OFF","state_l2":"ON","state_l3":"OFF","state_l4":"OFF","switch_type":"toggle"}' payload{"indicator_mode":null,"linkquality":152,"power_on_behavior":null,"state_l1":"OFF","state_l2":"OFF","state_l3":"OFF","state_l4":"OFF","switch_type":"toggle"}'
It seems to me that the problem is that the binding sends a command to the device in the payload with one command for one channel, and the device waits for four and interprets this command for all channels. I think the device receives the state of all four channels at once in one command. But these are my thoughts ;) based on the Z2M log.
cdjackson
commented
4 months ago It seems to me that the problem is that the binding sends a command to the device in the payload with one command for one channel, and the device waits for four and interprets this command for all channels.
Are you sure? This would be very strange. You migth be right of course, but it's very non-standard and it's not really possible to support this.
stvred
commented
4 months ago I can only see what the binding sends based on the logs. Well, again, z2m, as I see, sends the statuses of all channels at once.
cdjackson
commented
4 months ago Again, this is completely non-standard. Every endpoint should be separate - as though it is a separate device. So maybe there is other configuration that you are not seeing that gets sent before. I don't know, but this change is not easy for the binding to implement since it now bridges across multiple channels, and within the binding, the implementation is separate.
Maybe you can implement this as a rule if you are sure this is the issue.
Problem
Hi, i have a TS0004 4-gang switch and I have problems. When I press the physical button, everything works good. When i press button from OpenHAB, ON first channel they all 4 turn on, with turning off it’s the same
I tried to find a solution to this problem on the Internet, but without success.
Configuration
Logs
openhab> openhab:zigbee ncpversion
Ember NCP version 6.10.3.0, EZSP version 8openhab> openhab:zigbee ncpstate
openhab:zigbee nodes
log:set debug org.openhab.binding.zigbee log:set debug com.zsmartsystems.zigbee