This just rolled to my VeraPlus. Has anyone installed it yet? Are you noticing improvements or stability issues? I know it has been in beta for a bit but I still like to let others go first rather than bork my system.
TIA
I have. So far so good. I jave a very small network and no fancy things though.
Br Stefan
Skickat fr?n min SM-N910F via Tapatalk
[quote=“tixme, post:2, topic:195588”]I have. So far so good. I jave a very small network and no fancy things though.
Br Stefan
Skickat fr?n min SM-N910F via Tapatalk[/quote]
By small network, what do you mean? What devices are you controlling?
I consider mine small but I have several door/window sensors and control my pool and lights in the back yard. I just got the Blue Iris Plugin going to hook Vera into security cameras I am installing too; I notice that this f/w changes how Vera works with cameras which could be an issue for me it the Blue Iris Plugin is effected.
I still consider this a “small” system knowing all the other things I can do with it.
I have 3 wallplugs, 2 built in dwitches, 1 multisensor and 1 rangeextender. I use a bridge for Alexa. Thsts it, for the moment 
Br Stefan
Skickat fr?n min SM-N910F via Tapatalk
I did upgrade FW according to the procedure to restore the factory settings, upgrade FW and restore the backup (due to insufficient storage space my Vera Lite).
After logging in the browser disappeared me some equipment. Refreshing and clearing the browser cache does not solve the problem. I checked on MS Edge, Chrome.
Interestingly, these devices are seen in applications VeraMobile, ImperiHome, Grasshopper and working properly.
How to fix it?
I did the update this morning and haven’t seen any issues come to light but I can now set the temps of my CT100 z-wave thermostats using scenes again!
No problem, so far 
(FYI: 60 devices)
I believe I have found a bug with the new firmware and the Vera app on IOS.
My Vera Plus started reporting the error “error in lua for scenes and events”.
After checking the luup log I found that a scene had a function that just had a long string of random text instead of the code I wrote.
Yesterday I had added a Geofence to that scene on the Vera iOS app.
I deleted and recreated the scene, putting the Lua code back in, added the geofence and the same thing happened. To work around the problem I just saved the lua code again, using a PC.
I recommend you keep a copy of your code before you add any geofences to an existing scene.
Is anybody else getting this?
The NEW internal storage format for a scene LUA is Base64 encoded data. This just looks like a long line of characters.
The existing bugs are when various components (Browser, Mobil Apps, Vera) get out of sync with each other relative to if the Scene LUA is encoded(NEW standard) or not encoded (OLD standard).
MCV continues to struggle with this for the last 3 releases (including betas).
I would recommend ONLY using a PC or MAC web browser for creating/editing scenes for now.
Thank you Richard.
I’m still on 2138 after reading about the issues with 2414. I am hopeful that 2608 will be stable/reliable enough to upgrade…
[quote=“Sierek, post:5, topic:195588”]I did upgrade FW according to the procedure to restore the factory settings, upgrade FW and restore the backup (due to insufficient storage space my Vera Lite).
After logging in the browser disappeared me some equipment. Refreshing and clearing the browser cache does not solve the problem. I checked on MS Edge, Chrome.
Interestingly, these devices are seen in applications VeraMobile, ImperiHome, Grasshopper and working properly.
How to fix it?[/quote]
I have a VeraLite and did a straight upgrade after making a backup and saving it. I did NOT do a factory reset first and had no issues with space for the upgrade.
I have not noticed any issues post-upgrade but have not dug in to see if the issue with corrupting LUA code in a scene when I try to edit it persists (using my Mac to edit).
I took the plunge. Vera Plus from 2138.
I upgraded like I usually do:
- Backup ZWave
- Save backup file
- Reboot (via network settings menu)
- Upgrade
It went smoother than any previous updates.
One thing I noticed–even though my WiFi is turned off, the LED is on. I scanned the network, it is not on.
I’ve had the scene code changing issue in my VeraPlus on 2414. History has tought me to wait about a month before upgrading to their beta releases, and monitor the forum like a hawk. Think about it, if they were Tesla all of their customers would likely already be dead. 
I had some minor fits upgrading. Had to do a hard reset of the controller to get it to do a truly clean install. Because of that, I had to plug it into my router to configure the Wi-Fi. Then I could restore from the backup. Was working fine so I unplugged it from the router, moved it to its normal place, it booted up fine, things still working, so I went to bed.
At 5:30 when I awoke, the PLEG to switch from Night to Home did not execute (no notification that the cameras were disarmed). VeraMate could not connect so I could not confirm the heating was raised from 65 to 68. Looking at the thermostat, still set at 65. Looking at the controller, it was back to no WAN (just like after the hard reset). Rebooted. It came up fine and has been working since.
It reminds me to boot, boot, boot when making radical changes and patiently wait for LUUP reloads a couple of times when making minor changes. After a while it settles down until I tinker and “break” it again ;D
for the first time since buying my veraplus (2 years?), this upgrade didn’t go smoothly (2607)…
I upgraded while at work but the controller never came back. I had to go home and power cycle it. Even then it took a bit before it was up and it came back up without any devices. Super. I restored the backup i had and after it went through it’s routine with the devices it’s working again. I’m not thrilled with the experience but oh well. It seems to be behaving for now…
Sadly, this new firmware appears to be a lot less stable than the patched up 7.0.19 I had.
- I have observed a self vera reboot I have not seen for months
- Luup reload also more frequent causing the ecobee to lose its token frequently.
- at 2am I am getting a false alarm from one of my door sensors. I am certain the door sensor is not tripping. Somehow it flickers during the nightly heal and sound the sirens.
- WAPIRZ1 partially fixed. Still dealing with a ghost temperature sensor device.
Will be opening a ticket…
I’ve upgraded with no issues. All working fine.
Only have a few apps on my vera edge:
System Monitor
Imperihome
Deus Ex Machina II
HouseModes plugin
Concord 4 plugin
The previous update was a disaster for my vera. Tech support identified the Concord 4 plugin as the culprit. I would get about 6 LUUP restarts a day, usually when a scene was triggered. As a result of the LUUP restart the triggered scene would fail to execute. Geofence also went to a useless and unreliable status.
Some work from tech support and this update have brought me back to a stable system. All previous issues gone. Tech support advised removing the concord 4 device and restoring a backup, along with fixes in this latest update were responsible for the return of stability.
Given the relative speed this update was pushed out I am wondering if there were not critical issues caused with the previous UI7 version.
I have the Concord 4 plug in and didn’t have any problems with the last few upgrades. I think this just highlights how fragile the these systems are.
Agreed.
I was about to move over to ST but would have to rebuild my entire system. The concord 4 interface with vera has me hostage but I was so frustrated I was about to jump.