The Vera Community forums have moved!

Beta and Pre-Release (Public) => Beta Testing (Public) => Topic started by: micasaverde on April 20, 2011, 01:36:44 pm

Title: 1.1.1245 beta available for general testing
Post by: micasaverde on April 20, 2011, 01:36:44 pm
There are 58 users currently on the new beta, mostly our private beta tester group.  It has passed our internal tests.  We have 1 report of a user having problem, but there's no indication yet that his issue is related to the firmware.  So we're making it available to the general community.

If there are no confirmed regressions we'll make it an official upgrade from 1.1.1047 soon.

To try out the beta, visit http://micasaverde.com/vera2?beta=1 from a computer on the same network as Vera, and it will upgrade it.

If you have any regressions, please post them to this thread.
Title: Re: 1.1.1245 beta available for general testing
Post by: robinnes on April 20, 2011, 02:24:59 pm
Changelog from 1.1.1234?
Thanks!
Title: Re: 1.1.1245 beta available for general testing
Post by: Ap15e on April 20, 2011, 04:03:41 pm
Two Veras, V1@1.1.1186 and V2@1.1.1243 ...
Title: Re: 1.1.1245 beta available for general testing
Post by: Ap15e on April 20, 2011, 05:01:50 pm
Seems to work now ...
Title: Re: 1.1.1245 beta available for general testing
Post by: MNB on April 20, 2011, 09:49:18 pm
Changed from 1.1.1234 with no problems. Notice that my Log tabs on my Kiwkset locks are blank they were blank for 1234 also, was hoping that it would be fixed.
Title: Re: 1.1.1245 beta available for general testing
Post by: aschwalb on April 20, 2011, 09:53:32 pm
All looks good here Leviton Controllers and Ge Dimmers happily communing together...  :P
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on April 20, 2011, 11:00:24 pm
Changed from 1.1.1234 with no problems. Notice that my Log tabs on my Kiwkset locks are blank they were blank for 1234 also, was hoping that it would be fixed.

My Schlage locks sometimes wouldn't show logs as well then they would just show up and go away as they please.
Title: Re: 1.1.1245 beta available for general testing
Post by: markbawden on April 21, 2011, 04:20:51 am
Does anyone have the direct url for vera 1 update? I want to install remotely.
Title: Re: 1.1.1245 beta available for general testing
Post by: micasaverde on April 21, 2011, 11:59:30 am
Quote
Notice that my Log tabs on my Kiwkset locks are blank they were blank for 1234 also, was hoping that it would be fixed.

It's by design.  The Logs tab on UI4 only had a few recent entries, whereas the real, permanent list is in your cp.mios.com account.  There were complaints that having this in 2 places was too confusing.  See the http://wiki.micasaverde.com/index.php/Release_Notes, #99.
Title: Re: 1.1.1245 beta available for general testing
Post by: myhomeserver on April 21, 2011, 12:15:31 pm
I have some issues where events are not showing up on CP.Mios.com. I realize they are no longer in the tabs, but why do some events such as Schlage door lock open/closing doesn't show on one of my locks, yet it shows on the other?

How do we debug why one lock works and others don't? 

