Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jasco 14318 relay switch not detected as Z-Wave Plus #3436

Closed
3 tasks done
nmpu opened this issue Nov 25, 2023 · 3 comments
Closed
3 tasks done

Jasco 14318 relay switch not detected as Z-Wave Plus #3436

nmpu opened this issue Nov 25, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@nmpu
Copy link

nmpu commented Nov 25, 2023

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

9.3.2

ZwaveJS version

12.3.0

Describe the bug

Back of switch has the Z-Wave Plus logo, but Z-Wave JS UI displays with a red minus in the Z-Wave+ column. This poses no immediate functional problem, but I suspect it may affect advanced configuration (e.g. double-tap).

To Reproduce

I removed a new Jasco 14318-3 (FW v5.24) from a sealed package and used "Inclusion" to add to an AEON Labs ZW090 (FW v1.2). The Z-Wave+ column in Z-Wave JS UI shows a red minus.

Expected behavior

I expect the Z-Wave+ column in Z-Wave JS UI to show a green 1.

Additional context

I have tried restarting as well as "Re-interview Node". I have multiple 14318 devices with identical behavior.

@nmpu nmpu added the bug Something isn't working label Nov 25, 2023
@kpine
Copy link
Contributor

kpine commented Nov 25, 2023

Looks like Plus support has been disabled intentionally. According to this issue, the device just doesn't work properly otherwise:

This poses no immediate functional problem, but I suspect it may affect advanced configuration (e.g. double-tap).

It should not affect double taps. The double tap configuration is enabled by 1) auto-associating group 3 to the controller and 2) enabling basic events via a compat flag. This device's config has neither of those settings.

Here's an example of a device file that enables double taps: 14294

You could try adding the association groups and treatBasicSetAsEvent compat flag for this device to a custom device config file and see if that solves the missing double-tap support. If that works, contributing the config updates to node-zwave-js would be appreciated.

Adding a comment to the config regarding the removal of Plus support would also probably be a good idea.

@nmpu
Copy link
Author

nmpu commented Nov 25, 2023

Sorry I missed that history. What's the easiest way to edit the config? I'm running Home Assistant as a VM under ESXi. I have "Advanced SSH & Web Terminal" installed. It's not clear where the Z-Wave config files are hiding.

It may be less hassle to just move the 14318's to locations where I don't need automations based on double-tap events. The direct association for the double-tap group works as expected.

@kpine
Copy link
Contributor

kpine commented Nov 25, 2023

Use the Store Explorer to upload the file. https://zwave-js.github.io/zwave-js-ui/#/screenshots?id=store-explorer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants