Best motion sensor?

Thanks @vossivossi. I repeated the process and I think I got it included properly this time (the title now shows “Z-Wave Node 13: FGMS001 Motion Sensor” rather then just Node 21)
But the motion indication is not shown. The 4 flags Binary Sensor, Motion Alarm, Tamper Alarm, Alarm (general) are blank and they do not indicate ON or OFF in PaperUI, even though the sensor blinks (indicates general motion), and blinks when I move it (indicates moving the device)
Why are these flags blank?

This is the motion sensor I ended up going with, cheap, good battery and the report time is quick so if you walk in the room, the lights pop on instantly, I have a several WAPIRZ-1s and it takes up the 10 seconds to realize that you are there so I’m slowly replacing them with PIRZWAVE2-ECOs. I also have a couple aeotec sensors but the multisensor 6 only works well on USB power so if pluggable is the requirement I’d go with these. I ordered a fibaro motion eye once but only received an empty box so I have no experience though they look good. I’m still waiting for the zigbee support to mature so I can use my big bag of SmartThings sensors.

You probably need to configure the association groups for Lifeline and Motion for the Controller. You can do this in Habmin or PaperUi:

I am using the ZWay binding and not the zwave binding and I don’t see the Association groups in PaperUI.
In PaperUI I hardly see any configuration parameters (see img1)

Does Habmin depend on zwave binding? I’m asking because, for now I am using ZWay binding (one of my devices initializes properly with this ZWay but not with the zwave binding) and I read that Habmin requires the zwave binding.
In Habmin I see more configuration parameters but no Association groups either (see img2)



I never used the Zway binding so I am not sure. But for my understanding the Zway software ist the controller and the binding only connects OH to the other software. If this is the case, you probably need to configure the association groups with the Zway software.

I moved back to Zwave binding and included the device,
When I try to add the association in Habmin they show up as pending (in yellow)
I described my problem in here
How did you make the association persist?

Typical problem with battery powered devices. They are only reachable when awake. So press the button in Habmin or PaperUI and then triple click the button of the device.

I solved that by restarting openhab. Now the associations persist (without yellow warning) but I still don’t see the OFF/ON indication in PaperUI Control page :frowning:
Did you specifically set anything in the .items file, or any other file such as .sitemap, .rules?

p.s. I do get the events in the log file. It is just that they do not appear in the web page

tail -f /var/log/openhab2/events.log
2017-03-26 13:39:31.506 [ItemStateChangedEvent     ] - zwave_serial_zstick_02710de3_serial_sof changed from 181 to 182
2017-03-26 13:39:31.508 [ItemStateChangedEvent     ] - zwave_device_02710de3_node6_alarm_motion changed from OFF to ON
2017-03-26 13:39:57.434 [ItemStateChangedEvent     ] - zwave_serial_zstick_02710de3_serial_sof changed from 182 to 183
2017-03-26 13:39:57.436 [ItemStateChangedEvent     ] - zwave_device_02710de3_node6_alarm_motion changed from ON to OFF

Also note that I’m using the 2.0.0 release build for openhab2. I found out that is using snapshot I get into other problems, and I don’t want to chanse after a moving target (at least this version is supposed to be stable)

openhab> bundle:list -s | grep openhab
166 | Active   |  90 | 2.0.0                 | openHAB Core                                           | org.openhab.core
167 | Active   |  80 | 2.0.0                 | openHAB Karaf Integration                              | org.openhab.core.karaf
169 | Resolved |  80 | 2.0.0                 | openHAB Sound Support, Hosts: 111                      |
170 | Active   |  80 | 2.0.0                 | openHAB Dashboard UI                                   | org.openhab.ui.dashboard
187 | Active   |  80 | 2.0.0                 | HABPanel User Interface                                | org.openhab.ui.habpanel
188 | Resolved |  80 | 2.0.0                 | openHAB Paper UI Theme Fragment, Hosts: 186            | org.openhab.ui.paperui
199 | Active   |  80 | 2.0.0                 | HABmin User Interface                                  | org.openhab.ui.habmin
209 | Active   |  80 | 2.0.0                 | ZWave Binding                                          | org.openhab.binding.zwave

openhab> bundle:list -s | grep zwave
209 | Active   |  80 | 2.0.0                 | ZWave Binding                                          | org.openhab.binding.zwave


