Everspring - EH403 - Cannot change default configuration

[s8109csa]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
I cannot change default configuration on Everspring EH403. I have 3 of them, same issue on all. There are 3 parameters and for me the important would be the auto report lux value. I wanted to change 0 to 3 and when I clicked somewhere else in the Home Assisstant, there was only an error message: Error happened. Other Z-Wave devices are working as expected.

What did you expect to happen instead?
Update parameters

Steps to reproduce the behavior:

1. Go to Devices -> Z-Wave -> Everspring EH403 -> Settings -> Edit parameter 3 -> click out from the cell.
2. See error

Anything else we should know?
The devices are securely connected to Aeotec USB Z-Stick 7 - again, I can edit other devices. FW is default, I don't think there was ever a firmware update on these flood lights.

Software versions

Driver (node-zwave-js): ...

Z-Wave JS UI: ...

Home Assistant Z-Wave Integration: ...

Home Assistant Z-Wave JS Addon: ...newest but it was always the case

ioBroker.zwave2 Adapter: ...

If you are using something non-standard, tell us here: ...

Device information

Manufacturer: EverSpring
Model name: EH-403
Node ID: 11

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

home-assistant_zwave_js_2024-05-08T15-09-55.901Z.log

[AlCalzone]

Any chance you have a manual for that device you can share?

[s8109csa]

EH403-Manual_A501112670R02-0423.pdf
Absolutely and thank you for your support in advance.
Luckily my issue is not huge as I am able to query the device every x minutes with an automation, so no big pain, but would be nice if this would work perfectly.

Peter

[AlCalzone]

Ok the parameter that is sent matches the manual, so it's likely another device with broken Supervision implementation. We'll have to disable the use of that CC for this device.

[AlCalzone]

Escalated to an issue: #6829