HOPPE eHandle ConnectSense

[lieblinger]

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?
There's no output on node-zwave-js for the handle position state (open/close). It only publishes the state of the window sash (open/close).

What did you expect to happen instead?
According to the the manual it should expose the following:

Shouldn't be there a sensor for "Window handle in closed position (0x06 / 0x01)" and "Window handle in open position (0x06 / 0x02)" ?

Software versions

No response

Device information

Manufacturer: Hoppe
Model name: E0400Z-EF
Node ID: 016 and 063

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

log2.txt

[zwave-js-bot]

👋 Hey @lieblinger!

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

[AlCalzone]

0x06/0x01, 0x06/0x02 and 0x06/0x07 are notification events, not variables. By definition, events are stateless and only carry a meaning the instant they are received. They mean "manual lock operation", "manual unlock operation" and "manual not fully locked" respectively.

It seems that HOPPE have interpreted the Z-Wave specifications in an unfortunate way here, because there are actual states for handle open (0x06/0x18) and handle closed (0x06/0x19) in the specifications, which would do what you'd expect.