Problems with configuration

Community Playground Getting Started & Initial Setup
1

Hi,

I have a Vera Lite, curently talking to an Everspring 103 PIR, Fibaro FGS221 relay switch and a Danfoss Living Connect radiator valve.

I’m not doing anything with the configuration, but devices are almost constantly sitting in a state of “Waiting for device to wakeup for configuration.”

The PIR and Relay are right beside each other, but aren’t listing as neighbours (the PIR is on the Garage outside, and the relay is within the roof of the Garage).

The PIR is successfully tripping the lights, but seems permanently unconfigured.

The radiator valve, again, seems to be changing set points correctly, but is still showing waiting for configuration.

I’ve tried going out and “triggering” the PIR, but it doesn’t change anything.

The radiator valve was ok last night (it appeared to have “locked” onto the valve) but today it’s not, but the set points are setting correctly.

The distances involved aren’t great, but it’s a three storey house.

I’m mostly experimenting before committing to purchasing further valves and light switches (I do have a few more devices, but with these problems, I haven’t gotten round to wiring them in).

Any advice?

2

@kevinmcd,

Welcome!

For the PIR, I believe changing the state of the tamper switch will wake the sensor up for 10 minutes. Vera should be able to configure the sensor in that time frame. You can force the configuration by selecting [tt]Configure node right now[/tt]. See if that helps.

Similarly, for the Danfoss, is there a way to manually wake it up (by pressing a button, etc.)?

3

[quote=“oTi@, post:2, topic:172691”]@kevinmcd,

Welcome![/quote]

Thanks!

[quote=“oTi@, post:2, topic:172691”]For the PIR, I believe changing the state of the tamper switch will wake the sensor up for 10 minutes. Vera should be able to configure the sensor in that time frame. You can force the configuration by selecting [tt]Configure node right now[/tt]. See if that helps.

Similarly, for the Danfoss, is there a way to manually wake it up (by pressing a button, etc.)?[/quote]

I’ve tried that, after a day or less, it seems to go back to the same as before, I’ve tried healing, several times, and not changing much.

Earlier, I kicked off a heal with a stress test of 4, will see what I get.

I have the RfxTrx plugin installed, and it’s listening to Marmitek sensors, and doesn’t complain, just the z-wave stuff seems to be giving me headaches…

thanks,

Kevin

4

After you ‘fix it’, does it go back to the same state, even before 2am that night?

5

Just to clarify: you say the devices are functioning? The PIR trips the switch ok(which presumably is controlled from Vera or is it directly associated to the PIR?); and the Danfoss is taking the new setpoints (when it wakes up or by pressing the centre (*) button).
The Fibaro presumably does not have any error messages?
What default wakup intervals are showing up on the settings tab of both battery devices?

6

[quote=“Frasier, post:5, topic:172691”]Just to clarify: you say the devices are functioning? The PIR trips the switch ok(which presumably is controlled from Vera or is it directly associated to the PIR?); and the Danfoss is taking the new setpoints (when it wakes up or by pressing the centre (*) button).
The Fibaro presumably does not have any error messages?
What default wakup intervals are showing up on the settings tab of both battery devices?[/quote]

The PIR is being tripped through the Vera.

The default wakeup for the PIR is 1800 seconds, and, like clockwork, I can see the wakeup entries in the log.

04 09/14/12 21:11:56.129 <0x2ba2f680>

04 09/14/12 21:41:53.402 <0x2c013680>

I configured it, shortly after I started it, and set the Variable 3 value to 1, which should mean that it doesn’t sleep, and indeed, the battery is going down at a rather rapid rate.

I’ve tried changing it back to 0, “where 0 means power saving being enabled and others mean power saving being disabled.” which should fix it, it’s set as a “1 byte dec” as the SP103 manual refers to it being a signed value.

At the last wakeup (21:41:53) it didn’t configure.

The results of the most recent heal (stress level 4), worked, and the SP103 and Fibaro are now showing as neighbours.

The radiator valve wakeup was set to 300 seconds, i.e. 5 minutes, and I made no attempt to configure it, but it was picking up set points, but still showing unconfigured, when I set it up, it paired, and locked to the radiator, but today, it seems to have lost its pairing, and was loose on the radiator again.

I really have no idea what’s going on, other than looking at the logs on the machine…

I’ve pasted some logs below…

Any advice would be appreciated, if there’s any other info that might help.

thanks

Kevin

02 09/14/12 21:58:36.103 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
02 09/14/12 21:58:38.232 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
02 09/14/12 21:58:40.402 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>

Node 10 is the mains powered Fibaro FGS221.

02 09/14/12 21:49:36.114 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
02 09/14/12 21:49:38.492 ZWaveSerial::GetFrame 0x2c412f60 timed out now 0 m_listGetFramePending 0 <0x2c413680>
02 09/14/12 21:49:38.492 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2c413680>
01 09/14/12 21:49:38.493 ZWJob_PollNode::Run job job#22 :pollnode #10 (0xa3d3d8) N:10 P:100 S:1 ZW_Send_Data to node 10 failed 1 req 0xa4d660/1 abort m_iFrameID 0 <0x2c413680>
02 09/14/12 21:49:38.493 ZWJob_PollNode::PollFailed job job#22 :pollnode #10 (0xa3d3d8) N:10 P:100 S:1 node 10 battery 0 <0x2c413680>

