-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tuya TS0601_thermostat power indicator gone #4879
Comments
Can you make a screenshot of this? |
What do you see under the "State" tab when clicking on the device? |
Seems its caused because a battery report is missing, can you ask in this thread if others also experience this: #3821? (I don't have this device/knowledge about it) |
As far as I can tell (and I only have these valves for like 2-3 weeks), battery reporting never worked so far. |
We're working on it, we believe the DP 366 reports low battery - which hasn't been configured yet in Z2M...still testing. If you want to help I posted the clause needed to be added to report it, just need to make sure it solves it for all/most models of the valve. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
After 2 weeks of playing with my new thermostat, my thermostat reports low battery now in the "battery_low" boolean field, mostly when the motor is running to open/close valve. So if useful I can help to do some test with this. As a coincidence I also saw a screen shot how battery is displayed in Tuya app. And it seems that they display the battery voltage on there... so probably that value comes from the device. And should be quite straightforward to transform that to a (rounded) percentage. |
Do You mean that it reports low battery only when valve is moving the motor? Because that's what I think is happening, which gives a lot of state changes for this and basically makes it very unreliable since You can only judge by amount of state changes in the history? |
The battery low sensor starts flashing on and off when motor is moving, which is first signal that batteries are getting empty. This is no surprise because the motor needs the most power. After a day or two the sensor was constantly on. And shortly after that communication with device was lost and I needed to replace batteries. The battery percentage was never available.I had this experience now with two different Moes TRV devices. |
@groenmarsmannetje Was state of |
Apparently this device doesn't expose battery level just battery low. Probably needs removing. |
@Morphy99 thanks, removed it Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
Yes it was. |
@salopette what is showed in the state tab? |
`igbee2MQTT WC-EG-TRV |
There is no state for |
|
@salopette can you provide the herdsman debug log when doing the |
To me it is not clear what valve_detection should actually do. |
|
@salopette does setting the valve detection actually work? (I have no clue what this should do) |
I haven't found out anything yet. I don't know what this function is for. |
When the device initially is started it runs a sequence to determine the minimum and maximum position of the valve. That could be considered as some kind of “valve_detection” but if this is also intention of this switch is not clear to me. I have not seen anything happening when I tried the switch. |
i'm still having errors like this one, even after switched to edge version: |
So there is no way how to get battery state from Tuya? Uff.. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I got some information about this: #7270 (comment) It is a "valve fault detection" to indicate if the vault would stay closed (radiator not heating) even when the TRV is "open". |
Hello, there is a problem with tuya TS0601_thermostat
after updating to 1.16
the battery indicator disappears,% flashes in its place
What happened
What did you expect to happen
How to reproduce it (minimal and precise)
Debug info
Zigbee2MQTT version:
Adapter hardware: CC2531, CC2530, CC26X2R1, CC1352P-2, Conbee II
Adapter firmware version:
The text was updated successfully, but these errors were encountered: