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

Zen30 re-interview triggered after Update Z-Wave JS 0.6.2 and Zen30 automations also broken after update #3670

Closed
ddfault opened this issue Jun 28, 2024 · 1 comment
Labels

Comments

@ddfault
Copy link

ddfault commented Jun 28, 2024

Describe the issue you are experiencing

I feel like the crux of the issue is zwave-js/node-zwave-js@233b983
In Home Assistant OS I have running on my Raspberry Pi 4. I've done a number of Z-Wave JS add-on updates over the last 6 months without issue up to 0.6.0, but this update triggered all my Zen30 devices to have "errors' and showed up in the section for repair. As my automations weren't working I chose re-interview on all the devices.

A Zooz Zen30 is a double switch where the top rocker is a led dimmer and the bottom switch is a relay. For a bathroom light and exhaust fan or a modern ceiling light and ceiling fan. The controls show up as 3 entries. Which made enough sense to me as there were two sides of the relay.
image
Triggering either side of the relay in HA would after a sec change the other side. When I setup the devices I renamed and change the type of the switch which added the "Change device type of switch" to each device I did this on. I originally thought that was the culprit, but I have other devices with this that aren't affected. Part of the change device type to switch hides the original devices and so I used the new one with names and icons for automations.
In v0.6.0, this is the relay/switch on
image
In v0.6.0, this is the Dimmer On
image

After the addon_core_zwave_js upgraded to 0.6.2 the devices show up as only two entries instead of three and my fancy icon and labeled switches now said

This entity is no longer being provided by the zwave_js integration. If the entity is no longer in use, delete it in settings.
image

So for this Garage Zen30 switch in this screenshot below, only the top two devices entries still work while the rest are unavailable. I don't remember if Basic (1) device was there before the update or not but it doesn't work. on either version, meh. On v0.6.2:
image

I started digging and this commit seems the most logical/timely source of the change/discrepancy between 0.6.0 and 0.6.2.
The working vs not working Entity IDs don't make much sense as this one is working
image
But this one is broken
image

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.6.2

Steps to reproduce the issue

  1. Add Zen30 devices on 0.6.0 or before or restore 0.6.0 working config.
  2. Rename and change type of device (I don't know if this is a requirement)
  3. Setup automations based on the new devices and add those to your dashboard and hide the others
  4. Update to 0.6.2, cry, and watch it all stop working

System Health information

This is empty of z-wave related stuff.

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

I thankfully did a backup before the 0.6.2 update and restored the 0.6.0 backup to get back up and going for now, but I don't know:

  • If this is a common occurrence with updates?
  • If I just have to start over again with stuff post 0.6.2?
  • In the future use the hidden items for automation which I believe is harder as they won't show up in searches?
  • Setup the automations with the original entries visible and then hide them after?

As I am using the add-on as part of Home Assistant OS, it seemed here was the right place for this report?

I'm happy to provide further information on either version if you can provide some guidance or direction.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 28, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant