Please remove and fix Vera Plus update. It’s making units unable to boot properly.
1 Like
Trying to upgrade one of my units, a Plus. When I log in it tells me I can upgrade
|Running Version|1.7.4783|
|Latest Version|1.7.4833|
But when I click the upgrade button, the next screen it shows says
“ERROR: Server not allowed” in red
and then below it
“Click [here ] and try again”
When I try again I just end up with the same error 
I also tried pasting the URL, but same problem. Is this an issue with this release?
Andrew
For everyone attempting the upgrade read this first.
Im having the same troubles with my VP. Installed and let it be for 4 hours… wont boot. Get the 403 forbidden error. Power and blinking internet only. If you didnt install yet… dont. I have never had an issue with any updates in the last 5+ years with my vera units. Im disappointed to say the least.
Edit: Had to do a reset to get it to boot. Was then able to restore from a backup and I am back up and running. In hindsight, i should have waited a month to install this update like i usually do… but it could have been much worse. I’d still say hold off if you havent updated yet.
Agreed this update should be pulled until it’s been more thoroughly tested.
I would not recommend this update be installed by anyone who regularly experiences issues with their Internet access. I reported to engineering two weeks ago that 7.30 will completely disable itself if Internet access is lost for more than an hour. Very repeatable. Apparent changes in the Network Monitor for this release take drastic recovery actions around the one hour mark, and if Internet access continues to be unavailable through that process, the box leaves itself down with the Internet and Service lights blinking, no automations/Luup, and worse, no SSH. Only power cycling seems to recover it at this point. While I am not home to test this final build, I see no evidence in the release notes and have no other communications to indicate that this issue was addressed prior to this release. This is particularly disastrous for users with distant remote units, of course. I would hold off until it’s either confirmed that this was really addressed, or a respin with a fix is released.
4 Likes
Unbelievable - do the update and now the device is bricked. All I have is the power light now showing. Any ideas?
Contact Support. I “quasi-bricked” my Vera Plus with the last beta and called Support. Within 20 minutes Support called me back and with a short screen sharing session where Support reinstalled OpenWRT, I was back up and running with the latest firmware. Bottom-line, my unit was quasi-bricked for less than an hour. Kudos to Vera Support for the prompt response and remedy.
1 Like
I am extremely disapointed with this update.
Tried contacting customer support told to leave a voicemail and they will get back to me. I understand their trying to improve the product but this a failure of QA, customer service and its unacceptable.
Another Vera Plus dead from this update here. My friend did the update on a Vera Plus and it’s dead too.
I can SSH to it and browsing to it shows: 403 - Forbidden.
Any tips to come back from this? Reset procedure on a Vera Plus?
Thanks
Bengie
I am beyond words at this point. I don’t understand why Ezlo/mios would release a firmware without fixing the enormous critical problem found during the beta which we kindly called the “Christmas light” mode problem @rigpapa is describing and is due to the network monitor. If a firmware could have been released, it would have been the alpha we tested on the old kernel. While we could have waited for the kernel to be fully tested before release. I am really sorry for all of you who are dealing with the bricking issue. At this point try to avoid upgrading. I am even tempted to write a script to only do an upgrade on the image and not upgrade the kernel and the network monitor to help the community. It repeats the cycle I have seen in the past of beta firmware being more stable than the official release because mios makes a bunch of untested changes from the beta and ignores the beta feedbacks. I really had hoped that the Ezlo management changed this but sadly it hasn’t.
6 Likes
Updated an VeraEdge without problems, update took about 7 min.
Also tried to update a VeraPlus (remotely) from version 1.7.4800 to the now officially released 1.7.4833 but it has not com back online after 30min.
I will have to see what is going on when I get home in about 8h.
Vera Secure, “Xmas light” after several hours. Looks like a network monitor problem.
“Told you so”? 
This FW is total garbage!!!
I had to power cycle my VP twice to get it back and then when it did come up it’s been factory reset!
Im just doing a manual factory reset and trying again as restoring my backup after the upgrade left me with no rooms!
This upgrade is not fully reversible so to all people… DO NOT UPGRADE at this point. Not only it will get you to a frequent Xmas lighting mode about 80% of the time after a reboot, it will also prevent extroot and will not allow you to revert the broken changes when you downgrade.
1 Like
I accepted this update last night just before going to bed when I woke this morning at 5 I still have no update and the Vera appears to be bricked. I have unplugged and replugged twice. I have not tried reset procedures. Pull this update immediately. This may cause a lot of people to rethink Vera as I will all day long while I’m at work.
I do have ssh access but I’ll have to research the password as I haven’t ssh’d into the unit in a long time.
Don’t hesitate to ask help from our support team as well, if you need it.
Pull the update. Simple. I have started a full reset on my plus using the reset procedure. I’ll check on it when I get home.
The reset procedure worked now I have a new Vera with no devices. Well at least it’s not a brick for real