Hi Patrick, just an FYI - Reactor 3.4 auto-upgrade bricked itself on my Vera Plus and I had to replace all the files manually from GitHub to restore it to normality (so all good now).
It threw a metric ton of errors in the blue bar at the top terminating with a reactor LUA error. After restarting my Plus I had no Reactor and no sensors at all.
Hmm… part of my normal process for releasing the app is to do an install from the app store-there’s a way to do a test install before fully releasing–and I had no problems with that. I just reinstalled again on another unit from the now full release and it went fine, although it is very, very slow, and it did give me a “Failed to download all plugins, will retry in 10 minutes” along the way.
When there are connection problems or (Vera) server issues the download can stall and leave the unit with an incomplete set of files. The plugin then dies until Vera retries to get the failed file(s), which I’ve always seen it successfully do, but the plugin is borked until that’s done. Once it gets them all, it restarts and everything is back to (now upgraded) normal.
It sounds like you may have caught it at a bad moment. And unfortunately, based on my experience, it’s likely that if you had just left it alone, it would have recovered on its own.
Howdy, I wasn’t sure if it was unique to me and a fluke or not.
Hi Patrick,
Not sure if this is related to the update, but I just created a new reactor to check for camera motion and I add a motion sensor, save it, it looks correct and then it resets to the default config with the comment section instead of the condition I just created.
Roger
Roger, try again, and make sure you see your camera condition when you transition from the “Conditions” tab to the “Status” tab. Sometimes you may have to go out of the device and back in. There’s a lot going on in the background of Vera to save the state variables that are changed, and that doesn’t always happen as quickly as things are going on the UI. And sometimes, the UI is a little slow to pick up changes that occur on the Vera. It’s a hazard of this kind of client-server structure in web applications.
Hi Patrick,
I had a Reactor that monitored a bunch of water leak detectors. Am getting an auto shutoff valve later this week.I had about 10 or so sensors in it. The operative word here is had. One of the sensors tripped. Checked and it was a false alarm. Did a stress test on the sensor, which reset it. But now all the conditions in the reactor are missing. Any idea on how to determine what happened?
All that’s left in my logic report is
Water Leak Monitor (#635)
Version 19082.1 09/02/19 16:36:06
Message/status: Not tripped
Condition group “Water Leak Monitor” (AND) false as of n/a
Events
09/02/19 16:58:13 reload: notice=Luup reload
09/02/19 16:58:13 start:
Can you post a logic summary from the Tools tab?
It is at the bottom of the message. Everything above that is generic location info. Not sure I want to post pii in the forum.
Oh, I see, didn’t quite get the whole report in there (see that first line next time you do one). OK, anyway, onward…
Reactor is pretty tolerant of missing devices. It would flag “trouble” (yellow triangle over the ReactorSensor’s icon) when that occurs. There could be a bug where attempting to “save” with a non-existent device causes a problem, but I’m skeptical, because that kind of thing would not, in my estimation, write a partial config–the structure of the config is such that it has to be entirely well formed–you can’t write part of it and have it be valid, and if it’s incomplete, it’s not readable at all, and in that case, you’d get a hard error.
Have replaced the batteries in the leak sensor, going to reload LUA, but my Vera does that for me about every 10 minutes.
. Reloaded the browser, etc, reactor is still empty. Does each reactor have it’s own config file? Anything to look at there? It was not very complicated to rebuild so not that big of a deal.
Guess this would be a good time to request some type of automated backup that we could schedule.
There’s a backup facility in the Reactor master device. It’s up to you to use it.
Reactor does not rewrite configs on its own, except when upgrading from one version to another IF the format of config has changed. The format of config has not changed since March. So, unless you dragged the conditions into the condition editor. Did you do that? Even if you didn’t edit, did you do that?
I wasn’t even touching the condition editor, just looking at the status.
OK. Well, it obviously got corrupted somehow. If your Vera is reloading every 10 minutes, that’s certainly not healthy. But it sounds like you’re going to need to rebuild those conditions.
Very interesting. Added them all in again. Was playing with the sensor that I had put new batteries in because it was not showing the correct battery level. Ran a stress test on the device and vera reloaded and all the conditions in the reactor went away again.
Here are my repo steps:
Create condition for main bath sensor triggered in reactor. Save and test that it works.
Make backup of Reactor
Reload LUA
Refresh browser.
Confirm reactor still working
Stress test leak sensor
Vera says please wait then downloading LUUP Plugins
And reactor icon is grayed out and conditions are gone.
Restored from backup
Reload browser
Conditions is restored.
OK, what that tells me is that the stress test is actually hard crashing your Vera and it isn’t writing user_data back to Flash before it restarts.
“Doctor, it hurts when I do this.”
“Don’t do that.” 
Guess I had better. Looks to be erasing all my reactor’s
You might also check to see if your Flash is full or near full. SSH in and do a df -kh
Hope not, I exrooted it to a 60 Gig SSD
Filesystem Size Used Available Use% Mounted on
rootfs 54.4G 101.7M 51.5G 0% /
/dev/root 10.0M 10.0M 0 100% /rom
tmpfs 124.8M 5.1M 119.7M 4% /tmp
/dev/sda2 54.4G 101.7M 51.5G 0% /
tmpfs 512.0K 0 512.0K 0% /dev
/dev/sda1 487.8M 3.1M 455.2M 1% /mnt/sda1
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /storage
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /etc/cmh-firmware
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /etc/cmh-backup
/dev/mtdblock9 9.8M 9.8M 0 100% /mios
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules