Z-Wave JS and Zwave units

Configuration Z-Wave
1

Hello,
after migrating to Z-Wave JS 2 mqtt i have a couple questions.
When using Heatit Z-trm3 in climate card in lovelace the temperature of the air temp is showing in center, even when i choose F-floorsensor.
This temp is not relevant if having the unit outside the room in the hallway, when it control the floor heat in the bathroom.
Any way to change this?

Another thing that happend with zwave is that no units have the “zwave.” entity anymore.
So now i cant control things with my key-chain remote control as scenes with scene-id.
How do i overcome this?

Best regards Ed

2

Release 2021.5 (in beta now) adds support for detecting the temperature sensor used by the Z-TRM3.

Please read the docs, scene functionality is well described. You need to use the zwave_js_value_notification event now.

3

Hello @freshcoast,

Now with 2021.05, my Z-TRM3 still uses the incorrect sensor as input temp to the climate component

image

Is there anything I have to configure to get the compoenent to use the floor sensor?

4

Sorry, the above is the Z-TRM2fx. My Z-TRM3’s works fine. Does anyone know about a fix for the Z-TRM2fx?

5
6

Thanks. Looks like neither of these made it to 2021.05:

Looking forward to 2021.06 to get this resolved

7

Hi and thanks for reply,
I really dont understand what to do with this to get it work.
I have been searching and tried out different examples for many hours without any luck.
Should it be so hard to do? I cannot se the entity in the developer any more either, just the battery state and %.
Would really appreciate any kind of example of how to trigger an automation based on a scene from my battery-powered remotes.
Here is the data i read from listening to events:

event_type": “zwave_js_value_notification”,
data: {
domain: “zwave_js”,
node_id: 33,
home_id: 2574732845,
endpoint: 0,
device_id: “c51024c2b2c6b0fc04343305ef5783f8”,
command_class: 91,
command_class_name: “Central Scene”,
label: “Scene 001”,
property: “scene”,
property_name: “scene”,
property_key: “001”,
property_key_name: “001”,
value: 0,
value_raw: 0

The last thing that worked before migrating to zvawe_js was this:

trigger:

  • event_data:
    entity_id: zwave.heatit_scene_controller
    scene_id: 1
    event_type: zwave.scene_activated
    platform: event