yes, here is my sequence...
- Installed Driver from Github
- Add Zigbee Device
- Click Configure
- click initialize - param set to YES
Please post some debug logs when you press the physical switch on the device itself. Do you have a physical switch wired ( S0-COM ) ?
Hi, I have also having problem with Tuya 4Ch smart switch, it is picking the driving but showing this message, i have tried all the steps mentioned in the post i.e
After paring the device it picks the driver but when i press on, off buttons of switches or even parent it didn't work, when i repair it and click the already found link, on and off button works for some time but then it stops working. There are no errors i can see in logs.
Sounds like the well-known Hubitat connectivity problem with some new ‘Zigbee 3.0’ devices… is your hub the C-8 or some of the older models?
If during the pairing process the Zigee map shows "Unknown" devices like in this screenshot, for me this definitely means Zigbee 3.0 connectivity issue between the old hub and the new device SoC Zigbee stack.
Right, so any work around to make that work ? I purchased two devices only for testing.
No known workaround as of today (other than using SmartThings or ZHA/Zigbee2MQTT ).
I got a similar relay to the original poster, and after installing the Zemismart driver from @kkossev, I removed the old device, and repaired it. It was immediately recognised with the Zemismart driver, but I still get the repairing notice.
This is the device ID, and logs. There doesn’t seem to be any errors, but trying to change the switch to Momentary doesn’t work.
Any ideas?
Are the two gangs working normally? Can you turn the switches on and off from the child device pages?
Please copy and paste as a text (not screenshot!) the debug logs when you change the switch type to Momentary.
Yes, the 2 child switches work as expected turning on and off. Both come up as Generic Component Switch.
The log is:
dev:822023-11-09 06:54:54.358 PMdebugMaster bedroom - balcony Attribite FFE4 : 00
dev:822023-11-09 06:54:54.356 PMdebugMaster bedroom - balcony Attribite FFE2 : 38
dev:822023-11-09 06:54:54.355 PMdebugMaster bedroom - balcony Applicaiton version: 48
dev:822023-11-09 06:54:54.350 PMdebugMaster bedroom - balcony Parsed descMap: [raw:643D0100001801002048E2FF2038E4FF2000, dni:643D, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:48, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]] (description:read attr - raw: 643D0100001801002048E2FF2038E4FF2000, dni: 643D, endpoint: 01, cluster: 0000, size: 18, attrId: 0001, encoding: 20, command: 0A, value: 48E2FF2038E4FF2000)
1 Like
These logs are from the device check-in messages...
Clear the device logs, then select 'Momentary' switch type and click on the "Switch Type" above.
I need the Debug logs that follow clicking on this button.
Also, please copy and paste again as text (not as a picture!) the device details data (model and manufacturer).
Problem solved! Was caused by dumb user, as I didn't realise I had to click the "Switch Type" after choosing "Momentary".
Thanks for the help; I had been wondering how to save the setting as you mentioned Save Preferences doesn't do it.
1 Like
A lot of other uses are confused too... If you have any idea how to make it more clear, please let me know.
Perhaps a small button next to the selection dropdown that says "Set"?
I've now successfully set up another of those relays but with a single channel, factory new; even though it recognised as the Zemismart, and used that driver, it still has the same " In order to operate normally, please pair the device to HE after changing to this driver!" warning.
The device ID was:
- endpointId: 01
- application: 48
- manufacturer: _TZ3000_zmy4lslw
- model: TS0002
(TS0001 for the single channel).
This is a hardcoded info/reminder and it will not go away when you actually paired the device with this driver pre-installed and the driver was selected automatically.
But I just got an idea, probably it is probably possible to distinguish between the two scenarios, will have to experiment when I have time.
That would be ideal situation, wouldn't it, rather than a re-pairing exercise. I guess there is no way to check to see if the driver was selected from a clean driver install, or was selected after.
Does Not work with this switch, Some idea how to fix it?
- endpointId: 01
- application: 48
- manufacturer: _TZ3000_zmy4lslw
- model: TS0002
If you provide some more details what exactly does not work and what you are trying, I may be able to help.
