Problem with tuya switch 2 gang

[yesua.ambros.peralta]

Good morning,

 Regarding compatible zigbee devices, there are:

“TuyaTS0002 2 Gang”

I have been able to correctly synchronize this device on ihost, however when I click on one of the gangs from ihost, both are activated automatically, not the one I clicked on. Is it possible or is there an action/possibility to correct that only the gang on which I click is activated/deactivated?

aibridge-zigbee/zgateways.log

mqtt_pub : topic: zigbee/system/discovering, payload: {“discovering”:true,“countdown”:180,“reason”:“Discover request”}, property: reqClientId:api, reqSequence:1705395059828
mqtt_pub : topic: zigbee/system/discovered, payload: {“manufacturer”:“_TZ3000_ptjcjise”,“model”:“TS0002”,“serialNumber”:“a4c138be90cc93d7”,“firmwareVersion”:“5.2”,“displayCategory”:“switch”,“linkLayerType”:“Zigbee-ZR”,“capabilities”:[{“capability”:“power”,“permission”:“readWrite”},{“capability”:“toggle”,“permission”:“readWrite”,“name”:“1”},{“capability”:“toggle”,“permission”:“readWrite”,“name”:“2”},{“capability”:“rssi”,“permission”:“read”}]}, property: reqClientId:zigbee, reqSequence:1705395074102
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/information, payload: {“manufacturer”:“_TZ3000_ptjcjise”,“model”:“TS0002”,“serialNumber”:“a4c138be90cc93d7”,“firmwareVersion”:“5.2”,“displayCategory”:“switch”,“linkLayerType”:“Zigbee-ZR”,“capabilities”:[{“capability”:“power”,“permission”:“readWrite”},{“capability”:“toggle”,“permission”:“readWrite”,“name”:“1”},{“capability”:“toggle”,“permission”:“readWrite”,“name”:“2”},{“capability”:“rssi”,“permission”:“read”}]}, property: reqClientId:zigbee, reqSequence:1705395074104
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/toggle/1, payload: {“toggleState”:“on”}, property: reqClientId:zigbee, reqSequence:1705395074108
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/toggle/2, payload: {“toggleState”:“off”}, property: reqClientId:zigbee, reqSequence:1705395074109
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/rssi, payload: {“rssi”:-50}, property: reqClientId:zigbee, reqSequence:1705395074109
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/availability, payload: {“online”:true}, property: reqClientId:zigbee, reqSequence:1705395074110
mqtt_sub : topic: zigbee/system/discover, payload: {“discover”:false}, property: reqClientId:api, reqSequence:1705395091649
mqtt_pub : topic: zigbee/system/discovering, payload: {“discovering”:false,“countdown”:0,“reason”:“Discover request”}, property: reqClientId:api, reqSequence:1705395091649
mqtt_sub : topic: zigbee/device/a4c138be90cc93d7/update/toggle/1, payload: {“toggleState”:“off”}, property: reqClientId:api, reqSequence:1705395103161
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/update-result/toggle/1, payload: {“received”:true,“toggleState”:“off”}, property: reqClientId:api, reqSequence:1705395103161
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/toggle/1, payload: {“toggleState”:“off”}, property: reqClientId:zigbee, reqSequence:1705395103545
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/rssi, payload: {“rssi”:-51}, property: reqClientId:zigbee, reqSequence:1705395103546
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/toggle/2, payload: {“toggleState”:“off”}, property: reqClientId:zigbee, reqSequence:1705395103738
mqtt_pub : topic: zigbee/device/a4c138be90cc93d7/updated/rssi, payload: {“rssi”:-49}, property: reqClientId:zigbee, reqSequence:1705395103739

Thank you so much

[ward]

Hi yesua.ambros.peralta,

Appreciate your feedback! The issue you mentioned has been resolved in the previous firmware. Could you confirm if you’ve updated to the most recent version?

Also -

Will repeating additions possibly resolve the issue? The switch on zigbee2mqtt may also counter this problem. Essentially, it is because, during the process of pairing, if there’s a package loss, it will get all channels controlled afterward.

Additionally, providing a full log, accessible via the setting tab, would be extremely helpful for us to better understand and address any remaining concerns. You can send it to me through DM (Message button on my profile page) or Google Drive link.

Thanks for your patience!

Best,
Ward

[yesua.ambros.peralta]

Thank you very much for your reply.
My version is the most recent: 1.13.2
If it is true that the test was carried out with version 1.13.0 (I carried out the update to 1.13.2 yesterday.
This afternoon I will try to link the device again, seeing that the outcome did not work. And if you have the same problems, I will attach the complete logs.

[yesua.ambros.peralta]

I confirm that in this new version it does work.

One question, are there plans to make some type of multi-device functionality like Tuya? That is, have several switches synchronized to manage the same light bulb? At the moment, the only alternative I have is to create automation so that when I turn on one, it switches on the rest, however on some occasions if there is a delay it goes into a loop turning the lights on and off in an uncontrolled manner.

Thank you so much