Fibaro fgt001 / 0x010f reports additional battery level on endpoint 0

[kvaster]

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

Fibaro thermostat fgt001 have special section for reportion endpoint 0 as endpoint 1 for battery level. This is cause endpoint 0 and endpoint 1 are duplicated and endpoint 2 reports battery level for external sensor. With recent version endpoint 1 and endpoint 2 are shown during introduce and are working OK. Manual refresh also shows values OK. But when battery level is reported due to changes (withour request) - it is reported on endpoint 0 and is not remapped.

Also battery values found during introduce are shown as 'Battery v1'. And battery values reported on endpoint 0 are shown as 'Battert v0' in zwavejs-ui.

Software versions

Latest git as of this issue, but the problem was introduced since of September (approx).

Device information

Fibaro fgt001

zwave-1.tar.gz
zwave-2.tar.gz

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

No response

[zwave-js-bot]

👋 Hey @kvaster!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[AlCalzone]

Looks like we already have special handling in place for this device, which maps the battery to endpoint 1, but it still exposes the value on endpoint 0.

[AlCalzone]

This is now tracked in #6555