Z-Wave JS - wrong discovery of TZ65D

[BaconStivvy]

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

YES, BUT a Home Assistant developer has told me to come here

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• 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.

Describe the bug

What causes the bug?

when trying to add a device called TZ65D it is being detected as a TZ65S losing functionality of a dual switch
zwave_js-6ebd3030d04489d308a51b9fc7acf83a-Single Paddle Wall Dimmer-9ecff1430f42fe52337a47ce713956d7.txt.txt

it is a known issue already reported here https://github.com/home-assistant/core/issues/83283 and
here https://github.com/home-assistant/core/issues/101264#issuecomment-1750755317

Device information

Manufacturer: TKB Home
Model name: TZ-65D
Node ID in your network:

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version:
node-zwave-js branch:

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

No response

Attach Driver Logfile

zwave_js-6ebd3030d04489d308a51b9fc7acf83a-Single Paddle Wall Dimmer-9ecff1430f42fe52337a47ce713956d7.txt.txt

[zwave-js-bot]

👋 Hey @BaconStivvy!

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 make sure you upload the correct one.

[BaconStivvy]

zwave_js.log

[apella12]

As noted in the HA threads the device advertises itself with the TYPE:ID aligned with the single paddle model.

I'm new to ZwaveJS, do not have the device, and have never used HA, but maybe there is a manual way. I do see from the log that the device advertises 4 association groups. These are what the right-side paddle controls. At least in Zwave-js-ui you can go to the device and go the Groups menu. Are there four shown? If not try to ADD a group 2 (from root) and put some node that you want to control using the right-side paddle in it. Then on the Config section send a custom parameter (14 1 1) to activate group 2. See if that works. It is a longshot

[AlCalzone]

Looks like we have to expose the Basic Set "events" from the 2nd paddle like we did for the TZ66D.
The device won't show up as a dual channel switch though as it is not a multi channel device. The 2nd paddle can only be used to control and isn't able to be controlled.

[AlCalzone]

@BaconStivvy The next release should fix this, but you will still need to re-interview the device then and add the association group as @apella12 outlined.

[BaconStivvy]

that will be great thanks. i will wait for next release and let you know here :)

[BaconStivvy]

Hi, I confirm that secondary switch is being detected in logs after updated to latest and re included device.

Is group association possible in z-wave js? Still very green in yaml and have no idea what to do.

Or at least is it possible to add as an entity then I can configure second switch to control in automation? Any help would be much appreciated

[AlCalzone]

Association groups can only be managed in the Z-Wave JS UI addon, not the Z-Wave JS addon. You should have a "Basic event" entity or something like this now after re-interviewing. The Home Assistant Discord may be better to ask for help with this.

[BaconStivvy]

thanks for your help