I just upgraded the beta firmware and ran into a snag: The Z-wave chip/dongle in my vera2 isn’t being recognized so Z-wave isn’t starting and now won’t manage anything via scenes, etc. So, I figured I’d submit a trouble ticket, which was a good idea but the execution has become a problem since the submission process errors out with “Wrong response from server”.
Anybody know how to make my vera2 recognize the Z-wave chip?
From the LuaUPnP.log file during a “save” operation.
06 03/11/11 11:56:01.533 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastUpdate was: 0 now: 1299862561 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x400>
06 03/11/11 11:56:01.534 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 4 now: 4 #hooks: 0 upnp: 0 v:0x9a23a0/NONE duplicate:1 <0x400>
06 03/11/11 11:56:01.535 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: No ZWave dongle now: No ZWave dongle #hooks: 0 upnp: 0 v:0x9afb40/NONE duplicate:1 <0x400>
02 03/11/11 11:56:02.037 ZWaveJobHandler::Run connect to /dev/tts/1 -0 lock 1 <0xc04>
02 03/11/11 11:56:02.116 ZWaveJobHandler::Run connected to /dev/tts/1=1 i=0 <0xc04>
06 03/11/11 11:56:02.187 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 4 now: 7 #hooks: 0 upnp: 0 v:0x9a23a0/NONE duplicate:0 <0xc04>
06 03/11/11 11:56:02.188 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: No ZWave dongle now: Starting ZWave Network #hooks: 0 upnp: 0 v:0x9afb40/NONE duplicate:0 <0xc04>
03 03/11/11 11:56:06.972 ZWJob_Initialize::JobDone version 2.78 type 1 role is 2 house id 61d4c node id 1 suc 1 IsSecondary 0 bOnOtherNetwork 0 NodeIdServerPresent 1 IsRealPrimary 1 IsSuc 1 <0xc04>
06 03/11/11 11:56:06.980 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: VersionInfo was: 2.78 L:1 now: 2.78 L:1 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0xc04>
06 03/11/11 11:56:06.981 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: HomeID was: House: 61d4c Node 1 Suc 1 now: House: 61d4c Node 1 Suc 1 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0xc04>
06 03/11/11 11:56:06.982 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: Role was: Suc SIS:YES PRI:YES now: Suc SIS:YES PRI:YES #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0xc04>
04 03/11/11 11:56:06.985 <Job ID="0" Name="init" Created="11-03-11 11:56:02" Started="11-03-11 11:56:02" Completed="11-03-11 11:56:06" Duration="4.363044000" Runtime="4.361322000" Status="Successful" LastNote=""/> <0xc04>
01 03/11/11 11:56:07.120 ZWave::Start Initialize unrecognized Z-Wave module <0x400>
06 03/11/11 11:56:07.121 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 7 now: 6 #hooks: 0 upnp: 0 v:0x9a23a0/NONE duplicate:0 <0x400>
06 03/11/11 11:56:07.122 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: Starting ZWave Network now: Failure #hooks: 0 upnp: 0 v:0x9afb40/NONE duplicate:0 <0x400>
06 03/11/11 11:56:07.123 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastError was: Timed out initializing dongle now: Unrecognized Z-Wave module #hooks: 0 upnp: 0 v:0x9bbbd8/NONE duplicate:0 <0x400>
01 03/11/11 11:56:07.125 ZWave::StartupSuccess failures 6 <0x400>
01 03/11/11 11:56:07.125 JobHandler_LuaUPnP::StartPlugins ZWave failed to start <0x400>
02 03/11/11 11:56:07.132 JobHandler_LuaUPnP::StartPlugins Energy STARTED <0x400>
Whew… Downgrade to 1.1.1186 seems to have been uneventful.
Guess I’ll have to live with the limitations inherent in the current Z-wave firmware rev in terms of routing for now.