HI
Please tell when its safe to upgrade .Im on 7.0.29 now and it works good so i dont want to upgrade until its 99.9% safe to run 7.0.XX 
/Mattias
I don’t get the warm and cosy feeling based on all the reports here that the dev team has gotten to root cause. Be it the xmas light mode, the bad blocks or slow internet, extended download time don’t seem to be problems for people who reported issues. For sure the new kernel/upgrade process and the new network monitor are problematic but not completely sure why.
1 Like
I stand corrected, my thanks!
C
So I ran with this update for past three days on a failed update. Same fw as the title. I’m either going to have to downgrade or a fix is coming soon. The Ethernet and wifi have a serious problem. When I turn off wifi radios I lose all access even with a static IP.
I upgraded my Edge without any issues.
The Edge was not impacted by any of the issues discussed.
Drat Drat Drat. Given that ‘the Edge was not impacted’, I decided to do the update.
I now have a brick and the message ‘Luup engine is taking longer to reload’.
A few hours of ‘try again’ and I have got nowhere.
There is no answer from Support ‘leave a message’.All Edge users, beware!
EDIT Pretty quick response from Support! Remote access enabled and they fixed OK by uploading firmware. Sight of relief…
1 Like
My unit doesn’t report that any FW upgrade is available, was it removed?
Haha when i woke up this morning my VP with 7.0.29 had crashed after working perfect. Power and Wi-Fi light on.
Powercycled a coupe of times but nothing helped. Factoryresetted it and it was up after 20 min… Then i se that 7.0.30 was installed… run a backaup and after that it was online but it Didnt boot up the gui all way. Went to work and then i tried now and its offline… Support contacted…
So now a have a shiny dead VP with 7.0.30 
My kids Said o no … now we live in stoneage again… ( turn on lights manually) .
/M
1 Like
Was doing some other work in UI and noticed the LUUP engine reloading every couple minutes. This lines up with the horrid delays/fails I’m experiencing with my VeraSecure and Google/Alexa devices (“The hub … is not responding. Check it’s network connection.”)
Def running the latest version 1.7.4834 (7.30)
Verbose logging - this got enabled somehow and I can’t turn it off. I’m logging to a USB SSD. Whenever I attempt to disable verbose logging a message flashes in red so quickly that I cannot read it and I cannot find anything in the verbose log to indicate why it cannot be disabled. Other than this logging issue everything is working fine. But verbose logging prevents me from seeing anything that happened more than a couple of hours ago. Even though the space available for logging is quite large the log size seems to be limited to less than 20Mb. I’m running version 1.7.4833 (7.30) of the firmware.
@Matteburk. This is nasty. It seems like your unit went into some recovery mode and updated itself and crashed/bricked itself doing it. See what support say…
@tinman, The log size is defined by the RotateLogs.sh under /usr/bin. It dependent on what substrate the logs are saved on. You can manually remove the verbose option by going to /etc/cmh/cmh.conf and remove the log level 50 followed by a luup reload.
@melih, @edward, I hope you realize that you are losing users by doing what you did. You have a QA which is far insufficient and I would really encourage you to follow a proper protocol of build beta testing prior to release. It saddens me to see all these users flee the platform. Firmware and plugin should never auto upgrade. Should never auto download. Should never auto install. This needs to be a basic principle in your design when you have such brick prone hardware. You should also never release a different build from what is being beta tested. Your QA as we have all learned is not enough to insure release quality. It is not just you. It is true for most complex software and hardware and that’s why most industries need to rely on a beta testing process.
2 Likes
i did a post on how to recover a bricked VP but u need the factory firmware bin file … i dont have it it was on my main rig but the ssd died
pretty much the same steps and the veralite
http://wiki.micasaverde.com/index.php/Firmware_Flash_VeraLite
1 Like
Seems like Customers support has lot to do… not a word from them since this morning…
The cmh.conf file had no entry for LogLevels - so I added one. That seemed to resolve the inability to disable verbose logging and after reloading it was already disabled. I had never modified the cmh.conf file so I don’t know how the LogLevels line was removed.
Haven’t read any post since a while… I suppose they are all very busy right now, both customer support and developers (and all the C level)
Add my VeraSecure to the “problem child” list for the 7.30 firmware upgrade. After the upgrade, it just sat with with the Power LED only lit up.
After an hour on the phone with tech support (agent gets an “A+” for effort), he decided my unit needed to be REPLACED and sent me an RMA form, with the diagnosis “Software Defective”.
Using my laptop directly Ethernet connected to the Vera, the agent was able to remote control my laptop to connect the VeraSecure using PuTTY (which I could not do with it on my home network) and uploaded the firmware update to it manually using WinSCP.
After executing the upgrade script manually through PuTTY, my untrained eye didn’t see any error messages go by, but the VeraSecure still only sat there with the Power LED on.
So it looks like it won’t only be the Vera Plus owners having all the “fun”.
The vera secure and vera plus will have the same problems as they share much more similar flash storage structure. The edge should only be having the xmas light mode problem.
On a positive note, I was pleasantly surprised that I was able to restore my VeraSecure backup onto an old Vera Plus and it works perfectly, so I’m back in business.
