You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the device work using the Home Assistant Tuya Cloud component?
Is this device connected to another local integration, including Home Assistant and any other tools?
The devices are within the same HA subnet, and they get discovered automatically when I add them
What happened?
After more than a day of running 2024.5.0b2, this exception happened 3 times in a row. I logged such an event, its output at the bottom.
I must have said before, BLE capable gateways have not only "offline" and "online" lists. But, from my understanding, it should not matter in the way you parse the replies. On the other hand, all my Python experience is a few lines in LocalTuya. Now I see I was wrong!
I just wonder why it didn't happen before, and is happening very often right now. I have 2 BLE-capable gateways!
LocalTuya Version
2024.5.0b2
Home Assistant Version
2024.5.3
Environment
What happened?
After more than a day of running 2024.5.0b2, this exception happened 3 times in a row. I logged such an event, its output at the bottom.
I must have said before, BLE capable gateways have not only "offline" and "online" lists. But, from my understanding, it should not matter in the way you parse the replies. On the other hand, all my Python experience is a few lines in LocalTuya. Now I see I was wrong!
I just wonder why it didn't happen before, and is happening very often right now. I have 2 BLE-capable gateways!
The fix is:
without modifying
data
. But your current code:hass-localtuya/custom_components/localtuya/core/pytuya/__init__.py
Lines 826 to 833 in 298d561
looks safe, though does not take multiple replies into account yet. Nevertheless, I report this for your knowledge!
Steps to reproduce.
Have a BLE capable gateway, and Tuya BLE devices nearby.
Relevant log output
Diagnostics information.
No response
The text was updated successfully, but these errors were encountered: