hi
so i have this button in a battery version which works with the tuya user driver
but the powered version doesnt work with this driver..
i saw ppl use the zemismart user driver.. this seems to work and shows proper logs, but i cannot use it in button controller... it doesnt seem to be declared as a button device..i see it in rule machine as switch though.. can i declare the device as a button device manually?
also after switching drivers and repairing the device was layerd as a parent layer with 3 sublayers for the buttons.. never saw this before..maybe it means sth..
another important question: can the switch work as a smart device only, without using the relais? can the relais be turned off?
do i need the moes app for this? how can i bind it there? bluetooth?
The battery and the mains-powered 'versions' are actually very difficult devices, no matter that they have the same brand name engraved on the plastic...
Most of the mains-powered switches are presented as a 'Switch' type device is Hubitat, although there may be exceptions. It depends on the driver used, but basically, when a switching device has two stable states - on and off, it is always represented as a switch.
You could create a virtual button and use a very simple RM rule : when the physical switch state changes, then send the virtual button a push command.
When the State Variables or child devices become messy after experimenting with different drivers, assign the built-in 'Device' driver in HE, delete anything unnecessary, and then reassign the driver of your choice.
Some other models wall switches offer a 'detached relay' mode, but your device lacks this feature.
This is a Zigbee device. To use it with the Tuya ecosystem, you will need a Tuya Zigbee hub.
Remember, than one Zigbee device can talk to only one hub at a time.
