Help for the most wet-behind-the-ear noob ever

I’ll admit, I’m “that guy”. The guy who bit off more than he can chew. The one that shows up in forums, posts questions, and everyone starts PM’ing each other with subjects like “Can you believe he asked THAT?”

Anyway, I’m embarrassed at my noobness to the point that I’m ready to give up. I’m so clueless, I don’t even know how to describe the problems I’m having. Here’s my best attempt.

I bought a Vera Lite and set it up using the UI5 gui. With my one Aeon in-wall dimmer controller, it didn’t take long for me to figure out the logic limitations of the gui prevented useful condition-based routines. So I installed PLEG. I got one of the most basic scripts working - which boosted my confidence. So I went on a shopping spree.

I bought the z-wave cards for all three of my Kwikset locks, several in-line on/off and dimmer switches, 10 each of the smart dimming aeon controllers, and 10 of the same, as a switch. I also upgraded my Envisalink TP100 to the EVL3, and installed the DSC plugin.

For now, I’m limiting the ‘programming’ to the very basic IU5 scenes, and the PLEG routine I created earlier.

I’ve set up a routine where, when I enter a code on my kwikset, it triggers the disarm on the alarm. Likewise, locking any of the locks, or closing the garage door will cause VERA to arm the DSC.

Where the trouble started becoming apparent was when I unlock one of the locks, 90% of the time, that trigger will disarm the DSC within 2-3 seconds. But 1 out of 10, it’ll take 30+ seconds.

When I opened the log screen (the one that you can’t stop scrolling or reverse), I kept seeing a ton of ZW_Send_Data node XX NO ROUTE (nil) errors, and red messages like this: 01 02/15/14 20:27:16.291 ZWaveNode::DecryptMessage node 19 dev 20 failed and backup nonce is 0 <0x2b7db680>

The nodes and devices pointed to my keyless locks. Even when manually activating them through VERA, they seemed to perform the initial operation quickly, but subsequent operations were delayed by 10-20 seconds.

I ignored this, and continued to add more switches. At some point tonight, I started seeing the dreaded crash (stop 250) and reboot.

Knowing that, at this point, everything has been thrown together in no proper order or sequence, I figured I’d just wipe everything clean, and logically add devices. If first backed up (including the z-wave network) and then did a factory wipe.

On rebooting, before adding or restoring anything, I’m already seeing references to nodes that were previously there.

Is there any way to reset this box COMPLETELY so it is as it was when it was first taken out of the box? Do I need to exclude each device?

Regretfully, none of my problems (including error values) fit the search criteria in a way that is useful to someone like me. Nearly all search results and their corresponding explanations assume the reader has the most basic/fundamental understanding of programming, and RF network topography - which regretfully, I lack in spades.

In the interim, I’ve found the instructions on how to do a ‘complete’ reset:

  1. exclude all devices - did that by walking to each one with the VL in exclude mode
  2. Reset the z-wave chip
  3. Reset to factory

That seemed to do the trick, but on the initial reboot, the luaUPnP log showed that it crashed and restarted three times:

5/14 18:08:07.100	ZWaveJobHandler::SetDeviceStatus XXX2 0/0/0/0 <0x2b373680>09	02/15/14 18:08:08.101	Child_Devices::Synchronize removing 7 from parent 1 <0x2b373680> 06	02/15/14 18:08:08.102	Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastDongleBackup was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2b373680> 03	02/15/14 18:08:08.160	JobHandler_LuaUPnP::Reload: ChildDevices Critical 0 m_bCriticalOnly 0 dirty data 0 <0x2b373680> 06	02/15/14 18:08:08.262	Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 5 now: 2 #hooks: 0 upnp: 0 v:0xcb1800/NONE duplicate:0 <0x2b373680> 06	02/15/14 18:08:08.262	Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: Configuring ZWave devices now: Resetting ZWave Network #hooks: 0 upnp: 0 v:0xcc07e8/NONE duplicate:0 <0x2b373680> 09	02/15/14 18:08:08.263	ZWaveJobHandler::CheckReportChildDevices clearing backup flag <0x2b373680> 01	02/15/14 18:08:08.321	Mongoose XXX-mg_stop1 0xc82d08 1 1 <0x2ac40000> 01	02/15/14 18:08:10.321	Mongoose XXX-mg_stop2 0xc82d08 2 1 <0x2ac40000> 01	02/15/14 18:08:10.322	Mongoose XXX-mg_stop3 0xc82d08 2 1 <0x2ac40000> 01	02/15/14 18:08:10.322	Mongoose XXX-mg_stop4 0xc82d08 13340048 1 <0x2ac40000>   2014-02-15 18:08:10 - LuaUPnP Terminated with Exit Code: 250    2014-02-15 18:08:10 - LuaUPnP crash  01 2014-2-15 18:5:57 caught signal 6 <0x2b9e1680> 01 2014-2-15 18:7:8 caught signal 6 <0x2bfc5680> 01 2014-2-15 18:7:57 caught signal 6 <0x2be91680> 01 2014-2-15 18:8:10 caught signal 6 <0x2b973680> ---------------exited------------- PID USER       VSZ STAT COMMAND 1 root      1684 S    init 2 root         0 SW   [kthreadd] 3 root      

Now, before I start adding devices, is this something over which I should be concerned? Or is the “crash” just part of the initial setup process when a device is starting for the first time?

...the log screen (the one that you can't stop scrolling or reverse)...

and is so hugely frigging annoying, that I wrote this plugin:

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

[quote=“a-lurker, post:3, topic:179564”]and is so hugely frigging annoying, that I wrote this plugin:

http://forum.micasaverde.com/index.php/topic,13477.0.html[/quote]

In which I just happened to install today. Can’t believe I waited so long. If you have the room… This is one of the “Must-Haves”. Nice job @a-lurker!

I’d seen that thread before, but was overwhelmed at the installation process (told you I was green). Stuck through it now, and wow! I wish I’d done that sooner. Nice to be able to pause, scroll back, and filter.

I spent this evening adding back devices to a clean box. I think my initial problem was that my base devices were battery operated. This time, I installed every A/C powered device first, did a heal, and for the first time, everything came up with 5-stars in the heal report. I had ZERO before. I then added my locks. I have NO red lines in my log (other than initial UPnP).

I think I’m starting to feel a bit better.

[quote=“erkme73”]I’d seen that thread before, but was overwhelmed at the installation process (told you I was green). Stuck through it now, and wow! I wish I’d done that sooner. Nice to be able to pause, scroll back, and filter.

I spent this evening adding back devices to a clean box. I think my initial problem was that my base devices were battery operated. This time, I installed every A/C powered device first, did a heal, and for the first time, everything came up with 5-stars in the heal report. I had ZERO before. I then added my locks. I have NO red lines in my log (other than initial UPnP).

I think I’m starting to feel a bit better.[/quote]

Well done and stick at it and soon enough, you will be helping other through their problems!

[quote=“erkme73, post:5, topic:179564”]I’d seen that thread before, but was overwhelmed at the installation process (told you I was green). Stuck through it now, and wow! I wish I’d done that sooner. Nice to be able to pause, scroll back, and filter.

I spent this evening adding back devices to a clean box. I think my initial problem was that my base devices were battery operated. This time, I installed every A/C powered device first, did a heal, and for the first time, everything came up with 5-stars in the heal report. I had ZERO before. I then added my locks. I have NO red lines in my log (other than initial UPnP).

I think I’m starting to feel a bit better.[/quote]

Yes keep at it. Focusing on the mains powered devices to set your network was a great approach, and not a lot of “wet behind the ears” noobies (and former noobies) figure that out so quickly, so you are doing well!