I just built a new system and had to refresh myself on how to get Z-wave up and running. I'd love to see a remake of this video. I wish Zwave in Home Assisitant wasn't so balkanized. It would be nice to have just one, native Zwave component.
Super helpful, Chris! I was struggling with getting ZW JS UI integrated. A few things have changed since you recorded this video with HA updates but the content was clear enough to help me get it working. Thank you for your detailed videos. They are a great help.
Thank you so much for doing this video! I've been waiting about a year now for you to do it. I spent many hours trying to get this setup after the regular ZwaveJS was already installed. I'm just starting over now, but setup was a breeze with your video!
Thanks so much! I had installed/uninstalled ZwaveJS2mqtt multiple times following various instructions I could find, couldn't get it to work. Works now! Nowhere else did I see the port 3000 setup.
Thanks for this video. I was finally able to get a bunch of Z-Wave stuff fully operational that I had bought ages ago and only half-integrated with HA.
You just helped me figure out how to get my new iHeat Z-TRM3 floor thermostats to work in Home Assistant! I could not get them to work with the regular Z-Wave integration. Thanks!
Helpful video!! Thanks. Have 2 sites with extensive Zwave devices. Have been using samsung smartthings. Pros: Cloud control of devices Cons: lack of control logic. I selected HA specifically because I wanted to use Node Red for advanced logic operation. Smartthings >7 yrs. HA w/Zwave < 3 days. up and running already. Just switch from the Pi4 Mod 2 to my HA yellow (had to wait a while to get a CM4). Using Aeotec Zstick 7. did FW update before starting. Everyone that says Silicon Labs and Simplicity Studio sucks is understating it!
Good Morning Chris! Thanks for the great content as always. I watched this video around the time when it came out and found it to be very helpfu. Fast forward, my HA files were corrupted and long story short, I needed to start from scratch with my system. I upgraded to the new Zooz 800 stick and started the process. Here is the issue I am having...the devices are loading fine into Z-Wave JS UI (i believe this is the predecessor to the Z-Wave JS MQTT). I am naming all of my devices when saving them, but when I go to try and set up my automations none of the names I set up in Z-Wave JS UI are appearing. With over 90 devices in the house (30 of them being switches and dimmers), they all have the same name in automations. I am having to go back to JS Z-Wave add-on and rename the devices. Not sure if this is making sense or if this is a problem others have had. Any comments is greatly appreciated.
Thank you! I'm in the process of migrating all my non-security z-wave devices off of ring alarm to HA for the first time and your videos have been a great resource! My only question is what is the preferred method to include a device? is it through the z-wave JS integration or through the z-wave JS UI (formerly JS to MQTT UI) add-on web UI? And if there is a difference between the two methods, what are the benefits or drawbacks of the two methods?
Thanks for this video. I am using Z-Wave JS UI but it exposes the nodes just as you show right around 17:15. At that point in the video you are using the UI to set values in the node. Many of these values are not exposed as entities. I want to find these values (and later change them) for use, in my dashboard for example. How can I get these values? My use case is a schlage z-wave lock. So far my reading suggests I will need to use a service (z-wave.js) to get these values. Is that your understanding? Do you have any videos on using a service? TIA
I have a Z-wave 700 Plus USB stick running on Home Assistant on a Synology NAS. I can successfully pre-register devices with QR code. The best method I've found is to use Camera app (Lens) to identify the 52 digit number, copy that to Keep phone app, then copy from Keep browser to the app Z-Wave JS UI. When it is time to go to inclusion I do not have the 'Actions' button you have located next to Controller Statistics.
Zwave is very nice. I have 62 devices and they mesh and talk well together with some very surprising consistency. I do like how the parameters can be changed and customized way more then ZigBee. Another thing that is nice is you can set static connections (groups) to other devices for even more local out of hub control. Too bad they are insanely more expensive! It almost seems many of these manufacturers are preparing for Thread. Any guesses on if zwave will die out? Not sure if I want to sink more into the ZW echo system if matter+thread takes off.
I don't think z-wave is going anywhere soon. There are too many manufacturers stlil using it and Matter keeps getting delayed. Nabu Casa hired the developer of zwave JS so as long as we support Home Assistant and its efforts and as long as this platform continues to grow, we will have a strong voice in what infrastructures are supported and maintained.
Has the name changed? I'm seeing "Z-Wave JS UI, Fully configurable Z-Wave JS gateway and control panel". It has the same emblem/graphic and shows up under community addons. Google seems to think it's the same.
What’s the difference or advantage to using MQTT versus WS (web socket)? My understanding is they are both communication mediums between Z-Wave JS and HA, RIGHT?
This is total speculation. I think MQTT is a way of talking to numerous systems, not just HA. And the ws server is a streamlined way to get entities to show up in HA without even installing or dealing with an MQTT broker? Before there was a Zwave integration, maybe MQTT addon was the only way to get Zwave2MQTT to talk to HA so they leave it in there for legacy installations? If someone can set me straight, I would love an official answer!
Hi All I'm new to Home Assistant and have been struggling to set up the Smartthings integration for the last few hours. (Many hours!) I've discovered that the url in the Home Assistant Cloud (Nabu Casa) does not match the url I'm presented with when I try to configure the Smartthings Integration in 'Integrations'. Is this the issue and if so how do I correct it? Many thanks.
I have mostly 90% of my z-wave devices moved into Z-Wave JS (Ver 0.1.74) and off SmartThings. I now have a problem in trying to “associate” a master light switch (Eaton RF 9640-N) to an Accessory Switch (Eaton RF9642-Z) - seems Z-Wave JS will not do this. After much research, “I think” Z-Wave JS UI add-on might be the solution. Two questions: can I do the “association in Z-Wave JS UI for the Eaton switches” or better to stay in Z-Wave JS? My 2nd question: Is it really that easy to move from Z-Wave JS to Z-Wave JS UI as shown here: Z-Wave - Home Assistant. As you can see - very much a newbie here. All help is appreciated.
If I already have Z-wave JS configured with 20 devices and want to start using Z-wave JS to MQTT, what would be the proper steps to retain devices? Z-wave to MQTT won't allow usage of my Z-Wave stick because it's busy (obviously, with the Z-wave JS). Thanks for another great tutorial! *** UPDATE *** Upgrade from Z-wave JS went well. Only had to add 4-5 stubborn old devices.
@@dennisclark6548 Install the zwavejs2mqtt add-on through Supervisor, but don’t start it yet. Open the UI for the Z-Wave JS integration, click “Reconfigure Server”, uncheck the box for “Use the Z-Wave JS Supervisor add-on”, then submit it. Leave the web socket URL alone. Open the Z-Wave JS add-on through Supervisor Uncheck any boxes that will automatically restart it (watchdog/start-on-boot). Go to “Configuration”, and make a note of the service device ID and network key. Stop the add-on Open the zwavejs2mqtt add-on through Supervisor Start it Open the “Web UI” link which takes you to a page called “Control Panel” In its hamburger menu, choose “Settings” Under Z-Wave settings, copy in the serial port and network key details from before, and save. Check the control panel dashboard which should start listing your devices. Back in the zwavejs2mqtt add-on page, check the logs to ensure that things have started up ok. If you see any messages about failing to lock the USB device, double check that the old add-on isn’t running. If it keeps restarting, go back and check the integration setting. Assuming that everything seems ok, go back to the Z-Wave JS integration, click Reconfigure Server again, leave “Use the Z-Wave JS Supervisor add-on” unchecked, but change the websocket URL to “ws://a0d7b954-zwavejs2mqtt:3000”
Hey Gene. Glad you got it working. It is trivial to move over to js2mqtt, other than waking up battery devices, etc. You might also have to rename some things--or it used to be that way but I think now HA picks up the names from the names in js2mqtt.
@@mostlychris Yes Chris, but it has been reported that JS kept starting up and taking over the dongle, resulting in ZW2MQTT not reading any devices or even the Z-wave controller. Thanks for a great video and for the inspiration to revisit this process (failed couple of months ago). Glad I did.
at the 5 min mark, when we select the zwave device, generate keys & save... that's when i get this error, i've logged it but i don't know what to do from here... Logger: homeassistant.components.zwave_js.config_flow Source: components/zwave_js/config_flow.py:387 Integration: zwave_js (documentation, issues) First occurred: 2:53:47 PM (1 occurrences) Last logged: 2:53:47 PM Failed to get the Z-Wave JS add-on info: Addon is not installed
Do you have the z-wave add-on installed? There are two pieces...the add-on and the integration. You need to either use the default zwave in Home Assistant or the zwavejs2mqtt add-on.
Very helpful, thanks. I got this going one installation. On a different installation, I'm using port 3000 for DoubleTake facial recognition. Consequently, I get errors that port 3000 is already in use. Any suggestions for alternate port settings?
@@mostlychris I changed the port from the add-on configuration (roughly 2:21 in the video) to 3007, within Z-wave JS UI in Settings > Home Assistant > Server Port (not seen in video), and when adding the Z-wave JS integration (roughly 6:42 in the video). However, I am getting a "Failed to connect" error message when trying to add the integration. I also tried a suggestion seen in the comments of replacing "localhost" with "a0d7b954_zwavejs2mqtt" taken from the end of the URL. Neither has worked. Any suggestions on how to proceed?
I had trouble getting Zwave JS to connect to port 3000 using the pre-populated ws://localhost:3000. I went back to the zwave2mqtt addon info page and there it stated "hostname a0d7b954-zwavejs2mqtt". I went back the Zwave JS, pasted that hostname into the box, added ws:// to the beginning and :3000 to the end, making it ws://a0d7b954-zwavejs2mqtt:3000 and it connected right away. Not sure if that number is always the same, but both instances of HA I am running gave that same hostname. Next I need to add a device and see if it works...
@@stuartpittwood5469 Glad it helped you out! It seems like I always run into weird problems like this. I'll beat my head against the wall for hours and most times get nowhere.
If I'm already using ZwaveJS, can I add the zwavejs2mqtt add on without having to re-do everything? Edit: I'm getting an "failed to connect" message when I'm adding the integration using ww://localhost:3000 or the url in the documentation
You might have to do some renaming. For the connection issue, make sure the add-on is running and you have configured the port to be used in the add-on config.
I just built a new system and had to refresh myself on how to get Z-wave up and running. I'd love to see a remake of this video. I wish Zwave in Home Assisitant wasn't so balkanized. It would be nice to have just one, native Zwave component.
Super helpful, Chris! I was struggling with getting ZW JS UI integrated. A few things have changed since you recorded this video with HA updates but the content was clear enough to help me get it working. Thank you for your detailed videos. They are a great help.
Thank you so much for doing this video! I've been waiting about a year now for you to do it. I spent many hours trying to get this setup after the regular ZwaveJS was already installed. I'm just starting over now, but setup was a breeze with your video!
That's a long wait! I never realized I could be a blocker to projects, lol. Thanks for watching!
Thanks so much! I had installed/uninstalled ZwaveJS2mqtt multiple times following various instructions I could find, couldn't get it to work. Works now! Nowhere else did I see the port 3000 setup.
Excellent! Glad you got it working!
Thanks for this video. I was finally able to get a bunch of Z-Wave stuff fully operational that I had bought ages ago and only half-integrated with HA.
Excellent!
Thx for doing this. I just started rebuilding my old HA instance and zwave network. Perfect timing!
Excellent! It was definitely time for a refresh showing the new UI.
You just helped me figure out how to get my new iHeat Z-TRM3 floor thermostats to work in Home Assistant! I could not get them to work with the regular Z-Wave integration. Thanks!
Glad I could help!
I believe the Z-wave JS integration now comes up as just "Z-wave".
Helpful video!! Thanks. Have 2 sites with extensive Zwave devices. Have been using samsung smartthings. Pros: Cloud control of devices Cons: lack of control logic. I selected HA specifically because I wanted to use Node Red for advanced logic operation. Smartthings >7 yrs. HA w/Zwave < 3 days. up and running already. Just switch from the Pi4 Mod 2 to my HA yellow (had to wait a while to get a CM4). Using Aeotec Zstick 7. did FW update before starting. Everyone that says Silicon Labs and Simplicity Studio sucks is understating it!
Congrats on moving over the HA!
Good Morning Chris! Thanks for the great content as always. I watched this video around the time when it came out and found it to be very helpfu. Fast forward, my HA files were corrupted and long story short, I needed to start from scratch with my system. I upgraded to the new Zooz 800 stick and started the process. Here is the issue I am having...the devices are loading fine into Z-Wave JS UI (i believe this is the predecessor to the Z-Wave JS MQTT). I am naming all of my devices when saving them, but when I go to try and set up my automations none of the names I set up in Z-Wave JS UI are appearing. With over 90 devices in the house (30 of them being switches and dimmers), they all have the same name in automations. I am having to go back to JS Z-Wave add-on and rename the devices. Not sure if this is making sense or if this is a problem others have had. Any comments is greatly appreciated.
Thank you! I'm in the process of migrating all my non-security z-wave devices off of ring alarm to HA for the first time and your videos have been a great resource! My only question is what is the preferred method to include a device? is it through the z-wave JS integration or through the z-wave JS UI (formerly JS to MQTT UI) add-on web UI? And if there is a difference between the two methods, what are the benefits or drawbacks of the two methods?
Thanks for this video. I am using Z-Wave JS UI but it exposes the nodes just as you show right around 17:15. At that point in the video you are using the UI to set values in the node. Many of these values are not exposed as entities. I want to find these values (and later change them) for use, in my dashboard for example. How can I get these values? My use case is a schlage z-wave lock. So far my reading suggests I will need to use a service (z-wave.js) to get these values. Is that your understanding? Do you have any videos on using a service? TIA
I have a Z-wave 700 Plus USB stick running on Home Assistant on a Synology NAS. I can successfully pre-register devices with QR code. The best method I've found is to use Camera app (Lens) to identify the 52 digit number, copy that to Keep phone app, then copy from Keep browser to the app Z-Wave JS UI.
When it is time to go to inclusion I do not have the 'Actions' button you have located next to Controller Statistics.
Nevermind, must have been a UI change between this video and now. The + button reveals 'Manage Nodes' and that is the path to Inclusion.
Zwave is very nice. I have 62 devices and they mesh and talk well together with some very surprising consistency. I do like how the parameters can be changed and customized way more then ZigBee. Another thing that is nice is you can set static connections (groups) to other devices for even more local out of hub control. Too bad they are insanely more expensive! It almost seems many of these manufacturers are preparing for Thread. Any guesses on if zwave will die out? Not sure if I want to sink more into the ZW echo system if matter+thread takes off.
I don't think z-wave is going anywhere soon. There are too many manufacturers stlil using it and Matter keeps getting delayed. Nabu Casa hired the developer of zwave JS so as long as we support Home Assistant and its efforts and as long as this platform continues to grow, we will have a strong voice in what infrastructures are supported and maintained.
Has the name changed? I'm seeing
"Z-Wave JS UI, Fully configurable Z-Wave JS gateway and control panel". It has the same emblem/graphic and shows up under community addons. Google seems to think it's the same.
I have a problem when adding Z-Wave to Home Assistant, it disables Zigbee on MQTT.
What’s the difference or advantage to using MQTT versus WS (web socket)? My understanding is they are both communication mediums between Z-Wave JS and HA, RIGHT?
This is total speculation. I think MQTT is a way of talking to numerous systems, not just HA. And the ws server is a streamlined way to get entities to show up in HA without even installing or dealing with an MQTT broker? Before there was a Zwave integration, maybe MQTT addon was the only way to get Zwave2MQTT to talk to HA so they leave it in there for legacy installations? If someone can set me straight, I would love an official answer!
Hi All
I'm new to Home Assistant and have been struggling to set up the Smartthings integration for the last few hours. (Many hours!) I've discovered that the url in the Home Assistant Cloud (Nabu Casa) does not match the url I'm presented with when I try to configure the Smartthings Integration in 'Integrations'. Is this the issue and if so how do I correct it?
Many thanks.
I have mostly 90% of my z-wave devices moved into Z-Wave JS (Ver 0.1.74) and off SmartThings. I now have a problem in trying to “associate” a master light switch (Eaton RF 9640-N) to an Accessory Switch (Eaton RF9642-Z) - seems Z-Wave JS will not do this. After much research, “I think” Z-Wave JS UI add-on might be the solution. Two questions: can I do the “association in Z-Wave JS UI for the Eaton switches” or better to stay in Z-Wave JS? My 2nd question: Is it really that easy to move from Z-Wave JS to Z-Wave JS UI as shown here: Z-Wave - Home Assistant. As you can see - very much a newbie here. All help is appreciated.
Auto provisioning does't really work with wireless sensors.
If I already have Z-wave JS configured with 20 devices and want to start using Z-wave JS to MQTT, what would be the proper steps to retain devices? Z-wave to MQTT won't allow usage of my Z-Wave stick because it's busy (obviously, with the Z-wave JS). Thanks for another great tutorial!
*** UPDATE ***
Upgrade from Z-wave JS went well. Only had to add 4-5 stubborn old devices.
So what steps did you use to make the switch?
@@dennisclark6548 Install the zwavejs2mqtt add-on through Supervisor, but don’t start it yet.
Open the UI for the Z-Wave JS integration, click “Reconfigure Server”, uncheck the box for “Use the Z-Wave JS Supervisor add-on”, then submit it. Leave the web socket URL alone.
Open the Z-Wave JS add-on through Supervisor
Uncheck any boxes that will automatically restart it (watchdog/start-on-boot).
Go to “Configuration”, and make a note of the service device ID and network key.
Stop the add-on
Open the zwavejs2mqtt add-on through Supervisor
Start it
Open the “Web UI” link which takes you to a page called “Control Panel”
In its hamburger menu, choose “Settings”
Under Z-Wave settings, copy in the serial port and network key details from before, and save.
Check the control panel dashboard which should start listing your devices.
Back in the zwavejs2mqtt add-on page, check the logs to ensure that things have started up ok. If you see any messages about failing to lock the USB device, double check that the old add-on isn’t running. If it keeps restarting, go back and check the integration setting.
Assuming that everything seems ok, go back to the Z-Wave JS integration, click Reconfigure Server again, leave “Use the Z-Wave JS Supervisor add-on” unchecked, but change the websocket URL to “ws://a0d7b954-zwavejs2mqtt:3000”
@@genelevi1 Had a few old devices (battery) that needed a refresh, other than that all seems to have moved over just fine. Thanks.
Hey Gene. Glad you got it working. It is trivial to move over to js2mqtt, other than waking up battery devices, etc. You might also have to rename some things--or it used to be that way but I think now HA picks up the names from the names in js2mqtt.
@@mostlychris Yes Chris, but it has been reported that JS kept starting up and taking over the dongle, resulting in ZW2MQTT not reading any devices or even the Z-wave controller. Thanks for a great video and for the inspiration to revisit this process (failed couple of months ago). Glad I did.
at the 5 min mark, when we select the zwave device, generate keys & save... that's when i get this error, i've logged it but i don't know what to do from here...
Logger: homeassistant.components.zwave_js.config_flow
Source: components/zwave_js/config_flow.py:387
Integration: zwave_js (documentation, issues)
First occurred: 2:53:47 PM (1 occurrences)
Last logged: 2:53:47 PM
Failed to get the Z-Wave JS add-on info: Addon is not installed
Do you have the z-wave add-on installed? There are two pieces...the add-on and the integration. You need to either use the default zwave in Home Assistant or the zwavejs2mqtt add-on.
Very helpful, thanks. I got this going one installation. On a different installation, I'm using port 3000 for DoubleTake facial recognition. Consequently, I get errors that port 3000 is already in use. Any suggestions for alternate port settings?
You can change the port in zwavejs2mqtt under the settings. I had to move my port.
@@mostlychris I changed the port from the add-on configuration (roughly 2:21 in the video) to 3007, within Z-wave JS UI in Settings > Home Assistant > Server Port (not seen in video), and when adding the Z-wave JS integration (roughly 6:42 in the video). However, I am getting a "Failed to connect" error message when trying to add the integration. I also tried a suggestion seen in the comments of replacing "localhost" with "a0d7b954_zwavejs2mqtt" taken from the end of the URL. Neither has worked. Any suggestions on how to proceed?
Can I use this if I'm already using zwave js?
You would need to convert to js2mqtt.
I keep getting a driver error
Can you be more specific. Better yet, jump over to Discord so you can post code/screenshots.
I had trouble getting Zwave JS to connect to port 3000 using the pre-populated ws://localhost:3000. I went back to the zwave2mqtt addon info page and there it stated "hostname a0d7b954-zwavejs2mqtt". I went back the Zwave JS, pasted that hostname into the box, added ws:// to the beginning and :3000 to the end, making it ws://a0d7b954-zwavejs2mqtt:3000 and it connected right away. Not sure if that number is always the same, but both instances of HA I am running gave that same hostname. Next I need to add a device and see if it works...
Thanks for this, worked like a charm for me.
Incidentally, the hostname on my instances is exactly the same as yours.
@@stuartpittwood5469 Glad it helped you out! It seems like I always run into weird problems like this. I'll beat my head against the wall for hours and most times get nowhere.
If I'm already using ZwaveJS, can I add the zwavejs2mqtt add on without having to re-do everything?
Edit: I'm getting an "failed to connect" message when I'm adding the integration using ww://localhost:3000 or the url in the documentation
You might have to do some renaming. For the connection issue, make sure the add-on is running and you have configured the port to be used in the add-on config.