[question] Are dimmers still scaled down from 0..255 to 0..99 ?

[LordMike]

One of my pet peeves with z2m was that in some cases, it would scale the light values from a supplied 0..255 range to a 0..99 range. I was hoping this scaling wasn't present in zwavejs2mqtt, as it was a new project and it was possible to make breaking changes :)..

I'm seeing logs like this, so I guess it is. Is there a way to disable this scaling?

2021-01-20 22:16:08.328 INFO MQTT: Message received on zwavejs2mqtt/wallswitch_2/38/5/targetValue/set, '16'
2021-01-20 22:16:08.329 INFO ZWAVE: Writing 6 to 38-5-targetValue

[LordMike]

I actually may have my own answer.. Gateway.js scales multilevels in those ranges, but unlikc z2m, I can disable that code path by not having hass discovery..

https://github.com/zwave-js/zwavejs2mqtt/blob/3c6b99ec307f09924a962c4bdfc29d0509a95462/lib/Gateway.js#L705-L715

So I've disabled hass discovery.. :)

2021-01-20 22:25:08.331 INFO MQTT: Message received on zwavejs2mqtt/wallswitch_2/38/5/targetValue/set, '16'
2021-01-20 22:25:08.331 INFO ZWAVE: Writing 16 to 38-5-targetValue

[jcam]

With the fix-dimmers branch, this scaling will be removed entirely :)

[LordMike]

Fix dimmers branch?

Great if it disappears. You can indicate to HASS what the scale is, if needed, by the brightnes_scale setting. Setting this to 99, makes 99 be the maximum value.

[jcam]

Yes, we did that in the fix_dimmers branch which is now merged to master.

[jcam]

Unfortunately a side effect of switching from the template to the default schema (required to use brightness_scale), is that if brightness is not known, it will no longer send 255, which is the z-wave internal value that means turn back on to last brightness

[LordMike]

You can probably achieve that by reporting the payload_on value as 255 .. which in turn would mess with the on_command_type setting ... Hmm.