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

Wrong Unit Type for getTempPartyM1 and similiar commands? #59

Open
DerLandv0gt opened this issue Jan 21, 2024 · 1 comment
Open

Wrong Unit Type for getTempPartyM1 and similiar commands? #59

DerLandv0gt opened this issue Jan 21, 2024 · 1 comment

Comments

@DerLandv0gt
Copy link

DerLandv0gt commented Jan 21, 2024

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".

@DerLandv0gt DerLandv0gt changed the title Wrong Unit Type for getTempPartyM1 and similiar commands Wrong Unit Type for getTempPartyM1 and similiar commands? Jan 22, 2024
@dk1305hb
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants