Help diagnosing HC2 cause of battery drain on some Aeotec & Sensative devices

[k1s 1]

Hello,

 

Could somebody help me diagnose the cause of battery drain on  some Aeotec Recessed Door Sensors & Sensative Strips.  I have many of each but 5 of the Recessed Door Sensors chew through batteries in a matter of days and 6 of the Sensative Strips have red battery icons within a few weeks of installation.  None of the devices get triggered much - between 0 and 10 times per week.  

 

Aeotec, Fibaro & the retailer said try extending the wake-up interval, but that doesn't explain why several devices next to eachother don't behave the same way - e.g. An Aeotec recessed door sensor in one door works fine with the factory supplied batteries but the recessed door sensor next to it - with exactly the same factory default settings drains the batteries in a few days.

 

Fibaro Supoort's email response was:

"To be honest, Aeotec response is preservative and equivocal I will say. As you probably know, the thing is that the Aeotec door sensor is sending to our HC redundant command frames. It does not have to be HC fault. Battery durability of our Fibaro d/w sensors are around about 1-2 years and everything is working perfect and smooth. There is no redundant communication....Frankly speaking, diagnosing does not gives us many ways to go. It is not technically possible to disable/enable any command frames on Aeotec device or HC. We can not influence this frequency."

 

...which seems very lame. 

On the on hand they claim the Aeotec device sends redundant commands, but on the other they say can't diagnose it.  As the retailer put it "they're the only ones with root access to their controller and theoretically should be able to see how often device A wakes up / reports something to the controller."

 

...and like I said, why would some be sending redundant commands and not others?  And why some would devices of different manufacturers be behaving the same way, but not all of them?

 

 

 

 

 

 

 

 

[tinman 1,070]

1 hour ago, k1s said:

 

Could somebody help me diagnose

 

 

sure

[k1s 1]

14 hours ago, tinman said:

 

sure

Great, thanks, where do I start?