TA2k
Strange info log entry when changing slope and shift
I change shift values to prolong the compressor runtime.
When the value is changed (manually or per script) and the compressor is still running, there's a message in the protocol with level "info" every poll time (for me every two minutes): State value to set for "viessmannapi.0.xxx.0.features.heating.power.consumption.summary.heating.properties.currentYear.value" has to be type "string" but received type "number"
The described value "currentYear" is not (and can't be) changed by myself, this may be a Viessmann issue.
To Reproduce
Enter manually new values for the heating curve at point
viessmannapi.0.xxx.0.features.heating.circuits.0.heating.curve.commands.setCurve.setValue
e.g. {"slope":0.5,"shift":1}
while the compressor is active and have a look at the protocol.
Expected behavior
Values should be accepted (what works without problem) without a log entry.
Versions:
- Adapter version: 2.3.0
- JS-Controller version: 5.0.19
- Node version: 18.20.2
- Operating system: Debian 12
- Heat pump type 250-A (E3), latest firmware 2323
I already did this. It's created again, and the messages start with the next change and compressor running. I'm pretty sure it's a bug on Viessmann, but I wanted to ask if you can see what's coming (String or Number). At the moment the value for current year is 494.40000000000003.
It is Type Number and I think it should be Number - compare with lastMonth. It's not rounded, that's the difference I see. CurrentYear is the only entry with that error.
ok this is in issue on viessmann side please create a thread in their forum or write an email currentYear is a number but returns a value with more digits than a numbers allow in this will parsed as string
Great, thanks for investigating! https://community.viessmann.de/t5/Feedback-API/Bug-in-API-quot-currentYear-value-quot-has-to-be-type-quot/td-p/442741
[Hmmm, there seems to be a slight change (I don't know if someone tries to fix this...): No more unrounded numbers, but still the message (even with compressor off). The problem is now (or was also before), that the type should be number (what it is for the property "type", see screenshot two weeks ago), but in the property "value" it's string: ... Is this still a Viessmann problem? Then I'll write in their forum again.]
May be I wrote nonsense. After deleting the state and restarting the error is like described before. Still no fix or comment in the Viessmann developer forum.