Issue with the underline Z-Wave Driver - Nice / Fibaro IBT4ZWAVE Device

[jameswardzala]

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?

The device has stopped functioning in the last 4 weeks, i presume due to an update

What did you expect to happen instead?

cant open or close the gates any longer with this device

Steps to reproduce the behavior:

1. Go to '...'
   z-ui_2023-11-21.log

2. Click on '...'

3. Scroll down to '...'

4. See error

z-ui_2023-11-21.log
z-ui_2023-11-21.log

Anything else we should know?

There is a new driver available i see but not for home assistant implementation

Software versions

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

Z-Wave JS UI: ... 3.0.2

Home Assistant Z-Wave Integration: ... 3.02

Home Assistant Z-Wave JS Addon: ... 9.3.1

ioBroker.zwave2 Adapter: ...

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

Device information

Manufacturer: ... Figaro
Model name: ... IBT4ZWAVE
Node ID: ...008

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

z-ui_2023-11-21.log

[zwave-js-bot]

👋 Hey @jameswardzala!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

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

[jameswardzala]

zwave-js-ui-store.zip
nodes.json
node_8.json

please see attached logs as requested.

[AlCalzone]

After trying to control the device, it sends back an Application Status report, which is not understood by Z-Wave JS, but typically means "can't do that". Other than that, the log does not contain any info as to why this doesn't work. The commands to the device are received and understood, but not executed.

Maybe the motor is jammed?

[jameswardzala]

Good Morning [A screenshot of a computer Description automatically generated] The device keep coming up as unknown after I select 'open' for example I don't seem to get anything in the log now apart from : 2023-11-23 10:42:57.349 INFO Z-WAVE: [Node 008] Value updated: 38-0-targetValue null => 99 2023-11-23 10:42:57.351 INFO Z-WAVE: [Node 008] Value updated: 38-0-currentValue null => 99 2023-11-23 10:43:02.392 INFO Z-WAVE: [Node 008] Value updated: 38-0-targetValue 99 => null 2023-11-23 10:43:02.394 INFO Z-WAVE: [Node 008] Value updated: 38-0-duration unknown => unknown 2023-11-23 10:43:02.396 INFO Z-WAVE: [Node 008] Value updated: 38-0-currentValue 99 => null The motor is fine it opens and closes on the fob. Any idea where I can go with this ? could it be down to the driver update ? as it stopped a couple of weeks ago ? I see there is a new driver v9.3.2 but I cant see any way of updating this from home assistant ? Thanks James. From: AlCalzone ***@***.***> Sent: Thursday, November 23, 2023 9:41 AM To: zwave-js/node-zwave-js ***@***.***> Cc: James Wardzala ***@***.***>; Comment ***@***.***> Subject: Re: [zwave-js/node-zwave-js] Issue with the underline Z-Wave Driver - Nice / Fibaro IBT4ZWAVE Device (Discussion #6511) After trying to control the device, it sends back an Application Status report, which is not understood by Z-Wave JS, but typically means "can't do that". Other than that, the log does not contain any info as to why this doesn't work. The commands to the device are received and understood, but not executed. Maybe the motor is jammed? - Reply to this email directly, view it on GitHub<#6511 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEB5UT5M5AUTKEUR7E4FTV3YF4K2ZAVCNFSM6AAAAAA7WNHA2WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMNJQGEZDG>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[AlCalzone]

You cannot reply to this discussion via e-mail if you want to attach files or include images. You have to do it via the Web UI.

[AlCalzone]

Anyways, I don't see how this can be related to Z-Wave JS updates. The commands are standardized and can't be changed nilly-willy. What changed is how the device reacts to them. I'm not sure if the remote is also using Z-Wave commands?

You could try excluding, factory-reset and including it again.