The Vera Community forums have moved!

General => Upgrading => Topic started by: mfp on December 17, 2016, 05:15:49 am

Title: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: mfp on December 17, 2016, 05:15:49 am
I installed the latest firmware, see the release notes:  http://support.getvera.com/customer/en/portal/articles/2673588-ui7-%E2%96%BE-version-7-0-19-1-7-902-1-7-2406-1-7-2414-%E2%96%BE-december-12-2016 (http://support.getvera.com/customer/en/portal/articles/2673588-ui7-%E2%96%BE-version-7-0-19-1-7-902-1-7-2406-1-7-2414-%E2%96%BE-december-12-2016).

Reboots of LuaPNp are a lot less frequent. Stability is improved.

It is the 2414 release for the VeraPlus: http://dl.mios.com/firmware/mt7621/mios/release/mt7621_Luup_ui7-1.7.2414-en-mios.squashfs (http://dl.mios.com/firmware/mt7621/mios/release/mt7621_Luup_ui7-1.7.2414-en-mios.squashfs). Watch out this link is only for VeraPlus!

Bugs/Things I noticed on VeraPlus:
1. Everspring ST814 Child Humidity device is not working. Issue is the ST814 values are only updated on the main device, not on the embedded sub-devices (temp+hum). It is a known bug: http://forum.micasaverde.com/index.php/topic,38440.15.html (http://forum.micasaverde.com/index.php/topic,38440.15.html)
2. Leds are not working. If I turn off Wifi the LED stays on. From a terminal the command "/usr/bin/set_led.sh off wifi" works fine. It is also a older bug: http://forum.micasaverde.com/index.php/topic,38417.msg287344.html#msg287344 (http://forum.micasaverde.com/index.php/topic,38417.msg287344.html#msg287344)
3. CIFS modules got reset/removed. Probably new kernel modules (not checked) . They can be reinstalled the normal way http://forum.micasaverde.com/index.php/topic,38219.msg285586.html#msg285586 (http://forum.micasaverde.com/index.php/topic,38219.msg285586.html#msg285586)
4. Negative energy values not displayed (For energy produced by solar panels , worked fine in UI5 on Vera3)
5. Unused Radios (ZigBee/Bluetooth) can not be turned off.

I have not yet made my mind up if I will go back to an old firmware. Because of all bugs and instability of the previous firmwares I rolled back every time to the 1786 firmware.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: zalam on December 20, 2016, 03:35:58 pm
I upgraded my VeraEdge.  It now is giving "Luup engine is taking longer to reload".  I cannot access the device. Let message to customer service and also emailed them.  Waiting on response.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Operations on December 21, 2016, 10:39:07 am
My first experience on updating on a Veraplus 1.7.2414,  and of course First a backup of the system.  and start de online update..

