Hi all
Thank you again for all the responses. Took the advice and setup the machine with ProxMox along and have setup HA.
To be fair, I was expecting it to be a learning curve but so far, all up and running BUT…
Despite the setup taking under an hour in total… I’ve been stuck with the z-wave setup.
As per @mterry63 recommendation, I’m trying to setup the whole z-wave UI thing. First of all, the github URL just would not work stating it was already installed.
I ended up finding a thread to simply use http and not https and sure enough, that worked allowing me to find and setup z-wave UI.
As far as I know this is working - I can see the new z-wave stick and it correctly reports back the firmware version.
This is where I’m stuck - I then went into integrations, added Z-wave ensuring the supervisor checkbox was unchecked. It asks for a URL so I stick in ws://a0d7b954-zwavejs2mqtt:3000 and I’m getting failed to connnect.
I’ve reinstalled the z-wave UI, tried a different port, but always seem to get the same Failed to connect.
Have I missed something obvious and critical here?
I have two locations, each with a development and a production installations. I chose to run my VB headless under server Ubuntu linux which frees up a lot of system resources. I purchased refurbished PC for the hardware. I allocate 2 or 4 GB to the VMs. My problems with this set up have been operator error.
I did have a challenge with getting the USB connected to the VM in that the /dev/ttyUSBx would change numbers (x) depending on the the number of USB devices plugged into the box at boot. This was resolved by using the alternate name for the USB device as opposed to /dev/USBx. (I wish I could give a link, but it seemed to happen automatically when I set up the VM.)
My reason for being with HA is that it is not cloud based. This allows me to be somewhat in control of my security and privacy … I’ve been burned badly once by one cloud company and dodged the bullet by another.
The cummunity is genrally good, and, as you can see, helpful.
Yup - thats the document that I followed and spent a good amount of time going through it again and again to ensure I did.
I’ve been out most of the day so only got a chance to see your response but back on it now - Decided despite it being against every developer fibre in me, to ditch the VM and start again taking it a bit slower this time.
I was all good with it but now slightly more confused with the second link you sent.
The first and all others online state the serial port should be set to /dev/ttyUSB0
But your second link states NOT use use this one and instead, use the /dev/serial/by-id one:
Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
ok success! all up and running with Z-wave.
Untested any further than having the Z-stick 7 added with the Z-Wave JS UI add-on + Z-wave Integration as I need to start excluding devices from the old stick and including them on the new.
I guess I’ll never find out the cause of why I could not progress yesterday or what if anything was different today. But the “fix” seemed to be a complete rebuild of the HA OS VM in Proxmox.
FYI. I went with /dev/serial/by-id/X serial device which I realised was the one I went to yesterday too looking at my setup screenshots.
Going to bring over a few devices tomorrow and hopefully this is the beginning of my learning curve/experience and long-term use of HA!
Brilliant thank you - I too have gone for the /dev/serial/by-id/X serial device - Did not figure out the issue last night but today it is all good following a complete start again from scratch method (not ideal as I ‘need’ to know what broke it but there you go)
The cookbook looks great - will keep it to very close hand.,
Sounds like we’ve had similar experiences with cloud-based systems. One of the main reasons I stuck it out with Homeseer for so long but the most glaringly obvious thing to me was how active the HA community is (as it shows here!)