[Bug]: Can't add Wi-Fi T&H sensor (but could before) #191
Comments
|
It was bugged before it ignored the whole connection process, but now it doesn't connect to the non online devices. "0" skips the handshake, not the whole connection process. The handshake is the device is supposed to be reachable, but it doesn't have to wait for return status. The reason I fixed this it was that users were putting anything in manual dps, not only 0, and would let them succeed to add the device even tho device isn't connected. However, I'll make an exception for low-power devices to ignore the connection process. |
|
Thanks for confirmation! I hope it will work again soon. But please also consider to do something to not even try to connect to such a device, and keep the last known values of its properties without a need to fool the integration with big device sleep time values. But I can live even with as it was day before yesterday 😄 |
What do you mean I may misunderstand :) The last values will be cached for the amount of time sets in device sleep time. |
* Fix error if brightness is not defiend * Allow low-power device to connect while it sleep. * Restore old states if 0 in manual dps. * Diagnostics Obfuscate private data.
xZetsubou
added
the
master/next-release
|
I just installed 3.2.5.1b1 to test the fix, but the T&H Sensor and the other WiFi low power device (scene switch) disappeared from the "Choose device to configure" list! Another not added device ("Wired Zigbee gateway") is still in the list. If I download diagnostics from LocalTuya screen, I see both devices in the "cloud_devices" list. It is expected behavior and, unlike before, I shall "Add Device Manualy"? OK, I tried to add the T&H Sensor manually, set 0 for "Manual DPS's", 21600 for "Device sleep time", and it works. But is it how it is supposed to be now? |
|
I think I realized that LocalTuya had no IP addresses of the devices right after the restart, and that's the reason why it didn't list low power WiFi devices. It should list them after an event with their ID come through. Am I right? Edit: Yes, it works this way! But I'd prefer such devices to be listed to Add and then fill in IP address only, rather than fill Name/ID/key etc. |
|
Not that good as before with T&H Sensor: "Discover device entities automatically" works, but
|
|
The reason your devices doesn't shows up is that The reason they doesn't shows up instantly it's because they are sleep so you will need to wait for them to wake up at least once to show up. there's a tip as well that even if device isn't showing as long you insert the ID correct it will shows an error but then it will fix the other field for you. an example :)
This bug caused probably weeks ago I just noticed it. The scale value isn't pulling from cloud. I fixed it on master. |
|
Thanks for explanations and the fix! Good news is that Humidity finally appeared, and I hope the Battery one day will appear too. It's strange that, according to Tuya logs, the sensor was sending both temperature and humidity, and even once - the battery level, but the temperature appeared from the first time, while humidity only on the second time. Weird, but now they are in sync. So, I believe this ticket can be closed :) |
|
I thought LocalTuya should not try to connect to a low power device like this T&H Sensor. But I just enabled logging, and I see several lines like this:
Why does it try to connect to a device known as never responding? Yes, it has "Device sleep time" set to 86400. |
|
It does re-connect every 5-seconds, all the devices do that. However, sleep time is the duration during which, if the device hasn't connected successfully, entities will shut down, and even pending status will reset. |
|
OK, now I better understand how it should work, but I see it works not as expected. The current state on the Overview for Humidity value is "Unknown". The details show: updated 38 seconds ago, and Attributes/raw state is 36. The log records: While I was writing this, the Humidity updated to 36%. The "Device sleep time" is 86400 seconds. Why it showed "Unknown" for the humidity, if there were updates 4 minutes ago, and hour before, and the correct value for Temperature at the same time? I expect it to show the last available value at least 86400 seconds old, meaning, never "Unknown" after the first reading and with such data in the log. |
|
It seems that if the new value of a sensor is the same as the current one, it is not set, and the "time counter" (Device sleep time) is not reset. Right now I see Humidity was updated 1 hour ago, Temperature was updated some minutes ago. In the corresponding payloads, Humidity was the same value. |
|
Created #199 about values from the sensor are not updated. The sensor itself works correctly, so the issue in the title was resolved. |
|
Well, there is a series of WiFi devices, in particular AVATTO WT198 thermostat https://pl.aliexpress.com/item/1005005829037258.html that can hardly be added when connection through the port 6668 is required. They seem not to be low power devices. Maybe there should be some way to add such without this initial connection |
|
Hello, the same difficulties with WIFI temperature and humidity sensor. I looked at the network frames with tcpdump. In fact the sensor cuts off its network interface and turns it on when the temperature or humidity is changed. See image (HA on network 10, 192.168.10.18; sensor in VLAN50 192.168.50.31). HA sends a message to 6668 the sensor does not respond (same with ARP or ping). If the temperature or humidity changes the sensor wakes up and sends a message to "....eu-central-1.compute.amazonaws.com.https" and it can respond to Local Tuya. After a few seconds the sensor turns its network off.
To register the sensor in Local Tuya: Version Local Tuya 3.2.5.1 |
Go to Reconfigure the sensor, put 0 to Manual DPS's, put 86400 to Device sleep timeout, an then it should work.
I suggest to update to the latest 3.2.5.2 beta, because many bugs were fixed. |
|
ok |
github-actions
bot
added
stale
and removed
master/next-release
LocalTuya Version
3.2.5.1
Home Assistant Version
2024.03.1
Environment
What happened?
I have a Wi-Fi T&H sensor. It is low power device, but, unlike written in FAQ, it reports its status whenever it wants (temperature, or humidity, or battery level, changed) and never does it periodically. It can be several times per minute, or after some hours. The rest of the time it sleeps.
In 3.2.5, I was able to add it with manual DPS's list. Then I changed "Device sleep time" to 21600 seconds (6 hours), to prevent periodical "Unknown" states and holes in the graphs.
Today I've deleted it and tried to add again with DPS=0, as you suggested for BLE bulbs in issue #190 (and I succeeded for bulbs!). The attempt with the sensor failed with a message "An unknown error occurred. [Errno 113] Connect call failed ('192.168.0.37', 6668)." But now the same message appears if I want to add it as before, with the real list of DPS's.
So, it seems a change in 3.2.5.1 broke this feature for Wi-Fi low power devices! As I understand, with a list of DPS's, or with 0 as the list, the integration should not even try to connect to the device being added. It still works this way for BLE bulbs.
I tried to roll back to 3.2.5, but HACS does not allow me to choose an older version: when I choose it from the list, it reverts the selection back to the currently installed version. So, I can't strictly confirm that I succeeded in 3.2.5 not by a lucky chance.
Steps to reproduce.
Try to add a Wi-Fi T&H sensor like mine.
Relevant log output
There is nothing in the system log related to this problem.Diagnostics information.
The diagnostics file was taken right before I've deleted the sensor.
localtuya-944c1616039a1d1ec6b9745179bff74e-ГС_ T&H Сенсор-db4dcba3127fbe2f04514f763aa33397.json
The text was updated successfully, but these errors were encountered: