The temperature of the DS18B20 probes on FGK101 no longer rises

[OUARZA]

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

I use ZWaveJS through Jeedom.
Since version 8.25.1 of ZwaveJsUI the temperature of the DS18B20 probes of my FGK101 equipment no longer rises.

Software versions

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

Z-Wave JS UI:
zwave-js-ui: 8.26.0.08e6a7e
zwave-js: 11.14.3
home id: 3972900806
home hex: 0xeccda7c6

Home Assistant Z-Wave Integration: ...

Home Assistant Z-Wave JS Addon: JEEDOM

ioBroker.zwave2 Adapter: ...

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

Device information

"productLabel" : "FGK101",
"productDescription" : "Door Opening Sensor",
"manufacturer" : "Fibargroup",
"firmwareVersion" : "2.1",
NodeID : 35

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

zwave-js-ui-store.zip

node_35.json

nodes_dump.json

The screenshot in the help is no longer good.
https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

[AlCalzone]

There were no recent changes that would explain this, but in your dump the endpoint 2 where the sensor is exposed is missing. Please re-interview the device, make another driver log of that and upload it here again (just the current log).

[OUARZA]

@AlCalzone
Okay, I'll do that.
I have the problem with version 8.26.0
Is it possible to have the JSON file of version 8.22.0?
https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x010f/fgk101.json

[AlCalzone]

Not sure what's that supposed to accomplish. The last change was in v10.9 (Z-Wave JS UI 8.13.1) and that was meant to fix the missing sensor.

[OUARZA]

@AlCalzone Ok, I have the impression that the problem comes from this file, but not sure.
Is the log file you want after waking up the module? zwave-js-ui-store.zip

[AlCalzone]

Yes

[OUARZA]

@AlCalzone
I just did the manipulation and it works again!
I would like to point out that other people on the JEEDOM forum have the same problem as me.

[AlCalzone]

other people on the JEEDOM forum have the same problem

Do you know if re-interviewing actually does something for them?
As said before, I can't reproduce the issue with re-interview not starting in tests, but I also have no old enough device that behaves like this one that I could use to do a manual test.

[OUARZA]

I will ask them :)

[OUARZA]

Hello,
I'm sorry, the people with the problem didn't answer me :(

[Overbull]

Hello, I did a re-interviewing as @AlCalzone suggested on my 7 FGK101 and the temperature rises again on all of them, even a correct battery level.

Try to do from zwave-js control panel not from jeedom.