-
-
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
Siterwell GS361A-H04 Thermostatic Radiator Valve does not show valve postion #12870
Comments
Have the same issue. |
Hi, |
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 |
This is still a problem. |
Hi, I've just installed these and am having the same issue. My battery percentage is also reporting as |
I have looked at the siterwell manual (PFA) and also the github for zigpy/ZHA support for this TRA and as far as I can see, it does not support valve position. Its an error in the Z2M device js to expose valve position. What the TRV does support is valve fault detection (boolean) - see page 15 in the manual. You can see the ZHA supported functions here: (from here) Siterwell-ZigBee-Radiator-Thermostat-GS361A-H04-User-Manual.pdf |
Thanks @james-fry |
Same for me, no |
I've bought these thermostats as well and ran in the same issue. Apparently, my model (Nedis ZBHTR10WT) doesn't even expose it's valve position, unfortunately. I've paired it with a Tuya gateway and checked it's available DPs (names taken from Tuya IoT Dashboard):
There doesn't seem to be a "valve position" DP at all 😢 |
Edit: I see these have been discovered in #13820 (comment) Thanks, James |
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 own this valve as well, currently seeing this in my logs |
+1 got the same problem here. |
does the temperature reading work well for everyone here? The reading on mine always get stuck to some value after a week. I then need to reset the network key and repair them to make it work again. Beside this the link quality reading do seem to be updated, so it's only temperature that is stuck. |
Same problem for me, this has been going on for almost two months now I think. Pretty annoying, though I had no time to investigate the issue |
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 |
Hi, Any news ? |
+1 same problem for me, following this thread :-) |
In the end I was able to make one trv log its temperature consistently. Pairing these devices remains a headache. I always end up having to reset my network key.
Also the plastic mount easily breaks. I found a 3d part that can be glued to it as a replacement.
Jezza ***@***.***> schreef op 24 november 2023 12:23:10 CET:
…+1 same problem for me, following this thread :-)
--
Reply to this email directly or view it on GitHub:
#12870 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
+1 same problem for me |
+1 same problem. Following thread :) |
+1 also I guess no way to use any external temperature without resorting to better-thermostat? |
+1 same issue, following thread :) |
+1 any news on this?
|
What happened?
I successfully paired a Siterwell GS361A-H04 TRV with z2m. Values are coming through to the web UI for all exposed attributes except position and running_state, these are displaying N/A.
This issue was noted on #8813 after it was closed. It is still happening.
What did you expect to happen?
I was expecting the value of position to display the position of the valve as the valve changes, from 0% (closed) to 100% (fully open).
I was expecting running_state to change from idle to heat depending on whether the valve is open or not.
Note, the valve_detection value is set to "ON".
How to reproduce it (minimal and precise)
Make changes to the heating set point and hear the TRV's valve opening and closing.
Zigbee2MQTT version
1.25.2 commit: a252914
Adapter firmware version
20210120
Adapter
Electrolama zzh
Debug log
logX.txt
The text was updated successfully, but these errors were encountered: