Fibaro Motion sensor randomly stops communicating

Scotsman · September 26, 2018, 9:08am

I have three Fibaro motion sensors to control my lights in the Living room, Hallway and Landing. Two of them work flawlessly but one (Landing) seems to stop sending events randomly.

It can work fine all evening and then fail. For example last night it worked all evening until I went to bed at which point the Light never turned off.

Looking at the log (see below) I can see it change from OFF to ON and send the relevant command to the HUE bulb but then nothing. Its state doesn’t change back to off and so the light stayed on.

It happens at random times. Sometimes it fails to turn the light on. Also this Fibaro device is closer to the openHAB controller than the other two.

Any ideas?

  22:47:21.748 [vent.ItemStateChangedEvent] - Security_Motion_L changed from OFF to ON
2018-09-25 22:47:21.790 [ome.event.ItemCommandEvent] - Item 'Light_Hue_White_L' received command 1
2018-09-25 22:47:21.804 [nt.ItemStatePredictedEvent] - Light_Hue_White_L predicted to become 1
2018-09-25 22:47:21.810 [vent.ItemStateChangedEvent] - Light_Hue_White_L changed from 0 to 1
2018-09-25 22:47:21.815 [GroupItemStateChangedEvent] - gLights_HandL changed from OFF to ON through Light_Hue_White_L
2018-09-25 22:47:22.399 [vent.ItemStateChangedEvent] - LandingLight_Brightness changed from 0 to 1
2018-09-25 22:48:15.143 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:47:15.112+0100 to 2018-09-25T22:48:15.117+0100
2018-09-25 22:49:15.146 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:48:15.117+0100 to 2018-09-25T22:49:15.122+0100
2018-09-25 22:49:54.587 [vent.ItemStateChangedEvent] - Environment_Lux_L changed from 0 to 3
2018-09-25 22:49:54.630 [ome.event.ItemCommandEvent] - Item 'Light_Hue_White_L' received command 1
2018-09-25 22:49:54.652 [nt.ItemStatePredictedEvent] - Light_Hue_White_L predicted to become 1
2018-09-25 22:50:15.152 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:49:15.122+0100 to 2018-09-25T22:50:15.128+0100
2018-09-25 22:51:15.161 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:50:15.128+0100 to 2018-09-25T22:51:15.138+0100
2018-09-25 22:52:15.166 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:51:15.138+0100 to 2018-09-25T22:52:15.143+0100
2018-09-25 22:53:15.171 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:52:15.143+0100 to 2018-09-25T22:53:15.147+0100
2018-09-25 22:54:15.181 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:53:15.147+0100 to 2018-09-25T22:54:15.153+0100
2018-09-25 22:55:15.194 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:54:15.153+0100 to 2018-09-25T22:55:15.160+0100
2018-09-25 22:56:15.192 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:55:15.160+0100 to 2018-09-25T22:56:15.165+0100
2018-09-25 22:57:15.194 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:56:15.165+0100 to 2018-09-25T22:57:15.171+0100
2018-09-25 22:57:29.237 [hingStatusInfoChangedEvent] - 'chromecast:chromecast:fa1308ad9c45c17e91956204ea7861ab' changed from OFFLINE (COMMUNICATION_ERROR): Waiting for response timed out to OFFLINE
2018-09-25 22:57:42.318 [hingStatusInfoChangedEvent] - 'chromecast:chromecast:fa1308ad9c45c17e91956204ea7861ab' changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2018-09-25 22:58:15.207 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:57:15.171+0100 to 2018-09-25T22:58:15.182+0100
2018-09-25 22:59:15.212 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:58:15.182+0100 to 2018-09-25T22:59:15.187+0100
2018-09-25 23:00:15.220 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T22:59:15.187+0100 to 2018-09-25T23:00:15.193+0100
2018-09-25 23:01:15.222 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:00:15.193+0100 to 2018-09-25T23:01:15.198+0100
2018-09-25 23:02:15.233 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:01:15.198+0100 to 2018-09-25T23:02:15.203+0100
2018-09-25 23:03:15.231 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:02:15.203+0100 to 2018-09-25T23:03:15.209+0100
2018-09-25 23:04:15.565 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:03:15.209+0100 to 2018-09-25T23:04:15.538+0100
2018-09-25 23:05:15.570 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:04:15.538+0100 to 2018-09-25T23:05:15.543+0100
2018-09-25 23:06:15.590 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:05:15.543+0100 to 2018-09-25T23:06:15.552+0100
2018-09-25 23:07:15.583 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:06:15.552+0100 to 2018-09-25T23:07:15.556+0100
2018-09-25 23:08:15.592 [vent.ItemStateChangedEvent] - Date changed from 2018-09-25T23:07:15.556+0100 to 2018-09-25T23:08:15.564+0100
2018-09-25 23:08:31.587 [vent.ItemStateChangedEvent] - Environment_Temp_H changed from 21.5 to 21.2

dastrix80 · September 26, 2018, 9:31am

Does the range test indicate its healthy in terms of signal?

Scotsman · September 26, 2018, 9:56am

Certainly the last time I tested it did. I will test again tonight.

Scotsman · September 27, 2018, 3:44pm

I tested the range with the Fibaro and it failed. It passed before and I never thought to check again because it is litterally 8 metres away with one stud wall inbetween.

I took it closer to the controller and it passed the range test. I then took it back to its location and it again passed the range test.

I moved the controller closer to the sensor and another Fibaro started to play up.

I have ordered a couple of zwave plugs and all my devices are battery. Hopefully these will be able to route to the controller.

My controller is a Razberry2. I’ve seen others have had range issues with it and that there is a manufacturer approved mod where an external antenna can be added. I plan to do that also over the comming days.