It's not quick, so don't think to do this in an half hour.   (all my routers, en servers are upgrading faster, even an synology-server is faster, including all of the software packages)
and then :  after a reboot, lost al my configured devices, rooms and scenes.   (Wtf, so maybe I'm I have to check de the user manuals and releasenotes, again !!)

After restore a backup,  I've have my rooms, and scenes back, but de most of my Z-wave devices are gone. exept de Philips Hue configuration

Is this normal for an firmware update procedure ??
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: mfp on December 21, 2016, 02:40:59 pm
My first experience on updating on a Veraplus 1.7.2414,  and of course First a backup of the system.  and start de online update..

It's not quick, so don't think to do this in an half hour.   (all my routers, en servers are upgrading faster, even an synology-server is faster, including all of the software packages)
and then :  after a reboot, lost al my configured devices, rooms and scenes.   (Wtf, so maybe I'm I have to check de the user manuals and releasenotes, again !!)

After restore a backup,  I've have my rooms, and scenes back, but de most of my Z-wave devices are gone. exept de Philips Hue configuration

Is this normal for an firmware update procedure ??
I have not yet lost settings after upgrading to a newer release. If you backup you have an option to backup the Z-wave network. You can restore the Z-wave network by hitting a check box. Even after a complete reset I was able using this setting to do a full system restore including the Z-wave network.

I have had a lot of instability on m Z-wave network after my migration from a vera3. After I completly reset my z-Wave network and rebuild it from ground up it is very stable.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Pietor on December 22, 2016, 06:21:21 am
I've also upgraded the firmware and so far very positive.
However: My geolocation is not working anymore. Anyone else experiencing problems with this?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: CPrdam on December 22, 2016, 07:06:35 am
I als had two devices with can not detect. But there still working. And both devices are not working on batteries.
Put them on and out via app and there visible again????
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Inzax on December 22, 2016, 08:29:08 am
I've also upgraded the firmware and so far very positive.
  • Battery devices are indicating battery life again
  • Fibaro Dimmers do not give an error that the device cannot be detected anymore
  • Seems more stable and finally a dashboard withoudd any error
However: My geolocation is not working anymore. Anyone else experiencing problems with this?

Geolocation.  It still worked for me however it behaved badly the first few days with multiple "entry" and "exit" alerts.   After a few days the multiple alerts stopped and are now replaced with just entry and exit alerts which is still not right.  I had set up my system to alert me on entry and exit and when the security panel is armed/disarmed as a result of moving in and out of the geofence.  Each entry and exit should have TWO alerts.  The first alert that I left/entered the geofence.  The second alert that the security panel armed/disarmed.   Checking the system I can see that the arm/disarm function is working which means the alert is not coming through.

Odd....but since it is working I have not tried to resolve the issue.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Nailer00 on December 22, 2016, 11:50:13 am
I upgraded my VeraEdge.  It now is giving "Luup engine is taking longer to reload".  I cannot access the device. Let message to customer service and also emailed them.  Waiting on response.

I got the same message and refreshing a few times worked for me...
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: helge@fabricius.nu on December 22, 2016, 02:22:28 pm
Hi,
Updated my Vera Plus yesterday. It is now "semi bricked". It is not restarting but it is soooo slow. I did a factory reset (6 times reset) and it dropped of the login page. I could add it but it comes up as offline all the time.
Today I again tried factory reset with the same result. I have now connected a terminal via ssh and after like 20 minutes I am in. 10 minutes to get to the enter password, another 10 to get to the prompt. It is not disconnecting so it looks like something is slowing it down a lot.
Is there any way to re-flash it via the USB connector or in some other way get it back on track again?

//Helge
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: mfp on December 22, 2016, 03:17:05 pm
Hi,
Updated my Vera Plus yesterday. It is now "semi bricked". It is not restarting but it is soooo slow. I did a factory reset (6 times reset) and it dropped of the login page. I could add it but it comes up as offline all the time.
Today I again tried factory reset with the same result. I have now connected a terminal via ssh and after like 20 minutes I am in. 10 minutes to get to the enter password, another 10 to get to the prompt. It is not disconnecting so it looks like something is slowing it down a lot.
Is there any way to re-flash it via the USB connector or in some other way get it back on track again?

//Helge
Maybe yu could use the reset instruction from vesternet they give example commands for both telnet and commands for a browsersession:  http://www.vesternet.com/resources/application-notes/apnt-121 (http://www.vesternet.com/resources/application-notes/apnt-121)
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: helge@fabricius.nu on December 22, 2016, 03:38:39 pm
The APNT-121 instructions can not be used. SSH and html is timing out all the time.

//Helge
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: mfp on December 22, 2016, 04:19:17 pm


The APNT-121 instructions can not be used. SSH and html is timing out all the time.

//Helge

When it is so unstable I would advise you to contact support. Otherwise the next steps might help you to get in your vera, they were used on the previous veras but it might still work on VeraPlus. If it works you get on a clean prompt without all software loaded.

1. Connect your computer directly into the LAN port on the Vera unit (really not needed.  As long as both units are hard wired to same switch you just need to change your pc IP, cannot do this wireless)
2. Put a static IP on your computer (192.168.1.2) and the gateway 192.168.1.1 . You Can find
more information about it at step 8.
3. Plug the power adapter in Vera and when the led lights starts blinking, press and release
the reset button - led should be blinking
4. Open a command prompt and telnet into the unit: telnet 192.168.1.1

From the command promt you can give commands.

Title: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Wekurtz74 on December 23, 2016, 10:55:04 pm
I upgraded and have been getting numerous restarts, most noticeably between sundown and sunrise, on my veraplus.  Is there a way to rollback firmware ?


Sent from my iPad using Tapatalk
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: darthray on December 27, 2016, 02:03:10 am
I upgraded my VeraEdge.  It now is giving "Luup engine is taking longer to reload".  I cannot access the device. Let message to customer service and also emailed them.  Waiting on response.

I have the same problem but on a Vera 3 device. I've spent a few hours today trying to understand what's going on and all I can say is that the update to version 1.7.902 borked my Vera 3. I've reset the unit multiple times and the end result is the same: can't login because of the "Luup engine is taking longer to reload" problem. Mind you, I would sometimes get this error even before that but I was told by someone to clear my browser cookies and that mostly worked. Not this time though.

I'll contact support once they open again, but for now I'm trying to find a way to rollback to a previous firmware.

EDIT: by the way, the logs indicate that the Luup engine is exiting with code 16 over and over:

2016-12-26 22:47:20 - LuaUPnP Terminated with Exit Code: 16
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: alexk on December 27, 2016, 05:10:09 am
i also updated my vera plus recently to the new 1.7.2414 firmware.  There is a bug now when i create scenes with my thermostats where i cant set the temp any longer (assume it is firmware related). although it used to work now it reads the action of setting the temp during scene creation as a "custom action" (instead of set thermostat to 21 degrees) and it no longer works.

Trying to downgrade now but so far have failed twice.  (still on same firmware) anyone know the steps?

Alex
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: somthingobscure on December 27, 2016, 09:56:23 am
i also updated my vera plus recently to the new 1.7.2414 firmware.  There is a bug now when i create scenes with my thermostats where i cant set the temp any longer (assume it is firmware related). although it used to work now it reads the action of setting the temp during scene creation as a "custom action" (instead of set thermostat to 21 degrees) and it no longer works.

Trying to downgrade now but so far have failed twice.  (still on same firmware) anyone know the steps?

Alex

I am having the same issue with my Trane XR524 thermostat since the update.  I can change the temperature on the web interface, but not the iOS app.  On the iOS app, I can change the mode between heat/cool/off, but the temperature setting does not work.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Marc Shenker on December 27, 2016, 11:04:56 am
i also updated my vera plus recently to the new 1.7.2414 firmware.  There is a bug now when i create scenes with my thermostats where i cant set the temp any longer (assume it is firmware related). although it used to work now it reads the action of setting the temp during scene creation as a "custom action" (instead of set thermostat to 21 degrees) and it no longer works.

Trying to downgrade now but so far have failed twice.  (still on same firmware) anyone know the steps?

Alex

We are aware of the issue and the Mobile Apps Team is working on resolving it as soon as possible.

I am having the same issue with my Trane XR524 thermostat since the update.  I can change the temperature on the web interface, but not the iOS app.  On the iOS app, I can change the mode between heat/cool/off, but the temperature setting does not work.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: alexk on December 27, 2016, 11:24:52 am
Hi Marc happy holidays!

I have the mobile issue but my issue mentioned here is different.

I cant create scenes via web ui where the action is to set tenperature on the thermostat.
Didnt have this before
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: michaelhinchey on December 28, 2016, 02:19:07 pm
Does this release allow use of the amazon Echo or is that still in Beta?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: echino on December 28, 2016, 03:27:30 pm
After the latest firmware upgrade on my Vera Plus, I can no longer create or edit scenes containing Lua code with any special characters, like " quotation mark. Basically I lost any ability to use Lua code.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Spanners on December 29, 2016, 07:02:45 am
After the latest firmware upgrade on my Vera Plus, I can no longer create or edit scenes containing Lua code with any special characters, like " quotation mark. Basically I lost any ability to use Lua code.

After the upgrade I can no longer create any scenes at all. At the end of the scene creation wizard Vera finishes and the scene does not appear in the list.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: achfoo on December 29, 2016, 04:23:15 pm
Just chiming in to say I upgraded my VeraEdge for the first time and am now waiting to start an RMA.  :-\ I bought in mid-November and yesterday was the first time I noticed a prompt to update the firmware. Oh well.

Called customer service and he walked me through resetting and such to no avail. I could barely understand him, though, so I'm hoping there wasn't something lost in the language barrier. He said this has been a consistent issue for them, though. (Edit: The bricking has been consistent, not the language barrier! :D)

In other news, I enabled the Echo intergration before updating the firmware. I only have one dimmer switch on the network right now, but it worked great! :)
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: adustman on December 29, 2016, 08:00:36 pm
I went from a Vera3 to VeraPlus and lost associations, battery devices. All seemed fine initially, now my VeraPlus boots, then the wifi lights along with zigbee and bluetooth go out. I emailed help since 12-23, called numerous times - all without even a single ack. I'm quite frustrated with Vera support. BTW, who shall I bill for my Christmas lights getting stuck on for 4 days while I was away? Right now my VP is worthless. Doesn't do anything.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: treetop777 on December 30, 2016, 10:50:45 pm
Any success stories upgrading to the Vera Plus latest firmware (1.7.2414)?  My Vera Plus is running nicely right now and i wonder if there's any value-added to upgrading.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: marcjw on December 31, 2016, 07:55:30 am
Any success stories upgrading to the Vera Plus latest firmware (1.7.2414)?  My Vera Plus is running nicely right now and i wonder if there's any value-added to upgrading.

My Vera+ upgrade was seamless and went flawlessly.  Well, except for losing my rsa public keys but that was expected and happens every time.  If you aren't doing ssh from your Vera you won't have to worry about that.  The upgrade time was longer than normal - almost 15 minutes iirc - but everything came up fine.  As to value of upgrading for you, check out the Release Notes.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: 1937BCS on December 31, 2016, 10:20:57 am
Since the upgraded firmware install on my Vera Plus, my 5 countdown timers don't work. Support says they can see in the log that the counters reset, but they don't know why. Since it's a third party plugin I have to request a support ticket, and they'll look into it. That means, of course, nothing will be done! Anyone have a suggestion on how to replace the timers?

I'm not a programmer, but I looked into the PLEG plugin. Looks very confusing to me. And it doesn't look on my screen like it does in the instructions I've read. Guess that's why I'm not a programmer!
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: RichardTSchaefer on December 31, 2016, 01:38:42 pm
Sorry the docs and videos are for UI5 ... but the concepts are same ... the UI is different.

A single PLEG device can replace all of your countdown timers and combination plugins.

The need for multiple of these devices was a motivation for PLEG.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: treetop777 on December 31, 2016, 05:52:53 pm
Any success stories upgrading to the Vera Plus latest firmware (1.7.2414)?  My Vera Plus is running nicely right now and i wonder if there's any value-added to upgrading.

My Vera+ upgrade was seamless and went flawlessly.  Well, except for losing my rsa public keys but that was expected and happens every time.  If you aren't doing ssh from your Vera you won't have to worry about that.  The upgrade time was longer than normal - almost 15 minutes iirc - but everything came up fine.  As to value of upgrading for you, check out the Release Notes.

Thanks.  I'll just stay put this time (assuming this is not the release that supports Alexa) since this release doesn't have anything i need.  I just wish i could stop the UI7 from going to the upgrade section (notifying me there is an update available) every time i bring it up.

Thanks again.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: u20111223 on December 31, 2016, 11:52:51 pm
I updated my VeraPlus to 1.7.2414 this evening and noticed that the iOS Vera app no longer works.  I'm running iOS 10.2.1 and the app will open then flash away.  It's still running in the background but when you bring it back to the foreground it gets backgrounded as soon as the refresh is complete.  I tried uninstalling the app and reinstalling it with the same results.  I rebooted the controller and pulled the power with the same results.  I also cleared out the zwave logs and reloaded the engine and no luck.

Not really sure where to go from here apart from waiting on a new iOS app or firmware release to resolve the issue.  The web interface at home.getvera.com works fine.  I've also noticed that my scenes aren't working reliably any more after the upgrade.

Anyone else seen these problems on this version?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Spanners on January 01, 2017, 12:18:13 am
After the latest firmware upgrade on my Vera Plus, I can no longer create or edit scenes containing Lua code with any special characters, like " quotation mark. Basically I lost any ability to use Lua code.

After the upgrade I can no longer create any scenes at all. At the end of the scene creation wizard Vera finishes and the scene does not appear in the list.

Can't edit them. Can't delete them. Can't change any configuration. /sigh

So if I have anything that's wrong, I can't resolve it as the config just resets.

Maybe I have the ultimate stable Vera. It can never be changed so it can never go wrong.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: u20111223 on January 01, 2017, 02:08:07 am
How about editing user_data.json.lzo to see if that solves your problem?

Maybe something like this:

ssh root@my.vera.ip.address
mkdir ~/tmp
cp /etc/cmh/user_data.json.lzo ~/tmp
cd ~/tmp
pluto-lzo d user_data.json.lzo user_data.json.lzo.uncompressed
exit

scp root@my.vera.ip.address:/root/tmp/user_data.json.lzo.uncompressed
python -m json.tool user_data.json.lzo.uncompressed > user_data.json.lzo.uncompressed.json

// edit the file and take out characters
vi user_data.json.lzo.uncompressed.json
scp user_data.json.lzo.uncompressed.json root@my.vera.ip.address:/root/tmp/

ssh root@my.vera.ip.address
cd ~/tmp
pluto-lzo user_data.json.lzo.uncompressed.json user_data.json.lzo.changed
cp user_data.json.lzo.changed /etc/cmh/user_data.json.lzo
reboot;exit
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: u20111223 on January 01, 2017, 11:31:05 am
I'm back in good shape this morning.  I'm guessing it had something to do with time/leap seconds and when I coincidently chose to upgrade.

Thanks to @JoeTomasone for his time post that tipped me off.

http://forum.micasaverde.com/index.php/topic,41294.0.html

I updated my VeraPlus to 1.7.2414 this evening and noticed that the iOS Vera app no longer works.  I'm running iOS 10.2.1 and the app will open then flash away.  It's still running in the background but when you bring it back to the foreground it gets backgrounded as soon as the refresh is complete.  I tried uninstalling the app and reinstalling it with the same results.  I rebooted the controller and pulled the power with the same results.  I also cleared out the zwave logs and reloaded the engine and no luck.

Not really sure where to go from here apart from waiting on a new iOS app or firmware release to resolve the issue.  The web interface at home.getvera.com works fine.  I've also noticed that my scenes aren't working reliably any more after the upgrade.

Anyone else seen these problems on this version?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: rafale77 on January 01, 2017, 11:53:57 pm
Can't figure out what is going on. I am trying to edit a scene and indeed I keep getting a "failed to save system configuration".
I tried to edit another "test" scene and was able to save correctly. I even added some special characters to the LUA code and it saved fine.

Then I tried to copy and paste the Lua code from one scene to this test scene and now the "Save lua" button no longer works. If I delete the code and type anything else, it saves....

It looks like there is a specific part of the lua code which is causing problems. pasted it in the test Luup code and works fine.

I am guessing that a failsafe has been implemented to prevent corrupting characters but the result is that it is preventing the scene from being saved instead. Even if the current Lua code is valid, making any edits to the scene is causing it to check the code again. It's frustrating...

Edit:
I found it! I have an " ' " in one of the text strings preventing the scene from being saved.

Edit 2:
ok removing the apostrophe enables the "Save Lua code" button but somehow the scene still won't save and I am still getting the "failed to save system configuration"
Not sure if the beta FW had this problem. This is such an idiotic problem.

Edit 3:
Found the reason for the scene saving failure: It seems any trigger Lua code added to scene would prevent it from being saved.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Spanners on January 02, 2017, 01:13:18 am
How about editing user_data.json.lzo to see if that solves your problem?

Maybe something like this:

ssh root@my.vera.ip.address
mkdir ~/tmp
cp /etc/cmh/user_data.json.lzo ~/tmp
cd ~/tmp
pluto-lzo d user_data.json.lzo user_data.json.lzo.uncompressed
exit

scp root@my.vera.ip.address:/root/tmp/user_data.json.lzo.uncompressed
python -m json.tool user_data.json.lzo.uncompressed > user_data.json.lzo.uncompressed.json

// edit the file and take out characters
vi user_data.json.lzo.uncompressed.json
scp user_data.json.lzo.uncompressed.json root@my.vera.ip.address:/root/tmp/

ssh root@my.vera.ip.address
cd ~/tmp
pluto-lzo user_data.json.lzo.uncompressed.json user_data.json.lzo.changed
cp user_data.json.lzo.changed /etc/cmh/user_data.json.lzo
reboot;exit

Working through this, currently looking at my user_data.json.lzo.uncompressed in Notepad++ - problem now is just not knowing how to see what's messed up. Any pointers on what to look for?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: reneboer on January 02, 2017, 04:29:04 am
I'm in the same boat on my VeraLite. After the upgrade it worked fine, could save all my scenes with LUA without any issue. However, after some time not the start up LUA and now everything stopped. I have looked at the user_data, but nothing seems to stick out.  I have a ticket open, but only reply I got was to re-enable remote support, but that is still enabled.

So no solution for you, still waiting. Maybe have to install ALTUI again just to get it all working again. That worked for the last year when the Vera code was failing on saving.

Cheers Rene
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: u20111223 on January 02, 2017, 11:05:46 am
Working through this, currently looking at my user_data.json.lzo.uncompressed in Notepad++ - problem now is just not knowing how to see what's messed up. Any pointers on what to look for?

Looking at post #32 above it looks like there may be some characters that the new firmware doesn't deal with properly.  Maybe they changed character sets or started doing additional validation in this release.

Here's what mine look like and they work fine.  Of course the command to extract them from the pretty json file we created is line number specific to my file so you'd need to edit the file and see where your scenes start and end.  The "name" tags are what you would be looking for.  Make sure they don't have an special characters.  I have seen where single tick quotes are not the 0x27h single quote.  Verify with the ASCII table.

https://duckduckgo.com/?q=ascii+table&t=canonical&ia=web

sed -n '8150,8445p' user_data.json.lzo.uncompressed.json | grep -E 'modeStatus|name' | grep -v '                    '

            "modeStatus": "",
            "name": "Bathroom Fan Off",
            "modeStatus": "0",
            "name": "Bathroom Fan On With Light",
            "modeStatus": "0",
            "name": "Porch Light Off",
            "modeStatus": "0",
            "name": "Porch Light On",
            "modeStatus": "0",
            "name": "Outside Off",
            "modeStatus": "0",
            "name": "SinkLightOnWithKitchen",

Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: rafale77 on January 02, 2017, 08:03:39 pm
Out of despair, I ended up downgrading the FW to 1.7.1754 (7.0.13), made the edits and upgraded back.
Even the downgrade is very time consuming and tedious.
I had to unplug the ethernet during the initial bootup to prevent the unit from wanting to upgrade back to 1.7.2414.

It all works now but I can't say I am happy with how gross the bug is and how it could make it to a released FW version let alone 5 of them.

When your firmwares are so buggy, you shouldn't force people to upgrade and certainly make it so difficult to downgrade (force upgrade on bootup and force to reset all settings upon downgrade).
What should take 5 seconds to do (editing Lua codes) now takes hours and a lot of trickery.

Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: robie on January 07, 2017, 06:22:24 pm
Hi. Im encountering the following issues on the new firmware 1.7.2414. I've reconfigured my entire system and it's still the same. Issues are reported today to vera but im posting to warn those who will upgrade. Ofcourse, if the forum recommends a solution on the issues better.

1. The configurations doesn't always save to the device - ex. When i add a few devices as favorite devices, it will reflect in my dashboard for a short duration but when i refresh my browser, it will be removed again. This happens also when i change my yale deadbolt lock's pin code, when i added my smoke sensor and when i add scenes. The same problem if i change in my windows pc and android devices. This was most frustrating as it prolonged my reconfiguration to a whole day as i kept retrying to change settings and it randomly worked.

2. My aeon smart switch 6 stopped reporting energy consumption. Despite resetting device, unpairing and re-pairing, it still doesn't report my energy consumption since the new firmware.

3. My GoControl motion sensor stopped reporting motion detection. It also changed icon from "a circle with a man running that turns red when there is motion" to "a static mini motion detetector". I've also noticed that upon re-pairing it now adds a separate temperature sensor device which also doesn't work.

It was disappointing to upgrade firmware. Hope this is not the norm at vera or on smart home devices
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Pietor on January 09, 2017, 05:24:30 am
Out of despair, I ended up downgrading the FW to 1.7.1754 (7.0.13), made the edits and upgraded back.
Even the downgrade is very time consuming and tedious.
I had to unplug the ethernet during the initial bootup to prevent the unit from wanting to upgrade back to 1.7.2414.

It all works now but I can't say I am happy with how gross the bug is and how it could make it to a released FW version let alone 5 of them.

When your firmwares are so buggy, you shouldn't force people to upgrade and certainly make it so difficult to downgrade (force upgrade on bootup and force to reset all settings upon downgrade).
What should take 5 seconds to do (editing Lua codes) now takes hours and a lot of trickery.

I had exactly the same problem with the newest firmware, when saving lua code in a scene, it looked like it saved the scene, but in fact it gave a failed to save system configuration error. Downgraded to prvious version and then had to correct all my scene lua because it got corrupted (+ and % signs got replaced by random characters). After repairing, all is working fine again but still on older firmware. You upgraded to the newest firmware after this and now no problems?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: rafale77 on January 09, 2017, 11:01:15 am

I had exactly the same problem with the newest firmware, when saving lua code in a scene, it looked like it saved the scene, but in fact it gave a failed to save system configuration error. Downgraded to prvious version and then had to correct all my scene lua because it got corrupted (+ and % signs got replaced by random characters). After repairing, all is working fine again but still on older firmware. You upgraded to the newest firmware after this and now no problems?

Every firmware has at least one killer bug so it is a pick your poison problem. 7.0.13 enables me to edit and save scenes with LUA codes in the trigger section. 7.0.19 can't do this but is the only other firmware which enables saving special characters in the scene execution LUA code.
7.0.13 for me is excruciating slow and has tons of bug (no Zigbee etc). 7.0.19 is what I run until I have to create a scene with LUA in the trigger. Then I will downgrade again unless MCV fixes these bugs instead of adding new features between beta and official releases.

Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: YzRacer on January 11, 2017, 10:53:01 pm
I just got back in town and my Vera had been having issues on the July build so I went ahead with the latest upgrade. It turned into a 2 hour mind blowing experience, here are the details:

Never had a failed upgrade before, but there's a first time for everything. After 20 minutes of waiting I decided to give it a reboot. I gave it 40 minutes on that and just had the flashing power red/green along with USB lights blinking. I figured at this point it was a bust so I pulled it down and connected to the PC to reset.

Code: [Select]
flash_eraseall -j /dev/mtd7
sync
echo b > /proc/sysrq-trigger

This got me to a solid green light and an ssh connection to the 81.1 IP but no web interface. I got the failed to load page even with another reboot, and at one point it even rebooted itself. At this point I decided to get it back on the network and so I hooked up the WAN port and bam - I was able to load the web gui at the static IP (assigned in my router). Once it was up I had a welcome screen on the dashboard and no devices, as if it was reset completely. I checked the firmware page and saw it was on the latest version so I powered down and put it back where it normally sits.

Upon next reboot I logged in again and it was downloading some plugins. All of my devices were restored! Everything seems to be working so far, and I can only assume that once it finally booted on the new firmware that it runs a command to restore all the settings. I'm sure someone here can explain the technical details of how this happens.

Moral of the story is I'm glad I didn't reflash the firmware, and that even after using telnet to issue the reset commands it still managed to finish the upgrade and restore all of my configuration.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: robie on January 15, 2017, 02:14:19 am
 I have a relatively new installation and new to smart home devices. Does vera take action on the reported bugs here? What happens after we post the issues here? Does Vera monitor the boards?
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: RichardTSchaefer on January 15, 2017, 07:24:35 am
NO this is a user forum.
If you want Vera Support you need to contact them via email ... or better by phone.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: robie on January 15, 2017, 10:55:31 pm
NO this is a user forum.
If you want Vera Support you need to contact them via email ... or better by phone.

That's unfortunate, it could be better.  Atleast, let me warn other users on the current veraplus upgrade.  It has security risks among other non-functioning issues.  My veraplus switches modes by itself.  My experience is that it switches to Away Mode either from Home Mode or from Night Mode.  So my night mode security alarms were disabled already for several nights since the update.  Im also more worried that it will switch to Home mode or unlock the doors when it's not supposed to.

Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Don Phillips on January 16, 2017, 09:39:34 am
Perhaps you can set up a scene to notify you when Vera switches modes.  At least you will know about it and can change it back.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Khaztr on January 18, 2017, 04:02:14 pm
Phew, reading all this reminds me why I've learned to hold off upgrading to the latest major firmware release until after Vera releases the subsequent fix.  I'm sure you realize that all of you that upgraded are basically beta testers.  Thank you for your service!
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Sender on January 18, 2017, 04:46:32 pm
A long long time ago there was: http://micasaverde.com/my_view_page.php.

Now there is... mail.

Hard to keep track and the standard answer is "in the next firmware"
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: jlind on January 27, 2017, 09:37:53 am
Against my better judgement, I upgraded the firmware on my VeraPlus last night in an attempt to get a couple of new Ecolink sensors working.  After the hour long upgrade process, the sensors started working fine, but the luup engine has rebooted about 50 times in the last 8 hours. 

Here's the sweet part.  According to support, once you upgrade to this version of YOU CAN NOT DOWN GRADE!!!!! :o

He said the only thing I can do is put in a ticket and hope they resolve it.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: RichardTSchaefer on January 27, 2017, 09:40:49 am
You should be able to downgrade as long as your restore a backup that was from before the upgrade.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: jlind on January 27, 2017, 10:03:34 am
That's what I was thinking.  I have a local backup, but they also have backups.  I was amazed that the support guy would say that.  I usually have to call support while away from the device and not where I have my backup.  I was really hoping that they could just fix the problem and I could go on with my day, but that's not the case.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Marc Shenker on January 27, 2017, 10:35:34 am
I have a relatively new installation and new to smart home devices. Does vera take action on the reported bugs here? What happens after we post the issues here? Does Vera monitor the boards?

Robie, we do the best we can but the sheer volume of posts in the forum makes it beyond difficult. When we identify a thread like this we try to have someone in Customer Care keep an eye on it to record the issues and pass them on to the Development Team but we are not usually going to create a Customer Care ticket for you.

The best thing to do anytime you identify an issue with either a production build or a beta is to email Customer Care with your Remote Access code included so they can look into the issue and either resolve it for you, report it to the Development Team or both.

I am also available if you need me to intervene. My email is in my signature or you could PM me through the forum. I prefer email, it makes it easier for me to create a Customer Care ticket for you when I need to. There are many members of the forum who regularly contact me with issues. It is more efficient than hoping I see a post.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Marc Shenker on January 27, 2017, 10:54:37 am
One other thing. As we can't see everything that is posted in the forum, if anyone sees something that they feel should be brought to our attention please either send me a PM or email.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: jlind on January 27, 2017, 11:32:18 am
@Marc - the way the company uses this forum is extremely poor and inefficient.  First, when a firmware update is pushed out VERA should be creating a post stating what it is and inviting people to post their issues as responses.  Then your company should have the firmware development team, not just Customer Care, keep an eye on it to get a sense of what they've may or may not have introduced.

No offense, but after being on this forum for a few years it's apparent to me that NO firmware developers and likely NO company decision makers follow it.  It seems clear that Vera has its eyes on running a marathon, but is oblivious to the fact that its shoes are tied together.  These unstable firmware releases need to improve from about a 15% success rate to about a 98% success rate.

Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: rafale77 on January 27, 2017, 12:11:34 pm
Just to chime in: I take issues at the release strategy of these firmwares.

What are the betas for? test the build to iron out bugs after the addition of new features.

So each beta should be used to add features and released to us only after initial testing showed reasonable stability (alpha phase).
We, the customers who are willing, test and report bugs, and through different iterations you fix the bugs to the point where most of them are resolved and you can create a release build.
Then you restart the process on a new beta with new features etc etc...

I am seeing MCV doing completely the opposite. You have us a test a beta builds which then on the release comes with a ton of new features which create other bugs. Which then have fixes promised on the next betas. The result is that you have very unstable new releases. Firmware management has been a monstrous failure. I am tired of seeing new releases more unstable than the previous with new features of various level of usefulness added and apparently so are many other customers who have turned the veras into frisbees.
Having incompletely tested beta builds, I can understand, but releasing firmware with device killing bugs, which have been reported for months, not fixed and instead, adding a bunch of new device support or new features, such as ACM on this latest build, released between beta and release is what is killing you.
You should release betas also at a much higher rate with bug fixes only. You obviously have bugs being fixed but we have no idea why you want to have customer support manually implementing them to customers who complain as we hear about on this forum. The fixes should be in the beta build iterations where you experiment with new features.

Sorry for the grumbling but wanted to suggest improvements to your firmware development and release strategy.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Andrew on February 01, 2017, 04:53:32 pm
This beta is evil!

I installed in the hope of getting Alexa working in the UK. It didn't work. Instead, my Edge system started behaving erratically ( I don't have any of the WAPIRZ-1 either) The biggest problem was that the house mode kept switching back to night mode every 5 minutes by itself, arming certain PIR's and switching off lights and certain sockets. I couldn't find a way of stopping it. I tried disarming PLEG and other  plugins in case there was a compatibility problem but it kept re-arming every time night mode kicked in. agggh!

