Closed fzellner closed 2 months ago
The logs doesn't seem is full.
Ensure the WiFi connection of that device is good.
Try remove and re-add the device and you may also want to test protocol version 3.2
.
You may need to check the connection of home-assistant as well that it good
Try ping to that device e.g. ping -n 20 192.168.1.102
and see ensure that it stable and low ms and no losses.
Ty for the feedback and suggestions!
Made a ping session to the device, and has no packet loss and re add the device with 3.2 protocol and showed the same behavior. Also, the HA connection is healthy. I started to see the same delay on the Tuya app. Maybe, this is a issue regarding the device itself... it's a generic wall switch.
I am gonna try another switch ASAP
I started to see the same delay on the Tuya app. Maybe, this is a issue regarding the device itself... it's a generic wall switch.
If the issue happened on all devices feel free to open this, I'm kinda sure that this is a device behavior.
note: the empty payload in the debug is just a "heartbeat" payload to keep the connection alive with the device it shouldn't shows because a debug need to enabled for the device it self.
LocalTuya Version
2024.0.6
Home Assistant Version
2024.6.2
Environment
What happened?
After adding a wifi device, when I try to change the state of the switch the device takes a huge delay to reply. When I enabled the debug log, the log showed that when I tried to change the state, the payload was empty.
Steps to reproduce.
Relevant log output
Diagnostics information.
localtuya-9c64053becbaab0cec25dc25e17a7e4f-Interruptor Sala-6a23806208be7de35c69a65ffb11a378.json