Skip to content
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

Closed
Andy-Hennah opened this issue Jun 18, 2022 · 27 comments
Closed
Labels
problem Something isn't working stale Stale issues

Comments

@Andy-Hennah
Copy link

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.
screenshot-83e04bb0

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

@Andy-Hennah Andy-Hennah added the problem Something isn't working label Jun 18, 2022
@lbida
Copy link

lbida commented Jun 19, 2022

Have the same issue.

@Andy-Hennah Andy-Hennah changed the title Siterwell GS361A-H04 Thermostatic Radiator Valve not show valve postion Siterwell GS361A-H04 Thermostatic Radiator Valve does not show valve postion Jun 27, 2022
@Andy-Hennah
Copy link
Author

Hi,
I was wondering if there's anyone out there who can see the valve position property working?

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the stale Stale issues label Aug 24, 2022
@Andy-Hennah
Copy link
Author

This is still a problem.

@Andy-Hennah
Copy link
Author

Andy-Hennah commented Aug 24, 2022

@lbida and @TheLexus are you still seeing this as an issue?

@github-actions github-actions bot removed the stale Stale issues label Aug 25, 2022
@jcxldn
Copy link

jcxldn commented Aug 30, 2022

Hi, I've just installed these and am having the same issue. My battery percentage is also reporting as N/A %, but I suspect that is because the percentage has not changed and so has not been published/updated.

@james-fry
Copy link

james-fry commented Sep 9, 2022

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:
https://user-images.githubusercontent.com/49618193/143578078-1c3d43e2-56b6-40d1-8dac-801096880e3e.PNG

(from here)

Siterwell-ZigBee-Radiator-Thermostat-GS361A-H04-User-Manual.pdf

@Andy-Hennah
Copy link
Author

Thanks @james-fry
So, is this documentation wrong then?
https://www.zigbee2mqtt.io/devices/GS361A-H04.html

@peteh
Copy link

peteh commented Sep 24, 2022

Seems like it.
It does not have valve position and also the running_state is N/A on my device:
image

@eljoest
Copy link

eljoest commented Sep 24, 2022

Same for me, no position and no running_state. Just bought mine as "Nedis Thermostat ZBHTR10WT".

@peterkappelt
Copy link

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):

- 17 (State of the window)
- 2 (Set temperature)
- 18 (Window check)
- 3 (Current temperature)
- 19 (State of the valve) -> I'm not yet sure what this DP indicates
- 4 (Mode) -> manual, auto, freeze
- 20 (Valve testing)
- 21 (Battery capacity)
- 102 (TempSet) -> don't know what that's for, no messages traced so far
- 7 (Child Lock)
- 27 (Temperature correction)

There doesn't seem to be a "valve position" DP at all 😢

@jcxldn
Copy link

jcxldn commented Sep 30, 2022

Hi, from packet capture of my TCP Smart variant of the Siterwell GS361A-H04 I can see the following 'unknown' datapoints:

1 (binary?)
4 (seen values ranging from 0-3)
13 (hex? values of 0 and 16)
14 (binary?)

Edit: I see these have been discovered in #13820 (comment)

Thanks,

James

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the stale Stale issues label Oct 31, 2022
@peteh
Copy link

peteh commented Oct 31, 2022

unstale

Still in issue:
image

State message:
image

@github-actions github-actions bot removed the stale Stale issues label Nov 1, 2022
@jekkos
Copy link

jekkos commented Nov 8, 2022

I own this valve as well, currently seeing this in my logs
tuyaThermostat: Unrecognized DP #17 with data {"dp":17,"datatype":4,"data":{"type":"Buffer","data":[0]}}
I was thinking perhaps this is the valve or battery state?
(0xec1bbdfffe8d689b): GS361A-H04 - Siterwell Radiator valve with thermostat (EndDevice)

@Alph4d0g
Copy link

Alph4d0g commented Dec 2, 2022

+1 got the same problem here.
Unfortunately I currently got no time to dig into this, but for what it's worth I'm at least preventing a stale topic =)

@jekkos
Copy link

jekkos commented Dec 17, 2022

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.

@fstap
Copy link

fstap commented Jan 15, 2023

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

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the stale Stale issues label Feb 15, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 22, 2023
@GamerClassN7
Copy link

Hi, Any news ?

@Jezza34000
Copy link

+1 same problem for me, following this thread :-)

@jekkos
Copy link

jekkos commented Nov 24, 2023 via email

@tml89
Copy link

tml89 commented Dec 19, 2023

+1 same problem for me

@yggster
Copy link

yggster commented Jan 4, 2024

+1 same problem. Following thread :)

@tbrasser
Copy link

+1

also I guess no way to use any external temperature without resorting to better-thermostat?

@darioschmid
Copy link

+1 same issue, following thread :)

@meydominic
Copy link

+1 any news on this?

{
    "away_mode": "OFF",
    "battery": 100,
    "child_lock": "UNLOCK",
    "current_heating_setpoint": 26.5,
    "linkquality": 255,
    "local_temperature": 21.5,
    "preset": "manual",
    "system_mode": "heat",
    "valve_detection": "ON",
    "window_detection": "ON",
    "position": null,
    "running_state": null
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests