Thanks Richard, I’ll dig into the PLEGs and see if either of those is true although I tend to think NOW is not present anywhere … After you showed me how to use the Timer functions I use those instead. As I said I have no way to know that it’s PLEG, Tech Support suggested that
[Update]
As I suspected, “NOW” is not used in any of the PLEGs and only one timer was set to 00:01:00.
Not today, but last weekend, I installed a a new fan and a FanLinc in my Living room. I tried to set it up so that the ISY cycled through the states using 1 button (off, low, med, high). It worked until I tried to account for adjusting the state variable AND the button LED when turned on from another source (Via the Vera with the ISY Plugin, or even via the ISY admin screen). For some reason about once a day it would get stuck in a loop.
So, the night before last I gave up and instead each button is now “on/off”. When I turn it on, it turns the fans on Medium. If you use the fast on, it goes to high. The only bad part is that doing it this way is you have to turn it off if you turn it on Med and want to turn it on high. However, I plan on utilizing the Vera and when you only do a normal “on”, I am going to turn on the fan(s) to a specific speed based on the temperature in the room. For instance, if it’s 80 in the living room, it will go on high, but if it’s 72, it will go on low (just enough to move the air).
I also plan on tying this into the lights in the rooms where I have fans. If the lights are on, the Vera will adjust the fan accordingly. In the living room, I will also factor in the state of the Harmony Hub activity.
Well Last night we got our new TV for our Master (48" Samsung). I haven’t run all the necessary wires (it’s hot in Florida today), but I set up the Tv, The Roku and The Harmony Home control and using the harmony plugin available for the Vera, I now have it turning sending the “off” command to the harmony when you press the button to “turn the room off” (all the bedrooms have this feature).
I have 2 more Harmony Home controls to add in the Kids room so I can stop turning off the Tvs by turning off the outlet and turning it back on…LOL.
[quote=“clippermiami, post:799, topic:172785”]I continue to be plagued with a Vera Restart problem for which no one at Vera seems to have an answer.
I have two UI5 Veras; Vera-1 runs all the Zwave stuff and Vera-2 interfaces the DSC alarm and the Blue Iris camera system. Both exhibit very high memory utilization, Vera-1 85-95% and Vera-2 110-115%. Vera-1 also exhibits periodic high CPU utilization topping 90% about once per minute which I suspect may be PLEG serving timers but i can’t prove it.
Anyway the current problem is that Vera-1 may restart several times a day (others days not at all). About once a week it restarts but LuaUPnP does NOT start at all — the problem for which Vera Tech Support seems not to have an answer. I can access it via SSH and see that LuaUPnP is not running at all but it answers PINGs so there does not appear to be a nice clean method to use as a means of detecting startup failure and forcing a restart or power cycle.
So I’m thinking about a different approach. Two ZWave power outlets in a box, one controlled by Vera-1 and the other by Vera-2. Vera-1 is plugged into the Vera-2 controlled outlet and vice. Each Vera would have a VirtualSwitch/MultiSwitch, a PLEG function with a 1 minute short timer and a 5 minute long timer.
Each Vera would then use HTTP to set a VirtualSwitch/MultiSwitch on the other Vera. When each Vera sees the switch set it would reset the internal timer and set the switch on the other Vera and so one once every minute or so throughout the day.
Because LuaUPnP is not running commands received would be ignored on that Vera. If Vera-1-or-2 fails to see its control switch set by the other then the long timer will eventually expire and the Vera would trip the other-Vera-outlet OFF and then turn it back ON after 30 seconds. Thus each Vera would be monitored and power cycled by the other if it fails to function properly.
A convoluted solution to be sure but its what I’ve been able to devise to solve for a problem “that can’t happen” when it happens.
Opinions? Suggestion? Better solution?[/quote]
I’m making good progress on this solution with one glitch. I’ve built a short extension cord with a dual gang box to house two GE/Jasco Duplex outlets (‘m awaiting the two Ge/Jasco outlets, my local Lowes’ didn’t have any in stock.) Each of the outlets will power one of the Veras but be controlled by the other Vera.
I have a Vera-Vera Heartbeat function working and every minute each Vera sends the other a command to turn on a “pulse button” in a MultiSwitch. This button is set up as as TRIGGER in PLEG. When the trigger is received it resets the MONITORING PowerCycleTimer.
If a MONITORED Vera LuaUPnP fails to start for some reason the heartbeat is missed and after 10 minutes the MONITORING Vera PowerCycleTimer expires and it will cycle the outlet powering the failed Vera which will of course start that Vera cold.
The glitch occurs when the MONITORING Vera restarts. As soon as it recovers from the Restart it fires its PowerCycleTimer which power cycles the running Vera. So I need to find a way to suppress this on local restart but this appears to runs counter to the design of PLEG. I need to find a way to make the PLEG aware that a local restart has occurred and suppress firing the PowerCycleTimer that monitors the "other’ Vera.
Thoughts?
I need to find a way to make the PLEG aware that a local restart has occurred and suppress firing the PowerCycleTimer that monitors the "other' Vera.
You could add Lua to the PLEG Action. Load the value of a global variable NotFirst into checkFirst. Then set NotFirst to true. If checkFirst is nil it means Vera restarted so return false to kill the action.
[quote=“RexBeckett, post:805, topic:172785”]
I need to find a way to make the PLEG aware that a local restart has occurred and suppress firing the PowerCycleTimer that monitors the "other’ Vera.
You could add Lua to the PLEG Action. Load the value of a global variable NotFirst into checkFirst. Then set NotFirst to true. If checkFirst is nil it means Vera restarted so return false to kill the action.[/quote]
Thanks, I understand the principle. But I’m not conversant in LUA so could you “seed” the process 
Rex
I THINK I sorted this.
Created a Variable “StartUp” in the PLEG value “1”
Created a Device Property “CheckFirst” set to “PLEG Common/StartUp”
Modified the Condition “Vera1PowerCycleOFF” as “(Vera1PowerCycleTimer; !Vera1PowerCycleTimer) AND CheckFirst”
Will this do it?
[quote=“clippermiami, post:807, topic:172785”]Rex
I THINK I sorted this.
Created a Variable “StartUp” in the PLEG value “1”
Created a Device Property “CheckFirst” set to “PLEG Common/StartUp”
Modified the Condition “Vera1PowerCycleOFF” as “(Vera1PowerCycleTimer; !Vera1PowerCycleTimer) AND CheckFirst”
Will this do it?[/quote]
I don’t think so. If you just create the variable and give it a value it will not show that a restart has occurred.
Just put this into the Lua for the action:
local checkFirst = NotFirst
NotFirst = true
return (checkFirst ~= nil)
[quote=“RexBeckett, post:808, topic:172785”][quote=“clippermiami, post:807, topic:172785”]Rex
I THINK I sorted this.
Created a Variable “StartUp” in the PLEG value “1”
Created a Device Property “CheckFirst” set to “PLEG Common/StartUp”
Modified the Condition “Vera1PowerCycleOFF” as “(Vera1PowerCycleTimer; !Vera1PowerCycleTimer) AND CheckFirst”
Will this do it?[/quote]
I don’t think so. If you just create the variable and give it a value it will not show that a restart has occurred.
Just put this into the Lua for the action:
local checkFirst = NotFirst
NotFirst = true
return (checkFirst ~= nil)[/quote]
Rex, thanks. I did try my earlier “solution” and it worked occasionally so my guess is it was as much chance as anything. Thanks for the “actual” solution
Rex, thanks again, that appears to have solved the problem of false trips after restarts. Naturally I haven’t experienced any non-starts of LuaUPnP since implementing this so I have to keep waiting to see if this will properly handle that problem. But I haven’t received the GE outlays yet anyway so just as well
I set up my pebble smart watch to change my a.c.&heat target temp using pebble tasker+ tasker+ authomationhd. I was using the vera scenes app but my scene list was too big for convenience.
I added a 2nd interior motion sensor and some PLEGs to go with it. I’ve also been tweaking the PLEGs that supervise my garage lighting.
I realized the other day that there are a handful of light switches that I don’t even touch anymore… and that’s where I eventually want to get with of them (however unlikely). Very cool.
Completed my “LuaUPnP Failed Start” recovery device today.
Its ridiculous to have to do this but I have a failure to start LuaUPnP about once a week on one or the other of the Veras. Because the heartbeat is a function of LuaUPnP not simply the Vera box OS, failure of the heartbeat is a reasonable conclusion that LuaUPnP failed to start properly and in my experience the only way to get it running again is power cycle. This automates the process.
Each of the two Veras sends a heartbeat signal to the other Vera every two minutes. If the heartbeat is not received by one of the Veras for five minutes it is highly likely that the LuaUPnP has failed to start on “the other” Vera. The monitoring Vera then power cycles the failing Vera using a GE/Jasco Duplex outlet which should get the Vera running again properly.
It’s obviously possible to do this only once on the initial startup but this was cleaner.
U1.5?
Yes, I’m probably a long way from UI 7
Got my brand new vera Edge (UI7) to reliably turn the office light on.
Step 1) disconect the power and lan cables
Step 2) take aim at the light switch
Step 3) throw vera at the light switch
BINGO successfully turned the lights on.
[quote=“webdesco, post:816, topic:172785”]Got my brand new vera Edge (UI7) to reliably turn the office light on.
Step 1) disconect the power and lan cables
Step 2) take aim at the light switch
Step 3) throw vera at the light switch
BINGO successfully turned the lights on.[/quote]
And…now you owe me a new monitor. It did not like the coffee. ;D
[quote=“webdesco, post:816, topic:172785”]Got my brand new vera Edge (UI7) to reliably turn the office light on.
Step 1) disconect the power and lan cables
Step 2) take aim at the light switch
Step 3) throw vera at the light switch
BINGO successfully turned the lights on.[/quote]
Am I to interpret this as meaning you are not totally pleased with your new Vera and its advanced UI7?
[quote=“webdesco, post:816, topic:172785”]Got my brand new vera Edge (UI7) to reliably turn the office light on.
Step 1) disconect the power and lan cables
Step 2) take aim at the light switch
Step 3) throw vera at the light switch
BINGO successfully turned the lights on.[/quote]
LOL now that was FUNNY!!
[quote=“webdesco, post:816, topic:172785”]Got my brand new vera Edge (UI7) to reliably turn the office light on.
Step 1) disconect the power and lan cables
Step 2) take aim at the light switch
Step 3) throw vera at the light switch
BINGO successfully turned the lights on.[/quote]
You sir, win the Internets for today.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules