[SOLVED] Eurotronic Spirit Z-Wave Plus & external temperatures

I think the same thing is going here @dinuk - the external temperature is being overwritten by the actual temperature reading. This seems to happen every time the temperature is being refreshed or is getting a new value, no matter what triggered that. It should be fixed when the external temperature-channel becomes read only.

This issue has been fixed.
sensor_report channel should be write only #1054
I did a short test and it worked as expected (openHAB 2.4.0~20181108202519-1 (Build #1417)).

Fantastic! I’ll just have to update openhab now, right?

You are using the snapshot version, right? Then an update should be enough.
Otherwise: ZWave binding updates

It works as well for me now - thanks for your help guys!

I carefully studied this threat - unfortunately it is not working yet. What I did:

  • I am running the latest snapshot release
  • configuration settings of “Measured temperature offset” was changed to 128 / “External temperature sensor will be used for regulation”
  • I created a rule that updates the external temperature of the valve on every change of the external sensor. I can see that both values are synced correctly. Nevertheless the value has two decimal places and I am not sure if this causes the troubles.
  • I run a test this night - both rooms had target temperature of 18°C - in the morning I had one room with 21°C and one with 16°C

Did I miss something?

I think the device has a very bad PID controller algorythm implemented.

I see a fully open value even if the room is hotter the target temperature.

popp radiator controller looks more better. Read somewhere here.

Thanks for the update. That’s a pitty - but helpful information so I don’t spend more time with it.

I also use the Eurotronic Spirit with external temperatures. In principle everything works, however, when I monitor the valve positions I get the impression that the Eurotronic Spirit only uses the integer values of the external temperature.
For example, when I set the target temperature to 21 °C it only starts to react once the temperature goes above 22°C.
Here is example data (target temperature 21°C):


In the logs however it looks to me like the temperature is send with two decimal places:

12:24:05.443 [INFO ] [smarthome.event.ItemStateChangedEvent] - temperature_out changed from 22.49 to 22.38
12:24:05.468 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'SensorReport' received command 22.38
12:24:05.476 [INFO ] [arthome.event.ItemStatePredictedEvent] - SensorReport predicted to become 22.38
12:24:05.484 [INFO ] [smarthome.event.ItemStateChangedEvent] - SensorReport changed from 22.49 to 22.38
12:24:05.484 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Command received zwave:device:d9fe0ed9:node2:sensor_report --> 22.38 [DecimalType]
12:24:05.493 [DEBUG] [ass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Creating new message for command SENSOR_MULTILEVEL_REPORT, Set TEMPERATURE to 22.38 with scale 0
12:24:05.498 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
12:24:05.504 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_SENSOR_MULTILEVEL is NOT required to be secured
12:24:05.509 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Bump transaction 15236 priority from Set to Immediate
12:24:05.513 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue
12:24:05.519 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Added 15236 to queue - size 1
12:24:05.525 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
12:24:05.532 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 02 06 31 05 01 42 08 BE 25 25 24
12:24:05.539 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0D 00 13 02 06 31 05 01 42 08 BE 25 25 24
12:24:05.544 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - Message SENT
12:24:05.547 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

Does anyone observe a similar behavior?

1 Like

@TobiasLemke I am not so far with my SPIRIT to judge its efficiency yet.
It is very interesting observation. This could also explain lower price of the Thermostat on the market in reference to others.

However in this thread I got an answer on how to use external temp. sensor.
I understood. if the External Temp is being provided. SPIRIT does not require any rule to steer the vale and keep the temp in the room.
Correct me if I am wrong, please.

@TobiasLemke to be frank I don’t have any monitoring set up to graph the valve positions; if true, however, that’d be a bit of an issue. Do you think it could have something to do with “Measured Temperature report”?

@wiewior the thermostat doesn’t need any rule to steer the valve in the first place if you give it target temperatures. Am I misunderstanding you?

This is exact my understanding. No additional rules required to trigger or correct the valve.

@wiewior @Flynxify I just checked, somehow I don’t have the problem I described above anymore. I didn’t change anything in my setup so maybe it was fixed in some update of openHAB.

1 Like

Yes I see the same issue. Have you been able to change the scale to 2 yet?