die die my darling (c)

[10der 832]

Please login or register to see this image.

 

Hi!

 

my new AEON Labs sensors (3pcs / cabinet / child room / child room #2) die periodically. 

 

[Wake Up Dead Nodes In Section] button solve a problem in seconds but not for long.  

 

PS: the situation with my Fibaro HC2 becomes more ugly every day...

 

UPD: distance between HC2 and sensors not more than 10m (~30 foot)

Edited September 30, 2016 by 10der

[Sankotronic 2,370]

Why do you think that problem is in Fibaro HC box? Can you be definitely sure that problem is not in sensors them selves? I had similar problem with one sensor and double relay switch (both Fibaro made) that went dead from time to time. One would expect that mesh network with time build device neighbor table but it seems that it is not the case in all occasions. So I did mesh network reconfiguration on neighbor devices and this sensor and relay and after that they never showed up again as dead even after power failure.

 

By the way, my darling Angelina (name we give to our smart house) is getting more and more smart and capable day by day.

[10der 832]

12 hours ago, chaicka said:

 

 

>>> an you be definitely sure that problem is not in sensors them selves?

 

I want to believe you, but you thinking what offhand died three (3) new sensors that I bought yesterday?

 

lol! 

[10der 832]

 

3 hours ago, Sankotronic said:

Why do you think that problem is in Fibaro HC box? Can you be definitely sure that problem is not in sensors them selves? I had similar problem with one sensor and double relay switch (both Fibaro made) that went dead from time to time. One would expect that mesh network with time build device neighbor table but it seems that it is not the case in all occasions. So I did mesh network reconfiguration on neighbor devices and this sensor and relay and after that they never showed up again as dead even after power failure.

 

By the way, my darling Angelina (name we give to our smart house) is getting more and more smart and capable day by day.

 

btw, sensors  back in UI when sensor detect motion, for example.

[10der 832]

so, i have checked.

3:00 PM - motion

no dead icons in UI

3:02 PM - red  " transfer failed" 

3:03 - dead icons in UI on AEON MultiSensor 6

 

as i can understand AEON MultiSensor 6 go to deep sleep.

 

wall.

[chaicka 195]

Are the MS6 included to HC2 with 'secured mode'?

Are the MS6 running on Batteries or USB-powered?

What is the software version running on HC2?

Edited October 1, 2016 by chaicka

[chaicka 195]

8 hours ago, 10der said:

 

>>> an you be definitely sure that problem is not in sensors them selves?

 

I want to believe you, but you thinking what offhand died three (3) new sensors that I bought yesterday?

 

lol! 

 

Not sure why you quoted me when your response is not related to my post.

[Sankotronic 2,370]

On 9/30/2016 at 11:49 PM, 10der said:

 

>>> an you be definitely sure that problem is not in sensors them selves?

 

I want to believe you, but you thinking what offhand died three (3) new sensors that I bought yesterday?

 

lol! 

You see, this sensors are new, recently added to the z-wave network, so do what I suggest you to do, reconfigure mesh network on this devices and nearby devices, one by one so that they check neighbors near by. You have to wake them up if are battery operated after giving command to reconfigure on HC. See picture bellow:

 

From drop down list first select nearby devices and reconfigure them, one at a time, then reconfigure this new sensors and it should be ok. It worked for me.

Edited May 2, 2017 by Sankotronic
Attachment quota filled up / deleting older stuff sorry :-(

[10der 832]

On 01.10.2016 at 8:51 AM, chaicka said:

Are the MS6 included to HC2 with 'secured mode'?

Are the MS6 running on Batteries or USB-powered?

What is the software version running on HC2?

1) I do not know. How I can check it?!

2) battery 

3) last stable 4.100

[10der 832]

On 1.10.2016 at 7:53 AM, chaicka said:

 

Not sure why you quoted me when your response is not related to my post.

I am sorry. My mistake. 

 

 

 

Btw, sensors still died. Zwave reconfiguration not solve my issues. 

Btw2: near dead sensor works (above 1 foot) Fibaro power socket.. as I can understand this device should help battery powered sensor be in a touch... 

[10der 832]

So, I have re-added one sensory in my cabinet via double click on function button.

now Fibaro show me "waiting for wake up" message. 

OK

[chaicka 195]

17 hours ago, 10der said:

1) I do not know. How I can check it?!

2) battery 

3) last stable 4.100

 

1. Sadly, no way to check available via the GUI. This is the response I have gotten from Fibaro just several weeks ago.

 

Thanks for providing more info and these helps me better understand your setup and relate to the device's potential issues I have come to learn/observe. Here is what I can share, based on observations and testing done (over last two-three months, with firmware 1.07 for this MS6):

 

• With HC2 software version 4.090 and earlier, the MS6 (f/w 1.06 or 1.07) running on batteries have a tendency to go 'dead node' randomly (may be a few days, may be a few weeks, no fix pattern). This particular part of the 'dead node' phenomena has nothing to do with battery dead. Simply manual wake it up and it will run fine for awhile, up to 3/4 weeks, very random and can be as short as 1-2 days.
• MS6 (f/w 1.06 or 1.07) running on batteries have a tendency to go 'dead node' when battery in slot 1 is drained while battery in slot 2 is still full. Simply manual wake it up and it will run fine for awhile, up to 3/4 weeks.
• HC2 software 4.x until 4.090 does not seem to like MS6 running in 'Secured Mode', esp. if the distance between MS6 and HC2 is more than ~2 meters. Missing motion, missing safe, etc may happen intermittently when distance is further. The 'dead node' phenomena seems to be more frequent too.
• With some tweaking of parameters, the interval between the above 'dead node' phenomena can be lengthen.

