Migrating from Vera Plus to Home Assistant (or other?)
-
So how do I run a virtual machine? Gotta back up a bit for me!
-
Thanks to everyone for your input! It'll be a couple of days before I can get deep into this because I have very limited time these days to dabble.
-
This post is deleted!
-
Late posting, just saw this thread.
Welcome to abused Vera users club. I switched almost 2 years ago now and never looked back. When Vera Plus came out, it had such protentional and a loyal user base with great developers. I was running Vera Plus for I think 8 or 9 years, and had been experiencing deteriorating support from both Vera/Ezlo itself, as well as broken plugins that I constantly had to try to work around. When I switched, I had been monitoring the evolution of Ezlo, but it never seemed ready for prime time for me.
If you used Reactor on Vera, MSR is your answer. You can migrate your existing rules from Reactor on Vera to MSR easily.
Others have mentioned you can use Vera as a Z-wave radio. This is true, however, it's only capable of so much. If you want to use newer devices, Vera just can't take full advantage. I'm running my Home Assistant setup on a Rpi 4 with a Aeotec Zwave stick, and 80 Z-wave devices on the network, with hardly an issue. 75% of the devices are 700 series or newer with support for S2 encryption (won't get that on Vera Plus). I run MSR on my Fedora NAS server, and they work well together.
I'm constantly amazed at the possible integrations that I couldn't even dream about on Vera Plus.
-
Finally dug the NUC out of the garage. Getting ready to do with this. I'll post more ?? soon I suppose.
-
So I got to here but am going to set it aside for now.
How do I add a Z-Wave Adaptor? I currently have a HomeSEER Smart Stick Model SA370-2 Z-Wave Plus USB Dongle I'd like to use unless I need to get something else?
-
@CatmanV2 said in Migrating from Vera Plus to Home Assistant (or other?):
@sammy2 Feel free to message me direct and we can go to some kind of more interactive communications. I used Virtualbox (although I was on Mac) with the defaults and it took me about 10 minutes
C
I'm probably at the point to need some remote assistance in completing the installation.. I'll be available Friday morning around 5am PDT.
-
Hiya. Just updating my HA box which seems to be taking a long time!
Are you on Whatsapp or similar?
C
-
WhatsApp is on my phone. Sorry I didn't catch your response earlier.
I've got it up and running but am having issues with the USB Driver loading the USB Serial Port in Z-Wave JS. Here's the log:
[06:45:50] INFO: Successfully send discovery information to Home Assistant. 2024-08-16T13:45:52.981Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗ ███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2024-08-16T13:45:52.994Z DRIVER version 12.11.2 2024-08-16T13:45:52.997Z DRIVER Logging to file: /config/zwave_2024-08-16.log 2024-08-16T13:46:02.088Z DRIVER Failed to open the serial port: Error: I/O error setting custom baud rate of 1 15200 Unable to start driver ZWaveError: Failed to open the serial port: Error: I/O error setting custom baud rate of 115200 (ZW0100) at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1336:9) at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1171:5) { code: 100, context: undefined, transactionSource: undefined } [13:46:02] WARNING: Halt add-on s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/config.sh [09:33:32] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok. [09:33:41] INFO: Soft-reset set to automatic [09:33:41] INFO: Virtual Machine detected, disabling soft-reset cont-init: info: /etc/cont-init.d/config.sh exited 0 cont-init: info: running /etc/cont-init.d/structure.sh cont-init: info: /etc/cont-init.d/structure.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun zwave_js (no readiness notification) s6-rc: info: service legacy-services successfully started [09:33:57] INFO: Successfully send discovery information to Home Assistant. 2024-08-16T16:34:05.537Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗ ███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2024-08-16T16:34:05.555Z DRIVER version 12.11.2 2024-08-16T16:34:05.559Z DRIVER Logging to file: /config/zwave_2024-08-16.log 2024-08-16T16:34:14.741Z DRIVER Failed to open the serial port: Error: I/O error setting custom baud rate of 1 15200 Unable to start driver ZWaveError: Failed to open the serial port: Error: I/O error setting custom baud rate of 115200 (ZW0100) at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1336:9) at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1171:5) { code: 100, context: undefined, transactionSource: undefined } [16:34:15] WARNING: Halt add-on s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/config.sh [09:34:50] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok. [09:34:56] INFO: Soft-reset set to automatic [09:34:56] INFO: Virtual Machine detected, disabling soft-reset cont-init: info: /etc/cont-init.d/config.sh exited 0 cont-init: info: running /etc/cont-init.d/structure.sh cont-init: info: /etc/cont-init.d/structure.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun zwave_js (no readiness notification) s6-rc: info: service legacy-services successfully started [09:35:05] INFO: Successfully send discovery information to Home Assistant. 2024-08-16T16:35:09.664Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗ ███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2024-08-16T16:35:09.676Z DRIVER version 12.11.2 2024-08-16T16:35:09.678Z DRIVER Logging to file: /config/zwave_2024-08-16.logI'm wondering if I need to reset the dongle in HomeSEER first before attempting to use it with HA?
Here's some additional screen grabs which may be of interest:
Then after some additional trying I got this when adding a Z-Wave Device:
Unfortunately, I'm in a remote session and cannot continue to attempt to pair the device.
-
Additional logging that came up after the poste above:
Z-Wave API version: 9 (legacy) Z-Wave chip type: EFR32ZG14 / ZGM130S node type Controller controller role: primary controller is the SIS: true controller supports timers: false Z-Wave Classic nodes: 1 2024-08-16T16:52:35.072Z CNTRLR querying version info... 2024-08-16T16:52:35.116Z CNTRLR received version info: controller type: Bridge Controller library version: Z-Wave 7.17 2024-08-16T16:52:35.122Z CNTRLR querying protocol version info... 2024-08-16T16:52:35.259Z CNTRLR received protocol version info: protocol type: Z-Wave protocol version: 7.17.1 appl. framework build no.: 344 git commit hash: 30303030303030303030303030303030 2024-08-16T16:52:35.267Z CNTRLR querying controller capabilities... 2024-08-16T16:52:35.315Z CNTRLR received controller capabilities: controller role: primary is the SUC: true started this network: true SIS is present: true was real primary: true 2024-08-16T16:52:35.317Z CNTRLR querying serial API setup capabilities... 2024-08-16T16:52:35.342Z CNTRLR supported serial API setup commands: · GetSupportedCommands · SetTxStatusReport · SetLongRangeMaximumTxPower · SetPowerlevel · GetLongRangeMaximumTxPower · GetPowerlevel · GetMaximumPayloadSize · GetLongRangeMaximumPayloadSize · GetRFRegion · SetRFRegion · SetNodeIDType 2024-08-16T16:52:35.343Z CNTRLR querying max. payload size... 2024-08-16T16:52:35.372Z CNTRLR maximum payload size: 46 bytes 2024-08-16T16:52:35.374Z CNTRLR supported Z-Wave features: · SmartStart 2024-08-16T16:52:35.377Z CNTRLR Querying configured RF region... 2024-08-16T16:52:35.398Z CNTRLR The controller is using RF region USA 2024-08-16T16:52:35.400Z CNTRLR Current RF region (USA) differs from desired region (USA (Long Range)), config uring it... 2024-08-16T16:52:35.425Z CNTRLR Changed RF region to USA (Long Range) 2024-08-16T16:52:35.426Z CNTRLR Querying configured max. Long Range powerlevel... 2024-08-16T16:52:35.472Z CNTRLR The max. LR powerlevel is 14.0 dBm 2024-08-16T16:52:35.473Z CNTRLR Querying configured Long Range channel information... 2024-08-16T16:52:35.513Z CNTRLR received Z-Wave Long Range channel information: channel: Unsupported supports auto channel selection: false 2024-08-16T16:52:35.516Z CNTRLR Performing soft reset... 2024-08-16T16:52:35.561Z CNTRLR Waiting for the controller to reconnect... 2024-08-16T16:52:36.777Z CNTRLR reconnected and restarted 2024-08-16T16:52:36.779Z CNTRLR Switching serial API to 16-bit node IDs... 2024-08-16T16:52:36.783Z CNTRLR querying Z-Wave Long Range capabilities... 2024-08-16T16:52:36.815Z CNTRLR Switching to 16-bit node IDs successful 2024-08-16T16:52:36.900Z CNTRLR received Z-Wave Long Range capabilities: max. payload size: 148 bytes nodes: 2024-08-16T16:52:36.902Z CNTRLR Switching serial API to 16-bit node IDs... 2024-08-16T16:52:36.940Z CNTRLR Switching to 16-bit node IDs successful 2024-08-16T16:52:36.942Z CNTRLR querying controller IDs... 2024-08-16T16:52:36.967Z CNTRLR received controller IDs: home ID: 0xcbaf673c own node ID: 1 2024-08-16T16:52:36.970Z CNTRLR Enabling TX status report... 2024-08-16T16:52:37.032Z CNTRLR Enabling TX status report successful... 2024-08-16T16:52:37.033Z CNTRLR finding SUC... 2024-08-16T16:52:37.050Z CNTRLR This is the SUC 2024-08-16T16:52:37.205Z CNTRLR Interview completed Starting server on <all interfaces>:3000 2024-08-16T16:52:37.294Z CNTRLR [Node 001] Beginning interview - last completed stage: None 2024-08-16T16:52:37.297Z CNTRLR [Node 001] new node, doing a full interview... 2024-08-16T16:52:37.300Z CNTRLR » [Node 001] querying protocol info... ZwaveJS server listening on <all interfaces>:3000 2024-08-16T16:52:37.767Z CNTRLR « [Node 001] received response for protocol info: basic device class: Static Controller generic device class: Static Controller specific device class: PC Controller node type: Controller is always listening: true is frequent listening: false can route messages: true supports security: false supports beaming: true maximum data rate: 100000 kbps protocol version: 3 2024-08-16T16:52:37.770Z CNTRLR [Node 001] Interview stage completed: ProtocolInfo 2024-08-16T16:52:37.806Z CNTRLR [Node 001] Embedded device config loaded 2024-08-16T16:52:37.807Z CNTRLR [Node 001] Interview stage completed: OverwriteConfig 2024-08-16T16:52:37.810Z CNTRLR [Node 001] Interview completed 2024-08-16T16:52:37.812Z CNTRLR [Node 001] The node is ready to be used 2024-08-16T16:52:37.813Z CNTRLR All nodes are ready to be used 2024-08-16T16:52:37.818Z CNTRLR [Node 001] The node is alive. 2024-08-16T16:52:37.819Z CNTRLR Interviewing nodes and/or determining their status: New client Client disconnected Code 1000: New client -
I probably want to update the f/w but where to find the file??
-
Well looks like you got this working, bar the update? What happens when you hit the update at the bottom?
C
-
It gives me instructions. I had to go to HomeSEER's website to perform the update. I just finished that task and am restarting the HA VM now.
-
You got this!
C
-
Almost! LOL
-
Well I don't run my Z-wave on HA. I have it as an add on device. I have AltUI on a NUC with Mosquitto, and then HA on a Pi
C
-
I'm not going to bother with using rigpapa's (ToggledBits) update from Vera to HA using MSR as I currently have two thermostats and three switches connected to Vera since the move from my previous house required a decommission of that whole system. I really have set up any reactors in Vera for these devices so I'll just un-include them from Vera and include them in HA. What do you think, @toggledbits ?
-
@CatmanV2 said in Migrating from Vera Plus to Home Assistant (or other?):
with Mosquitto,
Hmm..
Should I be doing this instead??