At this point, I was expecting a HAL-like voice to say "I'm sorry Dave, but I can't open the front door". My machine had taken over my house!
Interestingly I also got an email from Wunderground (weather plugin) alerting me that I had gone over my 501 calls in a 24 hr period. Can't have been a coincidence - guess it's a measure of how many times it's restarting the engine. Not only had my system trapped me in my house, but it now had an obsession in knowing what the weather was doing.

Fortunately I was able to roll back to the last release and everything started humming again...and HAL let me in through the front door :)
(Question - why was I able to roll back (seemingly successfully) to 1.7. 2406 when the guidance given is that this isn't possible?)

Just hope the full release, when it arrives, doesn't lead to this kind of experience again.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: rafale77 on February 02, 2017, 01:29:07 am
Seems like it is buggy at least on the edge and the WAPIRZ problem is not fully solved. I would report your problems to Customer support to make sure they fix it.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: Sender on February 02, 2017, 02:04:13 am
I have a relatively new installation and new to smart home devices. Does vera take action on the reported bugs here? What happens after we post the issues here? Does Vera monitor the boards?

Robie, we do the best we can but the sheer volume of posts in the forum makes it beyond difficult. When we identify a thread like this we try to have someone in Customer Care keep an eye on it to record the issues and pass them on to the Development Team but we are not usually going to create a Customer Care ticket for you.

The best thing to do anytime you identify an issue with either a production build or a beta is to email Customer Care with your Remote Access code included so they can look into the issue and either resolve it for you, report it to the Development Team or both.

I am also available if you need me to intervene. My email is in my signature or you could PM me through the forum. I prefer email, it makes it easier for me to create a Customer Care ticket for you when I need to. There are many members of the forum who regularly contact me with issues. It is more efficient than hoping I see a post.

Marc, bring back to life the  Mantis bugtracker. Good for you and good for us. But I fear this forum will be dead then  ;D.
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: CPrdam on February 02, 2017, 06:28:09 am
i am sometimes very critical on Vera but with the betas i think that  people are nor reading the guide lines.
Its says it in beta testing be careful. But what i think is better to have a group of beta testers and when
the testing done then a release. Because we are all impatient people  8)
Title: Re: UI7 ▾ Version 7.0.19 (1.7.902/1.7.2406/1.7.2414) ▾ December 12, 2016
Post by: reneboer on February 02, 2017, 08:45:35 am
I think they used to have a Beta group. Most seem to have moved to other platforms for various reasons.