The above is the gist of my observations after months of testing MS6 through different HC2 software versions. There are other threads/posts within this forum that I have shared a great deal too. Search and have a read if it helps better understand what I am talking about.

 

Here is what's going to be interesting. With 4.091 beta, 4.092 beta and now 4.100 (only 4+ days on it), the above 'dead node' phenomena has not occur again for my setup with the customised parameter settings I have. Based on my notes written on each of the MS6 device, it has been stable since 27th August when I changed fresh pair of batteries and roughly coincide with the time when 4.091 beta released. The change log of 4.091 beta did not indicate much info but I have observed improvements in battery-operated devices (such as MS6 and ZXT-120).

[chaicka 195]

To put what I shared in perspective to your issue, I would recommend the followings, based only on the information you have provided thus far:

• Exclude the MS6 (since u do not remember whether it was included in 'Secured Mode'), wait awhile (say 3-5 mins, let HC2 background tasks to 'settle-in' after removal), re-include without secure mode (note: DO NOT check/tick the 'Add in security mode if device supports it' option in HC2),
• Tweak the parameters - wake-up interval, 4, 41, 101, 102, 103, 111, 112, and 113. The guiding principle is to reduce as much as possible redundant, unnecessary reporting/zwave traffic generated by MS6. Example: I do not need Battery, Temperature and UV to be reporting on such a high frequency so I place them in group 2 and 3 and set a very long interval for them so that it still meets my needs but not excessive reporting such as every wake-up interval. Oh, it will be good to be of multiples of wake-up interval so that it allows reporting to work every nth wake-up. 
• Optional: Reduce the distance between HC2 and MS6. I am not sure what is the max distance it will still behave well. So far the furthest for mine is ~3+m with 1 cabinet door and 2 walls (non-reinforced) in between.

 

Good luck. Hope this helps resolve or reduce the interval of its occurrence. As for me, I am keeping my fingers crossed that it is now permanently fixed with 4.100.

 

On 2.10.2016 at 10:50 PM, 10der said:

Btw, sensors still died. Zwave reconfiguration not solve my issues. 

Btw2: near dead sensor works (above 1 foot) Fibaro power socket.. as I can understand this device should help battery powered sensor be in a touch... 

 

Based purely on my understanding of z-wave and from information and issues of secured mode devices within this forum and Fibaro responses, I have formed a theory:

 

If a z-wave plus device is included in 'secured mode', it may not be routing through other z-wave nodes.

 

Again, I have not concrete proof to support this theory I have formed.

 

Reference Reads:

Please login or register to see this link.

Please login or register to see this link.

Edited October 3, 2016 by chaicka
Additional Notes/Comments

[10der 832]

Hey! 

please.

1) mark post as solved.

2) include in FAQ what some not Fibaro devices can added in Z-net as non-secure devices (!) by default

3) thank you so much, 

Please login or register to see this link.

 

have nice day, 

O!

Edited October 3, 2016 by 10der

[chaicka 195]

8 hours ago, 10der said:

Hey! 

please.

1) mark post as solved.

2) include in FAQ what some not Fibaro devices can added in Z-net as non-secure devices (!) by default

3) thank you so much, 

Please login or register to see this link.

 

have nice day, 

O!

 

May I ask what action solved the issue?

[alandee 79]

4 hours ago, chaicka said:

 

May I ask what action solved the issue?

I think he's getting at it with ;

 

12 hours ago, 10der said:

2) include in FAQ what some not Fibaro devices can added in Z-net as non-secure devices (!) by default

Added as secure initially I suspect.

Your support, as always on these forums, is impeccable Chaicka.

 

Cheers mate,

al.

 

Edited October 4, 2016 by alandee

[10der 832]

16 hours ago, chaicka said:

 

May I ask what action solved the issue?

after your question:

>>>Are the MS6 included to HC2 with 'secured mode'?

I have added sensor as secure device - this action solve my issue.

put another way: all 3 devices was added (at first time) as non-secure devices.

when i remove device(s) from FIbaro and add (double click on action button in MS6) as secure devices - all OK.

[chaicka 195]

On 03/10/2016 at 10:28 PM, chaicka said:

Here is what's going to be interesting. With 4.091 beta, 4.092 beta and now 4.100 (only 4+ days on it), the above 'dead node' phenomena has not occur again for my setup with the customised parameter settings I have. Based on my notes written on each of the MS6 device, it has been stable since 27th August when I changed fresh pair of batteries and roughly coincide with the time when 4.091 beta released. The change log of 4.091 beta did not indicate much info but I have observed improvements in battery-operated devices (such as MS6 and ZXT-120).

 

I may have jinxed it. One of the MS6 I have just went dead node on me this morning, after approximately 5 weeks of no issue. Upon manual wake-up, it shows battery is at 75%. Not too bad for a fresh set of batteries installed on 27th August to last 5 weeks and still have 75% left. But it means the overall random 'dead node' phenomena is still not resolve.

 

Please login or register to see this code.

 

Please login or register to see this code.