That’s what we asked. When we tested the alpha version 4783, we felt that version was ready for beta and probably release but the beta came with a ton of additional changes to the kernel and other problems. I expressed then that the alpha which was practically only a LuaUPnP program change could have been released a month or two ago while work continues on the kernel and OS. But no… instead we get this…
The correct way to manage software should have been:
4783 alpha moved to beta as is.
4800 alpha start
then 4783 move to release while 4800 iterations occur and eventually make it to beta. The alpha validated version and the beta must be identical.
Then iterations on the beta lead to a new build which gets validated by beta test and released without any additional changes…
I’ll second all of this, with this fact in particular. We were all enthisiastic about the 7.30 LuaUPnP alpha running on the 7.29 OS, and it could have been released that way. But then we got a new OS with a host of surprises and no documentation whatsoever on most of its changes, so we were also left in the blind with regard to what to test, and much of what we did find was by accident and took considerable effort to nail down.
But more to the point, it’s been a moving target the whole way, when the changes should have been critical fixes to release only. Their process is not a full lifecycle process, outwardly. I don’t know what it looks like internally, but from my view, it’s little changed from prior.
Just to add to the statistics, my VeraPlus got quasi bricked as all others: power light solid, second light blinking after the update to 7.0.30. Me in Ghana, my family at home without hot water in the morning. Thank you, they were very appreciative of this.
My lunch break was VPN’ing home, SSH’ing (yeay, it worked!) into the VP, reset it, restart as new and restore the backup. Weirdly enough, it occasionally still says “Controller busy, updating data” in the iOS app and drops offline in the web interface. Don’t understand what’s going on.
I had stopped looking to Homeseer, HA, etc options a couple of months ago, hoping for the best, but after this debacle, I don’t know,
Firstly the Release Notes did NOT include a list of known issues and limitations so that a user can make an informed decision as to whether or not to perform an update when offered. Although some of this information is available via this forum, it is not collated into a single document and it is difficult for a user to determine which of the issues found during testing are still current in the released version.
Secondly a link to the procedures to follow when perform an upgrade should be provided. These procedures should detaili the upgrade process, how to generate a back-up before upgrading, how long the upgrade process should take and how to recover in the event that the upgrade fails.strong text
Don’t upgrade to the latest firmware if you’re using Google Assistant or Google Home integration. After the update Google integration so that I can no longer control anything through my Vera Plus with voice control. I resynced devices and that worked for one action then stopped, tried resyncing again, with no success. The devices appear in my Google Home app and if I remove one of them from being able to be controlled by Google Home through Vera
I get a notification that switch has been removed from Google Home.
Thank you all for the heads up and allowing me to dodge this bullet. Sorry for your misery, but I’m SO happy I have kept with the wait-a-week-and-read process for updates for/from this device/company.
Same here. The 7.30 Beta on my Edge works fine but I am glad I have not upgraded my Production Vera Plus yet reading the comments above … I hope they will fix it soon because the 7.30 is much better …
This! I looked through the notes and didn’t see the Xmas tree / boot failure issue and assumed it has been fixed - I won’t be making that mistake again!
Inherently I agree, but I would observe that the aim appears that this is to be a consumer product which just works, so the documentation shouldn’t be required.
My assessment after the last releases is that they have some way to go and aren’t making great progress.
I posted earlier that I was able to reset. Now I get into settings and turn off wifi. It’s what I do save and apply and then a static IP. Only after this the controller loses its network mind and will not get back on Ethernet unless I reset again. I’ll give the plain ole backup a shot. I was thinking of rebuilding. This run lasted over 3 years so far.
