Troubleshoot a "missing" device.

[ppeterr 205]

So, i'm still setting up the HC3. And run into some problems. I have 2 Zwave devices: a 8 button wall switch and a Fibaro multi sensor.

The wall switch is configured to run some scene's. And the sensor is for later use, but also "adopted" in the device list.

This is the second time in a few days, that the zwave  devices stop working. The buttons stop activating the scene's, while when

i start the scene manually it still works. The multi sensor shows up with a red cross in the device list.

 

When i noticed this before, i just rebooted the HC3. And then it all works again.

 

How can i troubleshoot this ?  The console doesnt tell me anything..

 

Please login or register to see this attachment.

Edited July 19, 2021 by ppeterr

[ppeterr 205]

Well, this is what happend a few minutes ago.

 

I was looking around in the Zwave configuration tab.  Switching from the firmware tab, to the smart start tab.

 

This gave me a red box with "zwave protocol error", and after that, the cloud 401 image (not sure) i clicked it away 

a little to fast....

 

After this, the red cross was gone in the device list. And the wall buttons started to work. 

So i think, the protocol was reloaded, and started to function again.

 

Any ideas ?

 

I found the log file, but it seems encrypted?

LogsDump-HC3-00006194-19-07-2021_09_38_07.tar

Edited July 19, 2021 by ppeterr

[ppeterr 205]

Is it normal to get a decompress error at the logfile ?

[m.roszak 535]

Its encrypted.

Marking battery devices as dead (no connection) is correlated with wake up interval of specific node - if your sensor does not wake up to the controller in specified time (few times in the row) then device is marked as dead.
Please configure new wake-up interval for it in device settings and check if the issue will occur again.

Every value higher than 6h will be good for battery life.

Regards,
Michał 

[ppeterr 205]

32 minutes ago, m.roszak said:

Its encrypted.

Marking battery devices as dead (no connection) is correlated with wake up interval of specific node - if your sensor does not wake up to the controller in specified time (few times in the row) then device is marked as dead.
Please configure new wake-up interval for it in device settings and check if the issue will occur again.

Every value higher than 6h will be good for battery life.

Regards,
Michał 

 

Thanks Michal,

 

It was set to 0 s. 

I changed it to 25200 s / 7 hours

 

I'm not sure if thats good, or if it is related to the other zwave device not responding.

[m.roszak 535]

We will check it out (setting this to 0 should not result in marking device as dead).

Thanks for the input.


PS
As I understand, this is an old ZW300 Motion Sensor? Version 2.x? 

PS2
Z-Wave specification mandates for Z-Wave devices with Command Class Wakeup in version 1 to set wakeup interval as 0.
Probably because of that controller set this value during inclusion.

 

[ppeterr 205]

1 minute ago, m.roszak said:

We will check it out (setting this to 0 should not result in marking device as dead).

Thanks for the input.


PS
As I understand, this is an old ZW300 Motion Sensor? Version 2.x? 

 

Uhm thought it  was a recent model. Dont know actually

 

Versie

1.28

Node.Endpoint

8.0

[m.roszak 535]

Device version is from this field in interface?

Please login or register to see this image.

/monthly_2021_07/image.png.7f36650b13a22bc5ccc96ce2e20ac95d.png" />

[ppeterr 205]

Ahh sorry what i posted before was the wall switch

 

This is the sensor

 

Fabrikant

Fibargroup

Versie

3.3

Node.Endpoint

10.0

 

So actually the standard setting for the wake up interval is 7200 sec for the sensor.

I changed that one also to 7hrs. 

Edited July 19, 2021 by ppeterr

[m.roszak 535]

Understand, I was surprised to see version 1.28 as that one never existed in our Motion Sensor.
And this is a new revision (ZW500) so 7200s seems right as default. 

 

[ppeterr 205]

32 minutes ago, m.roszak said:

Understand, I was surprised to see version 1.28 as that one never existed in our Motion Sensor.
And this is a new revision (ZW500) so 7200s seems right as default. 

 

 

Just to make it clear for me, the "polling" the HC3 does every 7 hours now. 

Is something like "hey device, are you still there - wake up!" And it stays active ?

 

 

[akatar 207]

@ppeterr

No, the device is reporting to hc3. (i'm still here, are there any changes (settings etc))

after that it goed back to sleep, waking up for the next wakeup time or pir being breached, whatever comes first

 

Hc3 can not connect to the pir while it's asleep

 

Edited July 19, 2021 by akatar

[ppeterr 205]

28 minutes ago, akatar said:

@ppeterr

No, the device is reporting to hc3. (i'm still here, are there any changes (settings etc))

after that it goed back to sleep, waking up for the next wakeup time or pir being breached, whatever comes first

 

Hc3 can not connect to the pir while it's asleep

 

 

Thanks, learned something today   Hope it solves the little problem of the lazy sensor.

 

@m.roszak Thanks for picking this up. I will report back on it.