Hi,
I use @holand.ivar 's excellent Tuya driver to control an immersion heater switch as a timer.
I want to detect when the switch is manually pressed so I can turn it off after a period of time.
I setup a rule to act when it detects the switch is turned on, but it never triggers.
Any ideas or alternative solutions?
Thanks
Paul
Here are some trouble shooting steps to try. First, turn on logging for the rule and the device. For debugging change the wait time to 1 minute and remove the only between time restriction.
When you turn on the immersion heater switch through the device page, does the rule work?
When you manually turn on the switch, does the device page show that the device is on?
Thanks @pseudonym for your response, sorry for the delay!
The rule never triggers, even if I remove the restriction.
If I manually turn it on the device stays off on the device page unless I click status, then it updates it correctly.
If I turn it on & off through hubitat that fine works though.
On the device page, go into the Events tab. If there is no event showing that the heater was manually turned on, the rule is not going to be able to trigger.
No nothing showing up. So to solve it I added the Tuya cloud integration to my Home Assistant instance and shared the status from there. That seems to work ok, but a bit of a kludge and relying on the cloud.
Hi @PaulB, these driver are polled. In the device setting you need to enable polling of the device status. There is unfortunately no way of getting the tuya device to actively send messages to the Hubitat hub, the hub needs to poll the device for its status. Essentially what the polling setting does is that it sets up a schedule to run the status() function.
If you open your device settings you should be able to see the below setting:
I would not recommend polling the device too often as it puts a load on your network and hub. My recommendation is to poll often on things that needs to have a quick response and limit those who do not really need immediate feedback.
Oh that makes a lot of sense. I’ll ty that. One or two-minute polling should be fine for this situation.
Hi,
I dont know why but i'm having all sorts of issues with tuyaGenericDevice.groovy.
It was working well, but now it seems to justs to stop working. I'm using the latest code.
I have checked the local key, IP address and ID, and all appears good. Must admit, I sometimes struggle to identify the Tuya API version, but most are 3.3, so I don't think they have changed. Is there a way to identify the API version through the iot.tuya website?
Hereis a log, the only issue I get is
dev:42024-01-27 21:01:16.833errorjavax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. on line 1041 (method parse)
What can I send to help diagnose this? Its haooening with a few devices that previously all worked fine.
Thanks
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
