Motion Sensor goes crazy !!

[alijanah 1]

We have a serious issue with one of the customer house integrated with the fibaro motion sensors.

 

Here's a synopsis of the errors with the Fibaro modules.

 

Two of the Fibaro Motion sensors (round globes) is now going crazy, and reporting itself as Temperature Sensor, or Humidity sensor, instead of Motion sensor. There are also several cases of it stating that the temperature in the room exceeds 200deg C and possible fire, and spaming the email/notification every minute or so.

 

This started happening first on the TKB Door contact (which I was unable to 'unbreach'), and then after some time, it escalated to the Fibaro Motion sensor. So far, 1 TKB and 2 Fibaro Motion sensors has failed.

 

Fibaro HC 2 details:

 

Serial number: HC2-007570

MAC Address:00:22:4d:a9:ac:be

Software Version:3.600

Last Backup:2014-12-31 13:03:34

 

 

Some screenshots:

 

1. Fibaro Motion Sensor (Laundry area)

 

Laundry area sensor is reporting as humidity, with 0% no thumbpic and Device Kind as Humidity Sensor

 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

 

2. Fibaro Motion Sensor (Rear Hse area)

 

Rear Hse area sensor is reporting as temperature, with 0C, no thumbpic and Device Kind as Temperature Sensor

 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

 

I have tried to reset it and also pull out the battery (btw, you can see that battery icon is all full), but it seems like I can't even exclude the sensor from the Fibaro HC2.

 

 

As a comparison, this is how it should be like, when it's correctly operating:

 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

 

Here is also a similar problem, and there are several reports on the net which is on the same trend:

 

Please login or register to see this link.

 

 

Seriously. I don't know if this is due to the HC2 or defective batch of sensors. What should we do in this matter ? 

 

Thank you and looking forward to hear from you very soon.

[emielstroeve 22]

I also have problems with my 2 motion sensors, unreal humidity levels is what I see. Reset them, excluded/included them, doesn't seem to help.

 

cheers

emiel

[petergebruers 1,268]

You are using V 3.600 and for that version your problems are "known". They're fixed in version 4. But upgrade to V4 can be anything from easy to near impossible, and there are other issues. So please tell us if you're planning to do so. BTW as far as I know (I'm not from Fibaro) these issues will not be fixed in version 3, because they need drastic changes in Z-Wave engine and that's what V4 is for in the first place. Although the sensor changes kind (motion -> temperature) your scripting should still work.

Please make sure you first reboot your HC2, properly exclude, then include you sensors. If you don't trust that, you can do a reset *after* exclusion. If you can't properly exclude, then you have serious issues and I strongly advice to contact [email protected].

@emiel you are talking about Aeon MultiSensor, not Fibaro Motion? I can tell because Fibaro Motion has no humidity sensor...

[emielstroeve 22]

@emiel you are talking about Aeon MultiSensor, not Fibaro Motion? I can tell because Fibaro Motion has no humidity sensor...

sorry, my mistake. I'm using 2 fibaro motion sensors, but I meant the Lux sensor.

 

i'm on 4.033 btw.

 

cheers

emiel

[wienog 107]

I also have problems with my 2 motion sensors, unreal humidity levels is what I see. Reset them, excluded/included them, doesn't seem to help.

 

cheers

emiel

I always considered the 'extras' of these sensors (Fibaro's and certainly Aeon's and Philio) as just that 'extra's', meaning that I don't really care what they give as values and certainly do not use their values in scenes or so.

Especially the Aeon Multisensors have been a pain in the ass: their humidity is somewhat constant and more or less 'comparable' to other humidity sensors but temperature and lux are just ridiculous. And Aeon's motion sensor, on top of that is prone to false alarms, certainly if battery operated anot (very) close to the gateway...

[paleddar 0]

Ok, I am the one with the issue by the original poster, and after updating 3.600->4.033, it created a whole lot of other issues, more items were marked dead (with the large X. and not able to be woken up). Then I restored back to 4.033, and things were better.

 

BTW, you cannot roll back to 3.6 firmware once you have updated to 4.0x

 

Funny thing is, one of the Fibaro motion sensor just worked, like it's 'cured' magically, after the restore back to 4.033. I didn't exclude this one, but did a 'Reconfiguration' under that sensor's advance tab, and it seems to be working now.

 

The other Fibaro sensor and TKB motion sensor have been excluded and included back, and now seems to be fine.

 

Further investigation also concluded that the lower battery and further distance from the HC2, might have contributed to these issues, as these 3 sensor that had problems was actually the ones physically farthest away. Although, having said that, I have a Fibaro FGS-211 within 20 feet of these problem modules, and that should have been acting as a relay.

 

Hope this info helps, and I will continue to monitor it for next few weeks, and report back here.

 

Thanks!

[wienog 107]

Ok, I am the one with the issue by the original poster, and after updating 3.600->4.033, it created a whole lot of other issues, more items were marked dead (with the large X. and not able to be woken up). Then I restored back to 4.033, and things were better.

 

BTW, you cannot roll back to 3.6 firmware once you have updated to 4.0x

 

Funny thing is, one of the Fibaro motion sensor just worked, like it's 'cured' magically, after the restore back to 4.033. I didn't exclude this one, but did a 'Reconfiguration' under that sensor's advance tab, and it seems to be working now.

 

The other Fibaro sensor and TKB motion sensor have been excluded and included back, and now seems to be fine.

 

Further investigation also concluded that the lower battery and further distance from the HC2, might have contributed to these issues, as these 3 sensor that had problems was actually the ones physically farthest away. Although, having said that, I have a Fibaro FGS-211 within 20 feet of these problem modules, and that should have been acting as a relay.

 

Hope this info helps, and I will continue to monitor it for next few weeks, and report back here.

 

Thanks!

Just for you guy's information:

 

I had to send back my 'early' (Reg. number 531) to Poland because it became totally unresponsive a month ago.

I got it back with a little note saying that the 'motherboard was broken and that they replaced it'.

 

Then I decided to start allover anew. I did a recovery and installed the version 4.033. 

Then I readded my 77 nodes and rewrote my 66 scenes.

 

I must say: everything works fine for three weeks now: no dead nodes, not one module not working like it should, no strange errors or crashes, no reboots necessary...

 

Maybe something to think about for those guys that have been going from version to version to version taking along baggage and 'vrap' from earlier versions which makes their 4.033 work erroneously ?

[petergebruers 1,268]

Maybe something to think about for those guys that have been going from version to version to version taking along baggage and 'vrap' from earlier versions which makes their 4.033 work erroneously ?

Well, I'd say "most probably". I went to all the alphas and betas with my production system (because... I don't have a test system). At one point I decided to exclude and include everything that wasn't working well (just like Fibaro support asked me to do!) and around 4.024 my system was stable enough. I *know* it's a lot of work, but in the end exclude and include often is the answer...