I’m looking for a wireless motion sensor.

  • Mounted in the ceiling (flush);
  • As small as possible;
  • Obviously compatible with OpenHAB;
  • Acceptable battery life;
  • I don’t care about extra sensors (temp, humidity), certainly not if it is at the expense of battery life;

Any ideas?

The Auro Motion Sensor meets all requirements, except one: it’s not wireless. :-/

1 Like

One possibility is

There is a ceiling adapter sold separately

1 Like

Hi Pauli,

Thanks. I’ve read some mixed experiences regarding battery life. Some say they need to replace it every month, and that is way below what they advertise (2 years). Everything above one year is acceptable for me.

I also see that this motion sensor is slightly larger (75mm / 3″ space for Recessor is needed) than the wired one I have now (Auro needs 43mm). But I guess that is the consequence of providing space for batteries.

But so far, this is the best option there is, I guess. Thanks!

I have 7 of them and currently 4 are running with batteries. At least for me, battery devices have been working pretty well.

There is one bug at least which could cause very short battery life.

Battery Power
Parameter 111-113 report interval bug

  • If sensors are reporting around 4 minutes, it is possible that the sensor may send the signals 4 times in a row causing the battery to be used rapidly (users who have done this have seen battery drain within 2 weeks). (bug)
  • Can be set to a minimum 240 seconds without the need to set the wakeup interval for faster reports (but is receptive to the bug above at reports <10 minute intervals)

I have been using Vision motion sensor successfully for a couple of months.

It looks exactly identical to the Amazon product you linked.

I use the RFXCOM paired up with cheap 433mhz motion sensors from eBay. They run about 6 dollars each. There range is superb, response time is very fast. Most only report a tripped signal so using the expire binding I have them reset after 15s. If they receive the tripped signal again it resets the 15 second timer. I have Kerui sensors as well, although the binding doesn’t know what the received command is, it is easy to figure out by watching the logs. I have found that the RFXCOM works well and for a 1 time investment of around 100 dollars for the transceiver, you can get the sensors for cheap. So for the cost 3 zwave motion sensors you could have 3 433mhz motion sensors and be ready to expand. Plus there are plenty other 433mhz stuff out there. I do use the AEON Labs Multisensor 6 if I need Temp, Humidity…

How is it zwave or zigbee, do you need to ask for the status every 1s or so, or does it work like mqtt that it publishes to the gatway when there is a change and that Oh does not need to ask the gatway every 1s for it status?

I am using hue motion sensor now with refresh interval of 1.5s, but this is to slow for me, anything below 0.5s would acceptable, so any tips to wich door and motion sensor that can do this would be awesome.

It is neither zwave nor zigbee. The RFXCOM binding will register any change and the response time is milliseconds. I use the following motion sensors. RFXCOM receives the number 2 for tripped, and I have the expire binding return it to 0 after 15 seconds.

Hi all,

Thanks for your feedback.
I’m currently inclined to go for the Multisensor 6, since battery power issues seem to be addressed in the latest firmware, and the other proposals are not flush (ceiling) mounted solutions.

It looks nice, but what response time does it have?

It looks nice, but what response time does it have?

Well, I don’t have exact numbers, but response time is not many milli seconds. If I enter the room, where lights are controlled by the Multisensor 6, lights are ON normally before I take a second step. My lights are not z-wave based, so multi sensor send command to openhab, where rule is executed which then control the light. Most of my multisensors are directly below the controller, so there is no routing needed.

@chris probably knows better which is “normal” network delay in z-wave networks. Of course it depends when device recognise the movement as battery device is most probably on sleep mode most of the time.

Assuming there’s not a lot happening (ie you’re not initialising the system - just normal activity) then most 2 way transactions take a few tens of milliseconds (let’s say normally less than 40ms). If the device is further out in the mesh (ie it has to repeat through a few routers) then you could expect it to be something like 20ms for each hop (that’s a bit of a guess though). So, I’d expect a “normal” network delay well under 100ms in most cases.

I wouldn’t expect this to be a big driver. Most devices do sleep, but the sensors should be active, and it’s the microcontroller, radios etc that are powered down. When the sensor sensors movement, it wakes up the microcontroller which in turn will wake up the radio and any other circuitry it needs.