Glad to hear you found this useful As for Z-Wave JS to MQTT it depends on what you're trying to achieve This came out before the official Z-Wave JS add-on and reading the author's notes they now suggest using the official add-on, unless you want added features such as checking the state of your Z-Wave network But if you want to get more heavily involved with devices using MQTT then that add-on is certainly the way to go At the moment I only use MQTT for presence detection systems, so for now I'm sticking with the official add-on

@@TechTutorialsDavidMcKone Thanks

Thanks for the feedback Good to know the video was helpful

Good to hear the video was helpful

Thanks for the feedback and glad to hear you found this useful I have used the alternative mqtt option but I stopped using it as this one seemed enough for me But I'll put this zwave2mqtt one on my to do list

Thanks for the feedback and good to know the video was helpful

Do you mean the Z-Wave server configuration? If so then you need to click restart in it's Add-On page If you mean a Z-Wave device then you change it's parameters in Home Assistant but then you need to wait When it wakes up it will check in and update itself How long that will be varies and battery operated devices can wait several hours Devices usually let you wake them up but it can drain a lot of battery power

@@TechTutorialsDavidMcKone Thanks. Its for a non battery Z Wave device

@@timmark4190 In that case it wouldn't matter if you wake it up If you're not familiar with the process, I've found most devices have a button you need to double-click Otherwise check the manual if you don't already know

Unfortunately I don't really see me doing anything further for Z-Wave Each video takes several days to shoot let alone edit so I have to be quite selective I installed zwavejs2mqtt in my early HA days as I wanted to compare it to Z-Wave JS But I have to say it didn't bring any benefit, or at least none that I could see I tried it again at a later date and although the developer was then only suggesting it as an alternate control panel for the official Z-Wave JS, I did the full install again but soon reverted back to Z-Wave JS Z-Wave JS has a pretty simple install process and it's an official add-on which I prefer I've been using it for a long time and aside from the occasional hiccup when updates come around, it mostly works fine A lot of my devices are still Z-Wave ones and adding and removing them has been about as much I've needed to do The motion sensors needed their parameters changing but that was easily done But in the grand scheme of things I think Z-Wave has had its time Fewer companies are selling these devices and even some of the ones I bought not long ago are no longer available So I'm moving with the industry and will phase Z-Wave out when devices need replacing

@@TechTutorialsDavidMcKone David, all good info ! Was not aware of the Z-Wave environment. What is the industry moving to?

@@daviddonnelly8406 At the moment Zigbee is still available but Wi-Fi is becoming more popular. Bluetooth is also available but sooner or later Matter has to take off. Shame really as I do like Z-Wave

@@TechTutorialsDavidMcKone Many thanks David - as always, a source of knowledge!😀👍

The GUI has been updated since this video was released You now need to go to Settings | System | Hardware In the top right corner, click the drop down menu option and select All Hardware

Not sure why you're not getting a QR code I've just checked my Z-Wave JS installation and it still offers an option for the device I want to add to scan the QR code Home Assistant is offering I can only suggest checking on the forum

Ok thank you

Assuming the LED still flashes when it detects motion then it probably still works If it's no longer active in Home Assistant then try unpairing it then re-pairing it As a last resort you can delete it then re-pair it It might need renaming to fit back into the rules though

@@TechTutorialsDavidMcKone Some confusion here - my bad. The one motion sensor I have connected is not Node 7. I have no idea what Node 7 is. It has been there since I installed Z-WaveJS. So - part of the original install (?). The Aeotec Z-Wave Gen 5 stick is flashing. When Node 7 "died" then the 1 automation for a motion sensor (using Zigbee2MQTT) to turn on one light (Z-Wave Node 24) stopped working. I can turn the light on/off from the HA dashboard. I verified the Zigbee2MQTT is seeing motion. But the light will not come on or go off via the one automation I set up using a blueprint (motion). It worked all last night and again today until about 6 hours ago. Then Node 7 "died" and the automation will not work. Restarted Z-Wave JS, Zibee2MQTT, and MQTT broker and rebooted the Odroid N2+. I even disconnected the Aeotec Z-Wave Gen 5 stick and reinserted it. This did not fix anything. Am I sensing a remove/uninstall Z-Wave JS, reinstall concept? Is the uninstall that simple?

When you first install Z-Wave JS you shouldn't see any devices other than the Z-Stick It's possible node 7 might be something the Z-Stick itself learned some time ago as it stores devices it pairs with And it could potentially impact other nodes as Z-Wave builds a mesh Although have you installed ZWave2MQTT at any point as that would interfere with Z-Wave JS? You'll need to find out more about this Node 7 unfortunately The device details should at least tell you what type of device it is It seems a coincidence although you can check the logs to see why the rule failed; Settings | System | Logs The ones on the Z-Wave JS add-on page might also help As an aside, I prefer to use Node-RED for setting up rules as it makes things easier to set up and troubleshoot problems like this

@@TechTutorialsDavidMcKone Funny thing happened on the way to the store… After reading your reply and ....thinking......the one motion automation started working. uh? Why? Apparent solution: I removed Node 7. I had restarted Z-Wave JS, Zigbee2MQTT, and rebooted the Odroid N2+. Then it dawned on me - I did not restart the MQTT broker. So I restarted the add-ons in the following sequence: Z-Wave JS, then MQTT broker, and then Zibee2MQTT. I waited a bit… Whamo! The automation started working. General lesson learned, you have to restart all three to make sure they are sync’d up. Problem solved? I think so.😄

@@daviddonnelly8406 Good to hear it's fixed

I don't really see any benefit beyond running this as a VM The container option adds unnecessary security risks and I want to stick to the recommended guidelines of isolating smart home devices from the rest of your network The supervised method has so far proven to be impractical but I might revisit it as I want to use remote USB devices But I think it's beyond the scope of a home network to be running an individual z-wave js server so I don't see me ever touching the core method

@@TechTutorialsDavidMcKone Imho there is need for tutorials without using supervised, since there seems to be none around .. Attleast simple ones. I just installed z-wave js on container version, after googling around few days..

Well there are several videos that show how to do it using add-ons so there is a need for this method And if you're saying there are none for how to do it the way you have then why not post your own video? There may be others who would find it very useful