Keep Vera as a “tcp dongle” with ser2net + socat or similar approach. This approach makes me worry from the network stability standpoint.
Any reason why you are worried? Which network are you talking about? The zwave network or the IP network? In any case, I don’t see it as being possibly the main source of problems. I ran this way for quite some time but eventually did something similar to your solution 2 because of how bricking prone the vera is. The only difference is that I did a network clone (backup and restore) from the vera to a usb dongle instead of a controller shift.
Any reason why you are worried? Which network are you talking about?
I’m talking about IP network. Not sure about the way ZWave JS is communicating with dongle. But it seems that it establishes a connection at startup and expects that the connection will be persistent. So that if the connection between Vera and JS server breaks for any reason, the only way to recover is to reboot JS server. This is doable as JS has a health check URI, but still unreliable as it could happen at the inappropriate moment.
I tried to keep Vera and ZWave JS running for a while and found that JS server goes to “Driver: read ETIMEDOUT” error after a random period of time.
The only difference is that I did a network clone (backup and restore) from the vera to a usb dongle instead of a controller shift.
This is a big difference I assume. I saw your post about that somewhere on the net. Unfortunately, I’ve “luckily” bought SiLabs UZB-7 dongle which has UART chip unsupported by Vera’s kernel, and NVE backup/restore through Z Wave PC Controller also doesn’t work (btw not sure this is a bulletproof method as NVE seems to contains z-wave calibration settings).
I’m using zwavejs2mqtt addon with usb stick, i have 2 vera’s at home but i think that you can’t use ser2net on home assistant os or i don’t know how to do it if somebody found a way help is appreciated.
Sometimes i take out the usb stick from my nuc to pair faster some devices and when i plug it back in it resumes normal operation so you should not have a problem if it loses IP connection and reconect it should resume normal operation.
You can set tcp socket directly at serial port configuration of zwave js. Just go to Settings > Zwave and put tcp://xxx.xxx.xxx.xxx:yyyy into Serial Port field. If you are using zwave js docker setup you also need to set up a port forwarding settings (“-p” option) when starting container.
Unfortunately, I can’t say it is stable configuration. As I mentioned before, zwave js brings me an error saying the driver is timed out sometimes and it doesn’t recover the connection by itself.
I saw that someone has already publish some changes regarding this at git repository. Looks like this changes are not build into official container.
That makes more sense. I suspect that ezlo has added some scripts which are running in the background in newer firmwares. As per their usual selves, they love love love rebooting stuff as a solution to everything. Can you SSH into your vera and run a >ps aux and post the output of it?
I ran mine under that script for 6 months without a reboot but this was a long time ago. I have since migrated to z-way… and gave away my veras…
These two should not be there. I forgot a bit now but the nukevera script should have eliminated them. Try to edit these two files by adding “exit 0” at the beginning of the file or look into these two files to see if they call for a reboot and comment out these lines.
No, that’s not them. Start_LuaUPnP was actually modified by nukevera, but I added sleep before exit afterwards. StreamingTunnelsManager is not modified and I tried to add exit at the beginning and killed the process, but it doesn’t help.
I used something like this to monitor socat / home assistant. This could be changed to monitor zwave js and socat so when connection drops to vera, everything gets restarted
I’m now testing a vera edge with ser2net and zwave2mqtt in docker. It works fine, except if the edge restarts the zwave2mqtt does not automatically reconnect. I’m looking now for possibly a setting I missed, but that’s the last part of the puzzle i need to solve.
Vera edge with ser2net connected via network to zwave2mqtt running in docker inside lxc inside proxmox (inception anyone? ) using a single zwave device for testing for now.
Set zwave led (if ser2net is on) and service led (if a connection to sern2et is ongoing)
This uses port 7676 for zwave. Change to your port…
#!/bin/sh
COUNT=$( netstat -a | grep -i listen | grep -i "0.0.0.0:7676" | wc -l )
if [ "$COUNT" == "0" ] ; then
/usr/bin/set_led.sh off zwave
else
/usr/bin/set_led.sh on zwave
fi
COUNT=$( netstat -tenp | grep "ser2net" | grep "7676" | wc -l )
if [ "$COUNT" == "0" ] ; then
/usr/bin/set_led.sh off service
else
/usr/bin/set_led.sh on service
fi
Hello, I would like to use Home Assistant (HA) instead of the Vera Lite or Edge, which are becoming obsolete. The only thing is that Alexa works quite well with the Vera, but I believe that sooner or later, Ezlo will remove that functionality. There haven’t been any firmware updates for a while, so I’m wondering if it’s still possible to use a Vera with HA, as discussed in a previous post. Is it easily reversible in case it doesn’t work for me and I need to go back to the Vera? I’m thinking of using the “rafaale nukevera.sh” script, but I suspect that despite a reboot, it may still leave some traces. So, to return to the original state, can we still access the interface to create a backup of the Vera? Thank you for the information. Also, for HA, how can I use socat because things might have changed over time?
Stop tinkering with that obsolete sh#t. Ditch the Vera, buy a zwave stick and re-pair everything. It’s a black hole for a while but after that there’s only light! Jeez, It’s been a while since I have thought about Vera, it popped up since I ever replied this topic.
It was a hate-love with Vera… I started Domotica with it but since I have HA I never looked back
if somebody found a way help is appreciated.
) using a single zwave device for testing for now.
