Yeah, Looks like Amazon finally flagged the Edge…
[quote=“ServiceXp, post:821, topic:172785”]Yeah, Looks like Amazon finally flagged the Edge…
Well, that’s can’t make the boys at Vera feel good this morning 
Nah, they know they released a paperweight, or a projectile… . :-X
;D
Do they? I dunno… they seem to be in a constant state of denial of how badly they manage product development and launches. I’ll admit, that criticism of them has been harsh at times, but it’s deserved due to case after case of miscues over the years.
Like the most recent firmware release where they once again try to fix things, yet make fundamental changes, without telling anyone, which broke many plugins once again. Either they just don’t give a sh*t or are they that clueless?
Do they? I dunno… they seem to be in a constant state of denial of how badly they manage product development and launches. I’ll admit, that criticism of them has been harsh at times, but it’s deserved due to case after case of miscues over the years.
Like the most recent firmware release where they once again try to fix things, yet make fundamental changes, without telling anyone, which broke many plugins once again. Either they just don’t give a sh*t or are they that clueless?[/quote]
Maybe a little of both…
[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]
I propose he wins the Internets for the whole week, not just the day. Epic.
I finally got a Foscam camera working, with a motion sensor… after trying three or four times over the past year. MCV customer service got me started, and the forums pushed me the rest of the way.
EDIT: Wow… with another 30 minutes or so, I got a Hikvision camera to work as well. I should stop while I’m ahead.
@webdesco - That WAS really good. I was not drinking anything at the time, but if I were, I would also need a new screen ;D
I have so say, that after a tough road, I am finally impressed with Edge and UI7. I had the nerve to try and upgrade last year from vera lite. That was a waste of my time.
But, d iving more and more into PLEG on vera lite, forced me to upgrade to EDGE, due to memory limits. While the interface is less responsive than UI5, UI7, with it’s recent firmware upgrade (last week or so) finally got me to 100%!
Even my Leviton scene controllers work, my AEON 4 in one’s installed with no gyrations like required under UI5.
I owe much credit to the ability to reach the Vera support staff live on the phone, and spend time with me.
I have GE/ JASCO, AEON micro dimmers, Enerwave? Motions, enerwave door contacts, fibaro moton (need help getting that one to accept variables) Dimmers, mimo lite doorbell, aeon extenders, wireless camera, enerwave dual relays, foscam siren, first alert smoke, co2…Many of these were not supported on UI5, and now work.
You’ll get there, and this community will get you there, it’s an invaluable resource! 
A negative, though, is the UI7 app is usable for only a single command, then freezes on IOS. Anyone using an inexpensive app on IOS ? Wish Imperihome would come to IOS like yesterday!
Not so much about what I did as much as what I wanted to do with it… This thing is really starting to piss me off… I find, for a 4th time, in 6 weeks my Vera 3 had “lost” about 10 devices. They just vanish from the system.
I want to take this thing out back and punch several ventilation holes through it with my favorite rifle…
EDIT:
If anyone is following these events, the devices that are disappearing are HEM, Smart Switches, standard GE Wall Switches, standard appliance modules (HA02) and Temperature/Humidity sensors. There is no rhyme or reason as to which items disappear, other then it always seems to be z-wave devices.
[quote=“clippermiami, post:813, topic:172785”]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.[/quote]
Turns out my solution is less than a solution. For some reason every once in a while i get indication that one or the other or the Veras has “timed out” when in fact they are both running. (I have a bypass switch setting so that I can test it without it power cycling all the time.)
The sequence is:
-
Receive the Heartbeat from the other Vera (Heartbeat is sent on a PLEG interval timer 90 seconds)
- (turn on a Multiswitch “pulse” button to show the Heartbeat received — temporary)
- Start the PowerCycleTimer (PLEG self-retrigering timer of 10 minutes which SHOULD restart it from 10m:00s as I recall)
- uses Rex’s “checkFirst” logic in the LUA to make sure the timer process does not start until after the first HB is received
-
repeat
-
if the PowerCycleTimer expires
- (set a MultiSwitch button to show a Time Out has occurred — temporary)
- turn off the power outlet that powers the other Vera
- start a 15 second timer VeraOFF_ONTimer (PLEG self-trigger 10 seconds)
- starts the 10 min power cycle timer to keep it from tripping during the power off/on sequence
-
when the VeraOFF_ONTimer expires
- turn on the power outlet
As I said for some reason every once in a while it shows that it has timed out and would have power cycled if not for the bypass switch and it isn’t clear why this is happening. The Heartbeat is every 1m:30s and the PowerCycleTimer is 10m:00s so it would have to miss 7 heartbeats to have the timer expire and I don’t see how that can be. Its true that my ZWave Vera often hits 90% CPU for some reason and is often terribly slow in activating lights etc., but 10 minutes is along time.
Are you sure you are using “Self ReTrigger” and not “Self Trigger” on the timers ?
Today I “automated” my living room ceiling fan based on the state of the entertainment system. Using the Logitech Harmony plugin, I can tell if someone is watching TV. If they are and the fan was NOT already on, then it will turn the fan on Low, Medium, or High depending on the Temperature of the room. It will only do this if the ceiling fan was off when the TV was turned on and won’t do it if the Fan is turned off after the TV was on.
The PowerCycleTimer is a self-REtrigger so that it, I think, restarts when it I’d started. The PowerOFF_ONTimer is self-trigger. If I correctly understand the way these with that should work
It looks like my lash-up is finally working properly. Each Vera reports its operation to the other using HTTP to set a MultiSwitch pulse button on the other Vera. This switch is used as a trigger to start/restart the 10 min. PowerCycleTimer. If this timer expires it powers off the failing Vera and starts a 10sec OFF_ONTimer tha, when expired restores the power and the process begins again.
placed a user variable in the PLEG that controls the process called “checkFirst” with no value assigned. When the trigger starts/restarts the PowerCycleTimer it uses the code suggested by Rex to test/set “checkFirst” to prevent the timer from starting the first time — on the second heartbeat the timer gets started/restarted normally.
Naturally, now that it works I have not encountered any of the “failure to start LuaUPnP” situations that sent me down this path in the first place … Murphy is alive and well.
Now to continue my quest to get LuaUPnP CPU usage down from 50-90% into the single digits … but I don’t see how I’m going to get there.
I’ve been editing some particularly long PLEG statements in Notepad. I accidentally pasted an edited “OFF” statement for some lights in the condition I wanted to turn them ON. Since the statements had been modified, they weren’t quite the same, and the result was some spectacular blinking of that set of lights, until I figured out what I’d done.
Full-screen PLEG viewing would be great. I whacked some keys once by accident and my PLEG went full-screen. I can’t replicate it. I don’t know if that’s a feature or just a bug I uncovered, but I’d love to be able to see more of my PLEG statements on-screen.
I too have done this, and cannot for the life of me figure out how it happened. You are the first person, other than myself, that has mentioned this.
Maybe @RichardTSchaefer knows the secret…
I too have done this, and cannot for the life of me figure out how it happened. You are the first person, other than myself, that has mentioned this.
Maybe @RichardTSchaefer knows the secret…[/quote]
I’ve done this too. ESC key, in my case the cursor was sitting on a Condition Name but I suspect it would be the same anywhere.
I tried the ESC key while on the condition screen… no dice, using Chrome. It just closes the window. I was also using Chrome last time, when PLEG went full-screen accidentally. So I don’t know.
I added a Virtual Motion Sensor using the instructions in this thread. I also tweaked my camera sensitivity (and, ironically, turned off motion sensing) to suppress erroneous triggers.
[quote=“DeltaNu1142, post:839, topic:172785”]I tried the ESC key while on the condition screen… no dice, using Chrome. It just closes the window. I was also using Chrome last time, when PLEG went full-screen accidentally. So I don’t know.
I added a Virtual Motion Sensor using the instructions in this thread. I also tweaked my camera sensitivity (and, ironically, turned off motion sensing) to suppress erroneous triggers.[/quote]
As best I can recall This has happened to me several times in both FireFox and Chrome. But i just tried it again and as you note it just closed the dialog. I know it happened but i guess it must have been some other key or situation.