External integration - ZwaveJS

Development
41

Update deployed.

42

Hi,

Without further explanation, I just migrated two devices.

This removed them from my heating scenes.

Nothing works anymore.

They seem to still be there, but when you edit, it’s empty.

Screenshot 2026-11-07 at 15-10-05 Gladys Assistant
Screenshot 2026-11-07 at 15-10-05 Gladys Assistant1221×237 16.7 KB

Screenshot 2026-11-07 at 15-10-17 Gladys Assistant
Screenshot 2026-11-07 at 15-10-17 Gladys Assistant1193×345 18.3 KB

43

The issue I’m facing is that there’s no way to migrate the Variateur function, yet it’s the only one I use.

  • Variateur = 0 → Stop
  • Variateur = 15 → Frost protection
  • Variateur = 25 → Eco
  • Variateur = 75 → Comfort

Screenshot before migration:

Screenshot 2026-11-07 at 15-27-56 Gladys Assistant
Screenshot 2026-11-07 at 15-27-56 Gladys Assistant1208×143 12.7 KB

Intégration externe - ZwaveJS - #27 by gaetanb76

44

I redid 10 scenes an hour ago. I still have plenty left, but I haven’t migrated the other devices.

I just noticed that version 1.9.0 is available.

I started the update.

The devices now only have 2 features: 22-49-0-Air temperature and 22-38-0-currentValue

My 10 scenes are screwed up
 No more heating on the ground floor.

45

Hello,

This is what version 1.9.0 brings: real native support for the pilot wire. This didn’t exist before. Pilot wires were treated as variators without any logic or intelligence.

If this can make your life easier on the scenes (it can make complete sense) @gaetanb76, I can make sure the variator view is always available. What I mean is that after 1.9.0, the granular choice of setting a value between 0 and 100 disappeared in favor of something aligned with zWave expectations (the table you provide). I can make both coexist, even though the logic of ease of use suggests using the turnkey mode (Off, Away, Eco, Comfort 1, Comfort 2, Comfort).

Let me know,

46

I would leave both options available.
The dimmer still in place so no change for those who already have scenes with it and the wired mode which is simpler and therefore taken into account in the Thermostat integration.

47

Hi,

You do as you please.

I think the solution with the pilot wire and operating modes is the most logical.

If we keep both versions, it might be too much and users might wonder why we kept both.

However, for those who already use Z-Wave for heating, they will have to recreate all the scenes, which will take them time.

You confirm, Eco = Comfort -3.5°C?
On my Atlantic 020887 ambient thermostats, Eco = Comfort -2°C.
I set 25% and they switch to Eco. I think this won’t change.

thermostat_salon
thermostat_salon157×185 4.51 KB

48

It’s not the zWave integration that manages the temperature difference. It just guides the mode in which the device should position itself (Off, frost protection, eco, comfort1, comfort2, comfort). It’s the device itself that applies its logic afterwards. So if for your device Eco = Comfort -2° that’s what it will be, I suppose.

49

Yes I confirm. And on my radiators I can set the Eco temperature as I want there are no established rules with the sending of the Eco command