Given the Ezlo software has a ways to go to reach stability I am thinking of rebooting my Ezlo Plus daily. I would do that with a mechanical timer on the power cord and just kill power for 5 minutes at 3:30AM but thought a scene might be easier. My thinking is some of the memory leaks might not show up in 24 hours so I would at least avoid that sort of instability.
I see on Vera there are trheads to do this
os.execute("reboot")
some say not to do this if WAN connection is down so they suggest pinging Google before rebooting.
os.execute("ping -c 8.8.8.8 && reboot")
Not sure how I feel about the ping as a faulty ping could be a local problem with Ezlo and not the WAN connection. So if its dependent on a good WAN connection it might not reset when it should.
Anyway wondering what some of you more sophisticated users think.
Bad idea to reboot daily?
Is the os.execute command valid in Ezlo (example was from a Vera thread)? if not what would the Ezlo equivalent be?
I’m just thinking of a scheduled meshbot to fire everyday at 3:30AM and run the LUA comment to reboot.
Think the reason why they mentioned maybe checking the WAN connection first, is because the Vera hubs didnt have a real time clock battery and they could lose the correct time, if rebooted when the Internet was down.
Not sure how the Ezlo hubs handle this situation and problem?
You could maybe use the new Ezlo site sensor plugin with 8.8.8.8 and in your Meshbot don’t run your LUA script action to reboot if that site sensor switch device is currently off, likely indicating your Internet is down etc.
I did this with my Vera Lite for years without any problems until it bricked recently. I don’t think that is why it bricked but I am not an advanced user /programmer.
The other concern I have is what would happen if this script runs while the firmware is being updated. I don’t know what day/time the firmware updates and I haven’t seen a way to opt out of automatic updates.
Please update us in a month or two Let us know if you have had any issues.
We’ll it’s been 11 days and no ill effects. Just a simple one line lua script. A mesh bot runs it at 3:37AM everyday. I actually added a delay in the mesh bot of 2 minutes. That way when it reboots it is comfortably after the daily trigger time and doesn’t get into an infinite loop.
I doubt it would interfere with a firmware update. Think about it. If Ezlo is Re flashing itself it would be in some admin state not running the usual Ezlo app. So I doubt it is a risk.
I had a WiFi router years ago that had a reboot feature. I’m sure the software purists are cringing but memory leaks and stack overflows are not uncommon in new code. Just a catchall cleanup that occurs behind the scenes.
Do you know if there is a regular fw update schedule or is it just whenever they decide to push one out? Back when I was regularly tweaking my Vera Lite controller there was a page with all the release notes. do they have a page like that for Ezlo?
I’ve had updates turned off on my controller for a while and the current FW is 2.0.30.2041.2 … a little behind yours so I guess that means it disabled updates.
The question now is how do I manually update it? Also it would be nice to know what updates are included in the FW updates to decide if I want to risk updating if my system is mostly working correctly.
Currently I don’t think you can manually initiate a FW update. If you have updates enabled it just happens as and when they push a new FW release out.
Its not like the old Vera firmware hubs, where the user could choose to update or not and the user also had a website he could go to, to read all the release notes for that new firmware version.
Ezlo hubs and processes are currently lacking in this area compared to the Vera firmware hubs it seems.
Although saying that we are no longer getting any FW updates for Vera firmware hubs as you probably know.
Best Home Automation shopping experience. Shop at Ezlo!
