hassio-addons / addon-zwave2mqtt

Z-Wave to MQTT - Home Assistant Community Add-ons
https://addons.community
MIT License
57 stars 27 forks source link

Thermofloor Heatit Z-TRM3 wrong sensor showing #98

Closed espen4001 closed 3 years ago

espen4001 commented 3 years ago

Problem/Motivation

Using ZWave to MQTT in docker container alongside HomeAssistant in another container. When adding my Thermofloor Heatit Z-TRM3 thermostate to ZWave, it shows up in Home Assistant as expected. This thermostate har multiple sensor modes:

image

And based on the selected mode, one of 3 multilevel sensors are used to control the temperature based on setpoint:

image

Sensor 2-49-2 is the internal sensor. Sensor 2-49-3 is depends on an external connected sensor, which I don't have, hence the value "0" from this sensor. Sensor 2-49-4 is the connected floor sensor.

But regardless of which "Sensor mode" the thermostate is set to, the measured temperature value in the climate-entity in HomeAssistant is shown from sensor 2-49-2, which is the internal sensor.

I have selected sensor mode "F", Floor mode, which uses the floor sensor. Everthing works fine - my setpoint is 31,5 ºC, and the thermostates regulates to this and using the floor sensor. But the shown value in Home Asisstant is wrong.

image

Expected behavior

Shown value in Home Assistant to change based on selected sensor mode.

Actual behavior

Sensor 2-49-2 is shown, regardless of selected mode.

Steps to reproduce

I have 2 identical units, both with the same issue.

Proposed changes

I recently changed from using the OpenZwave(Beta) integration in Home Assistant and the Ozwdaemon to manage the zwave network. With this setup, the values were shown as expected. Changing sensor mode also changed which value was shown in frontend.

frenck commented 3 years ago

Hi there @espen4001!

Thanks for the extensive report! However, there is unfortunately not much I can do with it.

Add-ons wrap existing software, in this case zwave2mqtt. Therefore the application itself is not maintained by us.

Please report your issue upstream (copy this issue, as the detail is great!)

Sorry I don't have more satisfying answer for you.

../Frenck