You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
In v0.6.0, this is the Dimmer On
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.
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:
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
But this one is broken
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
Add Zen30 devices on 0.6.0 or before or restore 0.6.0 working config.
Rename and change type of device (I don't know if this is a requirement)
Setup automations based on the new devices and add those to your dashboard and hide the others
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.
The text was updated successfully, but these errors were encountered:
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.
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](https://private-user-images.githubusercontent.com/7560310/344024815-72806ee9-7413-4043-a331-c13853410009.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyNDgxNS03MjgwNmVlOS03NDEzLTQwNDMtYTMzMS1jMTM4NTM0MTAwMDkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NTk2YTQ0ZTE4MjAwOTYxMjEzNDhiYmMzMjlhNDg0OWMwOGE0N2ExYzJkZGUxNDIzMjgzNDQ4ZWEzMjliNDA1MiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.64lBMr2oB-HDLFQNEEpxpKaf-pvQPrm8TaV1_lUmZLU)
![image](https://private-user-images.githubusercontent.com/7560310/344022781-c74a5d2c-35f9-464c-b0be-f4159d5110db.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyMjc4MS1jNzRhNWQyYy0zNWY5LTQ2NGMtYjBiZS1mNDE1OWQ1MTEwZGIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjkyZGJiNjg5ODdlODk1ZjFlY2FiNDFlYjhjYmJmYzJhNzZkOWM3OGYxNjQxZGQxYWNlYTk2NTc5NDI0NjY1NiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.yRwgABaP1U3EFAxjE3tA9jBzOjCJn6Yl3m6XK-LeO8I)
![image](https://private-user-images.githubusercontent.com/7560310/344023026-cd3250b3-471e-402c-b3e5-29ddc3f269e3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyMzAyNi1jZDMyNTBiMy00NzFlLTQwMmMtYjNlNS0yOWRkYzNmMjY5ZTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OWE1NGY0MWUzMGY2YWQ3OGY3YjY0OGRjYWE4ODZmYzJmNTBkOTI4NDNjZGVhYmQ1MTc2MzA5NzJiOTRjMTQ0MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.xIvPobVuAvyAxsULltniZmenhzoAR4iu1F4I8Pe1idA)
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
In v0.6.0, this is the Dimmer On
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
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](https://private-user-images.githubusercontent.com/7560310/344023871-3201ab31-ddf8-4c0d-bc77-8039aae1cd55.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyMzg3MS0zMjAxYWIzMS1kZGY4LTRjMGQtYmM3Ny04MDM5YWFlMWNkNTUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZjlhOTA3MTY1MWU5NTdkYzgyYmU0NzBjNWE1ZjA2ZDFiNTUzZGQyMDdiNTBlZjA3YzVjOTEzZTYyMjMxMjcwNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.y1YFPMnYi3TLhLzJTV1y9VzifYaLdRlE3paN7CWNRiM)
I started digging and this commit seems the most logical/timely source of the change/discrepancy between 0.6.0 and 0.6.2.
![image](https://private-user-images.githubusercontent.com/7560310/344026144-65613bb4-1ae4-43fd-a840-303661e06356.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyNjE0NC02NTYxM2JiNC0xYWU0LTQzZmQtYTg0MC0zMDM2NjFlMDYzNTYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTRkZmU2ZTA4YWY3MDM3YWUxZDg5MzU1OWY5M2Y4ODc5YzU1YmFiN2ZlZDYyODA3ZDIwZjA5NmUwYTNjYjAwMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.0jDSemSlcx-lGUg_OOKszJrQCZBAO2NNPwu_4Ar_QCk)
![image](https://private-user-images.githubusercontent.com/7560310/344026160-448d376a-598b-4445-9172-547acaee72a3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMDIyOTcsIm5iZiI6MTcyMzIwMTk5NywicGF0aCI6Ii83NTYwMzEwLzM0NDAyNjE2MC00NDhkMzc2YS01OThiLTQ0NDUtOTE3Mi01NDdhY2FlZTcyYTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDlUMTExMzE3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OWUxNzA1NDM1YmNmYTdiZTM1YTc5ZjBmY2ExZjE1MDgwZWFmOTIwYmQwMTkwYTcwZGMxODJlNzY5Njg4NGZiMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.hnsquZw2EXb1YRoovPogZCwUS_cI3_o09ZvEBrxKoFY)
The working vs not working Entity IDs don't make much sense as this one is working
But this one is broken
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
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:
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.
The text was updated successfully, but these errors were encountered: