If you woken all the devices up, simply try to reboot.
My confusion is they aren’t battery powered. Should they need to be awoke?
I just pressed the paddle on one and saw something in the logs about it, but it’s still unavailable.
I’ll try the reboot
How do I prevent the currently stopped deprecated zwave from coming back on at boot?
No, you just need to wait until the network has started. For me, with about 58 devices, it takes 10 minutes. Overtime it should fill in information properly. I did notice, on my first time swapping, I had to wait until the network was fully initialized before adding the integration.
Remove it from configuration.
Welp, the darn thing about that, is now I don’t know what node is what because I can’t reference the deprecated names, having removed the previous integration.
There’s still a list of unresolved Node devices that are unavailable.
Is there a log file somewhere, the Log in the UI is very limited.
I’m a little late to teh game and tried to read (most) of the messages in this thread. Based on the release announcement, Z-Wave JS is the horse to back.
However, I’m totally confused at what the migration path is. Sounds like there is none. The devices are stored on the stick but we have to setup all our naming again.
This seems super painful to me, so wondering if someone can suggest the best practice in how to approach this so we don’t have conflicts in naming etc.
So as I am just about done with this renaming process this is what I did.
2 Monitors with an HA instance on each side.
Left has old Right has new
Go device by device and on the old device at the end of the entity name I add _old to it and then I copy and paste the device name over to the new hottness minus the _old part
Just want to say thanks to @petro and all of the great community here. Always willing to help. In addition, stunning to get this much work done as quickly as it was turned out.
and the integration is now released 
whats great is it runs nicely side by side with zwavejs2mqtt that i already had installed (i am not using the add-on)
this is why i like running zwavejs2mqtt docker container on a separate dedicated raspberry pi (i get why others won’t want to do that too).
yes if you setup MQTT integration you would see changes, that screen shot is for the MQTT path not the new zwavejs integration. You can run side by side if you want during testing but you probably only want to use one path. for example here is the same device - once with the MQTT path and once with the new integration (i am testing which i like)
Oh wait. To do a migration you did an entire new HA setup? How do you handle the restoring of your non zwave stuff into the new instance without also restoring the zwave too?
Now I’m even more confused. When I used the new zwavejs integration in Home Assistant I point HA to the zwavejs containers exposed websocket port. All of my devices appear to come from the Z-Wave JS integration.
No I didn’t do a whole new setup. I was using OZW so I had that config open on one screen and then the zwavejs on the other and then I just did it NodeID by NodeID all the way down the list. Since in ZwaveJS they show up as NodeXX I just started at the top of the OZW looked at what it said its NodeID was and then went back to the zwavejs found that nodeid there and did my thing.
I moved 85 devices today doing it that way.
Thats where they should be coming from.
Oh I see now. I was initially confused because you said “HA instance” but that just meant two browser Windows pointing at same HA instance.
After you do the migration did you have to reset anything else up? Or does the naming process you did allow everything else to remain intact?
Anyone getting the same error when using cover.open or cover.close?
Logger: homeassistant.components.websocket_api.http.connection
Source: components/zwave_js/cover.py:83
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:03:37 (1 occurrences)
Last logged: 09:03:37
[139845074968880] None
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 136, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1455, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1490, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 595, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 632, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/zwave_js/cover.py", line 83, in async_open_cover
await self.info.node.async_set_value(target_value, PRESS_BUTTON)
File "/usr/local/lib/python3.8/site-packages/zwave_js_server/model/node.py", line 248, in async_set_value
val = self.values[val]
KeyError: None
Calling set_position works.
I’m using the zwavejs2mqtt addon and Fibaro Roller Shutter 3
Also I cant change the temperature of my thermostat (Eurotronic Spirit Z-Wave Plus) although its reading every value correctly. But there’s no error in the log. It just doesnt do anything.
How do I determine what my USB device path is for my zwave stick? I’m running HA in a VM.
Thanks! it ended up being /dev/ttyACM0. However, when i use it and my zwave key, I"m getting “failed to connect”. I’ve tried to re-add the integration but automatically get “failed to connect” message again with no opp to change the USB path or zwave key.
how do i reset everything so I can try configuring again?