June 2015 upgrade.. The one No one is talking about

Think this is the strongest massage I’ve seen so far…

VERA… are you listening to the deafening silence…

Another upgrade and this time were not even bothered complaining about you introducing more issues and not fixing existing issues

Sent from my A0001 using Tapatalk

I did the update. Bricked my VeraEdge. Just got off the phone with customer support and they tried everything and it concluded with the VeraEdge is faulty. I’ll need to RMA it and the process can take up to 2 weeks >:(
2 weeks with all my automation down :frowning: out of state family coming over tomorrow too
Was excited to try the new update with the fixes and the web interface supposedly being a little faster. Not happy at all about the outcome. Very annoyed and frustrated

I saw the update notification day before yesterday. After 7.06 messed up my sensors, I figured hold off until I see what the responses are. So far I’m not sure if I want to upgrade from 7.05 to 7.08 at this time.

Upgrade seems fine to me.

Lost my Minimotes… again… I suspect due to a Zwave rebuild. At least this time, I didn’t have to downgrade (I would have had to skip two levels). I got one Minimote working and I’ll work on the second one tonight. Sheesh; it would be nice to upgrade and NOT lose my Minimotes!

The upgrade finally seemed to be getting back to good for me, on the Vera Edge.
Installed flawlessly. MiniMotes working again, seems stable.

I use the following:
Cooper Light Switches, Dimmers, 3-ways, Battery Switches
Linear/Jasco Outlets
Jasco Lamp Module
EcoNet Vents
MiniMotes
EZMultiPli (HSM200)
Fibaro Motion Sensor

Concord 4 Security Plug In with door sensors and motion sensors (with Honey Well Z-Wave and Schlage Z-Wave Locks running through Alarm.com better/easier apps and integration for those than Vera)
Sonos Plug In
KIRA Plug In
PLEG
PLT
PLC
EZMultiPli Color Plug In
UPnP Proxy Plug In

My only remaining bugs
EZMultiPli logs a ton of alerts (support says it is being targeted for the July firmware update
EZMultipPli light sensor says “LUX” instead of % (so minor I really don’t care)
EcoNet Vents say they are “Repeaters” when they aren’t (minor)

Haven’t tried setting up an association (my main other complaint right now) but I am hoping this is fixed, does anyone know? On older firmwares doing the Association would delete all my virtual devices so I would have to restore from backup afterword (generally I just use the MiniMote to the association instead)

Lots of stuff seems fixed for the devices I use, so feeling pretty good about this update in general compared to the last few.

My findings:

  • Rather a hassle getting it installed. Managed to bork root FS so had to telnet in & re-image from eeprom… then with it booted again, still took another 4 attempts to get the 599 version to finish flashing.
  • Now all seems good though… restored my 583 config no probs (eww… 583 saved backup restored to 599 ! ), and all devices came up clean.
  • Now waiting to see if any of my regular device anomolies are magically gone now.
  • Happy to say I’m finding the UI WAY more responsive now! Removing the batch of (10 or so) mystery generic devices was much easier now.

Re the problem with the upgrade… I found that when first running it, the UI showing the 15min timer had NO idea what the system was doing… left it to well after 15min (probably more like 30) and then hard booted it, only to get the flashing orange/green power LED with solid zwave LED. Thankfully the wiki recovery procedure worked a charm. Don’t really have much faith in the whole upgrade procedure… especially if something isn’t quite right, requiring user intervention.

Also, it would be nice if the relnotes were more logically arranged… with groups for device support, UI etc… while I LOVE a long list of fixes/enhancements, it IS rather laborious trolling past line after line of (for me) irrelevant device compat notes.

Anyway, thanks to the Vera devs for their release.

Stu.

Go for it. By far the best release this far. The sensors are fixed kind of. They do untrip but somehow send an alert when they do.

Does anyone know if there is a process/utility like this: http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera3
for the VeraEdge? I’m still trying to save my VeraEdge and not have to wait the two week RMA

Thanks

I’m sorry your upgrade didn’t go well. Perhaps I’m lucky but mine did go well. It even resolved two of my issues - minimote and garage door icon.

Hi all,
My upgrade went well.
I started the upgrade AND leeft for a music festival.
Found all up AND running when I came back.
The only thing was the back-up initiated from the Firmware upgrade page locked my Vera3.
Got out of this with a power cycle.
Jacob

Good news - Monoprice motion detectors issue is fixed, they untrip now.
Bad news - Monoprice door/windows sensors still do NOT untrip. Mine are again stuck in tripped state.

Hmmm. I only have 2 of the door ones but 5 of the motion ones. Still debating whether or not to go the 7.05 to 7.08 upgrade.

Anyone running pleg having problems with v599? My pleg now reports “error executing function pleg_inputs()”. ditto for conditions and action tabs.

Then again I also since installed event viewer and alternative ui plugins too. Not sure if this could be the problem.

OK, I can confirm on my Vera Edge that the Association UI now works again as well, can now set and change associations on devices without it deleting my virtual devices. Which is great!

Just to add that my upgrade also went flawlessly and fixed my problems from the last upgrade.

@sTuDeimus

Sounds like you lost some of the files for PLEG/PLC.

Just upgrade the PLEG wait for restart … then PLC … wait for restart … reload Vera one more time … wait for restart … then refresh browser.

See:
http://forum.micasaverde.com/index.php/topic,14446.0.html

Thanks Richard. That did the trick. Didn’t realise upgrading an app also refreshes it (if already at latest). Also didn’t realise the programming\plugin-dev subforum also had further subforums for each plugin! :slight_smile:

Stu.

[quote=“mrv777”]I did the update. Bricked my VeraEdge. Just got off the phone with customer support and they tried everything and it concluded with the VeraEdge is faulty. I’ll need to RMA it and the process can take up to 2 weeks >:(
2 weeks with all my automation down :frowning: out of state family coming over tomorrow too
Was excited to try the new update with the fixes and the web interface supposedly being a little faster. Not happy at all about the outcome. Very annoyed and frustrated[/quote]
Same thing happened to me. I have a Vera3 so out of desperation I tried to take the VeraEdge UI7 backup from the May Firmware and load it on to the Vera3 with 1.7599. Worked great for about 5 mins then a bunch of devices were assigned new device numbers and lost their former identities.

I wonder of I could load one revision older on Vera3 and then load this backup? If so, where do I get the previous backup link?

Sent from my XT1254 using Tapatalk

[quote=“chuck1026, post:19, topic:187571”][quote=“mrv777”]I did the update. Bricked my VeraEdge. Just got off the phone with customer support and they tried everything and it concluded with the VeraEdge is faulty. I’ll need to RMA it and the process can take up to 2 weeks >:(
2 weeks with all my automation down :frowning: out of state family coming over tomorrow too
Was excited to try the new update with the fixes and the web interface supposedly being a little faster. Not happy at all about the outcome. Very annoyed and frustrated[/quote]
Same thing happened to me. I have a Vera3 so out of desperation I tried to take the VeraEdge UI7 backup from the May Firmware and load it on to the Vera3 with 1.7599. Worked great for about 5 mins then a bunch of devices were assigned new device numbers and lost their former identities.

I wonder of I could load one revision older on Vera3 and then load this backup? If so, where do I get the previous backup link?

Sent from my XT1254 using Tapatalk[/quote]

Forget that… found the thread with the Vera3 firmware links. Stepped back one, tried loading the backup and… NOPE. Same issue. Ugh. Any workaround at all?