Information about valve position in HeatingThermostat devices missing

[lonestar2001]

The HMIP App is showing wheather the valve of a heating thermostat is opened or closed (small up/down arrows next to the room temperature).

Currently I'm simply comparing the setPointTemperature with the actualTemperature to get a similar result.

But this doesn't give me the valve position! I really need to know when the valve is opened and when not to better control the heatpump. Sometimes, the device is opening early (setPointTemperature still > actualTemperature) and closing later (SetPointTemperature < actualTemperature).

[Apollon77]

Which adapter version you use? In 1.20 there was adjsted something for valve positions?

If this is not your topic then please enable debug logging for the instance and post/send me to iobroker@fischer-ka.de a full debug log from adapter start and tell me exactly which device ID you would have expected these data

[lonestar2001]

I'm using the newest version, 1.20 and no, there never were any information about the valve position yet as far as I know. I'm pretty sure that this info is available in the API but not yet in the adapter. You can find the debug info as requested in the email.

[unstressable]

This is already implemented!

[lonestar2001]

I don't have those objects in channel 1. Even in channel 2 there is nothing like this. My functionalChannelType has a different value: WALL_MOUNTED_THERMOSTAT_PRO_CHANNEL Maybe it's not implemented for that device?

The only location where I have a valvePosition is inside the "groups" section, representing the different rooms. But here the value is always (null)

[unstressable]

maybe forgotten in that type? idk.

[Apollon77]

@lonestar2001 Hm ... "NORMALLY_CLOSED"? That more sounds like an electical alce that gets opened when power is on and closed when no power is there. In fact this do not have a real "valce position". In fact we can check which data are there. Set loglevel of adapter to silly. Then the adapter restarts. get the log from that restart from the logfile on disk at /opt/iobroker/log/... and send it to me as textfile via email to iobroker@fischer-ka.de with reference to this issue. Then please also tell the ID of the device (because not visible in your above screenshot). Then I check

[lonestar2001]

@Apollon77 email with silly information is out

I'm no expert reading the HMIP rest-api docu but maybe it's correct that the valvePosition is not with the device but with the group (=room). But why it is always (null) there?

https://homematicip-rest-api.readthedocs.io/en/latest/homematicip.base.html#homematicip.base.functionalChannels.HeatingThermostatChannel.valvePosition

[stale[bot]]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.

[timoglaess]

The "wall mount heating thermostat" does not give or need any valve poisition. It is the actor that is setting the valve motor! Valve position e.g for that "12 block floor heating actor" works just fine:

[lonestar2001]

@timoglaess, you have another setting and I'm glad that this is working for you I only have the WALL MOUNT HEATING THERMOSTAT that controls the valves which are NOT from Homematic. My theromstat is also the actor. However, the Homematic IP App knows whether the valve is open (arrow up) or closed (arrow down). I don't have this info in the objects yet.

[stale[bot]]

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 the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. 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üft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.