-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Moes BRT-100-TRV not reporting valve positon #8533
Comments
@vladi1234 maybe you could help |
This valve works strangely. After some time, I'm not able to even set temperature from Z2M. |
It looks like valve position is reported, but only when local_temperature changes. When you change set_temperature and then the valves position changes, it isn't reported. |
Hello @wizu. |
@vladi1234 I also noticed that it sends valve position whenever the backlight is active. |
@wizu This is not the fault of a Z2M integration. This is how TVR works, is how it was designed, I think this, it looks like it has something to do with the Stand-by function. |
@vladi1234 That's what I was afraid of. I've already ordered 10pcs of https://www.zigbee2mqtt.io/devices/TS0601_thermostat.html and will have to sell BRT-100TRV. |
Just a tip. pro: Display stays on and Valve reporting works all the time. |
The ones you have ordered have a hardware flow. Lid breaks over time |
Hi all, |
I've installed a few Moes BRT-100-TRV thermostatic valves and have problems with them.
What happened
Valve don't report valve position, It's get stuck and won't change even when i can see that, valve is moving. I'm changing set temperature and reported valve position stays the same, even after an hour.
What did you expect to happen
I would like to use valve position to control my boiler, but it's value doesn't change.
How to reproduce it (minimal and precise)
Change set temperature bolow or above local temerature and position don't change.
Debug info
Zigbee2MQTT version: 1.21.0 commit: 70891ee
Adapter hardware: CC2538
Adapter firmware version: 20200211
The text was updated successfully, but these errors were encountered: