So, as the system grows, i’d like to distribute the work to a more powerfull unit.
The plan i’ve started with is to have a “Master” running openLuup on a linux system (Chromebox with Debian), and to run all plugins and logging on/from that.
This enables me to connect more Vera’s and even EzLo units, and have Reactor work with all of it.
But some things i’d like to retain:
I started with the thought that there was a possibility for remote access to Openluup, but i guess thats not the case?
The User setup also seems dependent on Vera hardware, is there a way to set this up so I can have a registered lisence in my name without Vera base (and that its not overwritten when I connect vera’s)?
All input is appreciated, especially from the folks who mentioned that they’ve gone to using the Vera only as a z-wave/zigbee hub. I’d like to know how they solved retaining the functions mentioned above…
1, you can use vpn to connect to openluup or forward a port.
2, i do not use geo fencing, i use Automate on all house mobile phones to register when a phone connects to home wifi.
3, i also use the cloud message function of Automate to send notifications to any android device i wish, using reactor http notifications.
Its running fairly OK now, but I still have no icons (did the GetFiles thing), and on luup Reload, i get the “Os Command execution request failed. (returned error)”
in the log it days that it exited with code: 42.
Is it a permissions issue?
I also tested setting up a reactor to replace one that was slow running on Vera. Its even slower now, 3 secons response time. Any tips to how i find out where the delay is?
Exit code 42 is openLuup’s standard status for a Luup reload command. That’s how it knows to reload and not to exit:
# reload loop for openLuup
# @akbooer, Aug 2015
# you may need to change ‘lua’ to ‘lua5.1’ depending on your install
lua5.1 openLuup/init.lua $1
while [ $? -eq 42 ]