Title: Re: 1.1.1245 beta available for general testing
Post by: MNB on April 21, 2011, 01:19:01 pm
Thanxs for update @micasaverde, kind of missed that one ::), However after reviewing CP. MiOS.com events I do not see any lock/unlock events which by the way happens several times a day (if per chance I'm reviewing My miOS screen and a lock/unlock event occurs I do see that event message text under the specific lock device and it does indicate correctly e.g. Person Unlocked.

Also within the CP.MiOS.com event calendar on days that are bold I get the following message "Not Found The requested URL /luup-events.php was not found on this server." when selected. More clues please!
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on April 21, 2011, 02:56:18 pm
Thanxs for update @micasaverde, kind of missed that one ::), However after reviewing CP. MiOS.com events I do not see any lock/unlock events which by the way happens several times a day (if per chance I'm reviewing My miOS screen and a lock/unlock event occurs I do see that event message text under the specific lock device and it does indicate correctly e.g. Person Unlocked.

Also within the CP.MiOS.com event calendar on days that are bold I get the following message "Not Found The requested URL /luup-events.php was not found on this server." when selected. More clues please!

Same here the Events have never worked for me and I get the Not Found page when clicking on the event just like you but I have not tried it with the newest firmware yet so we'll see.

Title: Re: 1.1.1245 beta available for general testing
Post by: Grain on April 21, 2011, 04:01:56 pm
I am also having issues switching to 3.20
I performed the firmware upgrade to 1.1.1245 locally through the link that was provided, then went into settings and switched to 3.20, saved, waited 3 minutes and checked back...
tried switching back and forth without result..

btw. thanks for the update, it looks like you guys fixed a lot of things and made some nice changes!
Title: Re: 1.1.1245 beta available for general testing
Post by: computerjohn on April 22, 2011, 12:07:30 am
Well, upgraded tonight.  So far so good..  Is there a list of the new changes & fixes?
Title: Re: 1.1.1245 beta available for general testing
Post by: computerjohn on April 22, 2011, 12:13:10 am
Quick question, what size USB thumb drive should I use for keeping tracks of logs in Vera & what is the limit Vera can use are storage size?
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 22, 2011, 12:26:22 am
Is there a list of the new changes & fixes?
As always (http://wiki.micasaverde.com/index.php/Release_Notes). Relative to .1047.
Title: Re: 1.1.1245 beta available for general testing
Post by: computerjohn on April 22, 2011, 12:41:16 am
Thanks oTi,

It's showing all the changes in 1.1.1245, wow 99 changes...

Is there a list of the new changes & fixes?
As always (http://wiki.micasaverde.com/index.php/Release_Notes). Relative to .1047.
Title: Re: 1.1.1245 beta available for general testing
Post by: GT! on April 22, 2011, 07:33:47 am
It's not finding my Vera1 (fw .1183) even though I'm on the same network.  I can reach it through cp.mios.com.

Edit: Never mind ... I had a VPN session open that I had ended it but it still wouldn't work until I closed all of my browser windows.  Upgrade went fine  :).

-GT
Title: Re: 1.1.1245 beta available for general testing
Post by: computerjohn on April 22, 2011, 08:11:12 am
To my understanding, this update is for Vera 2. 
Title: Re: 1.1.1245 beta available for general testing
Post by: tt55du on April 22, 2011, 09:48:03 am
Is there a list of the new changes & fixes?
As always (http://wiki.micasaverde.com/index.php/Release_Notes). Relative to .1047.

Just confirming, is the z-wave fw only for vera2? and not the aeon labs dongle in vera1?
Title: Re: 1.1.1245 beta available for general testing
Post by: wseverino on April 22, 2011, 10:19:55 am
Correct only Vera 2 supports the Z-wave update.
Title: Re: 1.1.1245 beta available for general testing
Post by: tbever on April 22, 2011, 01:48:57 pm
Where is the option to upgrade the zwave firmware from 2.78 to 3.20?  I read the wiki below and I think it is supposed to be under the options tab of the Z wave device menu in toolbox, but I don't see it there.  I just upgraded the vera firmware to 1.1.1245.

http://wiki.micasaverde.com/index.php/MigrateTo452
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 22, 2011, 01:52:52 pm
Where is the option to upgrade the zwave firmware from 2.78 to 3.20?  I read the wiki below and I think it is supposed to be under the options tab of the Z wave device menu in toolbox, but I don't see it there.  I just upgraded the vera firmware to 1.1.1245.
Yep, should be there. Second check box ("Use Z-Wave version 3.20 instead of 2.78").
Title: Re: 1.1.1245 beta available for general testing
Post by: tbever on April 22, 2011, 02:05:51 pm
I think it must have been a cache issue on chrome.  I can see it when I log in from another computer.  Thanks!
Title: Re: 1.1.1245 beta available for general testing
Post by: Grain on April 22, 2011, 04:36:23 pm
well.. I have a V2 and been changing the settings back and forth, saving and waiting 2 minutes but without luck...
tried again today but result is the same.. stuck at 2.78

any tips?
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on April 22, 2011, 05:03:25 pm
well.. I have a V2 and been changing the settings back and forth, saving and waiting 2 minutes but without luck...
tried again today but result is the same.. stuck at 2.78

any tips?

(condensending voice on) Wait for the next firmware version when they fix it.
Title: Re: 1.1.1245 beta available for general testing
Post by: tejchicago on April 22, 2011, 06:15:07 pm
Uh oh, just upgraded.  Looked like everything was going smooth but now have a red "ZWave: Failed to Start" status.

Did do a backup just prior to upgrading,  can/should I go back to that ?   Other suggestions, kind of dead in the water otherwise.

thx
Title: Re: 1.1.1245 beta available for general testing
Post by: micasaverde on April 22, 2011, 08:00:25 pm
I see some users report problems going to 3.20.  Understand this is only for Vera 2.  Not Vera 1.  I just updated the wiki to be sure this is clear: http://wiki.micasaverde.com/index.php/MigrateTo452

Hopefully the reported 3.20 upgrade failures were caused by this.

tejchicago, would you mind turn on the tech support tunnel (advanced, tech support, enable it) and emailing your code to: aaron [at] mios dot com?  I can see your ZWave won't start.
Title: Re: 1.1.1245 beta available for general testing
Post by: ctbaker on April 22, 2011, 09:22:16 pm
I noticed that the passcode for my Kwikset lock no longer shows up as (****) but now shows the actual code (i.e. (1234)) which I rather it not do just in case the connection to the Vera2 got hacked. I only have one code assigned to the lock at this time.

I'll try to exclude the lock, reset it, assign a new passcode and re-include it to the Vera2 and see if that fixes it and then report back.

Thanks!
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 22, 2011, 09:50:46 pm
I noticed that the passcode for my Kwikset lock no longer shows up as (****) but now shows the actual code[...]
Is this option checked on the Control tab of the lock by any chance: "Keep a copy of my PIN codes so that I can view them later"?
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on April 22, 2011, 11:31:16 pm
If you un-check the box "Keep a copy of my PIN codes so that I can view them later" they will disappear and won't come back if you recheck the box. Only newly set codes will appear from that point on. I like that it shows the codes and I think it would be easier for someone to figure out the 4 digit code on the lock than the 14 letter and number code I have to get into Vera. I could see it being useful if you have someone else as a user and you don't want them to be able to use a code that isn't theirs.
Title: Re: 1.1.1245 beta available for general testing
Post by: futzle on April 23, 2011, 01:06:03 am
Understand this is only for Vera 2.  Not Vera 1.  I just updated the wiki to be sure this is clear:

When you say "only for Vera2", do you mean "only for Vera2 when using its internal Z-Wave chip"?  Recall that some of us are using a Vera2 with an external USB Z-Wave dongle*, and it isn't at all clear whether this configuration is upgradeable to 3.20 yet or not.

(This is largely academic; Z-Wave devices are far too expensive here for me to own more than a few of them, and my puny 5-device network has no issues, so I'm not going to deliberately break things.)

Upgrade to 1.1.1245 was seamless, to get this post back on topic.

* Not by choice, I might add.  This configuration is the only one that is available in markets that use the 919.82 MHz and 921.42 MHz frequencies.
Title: Re: 1.1.1245 beta available for general testing
Post by: Grain on April 23, 2011, 01:53:26 am
power cycling my Vera 2 seems to have solved the "issue"
now it's on 3.20

did a reset of my network but my device (only have 1 for now :) ) was still there, also after a power cycle..
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on April 23, 2011, 03:25:20 am
I just tested the .1245 with current schlage lock events on mios and when clicking an event on the calendar it still comes up with "Not Found - The requested URL /luup-events.php was not found on this server." Worse yet they don't show up on the logs now either. At least before they sometimes showed up in the logs.
Title: Re: 1.1.1245 beta available for general testing
Post by: hbarnett on April 23, 2011, 09:13:44 am
i just did the upgrade.  It was flawless.  I was immediately ableto delete a sensor i had been able to remove.  great job MiCasaVerde, 
Title: Re: 1.1.1245 beta available for general testing
Post by: pgrover516 on April 23, 2011, 01:25:47 pm
I see some users report problems going to 3.20.  Understand this is only for Vera 2.  Not Vera 1.  I just updated the wiki to be sure this is clear: http://wiki.micasaverde.com/index.php/MigrateTo452

Hopefully the reported 3.20 upgrade failures were caused by this.
Just to clarify (someone correct me if I'm wrong here) the 1245 firmware is fine for vera 1 and 2, but you can not upgrade vera1 (within the 1245 firmware) to the 3.20 branch of zwave. This may well also be true for Vera2 users working off an external dongle. Vera 1 can only make that leap if a new dongle firmware flash is put out by Aeon labs. If there are folks waiting restlessly for Vera 1 upgrade let MCV/Aeon labs know it.   8)
Title: Re: 1.1.1245 beta available for general testing
Post by: Radjin on April 23, 2011, 08:15:26 pm
I am finding that when I power the vera with the fully charged battery pack to go around and add devices, that I can add four before the z-wave light goes out and accepts no more additions. Probably not a big problem as one rarely adds that many at once.  Just saying...
Title: Re: 1.1.1245 beta available for general testing
Post by: Les F on April 24, 2011, 07:14:27 am

upgrade to 1245 and zwave 3.20 (using hack to convert 2.78 to 3.20) worked flawlessly!
Yay..... (I am usually the problem child when it comes to upgrades).  Not a single problem doing either one.

Title: Re: 1.1.1245 beta available for general testing
Post by: Intrepid on April 24, 2011, 08:27:54 am
I just upgraded from 1234 with no problems.  Everything seems to be working fine!

Title: Re: 1.1.1245 beta available for general testing
Post by: zener on April 24, 2011, 03:10:15 pm
just updated, smooth process, no problems
Title: Re: 1.1.1245 beta available for general testing
Post by: iflyM3 on April 24, 2011, 06:28:47 pm
Quick question on the Beta 1.1.1245 for anyone who might know.

Does anyone know if MiCasaVerde ever resolved the issue with trying to add secondary controllers such as the HA07, and HA09 to Vera after upgrading to 3.20 Z FW and using the previous beta?  I was having an issue trying to readd my Harmony 890Pro as a secondary controller.  A problem that was a similar when trying to add either of the HA's as a secondary controller.   I guess I could always try it again and see then report back later.  lol.  I just wanted to see if anyone might know.   Thanks.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 24, 2011, 07:35:28 pm
[...]resolved the issue with trying to add secondary controllers such as the HA07[...] having an issue trying to readd my Harmony 890Pro as a secondary controller.
HA07 include / re-includes fine for me. Have not tried AVL300.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on April 24, 2011, 08:41:53 pm
#12xxx running 1.1.1245
4/24/11 @ ~ 19:30:00
Unresponsive for ~ 5 minutes but recovered on it's own.

Code: [Select]
CPU:   0% usr  99% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 23.69 17.82 8.62 6/63 17669

*Edit.
Another incident:
4/25/11 @ ~ 18:00:00
Code: [Select]
CPU:   7% usr  90% sys   0% nic   2% idle   0% io   0% irq   0% sirq
Load average: 4.06 11.23 7.79 4/62 18525
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
    4     1 root     SW       0   0%   5% [kswapd]
18452 18451 root     S     1500   5%   5% /bin/ash /usr/bin/Report_AP.sh
25630 25445 root     R     1440   5%   1% top
    8     1 root     SW       0   0%   1% [mtdblockd]
17918 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17917 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
25423  2082 root     S     1200   4%   0% /usr/sbin/dropbear -p 22 -P /var/run/
17837  2165 root     S    19808  65%   0% /usr/bin/LuaUPnP
17912 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17883 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17885 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
18107 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17940 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17939 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17937 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17938 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
18524 17883 root     D    19808  65%   0% /usr/bin/LuaUPnP
17951 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17882 17837 root     S    19808  65%   0% /usr/bin/LuaUPnP
17935 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
Mem: 29824K used, 716K free, 0K shrd, 780K buff, 4140K cached
CPU:  15% usr  82% sys   0% nic   2% idle   0% io   0% irq   0% sirq
Load average: 4.30 11.16 7.79 4/61 18525
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
18523 18452 root     R     3432  11%  63% curl -k -s -S -f https://sta1.mios.co
18107 17882 root     R    19808  65%  10% /usr/bin/LuaUPnP
17883 17882 root     D    19808  65%   4% /usr/bin/LuaUPnP
    4     1 root     RW       0   0%   3% [kswapd]
25630 25445 root     R     1440   5%   1% top
    8     1 root     SW       0   0%   1% [mtdblockd]
17917 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
25423  2082 root     S     1200   4%   0% /usr/sbin/dropbear -p 22 -P /var/run/
17798 17705 root     S     1204   4%   0% ssh -y -T -p 232 -i /etc/cmh/ra_key -
17837  2165 root     S    19808  65%   0% /usr/bin/LuaUPnP
17912 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17885 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17940 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17939 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17918 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17938 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17937 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17951 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17935 17882 root     S    19808  65%   0% /usr/bin/LuaUPnP
17882 17837 root     S    19808  65%   0% /usr/bin/LuaUPnP

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 6464      6464         0 100% /rom
tmpfs                    15268      1092     14176   7% /tmp
/dev/mtdblock/4           9088      5048      4040  56% /overlay
mini_fo:/overlay          6464      6464         0 100% /
/dev/scsi/host0/bus0/target0/lun0/part1
                        516024     25896    463876   5% /tmp/log/cmh
/dev/loop/0               3072      3072         0 100% /mios

*Edit. Rebooted and everything was back to normal.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on April 25, 2011, 12:15:35 am
#12xxx running 1.1.1245
4/24/11 @ ~ 19:30:00
Unresponsive for ~ 5 minutes but recovered on it's own.

CPU:   0% usr  99% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 23.69 17.82 8.62 6/63 17669

JOD.

USB, or not to USB, that is the question?

I noticed that my USB key had "fallen out" over the last week.  I had similar unresponsiveness as it had silently fallen back to not using it (and my Vera is max'd)

I put a new one in today and it's running fine again.

When you see this, you can run "top" to see what's actually running (although SYS CPU% isn't always attributed correctly).  Also run "df -k" to see if any Filesystems are full.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on April 25, 2011, 10:02:02 am
Quote
USB, or not to USB, that is the question?
Alas, poor Yorick the USB key was connected, but good point, it could have been a been a read/write issue and an indication it's going bad. I'll change it out just in case. I did have top running and could only account for 72%  sys of the 99% reported.

It's been running really well lately.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: dkeefe on April 25, 2011, 10:31:45 am
Issues with 1245 and the multiwave pool controller (firmware 31):

1. vera still doesn't correctly show on/off status for the circuits. if circuit 1 is on, then it reports all 5 circuits on. if circuit 1 is off, it shows all 5 circuits off.

2. still can't set heater temp

3. still can't view water and air temp

4. main controller still shows turn on and off buttons, although these buttons don't do anything.

Title: Re: 1.1.1245 beta available for general testing
Post by: marcoose on April 25, 2011, 07:58:37 pm
Is anyone having trouble with Kwikset locks?  I am noticing that when I set up new pins, they seem to "take" fine in the UI and I get the green upper corner on the lock when setting them, but none of them work on the actual lock keypad.  I also find that when I press unlock/lock in UI4 I get a green "transmit OK" tag and the lock does the correct action, but the green highlighted button never changes (i.e. if Unlock is green, and I click Lock, it actually does lock and the screen shows transmit ok, but the Unlock button stays highlighted green).
Title: Re: 1.1.1245 beta available for general testing
Post by: achalhoub on April 26, 2011, 02:15:15 am
does anyone knows the link to download the latest firmware (1.1.1245)? my Vera2 does not work with the link provided
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on April 26, 2011, 02:34:56 am
http://download.mios.com/backfirebetafirmware/wl500gP_Luup_ui4-1.1.1245-1.squashfs
Title: Re: 1.1.1245 beta available for general testing
Post by: achalhoub on April 26, 2011, 02:54:23 am
Thank you strangely, you are a life saver
Title: Re: 1.1.1245 beta available for general testing
Post by: kalleochvera on April 27, 2011, 04:32:36 pm
The upgrade to 1.1.1245 happened without drama. :-) But, when I want to upgrade the z-wave firmware I read " Use 4.5 branch of Z-Wave (U.S. Vera2 only and not stable)".
Is this correct? The new z-wave firmware is only for U.S.? (I'm running a EU Vera2)
The Wiki doesn't say anything about "U.S. only". ???
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on April 27, 2011, 06:26:20 pm
Correct, US only at this time!
Title: Re: 1.1.1245 beta available for general testing
Post by: scotthay on April 27, 2011, 09:42:47 pm
If the electric goes out and comes back on causing Vera to reboot and then on reboot the internet is down and it cannot set the clock.  With Vera ever realize this and set the time again, or will it be stuck in some random date/time forever until manually rebooted again?

Title: Re: 1.1.1245 beta available for general testing
Post by: grybrd on April 27, 2011, 11:01:15 pm
Happy camper here ... just upgraded to UI4 1245 from UI3 which has run error free for over a year.   It works!!!!   Thanks to all the the beta testers and MCV  for developing a release I can finally trust  ;D
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on April 28, 2011, 12:09:37 am
If the electric goes out and comes back on causing Vera to reboot and then on reboot the internet is down and it cannot set the clock.  With Vera ever realize this and set the time again, or will it be stuck in some random date/time forever until manually rebooted again?


Stuck until the next reboot I believe! You can experiment if you like! :)
Title: Re: 1.1.1245 beta available for general testing
Post by: pncortes on April 28, 2011, 09:03:29 am
Just upgraded to 1.1.1245 and some strange things are happening:

1 - Just like tejchicago, it shows a message ZWave: Failed To Start
2 - Tried enabling Tech Support, it sais Operation Successful, but does not enable it
3 - Tried to telnet, but no success (on previous versions it was working)
4 - Tried SSH with the password on the bottom of Vera, also didn´t accept the password
5 - Tried going to advanced network configuration, but also asks for root password

I did the upgrade reseting to factory defaults.

For now, I will try to go back to the previous version I was using, 1.1.1047.
Title: Re: 1.1.1245 beta available for general testing
Post by: harphaulingdad on April 28, 2011, 01:11:10 pm
Just upgraded, and have an error message [24]: Startup Lua Failed, which did not exist prior to the upgrade. Any thoughts on what I should do to correct this? Thanks.
Title: Re: 1.1.1245 beta available for general testing
Post by: S-F on April 28, 2011, 01:19:49 pm
Just upgraded, and have an error message [24]: Startup Lua Failed, which did not exist prior to the upgrade. Any thoughts on what I should do to correct this? Thanks.

Yeah I just tried to upgrade and got [7]: Startup Lua Failed. What's up with this?
Title: Re: 1.1.1245 beta available for general testing
Post by: holger_40 on April 28, 2011, 04:06:07 pm
I just upgraded from 1.1.1047.  I unpaired all of my devices prior as I was unsure whether I would have to unpair them all again after doing a network reset then pairing them all up again.  Well, the install itself went ok: The PRI: NO was still showing but it did state I was on the new branch at least.  Then I tried to do a Reset Z-wave Network as stated in the wiki.  The soft reset did not work using the button on the gui.  I tried a hard reset by hitting the reset button twice in quick succession; did not work.  Tried 3 taps of the button, also without success.  Eventually went back to the gui and clicked the "hack" button because why not, what have I got to lose?  After that I was able to get a reset of the network, then paired up all devices again.

Short time yet on the new firmware but all else appears to be stable.
Title: Re: 1.1.1245 beta available for general testing
Post by: harphaulingdad on April 28, 2011, 04:59:02 pm
I unplugged my Vera instead of just rebooting, and the [24] Startup message disappeared. Go figure.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 29, 2011, 10:37:08 am
The LED control for Leviton zone/scene controllers appears to be a one-way street.

Once the SetLight interface has been used, there is no return to native, internal Leviton-control. Not even after a factory-default reset of the controller (i.e. buttons 1+3 until blinking red). The last LED pattern will persist indefinitely.

Assume: network V (Vera as primary), network L (Leviton VRCPG as primary), controller C (Leviton scene/zone -MR/-M0), dimmer D (Leviton).
- Include D into L.
- Include C into L.
- 2-way associate C and D.
- Turn on/off D.
=> LEDs as expected.

- Exclude C from L.
- Include C into V (auto-configure: off).
- Use SetLight API to set button 2 green, button 3 red, button 4 amber.
=> LEDs as expected.

- Exclude C from V.
=> LEDs off.

- Factory-reset C.
=> LEDs off.

- Include C into L.
- 2-way associate C and D.
- Turn on D (locally, or through C).
=> LED button 1 off, button 2 green, button 3 red, button 4 amber.

=> Ticket 1476 (http://bugs.micasaverde.com/view.php?id=1476).

(Note 1: this is just to show the pattern is the last one programmed; similarly, turning all LEDs off before excluding from V, would result in all LEDs being off indefinitely when included into L.)
(Note 2: scene/zone control works, i.e. it's just the LEDs. But on scene controllers the color of the LED also determines the state of the scene, so a scene can only be turned on, or off (not both).)
Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on April 29, 2011, 11:55:43 am
Vera2 Firmware 1.1.1245,  Z-Wave Firmware 3.20 - UPGRADE REPORT.
I am posting this in the hopes that it may help someone else and for the development team to investigate.
The 1245 firmware installs fine.  You then have a new set of Options under that tab in Toolbox - ZWave Device.  One of these is to check a radio button to use the new 3.20 firmware for the chip, after which you must do a Reset ZWave Network under the Advanced tab in ZWave Device, presumably for the system to recreate the identifier and routing table based on the new set of handles provided in the updated firmware.
The Sections and Rooms remain, but all devices are deleted, at least their graphical representations are removed from the UI.  However, I believe that within the code the data sets are not getting purged, because (in my case) the ZWave function was unable to learn any devices from this point forward, either by activating the ZWave button on the back of Vera or by the Dashboard method via a Wi-Fi connection.  In the latter case one could see the status window indicating that it was waiting to acquire a device while Vera's ZWave LED blinked slowly, but as soon as the device was triggered and the LED flashed rapidly, indicating having received the transmission, the status window would indicate: "ZWave Network failed to go into learn mode, Aborting... please wait 1 minute and try again".  No matter how long I waited, or how often I tried, the new firmware just would not go into learn mode.
So then I tried to revert the system back to the old firmware and found another interesting twist.  When Restoring to Factory Defaults (under Advanced - Backup), I find that the new firmware installs itself as the new default - Vera always comes up running 1245, no matter how many times I tried to Restore.  This did not happen before, you could always Restore to the pre-1047 version that was installed in the router originally, and then go to the Installation Wizard to re-install 1047.
I also attempted to Restore my last known good backup while running under 1047, but this did not work either - the 3.20 firmware just could not re-learn the network or recognize the IDs of the devices.
To get the system operational again, what I finally did was to un-check the "Use 3.20" firmware radio button and reboot Vera in order to reload the old 2.78 firmware.  I then went to each device and excluded them first, after which Vera was able to include them anew.  I now have all the devices back under full control, but running under MiOS 1245 with ZWave 2.78.
Last, but not least, as others have reported here, 1245 no longer logs lock events (I have 2 locks in my system) - I understand that this was done on purpose and that lock events are now supposed to be stored on the MiOS server (cp.mios.com - Events (next to the Dashboard button), however, no lock events appear there either.  Nor do any notifications that one may have programmed, either directly with the "Notifications" tab for each lock, or through any scenes that call for a lock notification.  The scenes run correctly, but no lock notifications get stored OR sent (if you have email or SMS selected for receiving notifications).  The funny part is that when I was first testing the system after I got it working again, I was able to receive 3 notifications in a row, but after that they stopped being logged or sent at all, even though they are set at 20 per day, and I have reset them multiple times to see if I could get them working.  They do not.
Title: Re: 1.1.1245 beta available for general testing
Post by: wscannell on April 29, 2011, 12:01:26 pm
After you reset the z-wave network, you then need to exclude each device and then include them.  They will not include until you exclude them first.  The devices themselves prevent inclusion because they think they are still connected to the old system.  Even though they do not show up ion the dashboard, you can still exclude them.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on April 29, 2011, 12:04:30 pm
[...]However, [...] the ZWave function was unable to learn any devices from this point forward,[...] To get the system operational again, [...] I then went to each device and excluded them first, after which Vera was able to include them anew.
You said it yourself! :) This would have worked with 3.20 too.

If you reset the network in your controller, you'll also have to exclude all devices, so their HomeID and NodeID get wiped out and they will accept new ones from your freshly reset (primary) controller.
Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on April 29, 2011, 01:21:18 pm
Oops... I was trying to be as detailed as possible but I guess I neglected to mention that I excluded each device three times in a row while trying to get the network back up with 3.20.  Maybe I just did something wrong in the original reset after the update, like perhaps interrupting the boot up sequence or something (I did pull an all-nighter on this).  Next time I go on site again I will try upgrading to 3.20 again, as it sounds like you guys have it working correctly.

Any insights about the Notifications issues - Do you have any lock notifications working with 1245?

Thanks for all you contributions in this forum!
Title: Re: 1.1.1245 beta available for general testing
Post by: sjolshagen on May 02, 2011, 07:22:06 am
After upgrading & running 1.1.1245 for several days, I'm noticing the following behavior:

Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 02, 2011, 08:32:16 am
Hi--

   Now running on 1.1.1245 I'm getting the following error for the GE/JASCO Outdoor Module: "Transmit failed with code: 1"

   Does anyone know what code 1 is?

   I have excluded/included and repaired this network several times.. without any change.

           Don
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 02, 2011, 08:57:44 am
Now running on 1.1.1245 I'm getting the following error for the GE/JASCO Outdoor Module: "Transmit failed with code: 1" [...]   Does anyone know what code 1 is?
Probably that the acknowledgment back from the module to Vera was not received. See here (http://forum.micasaverde.com/index.php?topic=5384.msg30831#msg30831).
Is everything ok when you move the module closer to Vera? Are you saying you didn't have this before the upgrade?

Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on May 02, 2011, 02:18:34 pm
Reading that last post triggered my mind about the problems that I was having in getting the ZWave network "failed to learn" error message after upgrading the firmware.  After performing a network "heal", I would receive the same error "Transmit failed with code:1" from one of my switches that is in the middle of the house and that switch's status would turn red.  That switch is a Cooper Aspire battery operated device that is acting in a group association to control a master switch at the other end (a faux 3-way).  It uses 2 button-batteries and goes to sleep almost immediately after you activate it.  So would it make sense to assume that since the new firmware (3.20) has a revised node routing schema, that the network fails to learn if one of the intermediate hops (nodes) does not poll because it is asleep?
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 02, 2011, 04:03:57 pm
Now running on 1.1.1245 I'm getting the following error for the GE/JASCO Outdoor Module: "Transmit failed with code: 1" [...]   Does anyone know what code 1 is?
Probably that the acknowledgment back from the module to Vera was not received. See here (http://forum.micasaverde.com/index.php?topic=5384.msg30831#msg30831).
Is everything ok when you move the module closer to Vera? Are you saying you didn't have this before the upgrade?



Hi oTi@--

  The irony here is that the module that isn't responding is about 3 feet from Vera.  I'll try to move Vera farther away.. Thanks

                 Don
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 02, 2011, 04:30:42 pm
The irony here is that the module that isn't responding is about 3 feet from Vera.
Hmmm. And you said you have already tried excluding and including the module right there, without moving the module or Vera?
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on May 02, 2011, 05:12:21 pm
Now running on 1.1.1245 I'm getting the following error for the GE/JASCO Outdoor Module: "Transmit failed with code: 1" [...]   Does anyone know what code 1 is?
Probably that the acknowledgment back from the module to Vera was not received. See here (http://forum.micasaverde.com/index.php?topic=5384.msg30831#msg30831).
Is everything ok when you move the module closer to Vera? Are you saying you didn't have this before the upgrade?



Hi oTi@--

  The irony here is that the module that isn't responding is about 3 feet from Vera.  I'll try to move Vera farther away.. Thanks

                 Don
I've been having this type of issue with a few modules and I was given the unsatisfactory answer by MCV that they believed it was an interference issue. Now admittedly mine are probably 10-15 feet away, but I never got this before the 3.20 release, and your 3 feet confirms that it shouldn't be an interference issue!
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 02, 2011, 05:59:34 pm
Hi Soiferheld-

   I'm stuck. I tried to logon to Vera but the Vera2 doesn't have the password printed on the bottom so I can't access the logs... Sorry would like to help..

                Don
Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on May 02, 2011, 07:19:53 pm
Thanks Don Diego.  Not sure about your password issue - the password on the bottom of the Vera2 is for accessing its Wi-Fi routing capabilities, not the Dashboard, which is accessed through a login to a MiOS.com account with a password that you create.

I would like to open the question up to ANYONE that is running on 1245 with Kwikset locks - Are you able to see lock events or logs anywhere - on cp.mios.com or anywhere else for that matter?  How about lock event notifications?  Are you able to be notified when a lock code is entered?  The only thing I am able to do remotely now with my locks is open and close them and change pins.

Thank you.
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on May 02, 2011, 07:30:31 pm
I get notifications for all 3 of my Kwickset locks. However, they were set up many months ago on a previous version if that makes any difference.
Title: Re: 1.1.1245 beta available for general testing
Post by: wscannell on May 02, 2011, 11:11:52 pm
Hi Soiferheld-

   I'm stuck. I tried to logon to Vera but the Vera2 doesn't have the password printed on the bottom so I can't access the logs... Sorry would like to help..

                Don
The Wifi password listed on the bottom of Vera is the root password.
Title: Re: 1.1.1245 beta available for general testing
Post by: 325xi on May 02, 2011, 11:33:39 pm
Tried to re-program HA07... big mistake.
Add device never finished, existing controller disappeared.
2 attempts to re-add created 2 new dysfunctional controllers (scenes couldn't be transferred)

Sigh...
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 03, 2011, 06:43:36 am

My vera 2 is old enough that there is not a password on the bottom!! Believe that this was discussed in previous posting by other individuals having the same problem.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 03, 2011, 07:50:47 am

Is anyone else having difficulty paring the Homeseer 3-1 Sensors (HSM100) on 1.1.1245? I have four HSM100s which are not getting configured  under 1.1.1245. Assuming this to be a 2.78 to 3.2 chip problem I reset the unit to factory defaults (and reset the Z-Wave network), excluded and re-paired everything. Reloaded 1.1.1245.

Everything else seems to work OK under 1.1.1245 but the HSM100s. I have excluded and re-included them at least 6 times without success. I get _Generic IO (waiting for wake up to configure) each time and pressing the blue button to configure doesn't seem to help. I have the four HSM100 devices sitting within 5 feet of vera but I can't seem to get them to configure. I have replaced the batteries several times. No luck.

I have another vera under 1.1.1245 where the two HSM100s work great. I can't figure out any differences.

Anybody have an idea what I'm missing? Any thoughts?

Don
Title: Re: 1.1.1245 beta available for general testing
Post by: CMRancho on May 03, 2011, 09:05:36 am
Quote
I have four HSM100s which are not getting configured  under 1.1.1245

Have you tried pairing and configuring just one? And have you tried pairing it using both methods - the UI Wizard and the Z-wave button on Vera?

The only other thing that comes to mind is that I've had a few instances where it took a very long time to configure. Sometimes I have given up in despair and returned the next day and it was configured. Oh, yeah, and I've also had units that would only configure if they were sitting right on top of Vera.
Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on May 03, 2011, 10:07:28 am

Hi Soiferheld-

   I'm stuck. I tried to logon to Vera but the Vera2 doesn't have the password printed on the bottom so I can't access the logs... Sorry would like to help..

                Don

I read a reply from MCV in another post were they said the logs are no longer saved on Vera in 1.1.1245, only on the cp.MiOS server.  However, when I go to the Events tab in cp.MiOS I only see 2 devices listed, one as 0 (zero) and one of my Kwikset locks, not the other.  When I select the lock and choose view events, I get a calendar of the current month and a note stating that bold days have events in them.  There are however no bold days listed, although I am certain that many days have had lock events.
Title: Re: 1.1.1245 beta available for general testing
Post by: huogas on May 03, 2011, 12:35:35 pm
@Soiferheld

I think MCV refers to operational logs requested through the notification tabs. Those go to MIOS.

There is also what can be called "system" logs. I think that these logs are kept within Vera and to get these logs we need to ssh login ?
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 03, 2011, 12:46:28 pm
[...]so I can't access the logs...
@Don Diego,

The LuaUPnP (http://forum.micasaverde.com/index.php?topic=6344.msg38566#msg38566) logs?
Title: Reprogramming the HA-07WD for use with Vera2 1.1245
Post by: silvereagle2208 on May 03, 2011, 02:53:46 pm
Last week I felt 325xi's pain when I tried to reprogram my HA-07WD controller to work with with Vera2 1.1245.  I also blew away the HA-07WD every time I tried to link it with Vera 2.   Then I remembered I had solved this problem once before and that I had submitted my solution to this forum as well.  The key is to realize that the HA-07WD is a handheld controller and therefore it needs to be updated in the following manner:

The solution is to repeat the Vera2 "Include a battery operated handheld remote and scene controller" procedure for the HA-07WD , even though the controller was previously been added as a secondary controller.
 
The full process is:
1) Locate the Vera 2 and HA-07WD within 3 feet of each other.

Vera 2 activities:
2) Select the Add/Remove a device option on the Vera dashboard
3) Select the Add One option in the "For battery operated handheld remotes and scene controllers" section

HA-07WD activities:
4) Immediately, Press the INCLUDE button on the HA-07WD. "Copy" will be shown in the LCD display. Release the INCLUDE button.
5) Press and release the Channel 1 OFF/DIM button on the HA-07WD. "RA" which stands for "Receive ALL data will appear next to copy.
Wait until the Successful message appears in the upper right corner of the HA-07WD display.  If the Unsuccessful message appears, repeat the process.

This procedure will download the current network and channel settings from my Vera 2 to the HA-07WD.  Once that was done all my lighting devices reacted to the HA-07WD All-On and All-Off signals.  No data on the HA-07WD or the Vera 2 was lost as a result of rerunning the Vera2 "Include a battery operated handheld remote" procedure.

Hopefully, this procedure will solve you problem for reprogramming the HA-07WD for use with Vera2 1.1245
Title: Re: Reprogramming the HA-07WD for use with Vera2 1.1245
Post by: oTi@ on May 03, 2011, 04:14:37 pm
Last week I felt 325xi's pain when I tried to reprogram my HA-07WD controller to work with with Vera2 1.1245.[...]
I wonder if there are different HA07 firmware versions or something. I have had no issue with my HA07 (Intermatic branded, not Wayne-Dalton). Just now re-included it 3 times in a row with full-power inclusion.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 03, 2011, 04:25:00 pm
The problem is that there is no password printed on the bottom of the unit. I have several different vera2s so I kno what you're talking about. Sorry,

        Jack
Title: Re: 1.1.1245 beta available for general testing
Post by: JimMac on May 04, 2011, 12:41:37 pm
I don't have any issues with my Intermatic HA07 or my HA-09.  Last weekend I made many changes to the scene buttons and had no issues.

What I am having difficulties with are maintaining the temp and light levels for my HMS-100.  The values lock and stay locked until you configure them again, over time they lock again.
I also can not detect my other Vera as a UPnP device.  It does not show up on the list of devices, everything but either Vera (I do see a "undefined" device).  I have lost the ability to control devices on my other Vera.
Title: Re: 1.1.1245 beta available for general testing
Post by: davidlee on May 04, 2011, 03:24:52 pm

After going to 1.1.1245 from previous beta firmware, I can not longer check for updates via: http://micasaverde.com/vera2?beta=1

Every time I try to select vera I get an error of:

Vera already connected.

I found Vera, but it looks like you've already started setting it up.
To continue setting it up or using it you can either go to your myMiOS account or connect to it directly on my network


What could be going on?
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 04, 2011, 03:48:24 pm
What could be going on?
A confusing way of saying you have the latest beta firmware?
Title: Re: 1.1.1245 beta available for general testing
Post by: davidlee on May 04, 2011, 04:08:42 pm
What could be going on?
A confusing way of saying you have the latest beta firmware?

Quite possibly, but in the past it identified the version you were running and said it was current.  Just have to wait for the next version to appear. 
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on May 04, 2011, 04:48:09 pm
That is the correct behavior and it normally only displays the versions when an update is available.
Title: Re: 1.1.1245 beta available for general testing
Post by: futzle on May 04, 2011, 05:54:58 pm
   I'm stuck. I tried to logon to Vera but the Vera2 doesn't have the password printed on the bottom so I can't access the logs... Sorry would like to help..

Hi Don,

If you're able to log in to cp.mios.com and access a backup *.tgz file for the unit, you can open it up in an archiving program and dig through the files for the password.  The wireless password is in /etc/config/wireless.  That's what was printed on the sticker that your Vera doesn't have.  Your root password may be the same.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 04, 2011, 07:18:01 pm
Hi futzle--

  I'll give it a try..

    Thanks.

       Don
Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 04, 2011, 08:18:36 pm
Hi

I did the upgrade to 1.1.1245, change the Z-Wave to 3.20.
All the updated worked fine.
But after abount 3-5 day's i have a very high load:

Mem: 30204K used, 336K free, 0K shrd, 392K buff, 5020K cached
CPU:   0% usr  99% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 23.30 22.20 19.20 19/76 5750
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
    4     1 root     RW       0   0%   0% [kswapd]
 5728  5725 root     R     1436   5%   0% [awk]

and some i think some Deadlock problems.

01      05/04/11 19:54:29.389   AlarmManager::Run callback for alarm 0x741f70 entry 0x825268 type 15 id 85 param=(nil) entry->when: 1304553265 time: 1304553269 tnum: 1 slow 0 tardy 4 <0x803>
02      05/04/11 19:54:35.005   JobHandler::Run job#8 :pollnode #3 (0xc2d198) N:3 P:100 S:0 is 31.437937000 seconds old <0xc04>
01      05/04/11 19:54:36.818   AlarmManager::Run callback for alarm 0x741f70 entry 0x82bd90 type 13 id 86 param=(nil) entry->when: 1304553265 time: 1304553276 tnum: 1 slow 0 tardy 11 <0x803>
01      05/04/11 19:54:42.681   AlarmManager::Run callback for alarm 0x741f70 entry 0xc29ac0 type 52 id 114 param=0x1175790 entry->when: 1304553276 time: 1304553282 tnum: 1 slow 0 tardy 6 <0x803>
02      05/04/11 19:54:46.885   ZW_Send_Data node 3 NO ROUTE (nil) <0xc04>
06      05/04/11 19:54:48.754   Device_Variable::m_szValue_set device: 171 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: LastWakeup was: 1304553212 now: 1304553285 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x803>
02      05/04/11 19:54:55.242   ZWaveNode::Wakeup did a poll for 93 73 seconds existing (nil) heal (nil) <0x803>
01      05/04/11 19:55:33.000   Failed to get lock(0x740e68) Variable: Device_Basic.cpp:567 last used RAServerSync.cpp:73  first used RAServerSync.cpp:73  thread: 0x402 (>13266)  handler 0x421c70 bOkToFail 0 <0x803>
02      05/04/11 19:56:03.072   Dumping 9 locks <0x803>
02      05/04/11 19:56:15.091   finished check for exceptions <0x803>
02      05/04/11 19:56:39.545   finished check for exceptions <0x803>
02      05/04/11 19:56:41.021   finished check for exceptions <0x803>
02      05/04/11 19:56:41.022   OL: (0x740df8) (>8863) ThreadedClass ../JobHandler/JobHandler.cpp l:394 time: 7:00:00p (1304553337 s) thread: 0x400 Rel: Y Got: Y <0x803>
02      05/04/11 19:56:41.022   finished check for exceptions <0x803>
02      05/04/11 19:56:41.023   OL: (0xa1ab60) (>13238) ThreadedClass ../ZWave/ZWaveJobHandler.cpp l:772 time: 7:54:42p (55 s) thread: 0x803 Rel: Y Got: Y <0x803>
02      05/04/11 19:56:41.024   finished check for exceptions <0x803>
02      05/04/11 19:56:41.024   OL: (0xa1ab60) (>13259) ThreadedClass ../ZWave/ZWaveNode.cpp l:5346 time: 7:54:55p (42 s) thread: 0x803 Rel: Y Got: Y <0x803>
02      05/04/11 19:56:41.025   finished check for exceptions <0x803>
02      05/04/11 19:56:41.025   OL: (0x740e68) (>13266) Variable RAServerSync.cpp l:73 time: *****DL******7:55:01p (36 s) thread: 0x402 Rel: N Got: Y <0x803>
02      05/04/11 19:56:41.026   finished check for exceptions <0x803>
02      05/04/11 19:56:41.027   OL: (0x740e68) (>13267) Variable Device_Basic.cpp l:567 time: 7:55:03p (34 s) thread: 0x803 Rel: N Got: N <0x803>
02      05/04/11 19:56:41.027   finished check for exceptions <0x803>
02      05/04/11 19:56:41.028   OL: (0xa1ab60) (>13268) ThreadedClass ../JobHandler/JobHandler.cpp l:394 time: 7:55:23p (14 s) thread: 0xc04 Rel: Y Got: Y <0x803>
02      05/04/11 19:56:41.028   finished check for exceptions <0x803>
02      05/04/11 19:56:41.029   OL: (0x740e68) (>13272) Variable ../ZWave/ZWaveJobHandler.h l:337 time: 7:55:33p (4 s) thread: 0x1406 Rel: N Got: N <0x803>
01      05/04/11 19:56:40.518   ZWaveSerial::Send m_iFrameID 231 type 0x0 command 0x16 expected 1 got ack 0 response 0 request 0 failed to get at time 222517 start time 220273 wait 2000 ack 0 m_iSendsWithoutReceive 1 <0xc04>
01      05/04/11 19:56:41.691   Deadlock problem. going to reload and quit <0x803>
01      05/04/11 19:56:41.691   ResetSercomm <0xc04>
03      05/04/11 19:56:43.490   JobHandler_LuaUPnP::Reload: deadlock Critical 1 m_bCriticalOnly 0 dirty data 1 <0x803>
02      05/04/11 20:05:59.502   UPnPCallbackEventHandler 4 start PIDLOG2 5614

Has anybody help ???

Thank's
Marcel

Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 04, 2011, 10:17:52 pm
Marcel,
You'll need to log a support ticket so they get the complete logs, there's nothing obvious in the log snippet given so far, but we might just be seeing the symptoms and not the cause.

When doing this, it's handy to have more of the output from TOP (in case one of the processes is leaking memory) and also a copy of the output from df so folks can see if the local filesystems are full or not....  The latter being the most common cause of long runQs and high sys CPU.


Also, what type of device is node 93, is it battery operated or a long way from Vera or other (powered) ZWave nodes?
Title: Re: 1.1.1245 beta available for general testing
Post by: sjolshagen on May 05, 2011, 06:08:50 am
Another observation after upgrading & using 1.1.1245 for a while:

After the problems with my Levitron VRCS2 (reported in Reply #65 of this thread - the controller is stuck with "Setting Special Associations")  I'm also noticing that any repair actions I take do not seem to complete (I "conclude" that based on the fact that there's never a report generated).

Also, since yesterday - not sure if this was just a fluke or a pattern yet - I'm not seeing the UI update to reflect a switch setting change (off to on, manually by pushing the switch did not cause the UI to reflect the switch being on this morning)
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 05, 2011, 06:30:16 am
After the problems with my Levitron VRCS2 (reported in Reply #65 of this thread - the controller is stuck with "Setting Special Associations")[...]
How did you get around the VRCS2 issue?
Title: Re: 1.1.1245 beta available for general testing
Post by: sjolshagen on May 05, 2011, 06:58:58 am
@oTi - Sorry, I guess I wasn't clear. I didn't get around it. It's still present, even after doing a breaker flip and keeping the power off for a while (minutes).

Added another "fun" detail to my 1.1.1245 experience now that I tried to report a trouble ticket on the "permanently configuring ZWave" problem I'm seeing:

Code: [Select]
Submitting trouble report...
ERROR:Wrong response from server:
Done.
Title: Re: 1.1.1245 beta available for general testing
Post by: huogas on May 05, 2011, 07:43:25 am
Sorry to ask, but is there someone from MCV monitoring this post they themselves started a few days ago ?

What is the plan now ? Releasing another beta to correct some problems reported here ? Making this 1.1.1245 version the official release ?
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 05, 2011, 09:39:25 am
@oTi - Sorry, I guess I wasn't clear. I didn't get around it. It's still present, even after doing a breaker flip and keeping the power off for a while (minutes).
I see. But with Vera stuck on that, I'm not sure that everything else gets configured / done / works as it should.

Regarding the VRCS2, have you tried deleting any scenes associated with it and/or just excluded the device just to see if any of your other problems remain, and/or a factory reset on the VRCS2, and/or moved Vera closer?

@JOD has one or more VRCS2's and no issues? (Not that I think it's specific to the 2-button, several folks, myself included, have seen this 'stuck' thing for the 4-button controllers.)
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 05, 2011, 10:01:42 am
Quote
Regarding the VRCS2, have you tried deleting any scenes associated with it and/or just excluded the device just to see if any of your other problems remain, and/or a factory reset on the VRCS2, and/or moved Vera closer?
The problem with deleting the scene is that you then dont have the associations to configure, I would suggest reworking the scene and adding one device at a time to it, maybe it's one particular device that does not like the association?
I dont believe it's an issue with the Leviton devices, just the way Vera handles setting the associations (IMHO)

Quote
@JOD has one or more VRCS2's and no issues? (Not that I think it's specific to the 2-button, several folks, myself included, have seen this 'stuck' thing for the 4-button controllers.)
My issues with the Levitons are slow & erratic behavior. I had this same issue with one of my 3 devices, that's why I suggested to @sjolshagen to cut the power temporarily to the device (mine configured afterwards) his did not.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 05, 2011, 10:10:57 am
Marcel,
You'll need to log a support ticket so they get the complete logs, there's nothing obvious in the log snippet given so far, but we might just be seeing the symptoms and not the cause.

When doing this, it's handy to have more of the output from TOP (in case one of the processes is leaking memory) and also a copy of the output from df so folks can see if the local filesystems are full or not....  The latter being the most common cause of long runQs and high sys CPU.


Also, what type of device is node 93, is it battery operated or a long way from Vera or other (powered) ZWave nodes?


OK, i will try to get some more info from the box. The problem is only it run's sometime only some minutes. I have connected a timer to restart it, because i had to go home. (Box is in US i am in switzerland)

Last time i made got this log. (See atta) Vera runs only some minutes.

The Node 93 is a door sensor: HM-DW001

I will try to open a ticket as soon the box will run again.

Thanks for helping

Marcel

OK, got also a new top after reboot.
But looks ok.
Mem: 29656K used, 884K free, 0K shrd, 1064K buff, 7340K cached
CPU:   0% usr   5% sys   0% nic  94% idle   0% io   0% irq   0% sirq
Load average: 0.33 0.73 3.75 1/53 28155
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
28155 27868 root     R     1444   5%   3% top -d1
27322   872 root     S     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
25291   912 root     S    18796  62%   0% /usr/bin/LuaUPnP
25395 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25394 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25743 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
27867 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25791 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25787 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25790 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25749 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25748 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25788 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25789 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
28144 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25815 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25391 25291 root     S    18796  62%   0% /usr/bin/LuaUPnP
25786 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
 1051     1 root     S     3600  12%   0% lighttpd -f /etc/lighttpd.conf
25401   944 root     S     2364   8%   0% /usr/bin/NetworkMonitor
Title: Re: 1.1.1245 beta available for general testing
Post by: sjolshagen on May 05, 2011, 11:32:05 am
Quote
... I would suggest reworking the scene and adding one device at a time to it, maybe it's one particular device that does not like the association?

My Levitron VRCS02 is controlling light fixtures wired to the Levitron itself, no other devices.
Title: Re: 1.1.1245 beta available for general testing
Post by: Ambrotos on May 05, 2011, 12:07:18 pm
@sjolshagen: That's interesting. I have a VRCS4-MRX that is also experiencing this "Setting special association" hanging problem. I also have a VRCS4-1LX which isn't. One difference between the two is that the -MRX has a built in relay switch. I wonder if the problem has something to do with Vera trying to associate a Leviton controller with an on-board device. I'll check tonight to see if I see the same problem when associating with some other device in my network.

-A
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 05, 2011, 12:20:37 pm
@Ambrotos,
I think between the folks who have recently reported on this, that the issue has been observed with most if not all flavors of the 4-button (scene/zone, -1L, -M0, -MR) and the 2-button controller.

(I personally haven't seen (nor have I attempted to provoke) it yet with the -M0, but I believe @aschwalb has, at least for the zone controller. Not that I think scene/zone matters. @merit has -1L exclusively, I believe.)
Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 05, 2011, 05:49:44 pm
Marcel,
You'll need to log a support ticket so they get the complete logs, there's nothing obvious in the log snippet given so far, but we might just be seeing the symptoms and not the cause.

When doing this, it's handy to have more of the output from TOP (in case one of the processes is leaking memory) and also a copy of the output from df so folks can see if the local filesystems are full or not....  The latter being the most common cause of long runQs and high sys CPU.


Also, what type of device is node 93, is it battery operated or a long way from Vera or other (powered) ZWave nodes?

OK, could catch a top befor the crash:

Mem: 30204K used, 336K free, 0K shrd, 368K buff, 5660K cached
CPU:   0% usr  99% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 19.53 19.18 16.76 6/69 4577
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
 4505  4476 root     D     2080   7%   5% /usr/bin/InternetOk
 3920  3787 root     R    19968  65%   5% /usr/bin/LuaUPnP
 3959     1 root     D     4048  13%   5% lighttpd -f /etc/lighttpd.conf
 3485  2367 root     R     1444   5%   4% top -d1
    4     1 root     RW       0   0%   4% [kswapd]
 4231  4210 root     D     1228   4%   3% ssh -p 232 -T -y -i /etc/cmh-ra/keys/
 3919  3787 root     R    19968  65%   3% /usr/bin/LuaUPnP
 2338   873 root     D     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
 4210     1 root     S     1516   5%   2% /bin/ash /usr/bin/cmh-ra-daemon.sh
  840     1 root     R     1452   5%   2% crond -c /etc/crontabs -l 5
 3942  3787 root     S    19968  65%   2% /usr/bin/LuaUPnP
 3945  3787 root     S    19968  65%   2% /usr/bin/LuaUPnP
 2937  2872 root     R     1444   5%   1% tail -f /var/log/cmh/LuaUPnP.log
 2752   873 root     S     1216   4%   1% /usr/sbin/dropbear -p 22 -P /var/run/
 3939  3787 root     S    19968  65%   1% /usr/bin/LuaUPnP
 3941  3787 root     S    19968  65%   1% /usr/bin/LuaUPnP
 4537  4477 root     R     1508   5%   1% /bin/sh
 3759   944 root     S     2312   8%   1% /usr/bin/NetworkMonitor
 3938  3787 root     S    19968  65%   1% /usr/bin/LuaUPnP
    8     1 root     SW       0   0%   0% [mtdblockd]



OK, i will try to get some more info from the box. The problem is only it run's sometime only some minutes. I have connected a timer to restart it, because i had to go home. (Box is in US i am in switzerland)

Last time i made got this log. (See atta) Vera runs only some minutes.

The Node 93 is a door sensor: HM-DW001

I will try to open a ticket as soon the box will run again.

Thanks for helping

Marcel

OK, got also a new top after reboot.
But looks ok.
Mem: 29656K used, 884K free, 0K shrd, 1064K buff, 7340K cached
CPU:   0% usr   5% sys   0% nic  94% idle   0% io   0% irq   0% sirq
Load average: 0.33 0.73 3.75 1/53 28155
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
28155 27868 root     R     1444   5%   3% top -d1
27322   872 root     S     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
25291   912 root     S    18796  62%   0% /usr/bin/LuaUPnP
25395 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25394 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25743 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
27867 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25791 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25787 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25790 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25749 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25748 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25788 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25789 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
28144 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25815 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
25391 25291 root     S    18796  62%   0% /usr/bin/LuaUPnP
25786 25391 root     S    18796  62%   0% /usr/bin/LuaUPnP
 1051     1 root     S     3600  12%   0% lighttpd -f /etc/lighttpd.conf
25401   944 root     S     2364   8%   0% /usr/bin/NetworkMonitor

Maybe that help's.

Thanks
Marcel


Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 05, 2011, 09:08:41 pm
OK, i will try to get some more info from the box. The problem is only it run's sometime only some minutes. I have connected a timer to restart it, because i had to go home. (Box is in US i am in switzerland)

Last time i made got this log. (See atta) Vera runs only some minutes.

The Node 93 is a door sensor: HM-DW001

I will try to open a ticket as soon the box will run again.

Thanks for helping

Marcel


Yup, the Ticket to MCV's team is the way to go here.  Check out the USB-Key stuff (referenced below) also, if you haven't done that.  It let me move Vera 2 off the timer once I did that.

Quote
OK, got also a new top after reboot.
But looks ok.
Mem: 29656K used, 884K free, 0K shrd, 1064K buff, 7340K cached
CPU:   0% usr   5% sys   0% nic  94% idle   0% io   0% irq   0% sirq
Load average: 0.33 0.73 3.75 1/53 28155
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
28155 27868 root     R     1444   5%   3% top -d1
27322   872 root     S     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
25291   912 root     S    18796  62%   0% /usr/bin/LuaUPnP
Yes, the Reboot likely cleared out whatever the situation was.  That said, you have a large/fat LuaUPnP Process.  I haven't checked mine lately, but last time I looked it was ~16M, yours is ~18M.  You also have a LOT of Z-Wave devices, and a large # of them appear to be Battery powered, but I only glanced so I could be wrong.

On device counts alone, I'd be running a USB Memory stick in your Vera.  You may also want to hook up with @JOD on experiences since he has a similarly large config.

I'd need the output of "df -k" during the "ugly" performance period to really know, but based upon device counts in your system, my guess is that you're running without USB Key's and are low on memory.

In Vera, the /var/log/cmh directory uses memory, and competes for it against the other processes.  This isn't bad when there are a small number of devices, and small log files, but gets ugly in larger systems.  This is what the USB Key support was added (for larger systems)
Title: Re: 1.1.1245 beta available for general testing
Post by: huogas on May 05, 2011, 11:33:00 pm
Sorry to ask, but is there someone from MCV monitoring this post they themselves started a few days ago ?

What is the plan now ? Releasing another beta to correct some problems reported here ? Making this 1.1.1245 version the official release ?
???
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 06, 2011, 07:05:23 am
  First, I need to acknowledge what a significant improvement firmware 1.1.1145 is over the previous versions:

     1. Door locks (schlage and Kwikset) all pair with a minimum of effort (as opposed to hours in time invested).

     2. Devices that were several hops away now work reliably.

     3. The UI is more responsive.

  However, having worked with 1.1.1145 several weeks now, there are two items that still require attention:

     1. Foremost is support for HSM100. I have pared these devices under several different UIs. If you're doing a complete network reset under 1.1.1145 they can be paired successfully. That is the only way I can get them to pair (and I've tried this on 2 different Vera2s all on 1.1.1145 - same result). If the devices were paired under a different UI they continue to work under 1.1.1145.  If they must be paired from scratch then I receive the device _GenericIO.  Which NEVER get resolved into the icon 3_in_1 Sensor (I've watched them for a week or more).

    To put this into perspective, this now has happened on two different Vera2s, for 8 different HSM100s. This isn't operator error, I have successfully paired HSM100s many times before with little difficulty. So the devices remain in the UI with the message "Waiting to wake-up to configure." Pressing the blue button to wake up the devices doesn't help.  Placing the devices within 1 meter of vera doesn't help. This needs to be looked at.

    2. Network repair/heal operations seems to be causing device configuration corruption. Often devices that have been configured correctly prior to a repair operation loose their configuration. This is especially true for battery operated devices. Running multiple repair operations does not repair the problem. The only solution that seems to work is to first exclude the device and re-include it.

    3. Z-Wave network reset doesn't work. I get the message "empty response" or nothing.. That's not very reassuring and makes it difficult to get to a solid baseline.

  Hoping that someone can look at these issues. Thanks in advance for any help, and feedback from others.


                Don


UPDATE: One HSM-100 correctly configured on  5/8.  
               One HSM-100 correctly configured on  5/11.
               Obe HSM-100 correctly configured on 5/13.
Five HSM-100 yet to be configured. Working continuously to configure. I work on this almost continuously. This really needs to be fixed.

Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 06, 2011, 12:54:56 pm
OK, i will try to get some more info from the box. The problem is only it run's sometime only some minutes. I have connected a timer to restart it, because i had to go home. (Box is in US i am in switzerland)

Last time i made got this log. (See atta) Vera runs only some minutes.

The Node 93 is a door sensor: HM-DW001

I will try to open a ticket as soon the box will run again.

Thanks for helping

Marcel


Yup, the Ticket to MCV's team is the way to go here.  Check out the USB-Key stuff (referenced below) also, if you haven't done that.  It let me move Vera 2 off the timer once I did that.

Quote
OK, got also a new top after reboot.
But looks ok.
Mem: 29656K used, 884K free, 0K shrd, 1064K buff, 7340K cached
CPU:   0% usr   5% sys   0% nic  94% idle   0% io   0% irq   0% sirq
Load average: 0.33 0.73 3.75 1/53 28155
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
28155 27868 root     R     1444   5%   3% top -d1
27322   872 root     S     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
25291   912 root     S    18796  62%   0% /usr/bin/LuaUPnP
Yes, the Reboot likely cleared out whatever the situation was.  That said, you have a large/fat LuaUPnP Process.  I haven't checked mine lately, but last time I looked it was ~16M, yours is ~18M.  You also have a LOT of Z-Wave devices, and a large # of them appear to be Battery powered, but I only glanced so I could be wrong.

On device counts alone, I'd be running a USB Memory stick in your Vera.  You may also want to hook up with @JOD on experiences since he has a similarly large config.

I'd need the output of "df -k" during the "ugly" performance period to really know, but based upon device counts in your system, my guess is that you're running without USB Key's and are low on memory.

In Vera, the /var/log/cmh directory uses memory, and competes for it against the other processes.  This isn't bad when there are a small number of devices, and small log files, but gets ugly in larger systems.  This is what the USB Key support was added (for larger systems)

OK, i try to get the df -k if the box is next time reachable. ( my vera is 5000 miles away ....)

@JOD
Got your message. I the point now, i have no right to send mail... (hope my account will be upgraded)
As i understand you right, i have to connect a usb-stick and change the logging to usb, and the problem is solved ??

Cheers
Marcel
Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 06, 2011, 01:38:02 pm
OK, i will try to get some more info from the box. The problem is only it run's sometime only some minutes. I have connected a timer to restart it, because i had to go home. (Box is in US i am in switzerland)

Last time i made got this log. (See atta) Vera runs only some minutes.

The Node 93 is a door sensor: HM-DW001

I will try to open a ticket as soon the box will run again.

Thanks for helping

Marcel


Yup, the Ticket to MCV's team is the way to go here.  Check out the USB-Key stuff (referenced below) also, if you haven't done that.  It let me move Vera 2 off the timer once I did that.

Quote
OK, got also a new top after reboot.
But looks ok.
Mem: 29656K used, 884K free, 0K shrd, 1064K buff, 7340K cached
CPU:   0% usr   5% sys   0% nic  94% idle   0% io   0% irq   0% sirq
Load average: 0.33 0.73 3.75 1/53 28155
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
28155 27868 root     R     1444   5%   3% top -d1
27322   872 root     S     1184   4%   2% /usr/sbin/dropbear -p 22 -P /var/run/
25291   912 root     S    18796  62%   0% /usr/bin/LuaUPnP
Yes, the Reboot likely cleared out whatever the situation was.  That said, you have a large/fat LuaUPnP Process.  I haven't checked mine lately, but last time I looked it was ~16M, yours is ~18M.  You also have a LOT of Z-Wave devices, and a large # of them appear to be Battery powered, but I only glanced so I could be wrong.

On device counts alone, I'd be running a USB Memory stick in your Vera.  You may also want to hook up with @JOD on experiences since he has a similarly large config.

I'd need the output of "df -k" during the "ugly" performance period to really know, but based upon device counts in your system, my guess is that you're running without USB Key's and are low on memory.

In Vera, the /var/log/cmh directory uses memory, and competes for it against the other processes.  This isn't bad when there are a small number of devices, and small log files, but gets ugly in larger systems.  This is what the USB Key support was added (for larger systems)

OK, i try to get the df -k if the box is next time reachable. ( my vera is 5000 miles away ....)

@JOD
Got your message. I the point now, i have no right to send mail... (hope my account will be upgraded)
As i understand you right, i have to connect a usb-stick and change the logging to usb, and the problem is solved ??

Cheers
Marcel


OK got the df:

root@MiOS_16273:~# df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 6464      6464         0 100% /rom
tmpfs                    15268      5300      9968  35% /tmp
/dev/mtdblock/4           9088      4476      4612  49% /overlay
mini_fo:/overlay          6464      6464         0 100% /
/dev/loop/0               3072      3072         0 100% /mios

Thanks for helping !!
Marcel
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 06, 2011, 05:45:37 pm
Quote
I have four HSM100s which are not getting configured  under 1.1.1245

Have you tried pairing and configuring just one? And have you tried pairing it using both methods - the UI Wizard and the Z-wave button on Vera?

The only other thing that comes to mind is that I've had a few instances where it took a very long time to configure. Sometimes I have given up in despair and returned the next day and it was configured. Oh, yeah, and I've also had units that would only configure if they were sitting right on top of Vera.

CMRancho--

  Sorry for the late response..

  I've tried configuring one HSM100 and I know what you mean about late responses. I've waited 3-4 days for it to configure.. I'm really out of ideas. Previously I could do a complete reset of the z-wave network and start from scratch.. But that's now not even working for me.. If the scenes didn't work I'd assume I have a broken vera.

  I've done a full power inclusion and exclusion as well as tried the normal process without any luck.


  I appreciate your help.

       Don

Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 06, 2011, 06:05:11 pm
Soiferheld --

  Thanks for the information..

  My vera2 has having difficulty paring devices. I tried a Z-wave network reset and it also would not work. You discussion below led me to wonder if reverting back to the 2.78 network routing might fix some of my problems.

  Sure enough I was able to reset the network which I could not do it under 3.0..

  I wonder what that means..

  Anyway... thanks for the brilliant idea..

      Don


UPDATE: Having un-paired and re-included all the devices I've finally gotten my first HSM100 to configure correctly. One down, seven to go!!


Vera2 Firmware 1.1.1245,  Z-Wave Firmware 3.20 - UPGRADE REPORT.
I am posting this in the hopes that it may help someone else and for the development team to investigate.
The 1245 firmware installs fine.  You then have a new set of Options under that tab in Toolbox - ZWave Device.  One of these is to check a radio button to use the new 3.20 firmware for the chip, after which you must do a Reset ZWave Network under the Advanced tab in ZWave Device, presumably for the system to recreate the identifier and routing table based on the new set of handles provided in the updated firmware.
The Sections and Rooms remain, but all devices are deleted, at least their graphical representations are removed from the UI.  However, I believe that within the code the data sets are not getting purged, because (in my case) the ZWave function was unable to learn any devices from this point forward, either by activating the ZWave button on the back of Vera or by the Dashboard method via a Wi-Fi connection.  In the latter case one could see the status window indicating that it was waiting to acquire a device while Vera's ZWave LED blinked slowly, but as soon as the device was triggered and the LED flashed rapidly, indicating having received the transmission, the status window would indicate: "ZWave Network failed to go into learn mode, Aborting... please wait 1 minute and try again".  No matter how long I waited, or how often I tried, the new firmware just would not go into learn mode.
So then I tried to revert the system back to the old firmware and found another interesting twist.  When Restoring to Factory Defaults (under Advanced - Backup), I find that the new firmware installs itself as the new default - Vera always comes up running 1245, no matter how many times I tried to Restore.  This did not happen before, you could always Restore to the pre-1047 version that was installed in the router originally, and then go to the Installation Wizard to re-install 1047.
I also attempted to Restore my last known good backup while running under 1047, but this did not work either - the 3.20 firmware just could not re-learn the network or recognize the IDs of the devices.
To get the system operational again, what I finally did was to un-check the "Use 3.20" firmware radio button and reboot Vera in order to reload the old 2.78 firmware.  I then went to each device and excluded them first, after which Vera was able to include them anew.  I now have all the devices back under full control, but running under MiOS 1245 with ZWave 2.78.
Last, but not least, as others have reported here, 1245 no longer logs lock events (I have 2 locks in my system) - I understand that this was done on purpose and that lock events are now supposed to be stored on the MiOS server (cp.mios.com - Events (next to the Dashboard button), however, no lock events appear there either.  Nor do any notifications that one may have programmed, either directly with the "Notifications" tab for each lock, or through any scenes that call for a lock notification.  The scenes run correctly, but no lock notifications get stored OR sent (if you have email or SMS selected for receiving notifications).  The funny part is that when I was first testing the system after I got it working again, I was able to receive 3 notifications in a row, but after that they stopped being logged or sent at all, even though they are set at 20 per day, and I have reset them multiple times to see if I could get them working.  They do not.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 06, 2011, 07:57:53 pm
1. Foremost is support for HSM100.
@Don Diego,
Strange. Just included a fresh HSM100 with .1245 without any issue whatsoever. Took perhaps 5 minutes.

When you reverted to 2.78 did you also restore a backed up configuration, or the only thing you did was unchecking the 'Use 3.20' box and then 'Reset Z-Wave' started working?
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 06, 2011, 08:36:11 pm
Hi oTi@ --

  Yes, I have backup configurations all along the way.. I'm now trying to include one HSM100. It takes a while to configure.

          Don


UPDATE 5/9/11 - I have reloaded several of the backups with no change in functionality. I have gotten one HSM100 configured out of eight.

I reverted back to 2.78 by unchecking the 3.0 routing box. I did a backup prior to reverting back to 2.78 (and tried reloading that backup). Still believe that there is a problem with configuring HSM100s.
Title: Re: 1.1.1245 beta available for general testing
Post by: tbever on May 07, 2011, 09:47:40 am
I have been experiencing similar glitches since upgrading to 1.1.1245.  Today my downstairs thermostat gave errors "failed to respond" so I tried to do a repair just using the individual node, but this failed also.  The device had been working fine for the past 2 months, and also over the past week or 2 after I updated to 1.1.1245 and zwave 3.2.  I excluded the node and then reincluded it, and now it works fine.  It is a PITA to have to redo all the various HVAC scenes, but not as much of a problem as others seem to have been experiencing.  I meant to copy the repair log but it was erased when I reset the vera to include/exclude.

Also a lamp module was doing the same thing.  It said it failed to respond, but I could turn it on using vera, but not off.  I have a separate remote controller that controls the light directly and this still works fine (this is included in vera, one of the $9.95 radio shack remotes).

My 2 HSM100s which I had included prior to the update are still working fine.

Don't think 1.1.1245 is ready for prime time.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 07, 2011, 10:07:13 am
Don't think 1.1.1245 is ready for prime time.
@tbever,
It sounds like you migrated your network to 3.20 (rather than start over). That migration does not come with any warranty.

The remote controller will always attempt to communicate with the device directly first. You (and the remote) were probably close enough to the module for that to work. Was Vera in the same spot, or farther away? Did a Repair not fix that either?
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 07, 2011, 12:41:09 pm
@JOD
Got your message. I the point now, i have no right to send mail... (hope my account will be upgraded)
As i understand you right, i have to connect a usb-stick and change the logging to usb, and the problem is solved ??
Assuming there is nothing else going on, yes.
A temporary solution (until you can get onsite to install the drive) might be to disable verbose logging. Bear in mind, verbose logging would need to be enabled for MCV to diagnose the issue, if you submitted a trouble ticket.
I've seen the same thing even with the drive installed, so there may be another issue with the log rotations.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: cityman on May 07, 2011, 03:03:08 pm
@JOD
Got your message. I the point now, i have no right to send mail... (hope my account will be upgraded)
As i understand you right, i have to connect a usb-stick and change the logging to usb, and the problem is solved ??
Assuming there is nothing else going on, yes.
A temporary solution (until you can get onsite to install the drive) might be to disable verbose logging. Bear in mind, verbose logging would need to be enabled for MCV to diagnose the issue, if you submitted a trouble ticket.
I've seen the same thing even with the drive installed, so there may be another issue with the log rotations.

JOD.

@JOD at the point now verbose logging is disabled. The box hangs also without verbose logging. I will send the usb stick to a neighbor, and can connect it.
Then a can open a ticket.
What you did, that your box works very well with about 100 Nodes ??


Cheers
Marcel
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 07, 2011, 03:37:12 pm
Other than adding the USB drive, rebuilding the network and not converting to 3.20, nothing. It's never been this responsive & dependable.
Thanks to MCV.

As I said, I've seen a couple of high loads which caused lockups even with the drive attached and just noticed my uptime is at 5 hours, so it's rebooted recently. Something for me to keep an eye on.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 07, 2011, 04:58:54 pm
Upgraded yesterday directly from 1.1.1047.

No problems so far that i can relate to the firmware.

Upgraded to 3.20 as well. No problem on the single device in my new network.

Rgards,

Henk
Title: Re: 1.1.1245 beta available for general testing
Post by: S-F on May 07, 2011, 09:31:45 pm
Other than adding the USB drive, rebuilding the network and not converting to 3.20, nothing. It's never been this responsive & dependable.
Thanks to MCV.



Why did you not upgrade to 3.20, for curiosity's sake? I thought it was supposed to fix some major issues.
Title: Re: 1.1.1245 beta available for general testing
Post by: tbever on May 08, 2011, 08:56:05 am
After I excluded/included the thermostat, one hard wired light switch and one lamp module started giving the error code one.  Rather than include/exclude I did a network heal last pm, and today everything works perfectly.  Whew...  I presume the routing table must have gotten messed up but now all is well.



I have been experiencing similar glitches since upgrading to 1.1.1245.  Today my downstairs thermostat gave errors "failed to respond" so I tried to do a repair just using the individual node, but this failed also.  The device had been working fine for the past 2 months, and also over the past week or 2 after I updated to 1.1.1245 and zwave 3.2.  I excluded the node and then reincluded it, and now it works fine.  It is a PITA to have to redo all the various HVAC scenes, but not as much of a problem as others seem to have been experiencing.  I meant to copy the repair log but it was erased when I reset the vera to include/exclude.

Also a lamp module was doing the same thing.  It said it failed to respond, but I could turn it on using vera, but not off.  I have a separate remote controller that controls the light directly and this still works fine (this is included in vera, one of the $9.95 radio shack remotes).

My 2 HSM100s which I had included prior to the update are still working fine.

Don't think 1.1.1245 is ready for prime time.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 08, 2011, 09:25:35 am
[...]Rather than include/exclude I did a network heal last pm, and today everything works perfectly.  Whew...  I presume the routing table must have gotten messed up but now all is well.
Yep, that's what it sounded like. Great that the repair actually worked! .1245 only.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 08, 2011, 01:01:07 pm
Why did you not upgrade to 3.20, for curiosity's sake? I thought it was supposed to fix some major issues.
The 1.1.1245 build addresses the issues, 3.20 is a new branch of Z-wave which allows manual routing. I'm using the Aeon dongle with a Vera 2 and the dongle is not supported (yet)

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Soiferheld on May 08, 2011, 01:14:23 pm
This has certainly become an interesting thread.  I would say that maybe MCV tried to cram way too much into this one release - the laundry list is about 99 items long - BUT, at the same time as trying to implement a newer Z-Wave topology.

The better way might have been to concentrate first on getting a known stable UI and OS operational with 3.20 (UI4 with 1.1.1047, fo example) and then make the other changes in  subsequent releases of the OS.  It must be a nightmare to try to figure out which line of code or which call to which routine is affecting what with so many changes at once.

I have a 3-week old system that I intend to grow (only 5 devices at present), but not until it becomes more stable.  If I had a system with dozens of nodes, hundreds of devices, like several of you on this forum, I would not mess with the network until they release it as a rock-solid upgrade, with well documented procedures.  Resetting and re-learning the whole network and its routing is a major undertaking that seems can have undesirable consequences.  I would not want to be doing that again and again with every new "fix" they find.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 08, 2011, 01:28:20 pm
[...]I would say that maybe MCV tried to cram way too much into this one release - the laundry list is about 99 items long [...] It must be a nightmare to try to figure out which line of code or which call to which routine is affecting what with so many changes at once.
.1047 to .1245 suggests 198 builds to me; in 8 months or so, for 99 (published) changes, with a bunch of the builds made available to the Beta Testers and some to the general public.

Quote
Resetting and re-learning the whole network and its routing is a major undertaking that seems can have undesirable consequences.  I would not want to be doing that again and again with every new "fix" they find.
I personally have not had or seen the need yet to reset my Z-Wave network.
Title: Re: 1.1.1245 beta available for general testing
Post by: S-F on May 08, 2011, 01:35:08 pm

The 1.1.1245 build addresses the issues, 3.20 is a new branch of Z-wave which allows manual routing. I'm using the Aeon dongle with a Vera 2 and the dongle is not supported (yet)

JOD.

So the firmware takes care of the issue spoken of in this thread http://forum.micasaverde.com/index.php?topic=5756.0 (http://forum.micasaverde.com/index.php?topic=5756.0) and the new z-wave firmware is just something extra? So there is no real need for it unless one wants "manual routing", whatever that is?
Title: Re: 1.1.1245 beta available for general testing
Post by: axill on May 09, 2011, 02:54:31 am
I did an upgrade without any problem but after upgrade I got an issue with pooling.
My network contains 36 z-wave devices, all appliances can be commanded from Vera and status will be updated.
The problem is that while I switch appliance manually or by remote Vera will not update this status for a time been (30-40 minutes no updates, did'nt check longer). By pressing "pool now" I can get status update without any problem. It seams that this issue related to a new betta
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 09, 2011, 04:31:36 am
@axill

Possibly a bug and if so, you should file it with MCS.
Some more testing would be usefull in that case, as well as other users reporting the same issue.

Perosnally i dont have that problem, but that could be due to much less devices in my network.

Did you try to "heal" your network?  The great new feature with 1245 is that the Zwave routing tables actually get updated in this version by the healing process. This should result in more reliabale routing and thus working polls

I would suggest you heal your network and report your findings here.

Hope to hear back!

Henk
Title: Re: 1.1.1245 beta available for general testing
Post by: huogas on May 09, 2011, 07:18:31 am
Sorry to ask, but is there someone from MCV monitoring this post they themselves started a few days ago ?

What is the plan now ? Releasing another beta to correct some problems reported here ? Making this 1.1.1245 version the official release ?
??? ???
Title: Re: 1.1.1245 beta available for general testing
Post by: axill on May 09, 2011, 03:34:04 pm
Did you try to "heal" your network? 
Yes, I did a heal after adding the last device into my network.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 09, 2011, 04:53:12 pm
Did you try to "heal" your network? 
Yes, I did a heal after adding the last device into my network.

@Axill

So let me recap, if yes applies to all answers, i would suggest to contact MCV support

1. you have 36 devices in your zwave network
2. you recently upgraded to firmware 1.1.1245
3. you are able to switch all devices through the vera UI and all devices respond
4. you recently added a new device and "healed" your network
5. this last heal/device add was AFTER you upgraded to 1.1.1245 (so you healed with 1.1.1245 installed)
6. polling of these devices takes longer than 10 minutes or does not even complete at all

You might consider installing Ap15e's ADD plugin. This will provide you with a graphical overview of your network and routing tables. The plugin can be found here:
http://forum.micasaverde.com/index.php?topic=5130.msg28579#msg28579

If any dead nodes (nodes that vera cant reach) are in your network, they should show up in this overview.

Hope this helped!

Henk
Title: Re: 1.1.1245 beta available for general testing
Post by: dkeefe on May 10, 2011, 09:44:21 am
more issues I noticed with 1245 and firefox 4.0.1:

when you enable the usb logging, the confirmation/warning window that opens has a couple of formatting problems. text that should be bold has <b> and </b> tags that are visible and the text isn't bold. there is another tag visible, but i forgot what it was (</f> or something like that).

also, after usb logging is enabled, if you go back into the log tab in the advanced menu, the check box next to the usb log enable box isn't checked. when you move the mouse pointer close to the box, the check appears.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 10, 2011, 09:04:43 pm
5/10/11 ~ 21:00:00 System non responsive.

Mem: 30012K used, 528K free, 0K shrd, 300K buff, 2132K cached
CPU:   0% usr   0% sys   0% nic  98% idle   0% io   0% irq   0% sirq
Load average: 22.98 22.55 22.51 1/67 20362
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
20230 20224 root     R     1440   5%   1% top
20222  1010 root     S     1180   4%   0% /usr/sbin/dropbear -p 22 -P /var/run/
18250 18246 root     S    20804  68%   0% /usr/bin/LuaUPnP
18252 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18246  1089 root     S    20804  68%   0% /usr/bin/LuaUPnP
18251 18250 root     S    20804  68%   0% /usr/bin/LuaUPnP
18297 18250 root     S    20804  68%   0% /usr/bin/LuaUPnP
18302 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
19564 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18334 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18335 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18333 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18332 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18331 18250 root     S    20804  68%   0% /usr/bin/LuaUPnP
18443 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18303 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
20087 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18397 18250 root     D    20804  68%   0% /usr/bin/LuaUPnP
18329 18250 root     S    20804  68%   0% /usr/bin/LuaUPnP
20088 18251 root     D    20792  68%   0% /usr/bin/LuaUPnP
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 11, 2011, 12:04:44 am
@JOD, check the size of your LuaUPnP process after a restart, since the one you've listed here is ~20M (mine's about 17.5M).  Not sure how it's managing to be locked up though since it's reporting 98% CPU idle.

What I'm wondering is if the size of this process changes [materially] over time, like a memory leak, or whether you've just gotta lot of junk in the trunk that's causing it to be fat all the time.

A few other things to grab "during an event":

a) when you clip the "top" output, can you include the top line?  This is the one showing the summary of memory buckets.
Mem: 29476K used, 1064K free, 0K shrd, 1032K buff, 6108K cached
CPU:   2% usr  32% sys   0% nic  64% idle   0% io   0% irq   0% sirq
Load average: 0.10 0.13 0.19 1/61 32543
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
    6     1 root     SW       0   0%  28% [kupdated]
31824 31819 root     R     1440   5%   1% top
 8558  1147 root     S     3028  10%   1% /usr/bin/NetworkMonitor
28572 18211 root     S    17392  57%   0% /usr/bin/LuaUPnP
18465 18211 root     S    17392  57%   0% /usr/bin/LuaUPnP


b) what does "df -k" look like at the time of lockup?
c) what does "logread" show
Title: Re: 1.1.1245 beta available for general testing
Post by: axill on May 11, 2011, 03:25:02 am
Henk, thanks for the link. I've installed the link but it is тище easy to interprit the result.
Sorry, my devices named in cyrillic and this does not work:

Signal quality (PollOk / PollNoReply / PollTxFail / failure rate)

17   128 01: Вкл.2: спальня                  41      8    nil  16 %
18   129 03: Вкл.: потолок спальня      17    nil    nil   0 %
16   130 10: Сенсор: спальня             141      2    nil   1 %
19   134 02: Вкл.вентилятор спальня - ванная      16    nil    nil   0 %
20   135 02: Скр.вкл.: линия спальня      15    nil    nil   0 %
21   136 02: Вкл.: коридор 2                 11    nil    nil   0 %
22   137 05: Сцены: спальня                 1    nil    nil   0 %
23   138 01: Вкл.: детская                    8    nil    nil   0 %
24   140 10: Сенсор: детская             112    nil    nil   0 %
25   141 01: Вкл.: кабинет                  275      6    nil   2 %
26   142 10: Движ.: кабинет                111      4    nil   3 %
27   146 10: Движ.: туалет                  164    nil    nil   0 %
28   147 01: Вкл.: туалет                    321      3    nil   1 %
29   148 01: Вкл.: душевая                  310      2    nil   1 %
30   149 10: Движ.: душевая                158    nil    nil   0 %
31   150 03: Скр.вкл.: коридор малый       3      2    nil  40 %
32   151 01: Скр.вкл.: коридор 1           3      2    nil  40 %
33   152 02: Скр.вкл.: потолок прихожая       3    nil    nil   0 %
34   153 10: Движ.: столовая              157    nil    nil   0 %
35   154 01: Вкл.2: гостиная                16      1    nil   6 %
36   155 02: Вкл.: софиты гостиная    8029      5    nil   0 %
37   156 03: Вкл.2: арка гостиная       22      2    nil   8 %
38   158 10: Сенсор: гостиная           150    nil    nil   0 %
  3   110 10: Сенсор: кухня                 190      2    nil   1 %
  4   115 04: ПДУ: гостиная                 nil    nil    nil   0 %
  5   116 01: Вкл.2: прихожая               146      3    nil   2 %
  6   117 03: Вкл.2: арки прихожая      155      3    nil   2 %
  7   118 01: Вкл.2: столовая               156      2    nil   1 %
  8   119 01: Вкл.2: кухня                     170      8    nil   4 %
  9   120 04: Вкл.: вентилятор кухня     120      2    nil   2 %
10   121 02: Вкл.2: подсветка кухня     121    nil    nil   0 %
11   122 03: Розетка: вытяжка кухня     641      1    nil   0 %
12   123 10: Движ.: прихожая              192      2    nil   1 %
13   124 10: Движ.: спальня - ванная     166      1    nil   1 %
14   125 01: Вкл.2: спальня - ванная      33      2    nil   6 %
15   126 04: Вкл.: комод спальня        17    nil    nil   0 %
39   162 15: Дым: кухня                         2    nil    nil   0 %
Title: Re: 1.1.1245 beta available for general testing
Post by: reiserx on May 13, 2011, 12:45:49 am
http://download.mios.com/backfirebetafirmware/wl500gP_Luup_ui4-1.1.1245-1.squashfs

I tried using this like remotely on a V2 and it says it's invalid. Any Ideas?
Title: Re: 1.1.1245 beta available for general testing
Post by: xlurkr on May 14, 2011, 01:25:19 am
I have a Vera 1.

I have tried to upgrade twice from 1.0.979.  Both times, I've had 2 major errors, and some smaller ones probably related to these two:  it says "Z-wave Failed To Start" on the dashboard, and when I click "Enable remote access" on MyMios, it says "I didn't detect a unit on your home network."

Today I just saw this thread:

http://forum.micasaverde.com/index.php?topic=2857.0

about updating the Aeon Labs dongle firmware.  Mine still blinks, rather than staying lit, so I guess it's not the latest.  Any chance that is holding me back from upgrading?  I'm asking because updating the dongle sounds like an ordeal, but I'm willing to do it if necessary to move to UI4.

-Tom
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 14, 2011, 10:41:03 am
@JOD, check the size of your LuaUPnP process after a restart, since the one you've listed here is ~20M (mine's about 17.5M).  Not sure how it's managing to be locked up though since it's reporting 98% CPU idle.

What I'm wondering is if the size of this process changes [materially] over time, like a memory leak, or whether you've just gotta lot of junk in the trunk that's causing it to be fat all the time.
Uptime is 2 days, LuaUPnP @ time of reboot was ~23M. It's now at 2M & I'm seeing incremental grow with each "top" refresh so I'll check it again in 2 days and see where it is.

*Edit. (12hrs later)
System not responding again this morning and will not recover on its own. As I suspected, this happens during log rotations.

"logread"
Code: [Select]
May 14 09:01:34 MiOS_12xxx user.err kernel: VFS: brelse: Trying to free free buffer
May 14 09:01:34 MiOS_12xxx user.err kernel: SQUASHFS error: sb_bread failed reading block 0x4bc
May 14 09:02:01 MiOS_12xxx cron.err crond[963]: USER root pid 8025 cmd /usr/bin/Rotate_Logs.sh
May 14 09:03:01 MiOS_12xxx cron.err crond[963]: user root: process already running:

"top" *Edit. Additional lines added per @guessed request below.
Code: [Select]


Mem: 29792K used, 748K free, 0K shrd, 504K buff, 2768K cached
CPU:   0% usr   1% sys   0% nic  98% idle   0% io   0% irq   0% sirq
Load average: 23.05 22.70 21.16 1/77 8620
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
 8610  8605 root     R     1440   5%   1% top
 8604  1009 root     S     1180   4%   1% /usr/sbin/dropbear -p 22 -P /var/run/
19940 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
19941 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
20002 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
20046 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
20008 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
20043 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
20047 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
19937  1089 root     S    21240  70%   0% /usr/bin/LuaUPnP
20041 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
20007 19939 root     D    21240  70%   0% /usr/bin/LuaUPnP
20045 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
19939 19937 root     S    21240  70%   0% /usr/bin/LuaUPnP
20069 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
 7944 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
20039 19939 root     S    21240  70%   0% /usr/bin/LuaUPnP
 4352     1 root     D     3664  12%   0% lighttpd -f /etc/lighttpd.conf
30283  1125 root     S     2648   9%   0% /usr/bin/NetworkMonitor
30288 30285 root     S     2648   9%   0% /usr/bin/NetworkMonitor8

"df -h"
Code: [Select]
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 6.3M      6.3M         0 100% /rom
tmpfs                    14.9M      1.1M     13.8M   7% /tmp
/dev/mtdblock/4           8.9M      5.0M      3.9M  56% /overlay
mini_fo:/overlay          6.3M      6.3M         0 100% /
/dev/scsi/host0/bus0/target0/lun0/part1
                        503.9M     25.6M    452.7M   5% /tmp/log/cmh
/dev/loop/0               3.0M      3.0M         0 100% /mios

*Edit. 5/15/2011 @ ~11:40am system uptime is 12min. System must have rebooted on it's own.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 14, 2011, 10:59:34 am
System not responding again this morning and will not recover on its own. As suspected, the error is during log rotations.
Had a very, very slow Vera last night as well. I already had a shell open, so at times was able to get a prompt, a top, a ps, etc. Not sure what triggered it. At some point it appeared really hung; I gave it a while and then power-cycled her.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 14, 2011, 11:08:30 am
Dont know if this helps, but here are my 2 cents from my responsive VERA2

TOP
Quote
Mem: 28820K used, 1720K free, 0K shrd, 3372K buff, 12528K cached
CPU:   2% usr   5% sys   0% nic  91% idle   0% io   0% irq   0% sirq
Load average: 0.16 0.15 0.15 1/50 6792
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
 1002   959 root     S     2400   8%   1% /usr/bin/NetworkMonitor
 6761  6648 root     R     1440   5%   1% top
 6627   889 root     S     1180   4%   0% /usr/sbin/dropbear -p 22 -P /var/run/
 6139   926 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6141  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6192  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6191  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6154  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6142  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6392  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6193  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6204  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6140  6139 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6201  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6216  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6160  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6189  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 6159  6140 root     S     8364  27%   0% /usr/bin/LuaUPnP
 1066     1 root     S     3732  12%   0% lighttpd -f /etc/lighttpd.conf
 1038  1033 root     S     2400   8%   0% /usr/bin/NetworkMonitor

df -h
Quote

Filesystem                Size       Used        Available Use% Mounted on
/dev/root                  6.3M      6.3M        0 100% /rom
tmpfs                       14.9M     4.5M        10.4M  30% /tmp
/dev/mtdblock/4       8.9M      4.1M         4.8M  46% /overlay
mini_fo:/overlay       6.3M      6.3M         0 100% /
/dev/loop/0              3.0M      3.0M         0 100% /mios

logread (last 3 entries)
Quote
May 14 17:02:01 MiOS_2xxx cron.err crond[854]: USER root pid 6813 cmd /usr/bin/Rotate_Logs.sh
May 14 17:03:01 MiOS_2xxx cron.err crond[854]: USER root pid 6958 cmd /usr/bin/Rotate_Logs.sh
May 14 17:04:01 MiOS_2xxx cron.err crond[854]: USER root pid 7111 cmd /usr/bin/Rotate_Logs.sh

Is that helpfull or do i need to add other info?

Henk
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 14, 2011, 11:10:20 am
@JOD,
Do you have a copy of the next few lines of top during the hot period also?

Generally speaking you need both the top section (provided) and the first few lines of the process list, matched, for a given event in order to serenata going on in a Linux system.

Logread itself looks ok, since it just timestamps when it runs.  I was looking for something else from that.
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 14, 2011, 11:15:53 am
@Henk,
Yours is like a clean baseline, which makes for a good reference.  JOD's is maxed out with a lot fo ZWave devices as well as some Lua stuff so you can see that his LuaUPnP process is much larger, and also that his system has less memory to spare... (both buff and cache are low in his, and there's little wiggle room when that next process kicks in... And Vera does fire up free standing processes for certain activities.... Which is why I wanted the next few lines of top.
Title: Re: 1.1.1245 beta available for general testing
Post by: sjolshagen on May 15, 2011, 07:32:58 am
Another observation on 1.1.1245:

My Kwikset Deadbolt does not appear to be getting its battery status read unless I manually poll the device.

I'm running @Ap15e's ADD script every 24 hours and I've noticed that, consistently, the battery level report in the script for my deadbolt has not been updated since the last time I manually polled the device (Hit "Poll" in settings tab). My current "PollSettings" value is 10800 (every 3 hours) for this device.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 15, 2011, 07:43:25 am
System not responding again this morning and will not recover on its own. As suspected, the error is during log rotations.
Had a very, very slow Vera last night as well. I already had a shell open, so at times was able to get a prompt, a top, a ps, etc. Not sure what triggered it. At some point it appeared really hung; I gave it a while and then power-cycled her.
OK; I'm going to attribute my observation to the fact that even though Vera says USB logging is enabled, she isn't actually logging to USB.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 15, 2011, 11:36:14 am
i will hook up a usb stick later this week and see if i can get some results there ok?
Title: Re: 1.1.1245 beta available for general testing-REGRESSION
Post by: Don Diego on May 15, 2011, 11:40:38 am
REGRESSION

I thought we had fixed the Daily Schedule being deleted during a repair for the Schlage deadbolt lock from version 1.1.1047.

Not true!! When the Schlage deadbolt lock gets reconfigured as part of a repair operation it looses ONLY those pins that have a daily schedule associated with them. Other pins that do not have a daily schedule remain unaffected. I have now had to re-enter the pins twice (each time it takes 45 minutes)!!

See mantis bug report #1403  http://bugs.mios.com/view.php?id=1403

Also, this does not happen with the Kwikset deadbolt lock.

Also, the Schlage lock is much more difficult to maintain than the Kwikset deadbolt lock.

Hope we can get this fixed soon. My renters who rely on getting into the property with the pin code would also appreciate it.

 :'(

   Don

UPDATE: I have re-typed the schedule codes into the Schlage lock two more times and had them wiped out again by a z-wave repair. This is intolerable. I'm not even re-configuring the Schlage lock anymore only updating the MIOS routing.
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 15, 2011, 12:07:00 pm
System not responding again this morning and will not recover on its own. As suspected, the error is during log rotations.
Had a very, very slow Vera last night as well. I already had a shell open, so at times was able to get a prompt, a top, a ps, etc. Not sure what triggered it. At some point it appeared really hung; I gave it a while and then power-cycled her.
OK; I'm going to attribute my observation to the fact that even though Vera says USB logging is enabled, she isn't actually logging to USB.
oTi@,
You can work that out by running    "df -k"   directly on Vera.  If your output looks like @Henk's (above) then you don't have the USB Key working.  If it looks like @JOD's then you have it enabled correctly.

The specific bit to look for is where /tmp/log/cmh is mounted.


(corrected, since I'd posted it with my test account)
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 15, 2011, 01:02:50 pm
You can work that out [...]
Yep, understood. I wasn't clear: I noticed this morning that the USB stick partition wasn't mounted, even though Vera says USB logging is enabled (which is odd). So I'm assuming that was the case as well a few nights ago when the lock-up happened, and may be the cause (in my case).
Title: Re: 1.1.1245 beta available for general testing
Post by: guessed on May 15, 2011, 01:50:43 pm
oTi@,
Yes, there are cases where the UI indicates success, but under the covers it's not mounted.  I saw it a few times in the early development (using recycled keys) and once recently when the USB Key was spewing errors in logread

Unfortunately I haven't been able to narrow the conditions under which it gets out of sync like that.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 15, 2011, 07:40:43 pm
Hi-

  I have a question about the routing tables.

  For node 60 my Neighbors    are 1,8,9,10,12,13,14,15,16,31,33,39,59,61,

  But node 59 only has one neighbor node 1.

  How can that be? We have one way routing?

      Don
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 15, 2011, 07:46:13 pm
Hi--

  Why do I get the message "Heal Successful" if the heal is unsuccessful (and I get messages -->Unable to get any information on node)?

          Don

Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 16, 2011, 09:58:56 am
Yes, there are cases where the UI indicates success, but under the covers it's not mounted.
I see. Thought I got lucky when it all was successful. :) Should have checked.

Quote
[...]using recycled keys [...]
Unfortunately I haven't been able to narrow the conditions under which it gets out of sync like that.
Mmm, and I thought this was an excellent afterlife for that 128MB stick I found in the drawer...

Took a quick look at the scripts. It seems she doesn't like sticks that have no recognizable partitions. Played with it a little bit, partitioned and formatted it manually, but gone after reboot. Will take another look.

Did see your post (http://forum.micasaverde.com/index.php?topic=6439.msg39551#msg39551) on this. Will add to that, if I find anything.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 16, 2011, 10:51:05 am
Why do I get the message "Heal Successful" if the heal is unsuccessful (and I get messages -->Unable to get any information on node)?
The UI is not smart enough to know the difference.
It's the same issue when you click "Configure node now" and get the message "Node configured" and then it tries to configure the node.
If it were up to me I would change the display messages to "Heal completed" & "Configuring node" Oh well..

  I have a question about the routing tables.
  For node 60 my Neighbors    are 1,8,9,10,12,13,14,15,16,31,33,39,59,61,
  But node 59 only has one neighbor node 1.
  How can that be? We have one way routing?
 
Neighbor nodes are the devices that a particular device sees at any given time. They do not represent the route.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 16, 2011, 11:24:14 am
Hi JOD --

  Thanks for the information.

  Was interested specifically in the door locks. Node 60, in my example, is a lamp module; node 59 is a schlage door lock. They are located three feet from one another. BUT, the lamp module sees 14 other nodes, the door lock sees only Vera 2 (one node).

   Since they are located so close to one another, was wondering why #60 sees 14 other members of the network, #59 sees only one?

   Also, how do I fix that.. I have very limited connectivity to the door lock, and great connectivity for the light. I need better connectivity for the door lock. I've run repair a dozen or more times and it doesn't make any difference.

  Thanks in advance for your help.  :D

     Don
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 16, 2011, 11:41:02 am
Was interested specifically in the door locks. how do I fix that.. I have very limited connectivity to the door lock, and great connectivity for the light. I need better connectivity for the door lock. I've run repair a dozen or more times and it doesn't make any difference.
I see you are running Version 3.20 L:1. Have you looked over the heal report? Do you see data for "Edge Node"?
With .1245 you should be able to define the route yourself. I'll see if I can find the link that explains how. I'm still running 2.78 so have not had any experience with setting this up.

Any user out there used "Manual routing" and care to chime in with a how to?

JOD.


Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 16, 2011, 11:58:01 am
Hi JOD --

  I have been doing "routing updates only" as part of the repair. These updates do not produce a repair report..  Also, on doing a full repair, nodes only have limited connectivity do not configure and are "lost" from the routing entirely.

  Also, it would help to define terms.  Not sure what specifically and "Edge node" is.

  Thanks again for your help.

     Don
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 16, 2011, 12:43:08 pm
I have been doing "routing updates only"
If you have never performed a full heal network, (at least 3 times) I'm not sure that a routing update will do anything for you as you dont have a route to update, except the 1 hop direct route.

Quote
Not sure what specifically and "Edge node" is.
An Edge node would be a device to wake your lock, FLiRS  ;D (Frequently Listening Routing Slave) and if Vera can't communicate with the lock directly (lock is out of range) you would need an Edge Node that is FLiRS (aka BEAM) capable in between Vera and the lock to wake the lock before passing the packets.
[/quote]

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 16, 2011, 03:30:04 pm
Hi JOD --

  Thanks for the information.

  I assume that the GE/JASCO light switches are FLRS compatible? How far can they physically beam?

     Don
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 16, 2011, 03:45:46 pm
Yes, the newer GE/Jasco's do support beaming. The distance is no different than any other typical device. 75'-100' in open air are the manufacturers specs, probably half that in a typical home setup would be my guess?

JOD.

Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 16, 2011, 05:43:10 pm
Hi JOD --

  How can I tell the new GE/JASCO devices that are FLSR compatible from the old ones?

  Thanks again  for your help. I would be nice if we could capture all this information in an updated wiki.

         Don
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 16, 2011, 07:19:49 pm
Quote
How can I tell the new GE/JASCO devices that are FLSR compatible from the old one
The firmware revision.

GE/Jasco Version 2.0a or 3.0a support beaming. If you didn't write down all the info from the device when you installed it you will need to remove the device and look on the side or back for the firmware or rev #.

Paper or plastic?  ;D

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 16, 2011, 07:39:44 pm
Hi JOD --

  Thanks.. For reference the version number for the GE/JASCO lamp and appliance module is in small print on the plug side on the lower left corner of the back.

      Don
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 16, 2011, 08:21:49 pm
Z-Wave firmware 5.02 and 4.52 support beaming. Which translates to 2.48 and up for the serial version, I think. Those are the second and third digit in the version string.

Example (3-way GE dimmer):

Capabilities    202,156,0,4,17,1,L,R,B,RS,|38,39,112,114,115,134,
Version            6,2,64,2,16
Manufacturer    GE/Jasco

2,64 -> 2.64 for the Z-Wave serial API = 5.02sp2 Z-Wave firmware = supports beaming.

(See also here (http://wiki.micasaverde.com/index.php/ZWave_Versions).)
Title: Re: 1.1.1245 beta available for general testing
Post by: Don Diego on May 17, 2011, 09:00:28 am
Hi oTi@ --

  Thanks for the information.

      Don
Title: Re: 1.1.1245 beta available for general testing
Post by: min2 on May 17, 2011, 10:49:50 pm
Hello, i needed some advice before I upgraded to 1.1.1245 from 1.1.1036.  I currently run 3 hsm 100s, 1 kwikset lock, 3 jasco switches, and ether rain controller.  My system has been running rock solid for a year.  I had upgraded to 1.1.1047 previously but reverted back because my system kept rebooting.  So basically after reading this entire thread I am a little nervous about upgrading especially the zwave firmware.  Please advise if I should even upgrade at all.  If so,  what procedure should I follow so I dont screw anything up.

Thanks,
Vera newbie
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 17, 2011, 10:53:12 pm
[...]My system has been running rock solid for a year.[...]
If it ain't broke, don't fix it?
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on May 17, 2011, 11:10:48 pm
@min2,

1.1.1245 is the best build I've used and have no hesitation recommending upgrading to it.. Moving forward to 3.2 could be an additional move at another time if you are hesitant.

FYI, Your currently running 1.1.1036? It has a bug where it shows the incorrect status for Kwikset locks.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: Dav1d on May 17, 2011, 11:36:23 pm
@min2

What do you hope to gain?

If the worst happens, and you need to reset your system, is what you hope to gain, worth the hassle of having to start over fresh? I'm a newbie, I'm starting on the ground floor, and this version does not feel like it is anywhere near ready to be called beta to me. Likely that will upset a few people here.

I hear you saying it has been rock solid, and it works for you, to my mind that's a great reason to stay with what you know.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 18, 2011, 04:14:24 am
@min2

What do you hope to gain?

If the worst happens, and you need to reset your system, is what you hope to gain, worth the hassle of having to start over fresh? I'm a newbie, I'm starting on the ground floor, and this version does not feel like it is anywhere near ready to be called beta to me. Likely that will upset a few people here.

I hear you saying it has been rock solid, and it works for you, to my mind that's a great reason to stay with what you know.

Upset is not the word, maybe you just dont have the experience JOD has.

Ive run 1047 (upgraded after it came out of the box and gave no issues) and upgraded to 1245. Its stable, no problems and yes of course it has bugs, as any other firmware/software package has. Dont get scared off by this thread for that reason.

Upgrading to 3.20... id stick to the advice JOD gave... save it for later if your system is up and running on 1245 for some time and you feel the "need"  to upgrade.

I myself have a very small network so little impact. On yours with all the variables... id wait a bit!
Title: Re: 1.1.1245 beta available for general testing
Post by: min2 on May 18, 2011, 09:56:29 am
Thanks for your help guys.  I will upgrade to 1245 but leave the zwave firmware alone for now.  Since I use a kwikset, I wanted to fix the status bug. 
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 19, 2011, 08:37:23 pm
What is the plan now ? Releasing another beta to correct some problems reported here ? Making this 1.1.1245 version the official release ?

From MCV:
.1245 is out actually, and is official.  micasaverde.com/vera2 will upgrade you.

All new Vera's get .1245 by default.  We're making it an automatic upgrade for all other users this week.
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 20, 2011, 02:58:35 am
yay! Firmware 1.1.1245 is official!

Does anyone know why the urls return "not found"? or am i the onlyone experiencing this?

http://micasaverde.com/vera2
http://micasaverde.com/vera2?beta=1

Might be of course because im already on 1245, but still, strange error message

For those upgrading and would like to know what changed,
read this:
http://wiki.micasaverde.com/index.php/Release_Notes
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on May 20, 2011, 07:07:05 am
Does anyone know why the urls return "not found"? or am i the onlyone experiencing this?
I seem to be getting the standard upgrade screens (now).
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 20, 2011, 07:20:44 am
Does anyone know why the urls return "not found"? or am i the onlyone experiencing this?
I seem to be getting the standard upgrade screens (now).

Ill check when im back home and report back

--edit--
Error 404 "not found"

Im using Chrome and forced https connections.
Ill try IE *yuck*

--edit--
Yep IE works.. most probably my HTTPS enforcement.
NOTE to self: Disable Chrome HTTPS enforcement and local authentication before updating Vera (nice and safe!)
Title: Re: 1.1.1245 beta available for general testing
Post by: ballroller on May 21, 2011, 06:42:41 pm
MCV customer support had me (nervously) upgrade to .1245. It went smoothly with no problems. Thankfully.

Will any of these versions speed up the time it takes to save data, or is it a function of the chip involved?
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 22, 2011, 05:50:45 am
@ballroller

check the release notes. I published the link a few messages earlier.
1245 provides a lot of stability improvements and bug fixes.

Maybe the response time you mentioned is improved to, but you should notice that soon enough!

Let us know what your experiences with 1245 are!
Title: Re: 1.1.1245 beta available for general testing
Post by: huogas on May 22, 2011, 04:53:39 pm
Just upgraded to 1.1245/3.2

Everything goes well so far.

Bravo !
Title: Re: 1.1.1245 beta available for general testing
Post by: xlurkr on May 22, 2011, 07:09:28 pm
I am still getting the "ZWave: Failed To Start" message.  This is a Vera 1, upgraded from a perfectly-functioning 1.0.996.  What now?

-Tom
Title: Re: 1.1.1245 beta available for general testing
Post by: Intrepid on May 22, 2011, 08:49:17 pm

If the worst happens, and you need to reset your system, is what you hope to gain, worth the hassle of having to start over fresh?

This may be best asked in a new topic, but...

Can anyone explain the process of 'starting over'?  I have not had to, I back up after most changes, but the backup contains what and would help me how if I did have to restart?

I'm concerned about having to re-create all my scenes and addons.  What's the best way to prevent/prepae for a start over?

Title: Re: 1.1.1245 beta available for general testing
Post by: djrobx on May 22, 2011, 11:33:29 pm
A friend of mine had the "Z-Wave: fail to start" error also with a Vera2.   He tried rebooting and restoring factory settings and it just wouldn't work. 

He reverted to 1183, and restored his backup and all was well.   He tried the upgrade again and it worked perfectly fine the second time.

My Vera1 had no problems.
Title: Re: 1.1.1245 beta available for general testing
Post by: xlurkr on May 23, 2011, 12:16:13 am
djrobx:

Thanks for the reply.

I have already tried several times (5, I think), though each time it has been from a UI2 build, mostly 1.0.996.  Maybe I'll try an intermediate UI4 build.

Has no one else had a similar problem?

-Tom
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on May 23, 2011, 02:20:02 am

If the worst happens, and you need to reset your system, is what you hope to gain, worth the hassle of having to start over fresh?

This may be best asked in a new topic, but...

Can anyone explain the process of 'starting over'?  I have not had to, I back up after most changes, but the backup contains what and would help me how if I did have to restart?

I'm concerned about having to re-create all my scenes and addons.  What's the best way to prevent/prepae for a start over?



AFAIK everything gets backed up except devices.

Quote
you cannot restore your devices from a backup, you have to pair each of them again. Before proceeding you have to manually unpair all the devices, otherwise you will create duplicate nodes which will compromise your Z-Wave network.
http://wiki.micasaverde.com/index.php/ZWave_Options

Maybe refer to these for more info:

http://wiki.micasaverde.com/index.php
http://wiki.micasaverde.com/index.php/Clone_Dongle
Title: Re: 1.1.1245 beta available for general testing
Post by: xlurkr on June 02, 2011, 02:19:26 am
Maybe I'll try an intermediate UI4 build.

Has no one else had a similar problem?

-Tom

Update: MCV support bailed me out.  They suggested I flash with 1.1.1062, and that worked.  Then I upgraded to 1.1.1245, and that's working great, too.  Maybe you can't go straight from 1.0.996 to 1.1.1245 on a Vera 1?

-Tom
Title: Re: 1.1.1245 beta available for general testing
Post by: Henk on June 02, 2011, 03:21:02 am
Maybe I'll try an intermediate UI4 build.

Has no one else had a similar problem?

-Tom

Update: MCV support bailed me out.  They suggested I flash with 1.1.1062, and that worked.  Then I upgraded to 1.1.1245, and that's working great, too.  Maybe you can't go straight from 1.0.996 to 1.1.1245 on a Vera 1?

-Tom

This sounds like its a know problem to MCV. Might be usefull to add that to the How To steps on upgrading Vera 1.
If so, a little more info from MCV would be usefull....
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 06:13:08 pm
OK, I am finally ready to make this jump.  How can I get my V1 (1.0.988) to accept the URL for the 1.1.1062 "baby step" upgrade?  I am able to download from here using my browser:

http://download.mios.com/backfirebetafirmware/wl500gP_Luup_ui4-1.1.1062-1.squashfs

But when I try to get Vera to download that, I get an "Invalid Firmware URL" dialog, and nothing further.

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 06:29:46 pm
Hi Richard,

Personally, I would make the jump straight to 1245 and avoid the issues of 1062
But, try this.
Copy & paste this link into the "URL for OpenWRT custom firmware" under the Firmware tab of Advanced and click Download.

http://download.mios.com/firmware/wl500gP_Luup_ui4-1.1.1062-1.squashfs

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 06:39:31 pm
Unfortunately, for those of us just leaving the dark ages (UI2), there's no Firmware tab under Advanced.  Just "Downloads", which has a textbox I can paste an URL into--and it doesn't like the format or something about these.

BTW, this is a V1, coming from UI2.  It's a big jump.  There are posts right above in this thread saying this is what MCV advocated to resolve someone's issues.  I'm not planning on staying at 1062--just using it as a stepping stone.

--Richard

Update:

http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1062-1.trx

Seems to be something my ancient firmware can grok.  Abandon all hope--here we go again.


Hi Richard,

Personally, I would make the jump straight to 1245 and avoid the issues of 1062
But, try this.
Copy & paste this link into the "URL for OpenWRT custom firmware" under the Firmware tab of Advanced and click Download.

http://download.mios.com/firmware/wl500gP_Luup_ui4-1.1.1062-1.squashfs

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 06:43:24 pm
Right!!!

So you are on findvera.com and not Mios.
Give me a few minutes.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 06:56:28 pm
Choose Setup, Advanced, Download.
Copy the URL into 'download' and click 'Download'

JOD.

*Edit. In case you didn't notice the two links are not the same.
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 07:43:33 pm
Choose Setup, Advanced, Download.
Copy the URL into 'download' and click 'Download'

JOD.

*Edit. In case you didn't notice the two links are not the same.

Yes.  The download worked, and as before, I don't seem to be able to get to this Vera now using cp.mios.com.  It tries, it fails.  Clicking on the links "enable tech support", etc do nothing.

Connected a laptop to it via hardwire to LAN2 port.  Set the laptop's IP to 192.168.81.2, gateway 192.168.81.1.  tried going to 192.168.81.1 using Internet Exploder, and get nothing.  Yes, I had the V1 set up with a static IP before, and just running as a switch.  I suspect the reason we're getting nowhere is it lost it in the "upgrade", and now isn't quite a proper citizen on the LAN here.

For a V1, isn't this the right life support attempt?  FWIW, the laptop's ETH port is lit up orange, which usually means the card doesn't believe it's hooked to  a useful network.  Any ideas of what to  poke next?  I am rapidly recalling why I gave up on this and did the painful reversion before.

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 07:54:55 pm
Good news!
If you havent already, you will need to set up an account on Mios.com

JOD.

*Edit. Dont give up yet, I think for V1 you need to connect to LAN 1
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 08:16:42 pm
Good news!
If you havent already, you will need to set up an account on Mios.com

JOD.

*Edit. Dont give up yet, I think for V1 you need to connect to LAN 1

I've tried that, but will try again.  I have a cp.mios account.  It sees my Vera SN, and thinks it has a local IP of 192.168.1.50.  My Cisco router doesn't think it has a DHCP client lease outstanding with that IP.  The old static internal was 192.168.1.10.  Pinging .50 does nothing.  Pinging .10 does nothing.  But I suppose they may have these guys configured to ignore ping requests.

What I see when I login to cp.mios is that I get to the "loading data in progress" and its buddy "server busy", and then I get a dialog with a pile of links to click that also hang and do nothing.

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 08:25:42 pm
Forget about Mios.com for now, the "loading data in progress" and "server busy" dont mean anything if i dosent load, heck, you dont even need a vera conncted to see those messages.
Have you changed the IP of your laptop to 192.168.1.2 and tried a direct connect on LAN1?

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on June 02, 2011, 08:39:01 pm
But I suppose they may have these guys configured to ignore ping requests.
Should be pingable (at least with current FW).
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 09:20:13 pm
But I suppose they may have these guys configured to ignore ping requests.
Should be pingable (at least with current FW).

Well, thanks for that info.  The poor thing has gone catatonic--it's chosen itself some funny address that isn't valid on the subnet it's on...not a DHCP lease it's gotten.  The LAN1/2 ports don't expose the 192.168.81.1 address it sounds like they're expected to.

Where do I launch my message upon a flaming arrow to file a trouble ticket?

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 09:27:20 pm
Have you tried rebooting it?

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 09:29:12 pm
Have you tried rebooting it?

JOD.

If you mean power-cycling it, perhaps twenty times now.

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on June 02, 2011, 09:39:53 pm
The poor thing has gone catatonic[...]
Wireshark installed on the laptop by any chance, power cycle Vera and see what happens?
Title: Re: 1.1.1245 beta available for general testing
Post by: strangely on June 02, 2011, 10:32:48 pm
Have you also tried 192.168.1.1 as address to ping or connect to? I'm not sure the V1 always uses that like the V2 IIRC.
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 02, 2011, 11:25:48 pm
Have you also tried 192.168.1.1 as address to ping or connect to? I'm not sure the V1 always uses that like the V2 IIRC.

Wireshark--nothing interesting.  Mostly the laptop crying into the night "who's my mama?".

I've tried pinging both 192.168.81.255 and 192.168.1.255 from a laptop connected to both the WAN and LAN ports.  Since these are the broadcast addresses, if Vera was paying attention to anything in those subnets/24,
it would have answered.

Time to rename this thing "Harpo".

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 02, 2011, 11:41:16 pm
If the upgrade completed ok, Vera should be there somewhere and she should have been on your original static IP.

However, if you feel you need tech support, this may be another & quicker solution.
http://wiki.micasaverde.com/index.php/Firmware_Flash

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: rlmalisz on June 03, 2011, 10:19:23 pm
If the upgrade completed ok, Vera should be there somewhere and she should have been on your original static IP.

However, if you feel you need tech support, this may be another & quicker solution.
http://wiki.micasaverde.com/index.php/Firmware_Flash

JOD.

I gave up on it for last night, but got up early this morning and flashed to 1.1.1062 using the V1 flash utility.  It looked like that failed, so I took the dog walking.  When we got back, Vera was alive and responsive.  Prompted me to upgrade to 1.1.1245, which I let happen.

Summary: I am up and running.  Vera lost track of what the names for about half the devices were, so I had to sort them out by hand.  HRSD1s all show up as motion sensors now, but I guess that's par for the course.  Lost all my scenes, but I got most of them recreated after work today.  Still have a few to go, and need to rejigger things for the Foscam.  And then deal with SQ Connect again.  But I believe the direction of motion is forward now.  Thanks for all the support.  There must be something funny about my UI2 settings that bricks the V1 on upgrade every time.

--Richard
Title: Re: 1.1.1245 beta available for general testing
Post by: surfingman1 on June 27, 2011, 10:48:46 am
I upgraded to Internet Explorer 9 now the dashboard will not work. Example click on advanced. The box comes up but none of the tabs function. Anyone else having this problem?
Title: Re: 1.1.1245 beta available for general testing
Post by: JOD on June 27, 2011, 04:07:37 pm
@surfingman1,

Try a Ctrl F5.

JOD.
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on June 28, 2011, 12:11:21 am
[...]Internet Explorer 9 [...] dashboard will not work.
Appears to work. As @JOD said, try refreshing/clearing caches and such.
Title: Re: 1.1.1245 beta available for general testing
Post by: surfingman1 on June 30, 2011, 10:34:02 am
Tried everything. Still not working. Could it be vera? Is there a way to download the firmware again?
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on June 30, 2011, 11:00:29 am
Tried everything. Still not working. Could it be vera? Is there a way to download the firmware again?
Not working with any other browser either, same symptom?

(Re-flash instructions are here (http://wiki.micasaverde.com/index.php/Firmware_Flash_Vera2). And a recent thread (http://forum.micasaverde.com/index.php?topic=6938.msg44403#msg44403). Not sure this is your issue though. Everything was fine with IE8? Maybe MCV Support has an idea?)
Title: Re: 1.1.1245 beta available for general testing
Post by: Jukka on June 30, 2011, 01:00:54 pm
I have the same problem.  I have Vista 32 bit and Internet Explorer 9 in my main computer. If I click advanced button nothing happens. If I click wrench “button” nothing happens. If I use IE9 compatible mode then I get message box saying "Your browser is no longer supported". If I then click advanced button > Advanced window opens but there are no tabs. If I click wrench “button” > "device settings window" opens but there are no tab.

If I use Google Chrome everything works.

In my laptop computer I have Windows 7 64 bit operating system and Internet Explorer 9. In that computer all works. I can open Advanced window and all tabs are visible. Also clicking wrench “button opens devise settings window and all tabs are visible.

I have tried to find what settings are different in both IE9 but can’t find the reason for this phenomen.
Title: Re: 1.1.1245 beta available for general testing
Post by: vincenthimpe on July 16, 2011, 05:52:42 pm
i have the same problem but with the 'delete' (trashcan) icon.
on some computers it works ( remote login )
local login it doesnt. my machines are W7-64 bit IE9

Also the mios marketplace requires popup blockers to be off.
they rely on a popup to actuall commit the install.
Title: Re: 1.1.1245 beta available for general testing
Post by: MNB on August 23, 2011, 02:42:40 pm
Z-Wave firmware 5.02 and 4.52 support beaming. Which translates to 2.48 and up for the serial version, I think. Those are the second and third digit in the version string.

Example (3-way GE dimmer):

Capabilities    202,156,0,4,17,1,L,R,B,RS,|38,39,112,114,115,134,
Version            6,2,64,2,16
Manufacturer    GE/Jasco

2,64 -> 2.64 for the Z-Wave serial API = 5.02sp2 Z-Wave firmware = supports beaming.

(See also here (http://wiki.micasaverde.com/index.php/ZWave_Versions).)
[/list]
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on August 23, 2011, 09:50:46 pm
@MNB,
Upon review of my devices; [...]
I think it's consistent:

9 < 40 < 64 < 78, which leaves the GE/Jasco, the 2GIG t-stat and the Kwikset lock.

The Kwikset requires a beaming device. And perhaps the 2GIG does too; assuming it's the CT30; can't that t-stat be run on batteries? (But perhaps with hard-wired power it will provide beaming, like the GE/Jasco's).
Title: Re: 1.1.1245 beta available for general testing
Post by: MNB on August 24, 2011, 12:01:33 pm
oTi@ many thanxs for the email and response, agree with your assessment that 2.9 should be 2.09 which makes sense as to why Leviton switches can not beam. Is there perchance later firmware for the various devices and if so is it possible for the home owner to update? Mike
Title: Re: 1.1.1245 beta available for general testing
Post by: oTi@ on August 24, 2011, 12:40:50 pm
Is there perchance later firmware for the various devices and if so is it possible for the home owner to update?
The firmware in the Leviton devices (switches, dimmers, scene/zone controllers) cannot be upgraded.

Some devices have been updated: the lamp plug-in module (http://forum.mios.com/index.php?topic=6911.msg43948#msg43948) and the RS232 (http://forum.micasaverde.com/index.php?topic=6463.msg39877#msg39877) controller.