Fibaro multisensor lost

[pos 22]

Hi

 

Just noticed I saw my newest Fibaro motion sensor (new device added 3 days ago) not reporting in to the controller. Opened it and pushed the button. Did not help. Re-inserted battery. Did not help. Change the device in the gui so it said "waiting for wakeup" it did not ever wake after the poll interval or by pushing the motion sensor button. It was lost. Did not see anywhere in the gui that it was dead either...

 

Tried to remove it the right way. Did not work. Still there...  Did try to add it again even though it existed in the gui. That worked (now double devices). Then I removed it again by unassign it. That worked as well. But the first device is still there hanging around. Had to hard delete it!

 

Then I did a factory reset on the multisensor and added it. Not it seems to work again.

 

Any clue of what could have caused it. Anyone else seen this? This has not happend before. Could the device be faulty?

 

The z-wave page in the gui says I have 35 devices. I have 4.150

 

/Peo

[Thomasn 77]

I would suggest to remove it from your Homecenter and the add it again - but with the motion sensor max. a meter (3 feet) from the Homecenter. Sometimes that helps.

[pos 22]

I did remove it and added it again. But I do not agree with your analys. It was added without errors and worked flawlessly for a few days. I think your suggestion better suites the case where if it was added and worked with problems from scratch. And that case is not what I described.

 

/Peo

[petergebruers 1,268]

When you clicked or triple clicked, what did the LED of this sensor do? If it did not do anything, I would say it was "crashed" or it is faulty. I do not think "crashing" is very likely. Maybe one user reported it, I cannot remember. But faulty isn't likely either, because now it seems to work again.

 

Can you do a range test? Just to confirm it is working correctly? This test performs the equivalent of "ping" on an IP network.

[Thomasn 77]

On 22/12/2017 at 9:08 PM, pos said:

I did remove it and added it again. But I do not agree with your analys. It was added without errors and worked flawlessly for a few days. I think your suggestion better suites the case where if it was added and worked with problems from scratch. And that case is not what I described.

 

/Peo

 

And a merry christmas to you too. Actually, I was trying to help you.

Edited December 23, 2017 by Thomasn

[pos 22]

20 hours ago, Thomasn said:

 

And a merry christmas to you too. Actually, I was trying to help you.

 

Just trying to be honest. But I did no mean to be rude if you felt it that way. I am sorry if that is the case.

 

/Peo

On 12/23/2017 at 10:34 AM, petergebruers said:

When you clicked or triple clicked, what did the LED of this sensor do? If it did not do anything, I would say it was "crashed" or it is faulty. I do not think "crashing" is very likely. Maybe one user reported it, I cannot remember. But faulty isn't likely either, because now it seems to work again.

 

Can you do a range test? Just to confirm it is working correctly? This test performs the equivalent of "ping" on an IP network.

 

Hi @petergebruers 

 

Range test is done and good now when it works again (it sits on the exact same spot). It actually sits 3 meters from the HC2. And just 1m from a repeater (dimmer2).

 

When it was lost I don't 100% remember the lights... But a click or a triple click did not do anything. The waiting for wakeup on the device in HC2 was still "waiting for wakeup after all clicks on the multisensor button.

 

When adding it a few days ago I put it up on the wall with the tape that came with it. It fell down on the flor from approx 2m height. Then I put it up again using a screw instead. The wall paint in that room was not optimal for using the tape. It continued to work after that. But later it was lost as I described earlier. As of today it still works after the lastest delete and re-inclusion described above.

 

Could maybe this drop in the floor have damaged it.  If not, what could have caused it?

 

Tnx

 

/Peo

[petergebruers 1,268]

15 minutes ago, pos said:

When it was lost I don't 100% remember the lights... But a click or a triple click did not do anything. The waiting for wakeup on the device in HC2 was still "waiting for wakeup after all clicks on the multisensor button.

 

15 minutes ago, pos said:

Could maybe this drop in the floor have damaged it.  If not, what could have caused it?

 

They are pretty robust... Maybe the battery got momentarily detached, this might cause the MCU to crash (firmware). Its pure speculation, but it is the "best case scenario" because the sensor will keep working from now on.

 

On the other hand, worst case, It might have a microscopic crack somewhere on the PCB (or a detached solder joint)... I can think of no way to establish this with certainty, not even with a microscope. But I have an idea!

 

What I would do is ... put it in a fridge for an hour (so between 0 and 6 °C). I'm not sure it will be able to report through all that metal, but that is not important. This will cause stress on the cracks (if there are any). Take it out after an hour and immediately wake it up to see if it is OK.

 

If you have the time, you can also test it at 40 - 45 °C using a "Bain-marie"

 

Please login or register to see this link.

 

So heat the water to  40-45 °C then turn off the heat and put the sensor in a waterproof insert. You'll have to be 100% certain about the temperature, please do not melt it ... With enough water, you can keep it at that temperature for roughly 15 minutes then take it out and test it.

[pos 22]

On 12/24/2017 at 12:30 PM, petergebruers said:

 

 

They are pretty robust... Maybe the battery got momentarily detached, this might cause the MCU to crash (firmware). Its pure speculation, but it is the "best case scenario" because the sensor will keep working from now on.

 

On the other hand, worst case, It might have a microscopic crack somewhere on the PCB (or a detached solder joint)... I can think of no way to establish this with certainty, not even with a microscope. But I have an idea!

 

What I would do is ... put it in a fridge for an hour (so between 0 and 6 °C). I'm not sure it will be able to report through all that metal, but that is not important. This will cause stress on the cracks (if there are any). Take it out after an hour and immediately wake it up to see if it is OK.

 

If you have the time, you can also test it at 40 - 45 °C using a "Bain-marie"

 

Please login or register to see this link.

 

So heat the water to  40-45 °C then turn off the heat and put the sensor in a waterproof insert. You'll have to be 100% certain about the temperature, please do not melt it ... With enough water, you can keep it at that temperature for roughly 15 minutes then take it out and test it.

 

@petergebruers I go for your "pure speculation" on the battery for now  This as it still works as expected now. Will try the other stuff if it happens anything more.

 

Tnx /Peo