Innogy Binding OH 3 - Thermostat set Temperature does not work 2

Ursusprimus · February 25, 2021, 4:54pm

I just tried to install my innogy-temperature-thermostat in OH3 for the first time. OH gets the values correctly. But when I change the target-temperature in OH, the information is not handed down to the innogy/livisy app (and then not to the thermostat either, of course).
Someone else had the same problem and there it helped to change the items type from numer:temperature to just number. But in my case, neither works.

Values in OH:

And values in innogy/livisy:

Ursusprimus · February 26, 2021, 3:57pm

Here’s some information from the logfile. So far it seems to be ok (the bottom 3 lines, at least), but maybe it clarifies something:

2021-02-26 16:53:00.678 [ERROR] [d4j.internal.RRD4jPersistenceService] - Could not create rrd4j database file ‘/var/lib/openhab/persistence/rrd4j/HeizkorperSchlafzimmer_Luftfeuchtigkeit.rrd’: Invalid file header. File [/var/lib/openhab/persistence/rrd4j/HeizkorperSchlafzimmer_Luftfeuchtigkeit.rrd] is not a RRD4J RRD file

2021-02-26 16:53:23.317 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘HeizkorperSchlafzimme_Solltemperatur’ received command 19

2021-02-26 16:53:23.318 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘HeizkorperSchlafzimme_Solltemperatur’ predicted to become 19

2021-02-26 16:53:23.321 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘HeizkorperSchlafzimme_Solltemperatur’ changed from 16 to 19

Marijn_Oudijk · February 26, 2021, 5:30pm

What’s the status of your innogy binding? I experience sometimes an offline binding.

Ursusprimus · February 26, 2021, 6:00pm

I had some issues with the binding being offline, but at the moment it works fine.
Could be that I can only receive values from innogy/livisi but not send any. If so, maybe somewhere there’s just a little setting that needs to be changed. (I experienced a similar problem with node red that didn’t send values to Openhab until I changed one parameter; possibly it’s similar here, but I don’t know where to look / what to check)

Marijn_Oudijk · February 27, 2021, 9:00am

To debug (when I started long te ago) I grey a status ‘heartbeat’ in Innogy which toggled after x minutes in the innogy app. This way you can easily see if you are still connected. My problem was that my innogy hub lost connection so had nothing to do with OH itself

Ursusprimus · February 27, 2021, 9:18am

But that doesn’t seem to be my problem: OH receives values from innogy; e.g. in OH I see the current temperature and the target temperature too. It’s just that I can’t change the target temperature in OH (more precisely: I can change it in OH and but that doesn’t change the values in innogy/livisy and thus not on the thermostat)

der_micha · February 27, 2021, 10:22am

Change the item to Setpoint, this should work.

Ursusprimus · February 28, 2021, 7:47am

strangely, it suddenly started working without any changes. Must’ve been something with the binding again (happens to me with innogy from time to time). But to make sure, I’ll change to setpoint anyway.

config-old · February 21, 2023, 2:35pm

The problem is that the new livitsi binding takes no more Numer objects inside the

item.sendCommand(value as Number)

Now you need to use it like this, because the thingproperty only takes strings…

item.sendCommand((val as Number).toString + "°C")

Works fine for me.