Author Topic: UI7 ▾ Software Update ▾ Version 7.0.23  (Read 3234 times)

Offline rigpapa

  • Full Member
  • ***
  • Posts: 140
  • Karma: +21/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #30 on: October 16, 2017, 10:13:10 am »
I backed up (exported, thank you Richard) all of my PLEG, and copied my user_data, so everything is right there in XML and JSON (i.e. plain text) to rehydrate. The work isn't really in that part, it's in combing out all the device and scene number changes (creating the rooms in order gives you the same IDs, at least).

It's moot at the moment. Right after including my last four devices (here comes Murphy...), I unplugged the Vera and moved it back to its usual spot, plugged it in, and it came up lighting only the power LED--no MiOS, no ZWave. It had done this several times during the last couple of days as I moved around the house re-including everything (simple reboots worked then, but not this time), so I'm not sure if there's a flash problem with the unit, or if this new firmware has a fragile filesystem (it gets up far enough that I can ssh into it and see that it's griping about a missing filesystem in the logs). But, nearly four years on this platform, I've learned--I have backups all along the way. If I can get it back to fresh MiOS, I'm pretty sure I can recover gracefully. A six-in-six factory reset didn't change anything, though.

I'm waiting for Vera Support to get back to me, but at the moment, I'm bricked.

