Problem with a trigger in a scene (proposed unit not consistent)

[gaetanb76]

Hello,
I want to create scenes to choose my heating modes (Comfort, Eco, Off, Frost protection) with buttons on my Heating Dashboard.
I haven’t found how to create a selector.
The problem I’m encountering is in the screenshot below:

A unit is being offered for the Eco mode???
To show the error, I put next to it what I get if I choose Comfort.

[pierre-gilles]

Hi @gaetanb76, where does this device come from? Which integration in Gladys?

[gaetanb76]

Sorry for my delay
It’s a Z-Wave device

[pierre-gilles]

Does it come from the Gladys Z-WaveJS UI integration or did you create it in MQTT?

[gaetanb76]

In Z-WaveJS UI it’s a Multilevel Switch that goes from 0 to 99 %.
Depending on the chosen values,

the heating mode is defined.
For Eco I set 25 and for Comfort 75.
In MQTT I created switches. Eco and Comfort are identical

I can’t reproduce the problem:
The « Device state change » trigger no longer offers a value but On/Off buttons.

Could an update have changed something?

[pierre-gilles]

Hi @gaetanb76, I understand better.

In the MQTT integration, you’re the one who created the devices manually.
What you see in the scenes is only the result of what you configured.

If you saw hectopascal before, it’s because you had created a feature that used hectopascal as its unit.

Now, you’ve created a switch, which is shown as an On/Off in the scenes — everything is normal

Now it’s up to you to decide what you want to do, and to choose the right feature for what you’re looking for.

[gaetanb76]

Oh well, I must have glitched that day…\nYou can delete this message