New version 7.0.11 (1.7.1419)

Thank you for letting me know about the enerwave motion sensor. I stayed at 1.7.9 because of this issue and have 7 of them.

:slight_smile:

I only finished today fixing the last little issues with my Vera3 from last month’s update (had to reset it)! Updated my vacation rental Vera Lite (no plugins only a few devices) and it went fine. Can’t believe I’m contemplating doing my Vera3 after what happened last time … someone stop me … please!!!

Wished I didn’t. I can ping the device, can’t connect to it in a browser. Last two updates worked fine… figures I should have left it alone.

You have to go at these things … always with a plan ā€œBā€. You did the backup before the upgrade right?

You tried ssh into your Vera?

Yep. Doing so now… Just wished it would stabilize… Plan B, C and D are available if necessary.

Now you are thinking like a Vera user! LOL Good luck; we’ve all been there. This latest upgrade took three passes for me. Each time, I looked up at my Vera expecting to see the orange light of death.

I updated earlier today. About 30 minutes after I updated, my First Alert ZCOMBO Smoke/CO detectors started showing as tripped in Vera and I began receiving notifications. This was extremely alarming as my wife and I had just left the house and I had never received a ā€œdetected smoke inā€ alert before. Now, all of the ZCOMBO smoke detectors are tripped and I am receiving occasional emails even though there is no smoke in the house and the alarms aren’t sounding.

Well, I got stupid and upgraded. Now I’ve lost my MonoPrice (Vision) glass break device. It’s still generating alerts but the device is nowhere to be found under devices. I removed and re-inserted the battery in the sensor but still not luck.

I’m hoping it’ll pop up again…

Update: I just read the above post on the ZCOMBO. I have 2 of those as well. Oh goody!

Removed the glass break sensor and re-adding it seems to have brought it back. New device ID so I had to update a few scenes.

Thanks for the above posts … you’ve kept my trigger-happy finger off the upgrade button for a while :slight_smile:

Upgraded my VeraEdge. No problems so far. Added 4 new GE Smart Switches, everything working fine

Hi, just upgraded to firmware version 1.7.1419 and SONOS plugin stop working ( devices are not show on device list ). Uninstalled and re-installed the app but when plugin creates the new devices they are not show on device list any way and it is not possible to customize/setup them… any feedback?

I just upgrade my VeraEdge and I Lost my inputs on Program Logic Event and I can NOT select a device anymore in the inputs menu

If you have First Alert ZCOMBO smoke detectors, stay far, far away from this firmware upgrade!!!

I have a scene that if one of them alerts to smoke, all zwave controller lights in the house switch on. Luckily I do not have a siren yet as in the last hour, this scene was fired twice due to Vera falsely thinking the ZCOMBO had detected smoke. No fun at freaking midnight.

As I type this, my Vera 3 is being rolled back to 7.0.10 as there is no way I’m going to deal with this…

Firmware URL thread: http://forum.micasaverde.com/index.php/topic,32278.0.html

I did return to 1.7.1320… and I have access again to the devices to create any inputs with the app ā€œthe logic program eventā€

An update since last night … since not having any devices listed after the update and 4 times trying to restore the backup, i tried downgrading back to previous 1320, now i[font=Verdana] cannot ping the device, can’t connect to it in a browser.[/font]
[font=verdana, arial, helvetica, sans-serif]tried the reset by holding the reset button in for 30 or more seconds… nothing … power light constantly flashing, internet light flashing but not on my network.[/font]
[font=verdana, arial, helvetica, sans-serif]not showing in my account on home.getvera.com … broken i think.[/font]

Just upgraded both my Vera Edge and Vera Lite units to this firmware.

On the firmware upgrade page, Vera Edge showed a notification about improved support for battery operated devices. Vera Lite didn’t give me this notification and I can’t find anything about it in the changelog, so I’m wondering what has been improved.

Findings until now:

  • upgrade went smooth on both devices;
  • everything is still working;
  • Vera Edge didn’t detect (can’t detect device) the Aeotec recessed door sensor (GEN5). This was fixed using ā€œconfigure this device nowā€ and pushing the button on the sensor;
  • Netatmo plugin is showing Can’t detect device and I can’t seem to get rid of this message

Other than that, fingers crossed!

Deleted

Where does this information about the fix in ver. 7.12?

I can confirm that PLEG does not allow editing (adding or changing) input triggers in the latest release.

MCV contacted me about this about the same time as I saw it in this thread. I sent them some details.
I am waiting on the response from the MCV folks.

Also did the new upgrade to see if the Qubino and Fibaro switches shows up correctly now in the UI, specifically FGS221 - Fibaro 2*1.5KW Relay.

Pre 7.10
Fibaro Double Relay showed up as 2 devices. (In my opinion correct)

7.10
Fibaro Double Relay showed up as 3 devices (1 Parent and 2 child devices)

7.11 - Latest firmware
Haven’t excluded and re-included devices, only configured the devices again.
Fibaro Double Relay shows up as 1 device. (Could be because support tried to fix it manually on my Edge after last firmware).
Qubino 1D Relay: 1 device now with 1 x ghost motion and Generic IO

Very frustrating…