UPDATE: I was able to recover the unit on my own (/overlay filesystem corrupt, but boot scripts weren't detecting it and recovering/resetting; erased it and rebooted and MiOS reinstalled and all is well--if you know a little about setting up OpenWrt, this will make sense).
« Last Edit: October 16, 2017, 12:10:46 pm by rigpapa »
Author of Rachio, Deus Ex Machina II, SiteSensor, and Auto Virtual Thermostat plugins. Using Vera Plus (1.7.3232), Vera3 (1.7.855), 50 dimmers and 40 switches (mostly Leviton, some Linear and GE), a dozen sensors, a truckload of PLEG, and of course, my own plugins.

Offline Wekurtz74

  • Full Member
  • ***
  • Posts: 226
  • Karma: +3/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #31 on: October 21, 2017, 04:25:38 am »
I was able to upgrade without apparent issues.  However, later I realized that one of my remote switches for a 3 way switch was somehow turned into a master switch that turned on and off every light in the entire home. 
This is not the first time something like this has happened.  However, I have noticed an increase in random restarts/reloads.  I have not yet pulled a log,  it wanted to see if anyone else has seen it.  It reminds me of the motion sensor restart issue from last December. 


Sent from my iPad using Tapatalk

Offline rigpapa

  • Full Member
  • ***
  • Posts: 140
  • Karma: +21/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #32 on: October 21, 2017, 08:01:47 pm »
I wrote an external script to monitor Vera luup restarts, just to get something a bit better than casual observation. As of right now, I've had 7 restarts in about 8 hours. Not really clear as to why; still looking at the logs (WWN is very chatty).
Author of Rachio, Deus Ex Machina II, SiteSensor, and Auto Virtual Thermostat plugins. Using Vera Plus (1.7.3232), Vera3 (1.7.855), 50 dimmers and 40 switches (mostly Leviton, some Linear and GE), a dozen sensors, a truckload of PLEG, and of course, my own plugins.

Offline rigpapa

  • Full Member
  • ***
  • Posts: 140
  • Karma: +21/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #33 on: October 21, 2017, 08:31:44 pm »
OK. So this is perhaps interesting. My logs for every restart show this:

01   10/21/17 18:56:44.568      [[31;1mMongoose XXX-mg_stop1 0x129d520 1 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop2 0x129d520 2 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop3 0x129d520 2 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop4 0x129d520 13838224 3[[0m <0x77bb8320>
03   10/21/17 18:56:46.824      LuaUPNP: ending <0x77bb8320>

[[7;36m2017-10-21 18:56:46 - LuaUPnP Terminated with Exit Code: 0[[1;00m

---------------exited-------------


What I find interesting about it is that the exit code is 0, which in most systems means an intentional exit with no errors. The lines preceding it suggest to me that this is an intentional stop of Luup.

Immediately preceding this is a bunch of directory and process listings, and then, right before that, is this interesting sequence of events:

02   10/21/17 18:56:33.855     ZWaveNode::Wakeup did a poll for 137 1793 seconds interval 10800 existing (nil) heal (nil) <0x77004520>
04   10/21/17 18:56:41.686     <Job ID="122" Name="update nnu 137" Device="149" Created="2017-10-21 18:56:33" Started="2017-10-21 18:56:33" Completed="2017-10-21 18:56:41" Duration="7.831563000" Runtime="7.831333000" Status="Successful" LastNote=""/> <0x76a04520>
02   10/21/17 18:56:41.718     JobHandler::Run job#123 :Wakeup done 137 dev:149 (0x1835198) N:137 P:102 S:0 Id: 123 is 7.862865000 seconds old <0x76a04520>
04   10/21/17 18:56:41.806     <Job ID="123" Name="Wakeup done 137" Device="149" Created="2017-10-21 18:56:33" Started="2017-10-21 18:56:41" Completed="2017-10-21 18:56:41" Duration="7.950552000" Runtime="0.87735000" Status="Successful" LastNote="SUCCESS! Transmit was OK" Node="137" NodeType="ZWaveMultiEmbedded" NodeDescription="Lower Stair Motion"/> <0x77004520>
03   10/21/17 18:56:42.100     ZWaveJobHandler::QuitAfterThisJob 1/0 UPDATE_STATE_NEW_ID_ASSIGNED <0x77004520>
03   10/21/17 18:56:42.101     JobHandler_LuaUPnP::Reload: QuitAfterThisJob Critical 0 m_bCriticalOnly 0 dirty data 1 <0x76a04520>
03   10/21/17 18:56:42.111     ZWaveJobHandler::QuitAfterThisJob 1/0 UPDATE_STATE_NEW_ID_ASSIGNED <0x77004520>

01   10/21/17 18:56:42.774     UserData::WriteUserData saved--before move File Size: 143264 save size 143264 <0x76a0452
0>


Notice the highlighted (bold) messages. The "QuitAfterThisJob" is quite... curious... as is "...NEW_ID_ASSIGNED". The device in question is an Aeon 6 Multisensor. Coincidentally, in another thread, others have reported that some sensors (Aeon 6 Multis among the reports) have spontaneously had a "1" appended to their device names (this has happened to me as well). I wonder if the two events are somehow related? What could be going on with a stable, unmodified device that makes Luup think it needs to restart? What ID is being assigned, and why, because nothing seems to change?

Guess I'm opening a ticket with Vera Support on Monday.
« Last Edit: October 21, 2017, 08:37:53 pm by rigpapa »
Author of Rachio, Deus Ex Machina II, SiteSensor, and Auto Virtual Thermostat plugins. Using Vera Plus (1.7.3232), Vera3 (1.7.855), 50 dimmers and 40 switches (mostly Leviton, some Linear and GE), a dozen sensors, a truckload of PLEG, and of course, my own plugins.

Offline svaleb

  • Sr. Member
  • ****
  • Posts: 394
  • Karma: +7/-7
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #34 on: October 22, 2017, 04:22:25 am »
My vera plus make a startup evry time I open the vera page on my pc or phone after upgrade.
I have not tried that before.

Offline micasasucasa

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #35 on: October 22, 2017, 08:27:13 am »
Support are now aware of my/the port_49451 problem (affecting at least the Sonos and Powermax plugins) and their reply was:


Quote
Hello,
We are aware of this issue related to this port function and we reported this to our colleagues. At this moment they are working on this matter.
Thank you for your patience!


Offline macstibs

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #36 on: October 22, 2017, 12:18:55 pm »
I have two problems on a Plus that I upgraded last week:

1. Going back to the Firmware tab throws an error about the device being out of space

2. I have the same thermostat problem that someone else mentioned earlier in the thread - status appears frozen at what it was prior to the upgrade and there's no control available.

Ripping down the whole system and rebuilding (again) really isn't an option for me.  I love the system's extensibility and flexibility, but the software instability is a real problem.  It's a shame, I would love to continue supporting the company (the Plus is the third Vera system I've had), but I don't have two days to rebuild the system every time there's a glitch.

Offline AndrewM

  • Sr. Newbie
  • *
  • Posts: 47
  • Karma: +1/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #37 on: October 27, 2017, 11:37:54 am »
Anyone else lost the blue message bar that appeared on top of the web interface since this upgrade?

Me too, have been running for a week and had not noticed until I went to add a new ZOOZ water sensor and sure enough, no blue bar. Makes inclusion a bit tricky!

Offline rigpapa

  • Full Member
  • ***
  • Posts: 140
  • Karma: +21/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #38 on: October 27, 2017, 04:56:55 pm »
You can turn that back on by going to User & Account Info > Notifications Settings and turning on Notifications Header (Additional diagnostic and operational messages displayed).
Author of Rachio, Deus Ex Machina II, SiteSensor, and Auto Virtual Thermostat plugins. Using Vera Plus (1.7.3232), Vera3 (1.7.855), 50 dimmers and 40 switches (mostly Leviton, some Linear and GE), a dozen sensors, a truckload of PLEG, and of course, my own plugins.

Offline xeinth

  • Full Member
  • ***
  • Posts: 138
  • Karma: +1/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #39 on: October 29, 2017, 01:54:25 pm »
Anyone have the URL for 7.0.23 for the VP?  Unfortunately this new release is giving me some of the same problems, most notably lots off errors and weird behavior about running out of disk space (likely a permissions issue), and I cannot remove/modify any of my apps. 

Thanks

Offline Forzaalfa

  • Sr. Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #40 on: October 30, 2017, 07:31:20 am »
Im running the previous version (1.7.3015) now because i had some problems like you.

I downgraded using this link: http://dl.mios.com/rl/BETA/722/mt7621_Luup_ui7-1.7.3015-en-mios.squashfs

Offline AndrewM

  • Sr. Newbie
  • *
  • Posts: 47
  • Karma: +1/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #41 on: October 30, 2017, 07:13:40 pm »
You can turn that back on by going to User & Account Info > Notifications Settings and turning on Notifications Header (Additional diagnostic and operational messages displayed).
Perfect, that worked. Thank you so much.
Andrew

Offline michaelhinchey

  • Full Member
  • ***
  • Posts: 143
  • Karma: +2/-1
Re: Upgrade 1.7.3232 and 1.7.987
« Reply #42 on: October 30, 2017, 09:30:03 pm »
Vera plus is not working correctly after lastest firmware update. Scenes is not registering. Temperatures has frozen to the temperature before update. In my living room it says it is 27 but the temp is 22. So i got no heating in the house atm. Can't connect to vera from internet. When troubleshooting network it states that all is fine. But controller is offline. Restartet vera plus 3 times now. Think I have to resett to factory settings and upload a backup.


=== IP Configuration ===
br-wan    Link encap:Ethernet  HWaddr B4:A5:EF:E8:E0:73 
          inet addr:192.168.0.131  Bcast:192.168.0.255  Mask:255.255.255.0
eth0      Link encap:Ethernet  HWaddr B4:A5:EF:E8:E0:73 
eth0.2    Link encap:Ethernet  HWaddr B4:A5:EF:E8:E0:73 
          inet addr:127.0.0.1  Mask:255.0.0.0
========================
External IP: 82.194.207.147

=== Testing Gateway: 192.168.0.1 ===
.....
GATEWAY:OK
=== Testing DnsServer: 192.168.0.1 ===
.....
DNSSERVER1:OK
========================
=== Testing External Servers ===
.....
GOOGLE.COM:OK
.....
STA server: OK
.....
EVT server: OK
TS server tunnel connection: OK
.....
FWD server: network errors detected
FWD server tunnel connection: OK

=== SSH_TUNNELS: ===
Found 1 ssh sessions running
Remote Control Tunnels are running
== DONE ==
What was the outcome of this?  I think this is maybe what happened. Although I upgraded about 10 days ago.  I went in to add a scene and it stated it failed to write.  I rebooted AND RESET AND NOTHING.  Q

Offline Wekurtz74

  • Full Member
  • ***
  • Posts: 226
  • Karma: +3/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #43 on: October 31, 2017, 03:23:37 am »
OK. So this is perhaps interesting. My logs for every restart show this:

01   10/21/17 18:56:44.568      [[31;1mMongoose XXX-mg_stop1 0x129d520 1 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop2 0x129d520 2 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop3 0x129d520 2 3[[0m <0x77bb8320>
01   10/21/17 18:56:46.569      [[31;1mMongoose XXX-mg_stop4 0x129d520 13838224 3[[0m <0x77bb8320>
03   10/21/17 18:56:46.824      LuaUPNP: ending <0x77bb8320>

[[7;36m2017-10-21 18:56:46 - LuaUPnP Terminated with Exit Code: 0[[1;00m

---------------exited-------------


What I find interesting about it is that the exit code is 0, which in most systems means an intentional exit with no errors. The lines preceding it suggest to me that this is an intentional stop of Luup.

Immediately preceding this is a bunch of directory and process listings, and then, right before that, is this interesting sequence of events:

02   10/21/17 18:56:33.855     ZWaveNode::Wakeup did a poll for 137 1793 seconds interval 10800 existing (nil) heal (nil) <0x77004520>
04   10/21/17 18:56:41.686     <Job ID="122" Name="update nnu 137" Device="149" Created="2017-10-21 18:56:33" Started="2017-10-21 18:56:33" Completed="2017-10-21 18:56:41" Duration="7.831563000" Runtime="7.831333000" Status="Successful" LastNote=""/> <0x76a04520>
02   10/21/17 18:56:41.718     JobHandler::Run job#123 :Wakeup done 137 dev:149 (0x1835198) N:137 P:102 S:0 Id: 123 is 7.862865000 seconds old <0x76a04520>
04   10/21/17 18:56:41.806     <Job ID="123" Name="Wakeup done 137" Device="149" Created="2017-10-21 18:56:33" Started="2017-10-21 18:56:41" Completed="2017-10-21 18:56:41" Duration="7.950552000" Runtime="0.87735000" Status="Successful" LastNote="SUCCESS! Transmit was OK" Node="137" NodeType="ZWaveMultiEmbedded" NodeDescription="Lower Stair Motion"/> <0x77004520>
03   10/21/17 18:56:42.100     ZWaveJobHandler::QuitAfterThisJob 1/0 UPDATE_STATE_NEW_ID_ASSIGNED <0x77004520>
03   10/21/17 18:56:42.101     JobHandler_LuaUPnP::Reload: QuitAfterThisJob Critical 0 m_bCriticalOnly 0 dirty data 1 <0x76a04520>
03   10/21/17 18:56:42.111     ZWaveJobHandler::QuitAfterThisJob 1/0 UPDATE_STATE_NEW_ID_ASSIGNED <0x77004520>

01   10/21/17 18:56:42.774     UserData::WriteUserData saved--before move File Size: 143264 save size 143264 <0x76a0452
0>


Notice the highlighted (bold) messages. The "QuitAfterThisJob" is quite... curious... as is "...NEW_ID_ASSIGNED". The device in question is an Aeon 6 Multisensor. Coincidentally, in another thread, others have reported that some sensors (Aeon 6 Multis among the reports) have spontaneously had a "1" appended to their device names (this has happened to me as well). I wonder if the two events are somehow related? What could be going on with a stable, unmodified device that makes Luup think it needs to restart? What ID is being assigned, and why, because nothing seems to change?

Guess I'm opening a ticket with Vera Support on Monday.

I recently added an Aeon 6 multi sensor.  Perhaps this is part of my issue.  I still haven't had the time to pull a log to check it out.  Please let us know what support does to help you.


Sent from my iPad using Tapatalk

Offline elo

  • Sr. Newbie
  • *
  • Posts: 40
  • Karma: +0/-0
Re: UI7 ▾ Software Update ▾ Version 7.0.23
« Reply #44 on: November 01, 2017, 10:04:42 pm »
I have two Veras one Vera 3 and one Vera Pluss. The Vera 3 upgraded ok but the Vera Pluss presented the setup screen for a new controller when it came back online. I restored the backup taken just before the upgrade (I did not downgrade the firmware) and after a power cycle it seems OK.

The previous update was skipped and I had to downgrade again because my PLEG's dissapeared. My trust in Vera is at a very low level at the moment....