No no,
Did not make the xml. used the custom file from stiansoevik.
I forgot to tell you that you need to associate the different groups manually to the controller under zwave setup. Then the temperature measurement works. Now the external temp seems ok, which is the one that I’m using, but the internal temp does not update.
Not sure that I will bother updating my other thermostats as the only gain is getting several temp readings, perhaps nice having floor and air temp. Reporting state heating/idle is achieved with older firmware anyways, reporting of decimals are nice though, but not really that big of deal.
If the z-dim is already supported by openzwave you can simply git clone the updated files and change the config directory in hass. If you want to make your own, I would go with the same process instead of changing the zwcfg*.xml, cant help you with how to make the file though…
I’m working on the same. I’ve updated a Heatit/Multireg til FW 1.92 and do get the Relay as a switch entity. But it’s not updating it’s status automatically.
In Zwave JS UI/Zwave2mqtt I created this under Settings → General (Remember to hit save at the bottom) and the Relay status is now updating.
I’m trying to add the same setting under Zwave JS UI/Zwave2mqtt as you have, but I cannot find “Current value (37-1-currentValue)” in my dropdown list - only “Current Value…” for the 4 Endpoints and various other alternatives.
What is the Endpoint/Group setup I should use for these thermostats?
Could wrong Endpoint/Group setup be the reason for not seeing the correct value in the dropdown list?
I have not added the xml file mentioned in the old posts in this thread - do I need to?
Turns out you can do the same thing with firmware 1.8. This is how I did it.
You need to change device_id: in the automation and change how many Watts the heater is under state: in template sensor.
# FW 1.8
# Bad start
input_boolean:
termostat_bad:
name: Termostat Bad
icon: mdi:toggle-switch-variant
# Automation to turn on/off helper when Basic: 255/0 received
automation:
- id: 'e7334376c0824758b2b45d0084d10000'
alias: 'Termostat bad on - Relay status'
description: "Turns on helper when thermostat kicks in"
trigger:
- platform: device
device_id: 64b1856cf1457b45f46e137ea5efb523
domain: zwave_js
type: zwave_js.value_updated.value
command_class: 32
property: currentValue
to: "255"
condition: []
action:
- service: input_boolean.turn_on
data: {}
target:
entity_id: input_boolean.termostat_bad
mode: single
- id: 'de1e1920da69458cab56db2bb73ebc19'
alias: 'Termostat bad off - Relay status'
description: "Turns off helper when thermostat kicks in"
trigger:
- platform: device
device_id: 64b1856cf1457b45f46e137ea5efb523
domain: zwave_js
type: zwave_js.value_updated.value
command_class: 32
property: currentValue
to: "0"
condition: []
action:
- service: input_boolean.turn_off
data: {}
target:
entity_id: input_boolean.termostat_bad
mode: single
template:
- sensor:
- name: 'Termostat Bad Electric Consumption [W]'
unique_id: '1d6b39d3b0794d7a84bf39326abf0c67'
unit_of_measurement: "W"
device_class: power
state: >
{% if is_state('input_boolean.termostat_bad', 'off') %}
{{0|float}}
{% elif is_state('input_boolean.termostat_bad', 'on') %}
{{500|float}}
{% else %}
{{0|float}}
{% endif %}
sensor:
- platform: integration
unique_id: '0501d1fb0ad84f61bb6791b24a0146cc'
source: sensor.termostat_bad_electric_consumption_w
name: 'Termostat Bad Electric Consumption [kWh]'
unit_prefix: k
round: 2
method: left
### Bad end
I cant even get the zwave_js.value_updated to trigger… when reading the docs it says that it should be “enabled on a per device and per entity domain basis”
But it doesn’t say how that should be done… any idea?
I’ve been waiting for this! But how does this work? I’ve tried re-interviewing a few of these thermostats and now I have this:
a basic light entity no longer available
a basic number entity which is unavailable
a basic sensor entity which is always 99.0
should the basic sensor entity update when it’s heating?
Yes, they should.
Mine change between 0, 99 and 255 where 255 is on and 0 and 99 is off.
You need to group the on/off control to gateway if you have not allready done so:
