New version 7.0.11 (1.7.1419)

Just a few observations on the upgrade.

My Cameras work, but still show the “Can’t Detect Device” message. It was not on the list of fixes, but I was hoping.

The phantom or ghost device previously created is still there, and won’t delete from the Delete Device option. I’ve not tried other methods.

But, has anyone mentioned the new icons? See the picture attached. When the motion is tripped, the little man turns red, but the lines above do not. Not sure if this is an improvement, but it is a change.

Just upgraded my Vera Edge. No problems during upgrade and all devices working.

Upgraded to new version last night, woke up this morning and all settings, apps, scenes, rooms, have been wiped clean… it’s like I got a brand new system!!! ‘( :o :o :’(

[quote=“birchey, post:19, topic:188710”]All seems good this end. Upgrade went through in about 6 minutes.

One thing i have noticed is that i was suffering with a little lag when pleg was firing or even direct control form the UI

It seems a lot quicker now, fingers crossed.

Fibaro binary sensor still not working as mentioned. Its nice to see that they have got their priorities in order by fixing alignment of buttons in the UI when fixing something like the Fibaro issue that’s bringing automation to its knees for some customers is not due until next month.

I wonder sometimes if they randomly pick the bugs out of a very large hat, don’t like what they pick and pick another one.

I guess this is down to the level of developers they have to fix different issues i guess.[/quote]

Birchey, We are working on issues with their UBS. I believe that they sent us a sample and we are working on resolving the issue. Hopefully it will be part of the next update.

To respond your query on how we choose what issues get addressed in a particular update; the Dev Team does not randomly pick and choose and different people are working on different issues. Graphics issues are not addressed by the same person who works on device integration. In device integration issues there are a number of steps, the first of which is identifying the problem once we have we need to figure out why. Sometimes need help from the manufacturer, some are very responsive, some are slow to respond and some never communicate with us at all.

So we don’t randomly choose, somethings just resolved faster than others for one of my reasons.

On a separate note; I and the team will be monitoring this tread for issues with the FW update but if you do identify something that is not working properly the best thing to do is to email support@getvera.com and cc me or go to http://support.getvera.com/customer/portal/emails/new and forward me our confirmation email so I can keep track of it.

If we are not made aware of a problem we can’t address it. Do not assume that we will see a post in the forum, there are hundreds if not thousands of posts a day, we can not read all of them. Contacting Customer Care is the best way to bring things to our attention.

Simian, I am sorry if the alert made your heart skip a beat.

We are aware of the issue and are already working on it. I have six ZCOMBOs, I have updated my firmware. We have replicated the issue. Customer Care is already looking at my controller to identify and resolve the issue.

Hi Marc,

It should be interesting to known the list of manufacters that respond slowly or never .

Otherwise may help to know the list of devices that the dev team tested when a new firmware is released.

tnks

Donato

I can laugh about it now but I was pretty freaked out l last night when all lights came on as for a few seconds waking up I thought I had a fire. When I heard no screeching smoke alarms it dawned on me that wasn’t the case. (I have both zwave smoke detectors and the older non-zwave ones as a backup) It also proved that my ‘Fire!’ scene setup is functioning.

Another silver lining is finding out what others have setup. Although I can’t have Vera switch on my TV’s, she can control my Yamaha HTR receivers. So I will be adding those to the scene to switch on and play the radio loudly as I like that idea very much. I don’t want the garage door to open though. In case the fire is in the garage and the door opening may give it a more plentiful supply of oxygen, fanning the flames. I ado agree with unlocking all doors. This will make it easier for first responders to get in and save my dogs…

Tried upgrading last night on a ver a3 and it stalled. Around 20 minutes in, I unplugged and replugged it. Took a few minutes to start back up, and it had rolled back the update. Tried again this morning and it went smoothly.

Feel free to let us know which vendors are more Vera-friendly. We will give them some love considering they are working with our controller vendor to fix any problems.

No issues. 6 generic IP cameras. 7 zwave light switches. House mode plugin and Concord 4 plugin all working.

:slight_smile:

Did the upgrade 24 hours ago. No problems at the time and none since.
That said, all devices are lighting/power control plus RGBW so no awkward devices anyway.

It’s been 24 hours and only one issue that caused the alarms to go off last night. Discovered it was my error as a sensor in the kitchen was on when it was supposed to be off. Don’t know if it was me or a result of the upgrade in the night mode. Can’t get it to happen again so will wait for the electron Leprechaun to do it tonight maybe.

Well, the upgrade went fine on my Vera 3, however it wiped out my Linear GD00Z Garage Door Openers, but only from the PC UI. The Vera IOS app, VeraMate and Imperihome all show the devices and they work fine. Anything I can do to restore them? The devices are obviously still working. I’d really prefer not to remove them and re-add them.

My 2 VeraLites and my VeraEdge have been updated smoothly with the UI7.0.11 SW version

  1. The validation of my phone nows works … probably due to this fix " Improvement Critical Revise phone number usability for setup wizard "

  2. “My General system alert” has been added in the dashboard but this is not documented in the changelog

  3. The notification was de-selected for the 4in1sensor DSB05 in the VeraEdge (Notification tab of the device) , ok after activation of the notification

  4. Garage door sensor Vision ZG8101 always tripped (regression from previous release = not fixed)

  5. Notification “quota limit reached” after 20 mails of notification (r?gression 1.7.569 = fixed )

[quote=“RichardTSchaefer, post:39, topic:188710”]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.[/quote]

Just let us know when it will be working again so I can move with the upgrade…

It looks like we have an issue with the Sonos plugin with this firmware.
The Sonos device is not present in the devices list anymore.

my sonos is also not showing, is working though, just no device on the devices page

also same issue with ZCOMBO smoke detector always showing tripped

the Zipato RGBW bulb has red bar setting user configuration, unpair\pair did not resolve (works fine though)

as well as pleg issues, though they appear to be working too

updated on veraedge

After logging out, clearing the browser cache, doing a reload of the engine, my Garage Doors are back…

I’m having false report issues with my First Alert Smoke and CO detector falsely detecting smoke
::slight_smile:

After upgrading my Vera Edge, most of my alerts were gone in VeraAlerts! Only the notifications connected to scenes were still there. My browser gave several strange error popups when loading the “Notification Configuration” page, forgot the exact message.

I reverted back to the previous firmware (never did that before, very lengthy process with seemingly never ending reboots, I even had to do a hard reset, but in the end it worked). Now VeraAlerts is functioning as normal again.

Did others experience the same?