Have you tried pairing the switch again to HE?
With the "Zemismart ZigBee Wall Switch Multi-Gang" driver selected, pair the device again and let me know if there is any difference.
I need the device fingerprint - assign temporary the HE inbuilt driver named 'Device', click on the 'Get Info' button and copy and paste as a text the fingerprint that you should see in the live logs.
After obtaining the fingerprint, and after pairing again with the driver version that you are using now, if it still doesn't work - you can update to the new dev. branch version, where this device manufacturer and model is added, but the fingerprint is most probably wrong.. So I still need the actual fingerprint, as shown by Hubitat 'Device' driver.
Yes each time when I pair it to HE it automatically picked up the "Zemismart ZigBee Wall Switch Multi-Gang" driver so I didnt need to change driver but after that I wont be able to control the device.
The weird think is that when device is in pairing mode it will make a continuous beeping sound which never goes away once paired with HE, But when paired with my Zemissmart Hub after pairing the beeping sound goes away.
For now I have it paired to my old Zemissmart Hub as need to make sure that the device itself is working fine. I will repair it to HE tomorrow and report back
1 Like
Here you go:
dev:2922023-04-06 08:49:24.760 AMtraceZCL version:03
dev:2922023-04-06 08:49:24.757 AMtraceSoftware Build Id:unknown
dev:2922023-04-06 08:49:24.754 AMtraceModel:TS0003
dev:2922023-04-06 08:49:24.751 AMtraceManufacturer:_TZ3000_pfc7i3kt
dev:2922023-04-06 08:49:23.742 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,0702,0B04,E000,E001,0000", outClusters:"0019,000A", model:"TS0003", manufacturer:"_TZ3000_pfc7i3kt"
dev:2922023-04-06 08:49:23.375 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,0702,0B04,E000,E001,0000", outClusters:"0019,000A", model:"TS0003", manufacturer:"_TZ3000_pfc7i3kt"
dev:2922023-04-06 08:49:22.742 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,0702,0B04,E000,E001,0000", outClusters:"0019,000A", model:"TS0003", manufacturer:"_TZ3000_pfc7i3kt"
1 Like
Ok so looks like if my Hub is close to device then it works fine but if it has to hop through another device to connect to Hub then it stops responding.
Right now I have temporarily relocated C7 hub closer and will monitor how this works.
1 Like
Can you update to the latest version 0.5.1 ? There was a bug fixed that may be related to your device initial pairing problem.
I am moving my devices from C7 to C8 and am finding some after joining C8 have this error
dev:182023-04-23 10:45:33.832 AMinfoRelay Switch 2 initialize aborted!
And I can no longer control them even if I try removing and re-adding
- endpointId: 01
- application: 50
- manufacturer: _TZ3000_18ejxno0
- model: TS0012
Any chance I can get driver version Ver. 0.4.1 2023-02-10 to see if this works?
Also just to check once device is paired next step is to press Initialize right and then you should be able to use device as per normal?
Ok now when I am trying to move Moes Zigbee light switches back to C7 they pair, but do the same behaviour as it was doing on C8, no control, I cant turn on/off device and device status are not updating so this makes me thing there is an issue with the latest driver, as I have had these on my C7 before for awhile and they had no issues only deference is that when I would have paired them on my C7 back then driver version would have been a lot older.
1 Like
It is quite possible that something got broken between the versions... I will try to upload the older version now.
This is the link to version 0.4.1
About the warning - I will suppress it in the next version, it is one of the many check-in messages that Tuya devices send to the hub and is not of a real use.
And also if I remove and re-add I get these warnings
When I am adding I am not pressing initialize. Just adding and then waiting for 2 mins before I try using to see if its working as seems to automatically do that step and adds the child devices.
Whereas in the older drivers I remember after pairing we had to do configure or initialize to finalize the setup. (Cant remember)
It is the same warning, that must be downgraded to a simple debug message.
Initialize is executed automatically when a new device is added, so there should be no need to do it again.
Initialize() first deletes any child devices that may exist (created by the same or other drivers), and then creates the child devices again depending on the Tuya switch model.
In the latest driver versions, I have modified the button to require explicit selection of the 'Yes' option, as it happens the button to be activated accidentally, especially when browsing from a touch-screen device..
configure() button sends only some configuration commands to the parent device. It is also invoked automatically during the pairing process, so there is also no need to click on it.
One important detail of Tuya devices - some of them require the specific configuration to be made during the pairing process! So unlike all other Zigbee (or Z-wave) devices, the Configure button may not have an effect. That's why I am always recommending the Tuya devices to be re-paired again to HE.
Wait ... This message should not show up during the pairing process!
Update: Do you see it in the past logs (during the pairing process), or you see it later, when you click on the Initialize button, without selecting 'Yes' ?
I am seeing it during the pairing process only on C8 hub but not seeing that on my C7 hub.
Both Hubs on latest version
I am also seeing that devices are being controlled but status is not updating
After this Moes 3-gang switch was paired to the hub and the "Zemismart ZigBee Wall Switch Multi-Gang" was automatically selected during the pairing, you can try the HE inbuilt 'Generic Zigbee multi-endpoint Switch'. Just manually change the driver to the stock one and click on the Configure button.
It may work this way, but it is obligatory that the device was first paired with the Zemismart driver.
I have the Moes 3 gang switch which identifies itself as "xxx model: TS0601 gangs:1 child devices: 0" in the logs on initialisation.
I have not added any Moes specific drivers in HE driver code, but I don't know if this is needed?
No child devices are created for this device, and it does not seem to be properly initialised. When I look at version 0.5.4 of the code I see a TODO below:
- Ver. 0.5.4 2023-10-29 kkossev - (dev. branch) - added TS0002 _TZ3000_qcgw8qfa
-
TODO: add LIDL // https://github.com/Koenkk/zigbee-herdsman-converters/blob/38bf79304292c380dc8366966aaefb71ca0b03da/src/devices/lidl.ts#L342 // https://community.hubitat.com/t/release-lidl-smart-home-drivers-with-device-health-status/86444/15?u=kkossev -
TODO: check a possible problem w/ initialize() : https://community.hubitat.com/t/driver-needed-for-moes-3-gang-smart-switch-module-ms-104cz/116449/15?u=kkossev -
TODO: automatic logsOff() -
TODO: add healthCheck -
TODO: add numberOfGangs setting -
TODO: deviceProfiles
Is this still an open TODO, and do you think it could solve the problem?
Many thanks
Is your device manufacturer this one?
Hi Kassimir,
From what I can see it is
2023-11-09 14:07:17.319debugxxx Manufacturer name: _TZE200_tz32mtza
Thank you for coming back so quickly.
Many thanks