02 09/14/12 21:57:06.103 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
01 09/14/12 21:57:06.560 got CAN <0x2c813680>
01 09/14/12 21:57:06.561 ZWaveSerial::Send m_iFrameID 335 type 0x0 command 0x16 got repeat failure 24 iNumFailedResponse 1 time 2164561 start time 2164540 wait 2000 m_iSendsWithoutReceive 0 <0x2c413680>
01 09/14/12 21:57:06.562 ZWaveJobHandler::SendDataAbort failed <0x2c413680>
01 09/14/12 21:57:06.562 ZWJob_PollNode::Run job job#27 :pollnode #10 (0xbb6fc8) N:10 P:100 S:1 ZW_Send_Data to node 10 failed 1 req 0xa4d660/1 abort m_iFrameID 0 <0x2c413680>
02 09/14/12 21:57:06.562 ZWJob_PollNode::PollFailed job job#27 :pollnode #10 (0xbb6fc8) N:10 P:100 S:1 node 10 battery 0 <0x2c413680>

And the Garage sensor…

02 09/14/12 21:41:53.272 ZWJob_SendData UPDATE MANUAL ROUTE 11=(nil) <0x2c013680>
02 09/14/12 21:41:53.288 UPDATE MANUAL ROUTE2 11=(nil) <0x2c413680>
02 09/14/12 21:41:53.288 ZW_Send_Data node 11 NO ROUTE (nil) <0x2c413680>
04 09/14/12 21:41:53.402 <0x2c013680>
02 09/14/12 21:42:06.103 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
02 09/14/12 21:42:08.242 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
02 09/14/12 21:42:10.382 ZW_Send_Data node 10 NO ROUTE (nil) <0x2c413680>
04 09/14/12 21:42:10.582 <0x2c013680>

7

Oh, and I have the Fibaro FGS221 being polled every 60 seconds, but I regularly see…

02 09/14/12 22:15:08.231 ZWaveSerial::GetFrame 0x2c412ef8 timed out now 0 m_listGetFramePending 0 <0x2c413680>
02 09/14/12 22:15:08.231 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2c413680>
02 09/14/12 22:15:08.232 ZWJob_PollNode::ReturnMessageNotReceived -end- job job#40 :pollnode #10 (0xbe3230) N:10 P:100 S:5 node 10 didn’t reply iOK 30 iBadTx 0 iNoReply 2 Abort returned m_iFrameID 0 <0x2c413680>
02 09/14/12 22:15:08.232 ZWJob_PollNode::PollFailed job job#40 :pollnode #10 (0xbe3230) N:10 P:100 S:5 node 10 battery 0 <0x2c413680>
06 09/14/12 22:15:08.233 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastError was: Poll failed now: Poll failed #hooks: 0 upnp: 0 v:0xa06568/NONE duplicate:1 <0x2c413680>
04 09/14/12 22:15:08.233 <0x2c413680>
02 09/14/12 22:15:08.234 JobHandler::PurgeCompletedJobs purge job#40 :pollnode #10 (0xbe3230) N:10 P:100 S:2 pollnode #10 3 cmds status 2 <0x2c413680>

So, speculation is, that the Z-wave just doesn’t have the range, this would be a big blow for me, but it’s puzzling, as I’ve noted, despite the Vera indications to the contrary, the switching is working.

In terms of the range, the Vera is on the top floor of the building (only thee storeys), and the distance between the house and the garage is no more than a narrow (1 metre max) passageway, the Fibaro is within a wooden roof, and the SP103 is on the outside.

Certainly, well within the 90ft projected in-house ranges I’ve seen for Z-Wave, I have an OWL CM160 talking to an RFXtrx433 inside Vera, and that’s fine, I have a Marmitek PIR, both talking to the RFXtrx433 and as far as I can see, they’re both working fine.

8

If you can’t reset configuration 3 from the Vera, the manual seems to suggest that removing the batteries should cause it to reset itself?

If you suspect that its a range problem then is it practical to relocate the Vera, even on a temporay basis to confirm this?
If that is the issue then maybe just adding a mains powered plugin module or switch closer on a lower floor might be enough to cure it once it finds the neighbours.

9

[quote=“Frasier, post:8, topic:172691”]If you can’t reset configuration 3 from the Vera, the manual seems to suggest that removing the batteries should cause it to reset itself?

If you suspect that its a range problem then is it practical to relocate the Vera, even on a temporay basis to confirm this?
If that is the issue then maybe just adding a mains powered plugin module or switch closer on a lower floor might be enough to cure it once it finds the neighbours.[/quote]

Sure, I’ll remove the batteries tomorrow in day-light, and reset it, it’s just odd that it’s waking up, checking in, but not reconfiguring, even with the “default” setting, which is supposed to set the device to its defaults…

I can actually put my Vera in the Garage, ethernet is no problem in there :slight_smile:

thanks for taking time to respond, I’ll update tomorrow.

Kevin

10

Ok,

I reset my Z-wave network, re-added the FGS221 in the Garage and the SP103 PIR on the outside, left it to run overnight, and the sensor was still waiting for the sensor to wakeup to configure.

I can see from the logs that it was waking up, the only configuration item in the setup was monitoring the Parameter 3, which indicates whether or not it’s sleeping or not, I had it on monitor, so it shouldn’t actually be configuring anything…but, am wondering if there’s a bug which tries to “configure” even for things that are not being configured.

The other puzzling thing for me is that again, the devices are not detecting neighbours, the FGS221 mains-wired relay had detected Node 1 (Vera), but the PIR had no neighbours, having moved the Vera to the garage and with the PIR and Relay within 2 feet of one another, I’d expect the PIR to see the relay directly…

Is there something I’m missing?

I’ve just kicked off yet another repair, with only routing and 4 cycles.

thanks

11

I encountered similar finicky behavour and found that I needed to be careful setting my devices near metal objects. My Fortezz leak detector warned about this and it seems it can be an issue.

It doesn’t take much nearby metal to interfere with the radio signals. I found by being careful about this I improved my range and reliability.