You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a V200KW1 i cant read or write the "party temperature". I think this problem is based on a wrong Unit of "getTempPartyM1" in vito.xml. The Unit is ST (Status) instead of UTI (Temperatur 1Byte ganzzahlig) .
More commands that relates to this problem are: "setTempPartyM1", "getTempPartyM2" and "setTempPartyM2".
The text was updated successfully, but these errors were encountered:
DerLandv0gt
changed the title
Wrong Unit Type for getTempPartyM1 and similiar commands
Wrong Unit Type for getTempPartyM1 and similiar commands?
Jan 22, 2024
I think the fastest way is to try out with your own instance of vcontrol, connected by IP in the add-on configuration. I never test this params with my 20CB, because this values are once set and never touched in the last 10 years (same for TempWWSoll). As you I am pretty sure it must be UTI.
Maybe the add-on owner can integrate the newest version / xml files from openv in future.
On a V200KW1 i cant read or write the "party temperature". I think this problem is based on a wrong Unit of "getTempPartyM1" in vito.xml. The Unit is ST (Status) instead of UTI (Temperatur 1Byte ganzzahlig) .
More commands that relates to this problem are: "setTempPartyM1", "getTempPartyM2" and "setTempPartyM2".
The text was updated successfully, but these errors were encountered: