So - I have one of these 4-way switches, and a while ago I was having trouble getting it to initialise at all - an upgrade to a C-8 seems to have dealt with that, but then the device (including the child devices) would work exactly as expected for a short while (say around 10min) then seemingly disappear from view - they worked locally, but the hub could no longer communicate with them. So I upgraded to the "Ver. 1.1.0 2024-05-02" driver, and now they still initialise properly (in particular for example I can set the switch type to momentary, which is not the reset default), but even though the child devices are created, they do nothing. Unfortunately I didn't keep track of with which driver version the switches were working for a short time.
Two questions:
What logs/debug would be useful for debugging this behaviour?
Any recommendations for a specific brand of 4-way switch that's known to work as expected?
Thanks!
Sorry, I have missed your post.
Can you let me know what is your device? (The Zigbrr model and the manufacturer, as shown at the bottom of the device web page)
Hi - I don't currently have the device installed, but I have this info from before:
endpointId: 01
application: 44
manufacturer: _TZ3000_ltt60asa
model: TS0004
One thing that I've noticed that might help with debug etc.. for both this and another Zigbee switch which I think is also a Tuya based item is that once they have been detected and you get the device install page, the device actually works correctly (i.e. you can turn switches on and off, the device page reports correctly the state of the switches, you can set settings, etc....) UNTIL the device times out of its discovery mode, at which point it stops working and seems to drop off the mesh.
So - almost as though there is some step missing to tell the device that the hub has seen it and it can stop being in discovery mode now.
I'm on a C8 if that's useful.
I have a currently unused C-7 (I upgraded to the C-8 when that came out to improve Zigbee range in particular with the external antennae) that I could pair them to and do a hub mesh with the C-8 if that's the case...
One anxiety: I used the "no need to re-associate" upgrade path when I got the C-8, so what would happen if I turned on the C-7? Would all my Zigbee and Z-Wave products try to connect to the old C-7 again...?
Yes, this is C-8 hub only. The same device will pair and stay connected to C-7 without a problem.
I have the same doubts and same questions how to proceed with my old C-7 that I migrated to C-8-Pro. I haven't powered it on since the migration a few months ago..
The answers to these questions are probably in the documentation and also in a lot of threads in this forum, but I haven't read them.
Im getting the following error " 2024-11-04 08:46:00.075 AMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_muxa_Zemismart_ZigBee_Wall_Switch_Multi_Gang_1485.autoPoll() is applicable for argument types: () values: Possible solutions: toggle() (method autoPoll)"
based on some past discussion, I switched to the driver Device and then switched back to the Zemismart driver Ver. 1.1.3
but I still get the error...
Note most of my use of these smart switches uses the "momentary" option with a switch that is momentary ... this switch is a standard switch so i set the switch type to toggle.
For fun I tried setting the switch type to state (not that I know what that means) but the error did not go away.
