Sensors die with 50% battery left

[Vinisz 15]

Hi All,

 

Does anyone else have the problem that sensors (or at least the fibaro multisensor) dies when there is 50% battery left ?

I did not receive a low battery warning (shouldn't with 50% left) but 2 sensors died while the HC2 reported 50% left...

 

 

[alexpelli 3]

I have the same problem from the very beginning

[T.Konopka 8]

What do you exactly mean by " dies"?

Either way, try replacing the battery and if this won't solve the problem contact our support.

[Vinisz 15]

Wel,, thats a very simple answer isn't it ? of course replacing the battery helps.

What I mean is, the fibaro HC2 reports 50% battery capacity left but the module stops working (marked ad "communication problem)

So, what use does a battery indicator have if it doesn't indicate proper battery cappacity ? 

[T.Konopka 8]

I meant that you should see if the same thing happens with a new battery. If the new one won't die at 50% then maybe the it was the battery's fault.
Communication problem hints at the fact that there's an issue with the network. How far away is the MS from your HC? Could you try setting it up closer and see if that solves anything?

[Vinisz 15]

It has nothing to do with range.... I have lots of devices and it is not the first time, the sensor normally works 100% of the time, for about 3/4 of a year now...

I had the problem before and hear some rumours that it might have to do with the default battery shipped with the sensor.

I replaced a lot of others but not these ones I think... so, the fault might be the battery but then it still is something fibaro can look after, because it is the shipped one.

[T.Konopka 8]

Still, I'd ask you to try that. If that does not help, then try with a new battery. If it turns out that it's the battery's fault, then we'll have an important information that we should consider shipping different batteries in the future.

[Thomasn 77]

3 hours ago, A.Smolinski said:

Still, I'd ask you to try that. If that does not help, then try with a new battery. If it turns out that it's the battery's fault, then we'll have an important information that we should consider shipping different batteries in the future.

 

Then you should really consider to change battery provider. I have expirenced the same: A Fibaro eye reported 50 % battery but died. A new battery worked. Needless  to say, the Fibaro eye was only 2 month old when it happened. This has happened twice with two different Fibaro eyes.

[Vinisz 15]

Tested it, and, As I was saying... not a range problem... only new batteries help....

I think these are the last two with orignal batteries still in them, I changed al the others (I own 18 of them.....) so I know what I'm talking about....

and @Thomasn is very right, this is a problem, I have seen things like this on the forum and since the fibaro HC2 system gets very unstable when it cannot reach his modules (don't know why that is) accurate battery info is important.

So, you indeed might consider changing provider for the batteries or make sure the provided info about current usage is correct.

[cyberlabs 2]

Yes, I can confirm that 'eye' with battery from the box works about 4 months, but sensor stop working with 50% indicator, without warning, so I was replace the battery for Duracell, and now works fine, see how long...

 

regards,

 

Chris

 

[T.Konopka 8]

Sorry guys, I posted in a wrong topic!

As for your case, We appreciate your feedback on this case.
However, I can't provide any other solution than replacing your batteries. The ones that are part of the original package are supposed to serve as a start-up battery and should simply be replaced when drained.

[Vinisz 15]

Sure, in english please ?

[Vinisz 15]

That's ok, I understand they drain faster then a replaced duracell but maybe you can do something in firmware that at least the battery cappacity is reported correctly ? 

[T.Konopka 8]

We're constantly working on this. In the meantime, placing it closer to the HC should improve the reporting.

[Vinisz 15]

Yeah, well, I totally ignore this answer, placing it closer ? I already told you I moved the sensors 1 meter away and they still do not report right.

Range is not the problem, reports are received at regular intervals without problems (It's z-wave -> Mesh network, remember ?) ... It is the cappacity value that is the problem...

And we're constantly working on this ??? come on.... the issue was reported before, you did nothing.... not a single change log shows anything you are improving this....

 

So, come up with good answers and real solutions and stop talking nonsense... You're not talking to a total noob here... 

 

[T.Konopka 8]

I took it as just a temporary measure, meant for testing. My bad, sorry.
We are working on this as it's a well known issue.

As I've said, we'll need a bit more of your patience. Until then, there's not much more I can recommend beside replacing the battery.