Valve position probably not shown correctly

jens-maus / RaspberryMatic

:house: A feature-rich but lightweight, buildroot-based Linux operating system alternative for your CloudFree CCU3/ELV-Charly 'homematicIP CCU' IoT smarthome central. Running as a pure virtual appliance (ProxmoxVE, Home Assistant, LXC, Docker/OCI, Kubernetes/K8s, etc.) on a dedicated embedded device (RaspberryPi, etc.) or generic x86/ARM hardware.

Apache License 2.0

1.56k stars 192 forks source link

Describe the issue you are experiencing

2x HmIP-eTRV-B grouped with HmIP-WTH-B to control heating in the same room. Temperature is set to 19°C, at around 19,5°C (dropping) the heaters start to warm up, while valve position is still 0% in CCU3. When I do set the temperature to 19,5°C via group control, the valve is opened to 6%. After I set the temp to 19°C again shortly after setting it to 19,5°C, the valve is set to 1%.

If I do assume, that the eTRV-B does not open the valve automatically without command for the CCU3: I asked myself why the heater gets warm. So I have to assume, that the valve position may not be displayed correctly and the valve is opened to allow flow of warm water through the heater (which would make sense to prevent the temperature dropping below 19°). Maybe I‘m assuming something wrong here and the valve can be opened without notifying the CCU3. Or could this be an issue of the direct shortcut between the eTRV-B and WTH-B?

Describe the behavior you expected

If the valve is opened, the position should be displayed correctly in the CCU3.

Steps to reproduce the issue

Please see above

What is the version this bug report is based on?

3.67.10.20230114

Which base platform are you running?

rpi4 (RaspberryPi4)

Which HomeMatic/homematicIP radio module are you using?

n/a

Anything in the logs that might be useful for us?

N/a

Additional information

No response

Thanks for your contribution!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of RaspberryMatic and tell us. Also check that all relevant details,

Vielen Dank für die Unterstützung!
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüfen Sie, ob das Problem auch in der aktuellsten Version von RaspberryMatic noch relevant ist, und teilen Sie uns dies mit. Überprüfen Sie auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind oder aktualisiert werden müssen.

jens-maus / RaspberryMatic