OK - followed a guide - installed a z-wave stick no problem. I had already installed Z-Wave JS but not set it up.
My Z-wave device appeared in integrations automatically. I ran it’s config and it claimed to also setup z-wave JS automatically. All seemed fine.
I opened z Wave JS “Configure” link and selected add a device, and I succesfully added a power outlet. It works perfectly. Added a card and tested it. Brilliant.
However, if I go into z-wave JS UI then there is nothing in there. I entered my USB port in the device and let it generate 4 keys by hitting the refresh buton next to each one.
I now get the error, " Driver: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)swap_horizontal_circle infohistory"
Going into the zwave JS integration works perfectly, i can add devices, and I can see a list of devices.
Just JS UI won’t work.
A google tells me there is a clash and that “Zwave 1.4” integration is interfering - thing is - I have no other zwave integrations or apps. Just Zwave JS and Z wave JS UI.
I have the “disable MQQT Gateway” option seletced as default btw - and I’ve left that alone until I get the UI working.
What should I be looking at.? Is the UI simply that? or are you supposed ot be able to add devices in there too?
Ahh scratch that - I’ve done more reading - seems Zwave UI is a replacement / alternative to z Wave JS from the same people - with a bit more detail. I’ve found a guide for switching over to UI.
I’ve decided that as Zwave JS is workign fine, to leave Zwave JS UI out of it for now - unless nayone has an argument why I should indeed switch over now (I’m in a test environment so no long list of devices to lose)
JsUI has many tools for managing your ZWave utilities you will find helpful. Especially the ability to back up and transfer yoir stick to another if it fails.
If you are starting fresh and are at the point you are I’d highly recommend it.
Cheers - I’m doign it now. Just stuck on reconfiguring z-wave JS integration.
I uncheck " Use the Z-Wave JS Supervisor add-on" as per the instructions but then it asks for the websocket url and defaults to ws://localhost:3000 which then fails to connect. Tried replacing localhost with the IP of my virtual machine with no luck
Thank you. All working now. About to start unjoining all my zwave devices from ST and move to HA! Got Alexa working following a superb guide on YT which was critical.
Been fun so far. Slightly confusing as all current YT tutorials for various bits in HA are based on a not-much-older version of HA and don’t allow for the fact all app configs in the Gui now split the scripts into three or four sections.