How to Decouple your Vera Home Automation Controller from the Cloud, Part 1
With the upcoming change to the Vera cloud service requiring an annual subscription, I wanted to try out the Vera Decouple package from @toggledbits9663 (link below) and see how well it works.
Some advantages are:
It is generally accepted that Veras are more stable when not connected to the "mother ship", as outages of these cloud services often causes spurious reloads of Luup or even reboots of the system. Decoupled systems use less RAM and CPU as well. Decoupling also improves system reliability when Internet access is not available.
I had thought about doing this for about a year and when Ezlo started pushing their subscription service, that was the motivation I needed to give it a try.
I plan on using my Synology NAS as the main server for the Vera. I already have it set up as an NTP and DNS server and just needed to add the SYSLOG and FTP services. I also have the Personal Web Service running on the NAS and set up a Vera user account and hosted the pre-edited Vera Decouple files there.
I ran into some issues that may be due to the above setup, but I simply copied the three .sh files over instead of trying to work with the ZIP file, for example:
curl -O http://server_ip/~Vera/decouple.sh
repeat for the other 2 files and this transfers the shell script files from the Vera personal web folder to the Vera's root folder.
GitHub:
https://github.com/toggledbits/Vera-D...
Initial results are promising, update on the decoupled system the day after in an upcoming video...
Thanks for sharing and subscribing!
And as always, thanks for watching