We have moved at community.getvera.com

Author Topic: 1.1.1245 beta available for general testing  (Read 87696 times)

Offline Henk

  • Hero Member
  • *****
  • Posts: 820
  • Karma: +3/-0
Re: 1.1.1245 beta available for general testing
« Reply #120 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
| Vera2 @ UI4 1.1.1350 / 3.20 | Vera Lite @ UI5 | Vera 3 @ UI5 | 2x Merten  504519 | 1x Duewi  064374 | 1x Everspring SM103 doorbell mod |1 Y-cam IP cam | various LUUP plugins |

Offline S-F

  • Hero Member
  • *****
  • Posts: 1248
  • Karma: +62/-12
  • Clueless N00b
Re: 1.1.1245 beta available for general testing
« Reply #121 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.
My forum account was apparently hacked by a leprechaun. And he's drunk all of the time. If a post of mine seems a little off kilter, it's probably because he made it.

Offline tbever

  • Sr. Newbie
  • *
  • Posts: 40
  • Karma: +0/-0
Re: 1.1.1245 beta available for general testing
« Reply #122 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.

Offline oTi@

  • Community Beta
  • Master Member
  • ******
  • Posts: 4041
  • Karma: +32/-6
  • UI what ?!
Re: 1.1.1245 beta available for general testing
« Reply #123 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.
Dezwaved at the moment...

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: 1.1.1245 beta available for general testing
« Reply #124 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.
I'm sorry, my responses are limited. You must ask the right questions.

Offline Soiferheld

  • Sr. Newbie
  • *
  • Posts: 29
  • Karma: +0/-0
Re: 1.1.1245 beta available for general testing
« Reply #125 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.

Offline oTi@

  • Community Beta
  • Master Member
  • ******
  • Posts: 4041
  • Karma: +32/-6
  • UI what ?!
Re: 1.1.1245 beta available for general testing
« Reply #126 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.
Dezwaved at the moment...

Offline S-F

  • Hero Member
  • *****
  • Posts: 1248
  • Karma: +62/-12
  • Clueless N00b
Re: 1.1.1245 beta available for general testing
« Reply #127 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 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?
My forum account was apparently hacked by a leprechaun. And he's drunk all of the time. If a post of mine seems a little off kilter, it's probably because he made it.

Offline axill

  • Full Member
  • ***
  • Posts: 183
  • Karma: +3/-0
Re: 1.1.1245 beta available for general testing
« Reply #128 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

Offline Henk

  • Hero Member
  • *****
  • Posts: 820
  • Karma: +3/-0
Re: 1.1.1245 beta available for general testing
« Reply #129 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
« Last Edit: May 09, 2011, 04:33:29 am by Henk »
| Vera2 @ UI4 1.1.1350 / 3.20 | Vera Lite @ UI5 | Vera 3 @ UI5 | 2x Merten  504519 | 1x Duewi  064374 | 1x Everspring SM103 doorbell mod |1 Y-cam IP cam | various LUUP plugins |

Offline huogas

  • Sr. Member
  • ****
  • Posts: 301
  • Karma: +0/-0
Re: 1.1.1245 beta available for general testing
« Reply #130 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 ?
??? ???
Vera2 UI4(1.1.1245/3.2), Kwikset x1, HM-DW001 x1, ZRP100 x1, HA-04WD x1, ZDP100 x6, HSM100 x2, VRI06-1LX x8, ZW5301 x1, HM-FS001 x2, ZRW103W x1, GE 45606 x2, HA05C x1, TED5000 x1

Offline axill

  • Full Member
  • ***
  • Posts: 183
  • Karma: +3/-0
Re: 1.1.1245 beta available for general testing
« Reply #131 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.

Offline Henk

  • Hero Member
  • *****
  • Posts: 820
  • Karma: +3/-0
Re: 1.1.1245 beta available for general testing
« Reply #132 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
| Vera2 @ UI4 1.1.1350 / 3.20 | Vera Lite @ UI5 | Vera 3 @ UI5 | 2x Merten  504519 | 1x Duewi  064374 | 1x Everspring SM103 doorbell mod |1 Y-cam IP cam | various LUUP plugins |

Offline dkeefe

  • Full Member
  • ***
  • Posts: 141
  • Karma: +0/-0
Re: 1.1.1245 beta available for general testing
« Reply #133 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.

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: 1.1.1245 beta available for general testing
« Reply #134 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
« Last Edit: May 14, 2011, 11:06:29 am by JOD »
I'm sorry, my responses are limited. You must ask the right questions.