-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Sonoff TRVZB - Completely unusable #1372
Comments
Attaching the debug from BT on the same valve. You will notice that one other sensor initiallyu configured has values out of range. I can confirm that this is not the issue. I reconfigured the valve in BT without taking the values from that sensor but taking them directly from the valve itself. Unfortunately the valve has the same behavior described in the bug opening. What resonates to me is the error "ERROR (Recorder) [homeassistant] Error doing job: Task was destroyed but it is pending! (<Task pending name='Task-93145' coro=<control_queue() running at /config/custom_components/better_thermostat/utils/controlling.py:47> wait_for=>)
|
Same issue with my HA instance (2024.8.3) and at my daughter's house one. |
I can not confirm this, everything is going as usual with me. |
Test should be done in the same situation, is it the case? |
I suspect the issue happens specifically with sonoff latest 1.1.5 firmware. But I have no evidence for this. thanks @msd3287 for sharing about the alternative thermostat integration. I will give it a try! |
Cannot confirm this. Actual HA, BT and Firmware. |
I can confirm this on 1.1.5. I have 2 TVRZBs in one BT, and turning the dial on the TVRs does not change the setting in BT. Also it does not update the other TVR as I would expect since they are somehow grouped by BT. |
As already written, I don't have this problem. However, I do not use the integrated schedule. In my case, the sensor in the HA shows unknown. |
Disabling the TRV schedules is pretty much mandatory as they break a string field length limit that neither MQTT nor HA people can agree on whose fault it is, HA used to just move on and leave it as unknown, but recently started throwing errors instead which causes the device to reset @Unclezz - it looks like it's trying to set the temperature of the TRV to 120 degrees, which is causing errors, as it's a bounded value in MQTT, are you working in C or F? |
Thanks for looking into this one. Disabling the schedules did not help. |
Prerequisites
Sonoff TRVZB
Description
Every time you try to control a Sonoff Valve through BT, the valve goes offline and reset its state. On the valve LED you always read OF.
If you try to change value on the valve, the same is not reflected in BT or anywhere else. Then the valve goes again to OF.
Steps to Reproduce
Simply use BT to realize what described above.
Expected behavior:
Valve to react on BT input and viceversa.
Actual behavior:
Every time you try to control a Sonoff Valve through BT, the valve goes offline and reset its state. On the valve LED you always read OF.
If you try to change value on the valve, the same is not reflected in BT or anywhere else. Then the valve goes again to OF.
Versions
HA:
Core 2024.7.3
Supervisor 2024.06.2
Operating System 12.4
Frontend 20240710.0
BT: 1.6.0
Additional Information
If you remove BT the valves are working perfectly with the standard HA climate control.
The text was updated successfully, but these errors were encountered: