openHAB friendly Motion Sensor Suggestions

Philips Hue motion sensor
Update June 15 2019:
I put a second pair of batteries (from the same package of batteries) and instead of 67%, these two are reporting 100% battery level and motion and luminance are now working again.

earlier comment
Hue motion sensor has stopped reporting motion and luminance. Sensor died completely at about 4 months. I replaced the batteries (2 AAA) and it came back but motion no longer reported. Couple weeks after replacing the batteries, luminance stops working. Light level channel however continues to function(??) battery level is reporting 67% with few week old batteries

in Paper UI & habmin this device shows up as 3 separate ‘things’
in shows up as a ambient light sensor thing, a motion sensor thing and a temperature sensor thing all with individual channels (some overlapping such as battery level and low battery)

TLDR: good so far with caveat *

Protocol: zigbee

Channels reported:
light level
last updated (for all 3 things?)
battery level
low battery

Discovery in openhab:
child’s play… popped right up but used Hue app as well

motion detection on motion channel, fast, quick response but time out built in. not good for real time lighting

Battery type 2 X AAA (last a little less then 6 months)

cheap 32$us

more details
sensors is big and obvious, 2.17" x 2.17" x .79" (55mm x 55mm x 20mm) square shape

interesting note from extended use, this sensor reports luminance in almost real time. I have thus ended up using the luminance channel to control my day time lighting. When the sun is bright, it lowers the light, when the sun goes behind a cloud, the lights come up

I run Hue binding in openHAB but also run Hue app on tablet and use Hue bridge. Happy to report Hue lights continue to work when internet connection is lost. Running Hue app on tablet (occasionally) allows bulbs, bridge and sensor to be update which happens fairly regularly.

Wake it up, upgrade to the latest 2.5 snapshot.

Thanks sihui
but as stated in other thread

bundle:list | grep ZW*


191 │ Active │ 80 │ │ ZWave Binding

we be rocking the SNAPSHOT 2.5

oh and pokey pokey with paper clip but still no joy but will continue, I’m sure it will pop up eventually
Update… got it!
comes up as a Zooz4

Good stuff, then wake it up :innocent:

1 Like

Fibaro FGMS-001

in habmin reported as FGMS001
TLDR: sensor is reporting motion

Protocol: zwave

Channel reported:
binary sensor (don’t use for motion)
seismic intensity
motion alarm (use for motion)
tamper alarm
battery level
general alarm

Discovery in openHAB:
I could not get this sensor to be recognized, it showed as unknown device and ultimately required a new snapshot version of the binding to be recognized. At least one post in link indicates it should have worked in 2.4 version binding
here is link:

Battery type CR123A

not cheap

More details:
This motion sensor is now reporting motion in openHAB. It was tricky to get recognized and took waking it up a couple times to finally start reporting but it is working. Will add more as I learn

Golf ball shaped sensor with cat eye LED
no magnetic mount, just a little clip it snaps in to that can be screwed to something

Monoprice 15902

Update June 15, 2019:
Monoprice has stopped at 5 month mark. I am going to replace the batteries and see if it comes back. Reporting intervals were adjusted in the beginning to save battery life. Grafana has battery level and all other channels until June 5 (11 days ago) In HabMin it reports node is not communicating with controller Putting batteries in it has brought it back from the dead. The sensors status immediately changed in HabMin and shows online. Motion so far does not seem to be reported. Illuminance, temperature and humidity have reported values so far
update Motion has begun to report! Batteries seem to have restored this sensor to full fuctionality

in habmin reported as ZSE40 Zooz 4 in one sensor
TLDR: works with openHAB but not first choice functionally

Protocol: zwave

Channels reported:
motion alarm
battery level

Discovery in openHAB:
easy, install batteries, click discovery in openHAB, pops up as unknown, paper clip in little hole, pokey pokey, light blinks, device gets recognized

Battery type:
2 x AAA, delivered new reporting 100%
last a little less then 6 months

cheap: $30us

kind of big and clunky looking, square 2.25" x 2.25" x 1.5" (57mm x 57mm x38mm)
comes with two AAA batteries and a little piece of double sided tape

motion reports on motion channel and on motion alarm channel

More details:
This motion sensor seems to have a short detection range, you must be fairly close to trigger it. How close? Like 5’ away (1.5m) This is at odds with some of my other motion sensors that trigger thru an open door from the next room 30’ away (9m) It also seems sluggish the first time detecting motion although it does seem to get quicker after a few triggers.
The Monoprice motion sensor also seems to have a ‘cool down period’. In other words, once motion is triggered it requires a period of no motion before it will detect motion again. This is sort of like the way you would expect an outside motion triggered light to work. This behavior does not work to well with a automated lighting system where you wish the lights to stay on as long as there is activity in the room.
I have tried adjusting the Configuration Parameters (from in Habmin) and the Monoprice is much less configurable then some of my other sensors. Specifically, the Monoprice motion sensor has the following Configuration Parameters:
1: Temperature scale (Celsius or Fahrenheit)
2: Temperature offset
3: Humidity
4: Light sensor
5: Trigger interval
6: Motion Sensor Sensitivity
7: LED

Some of my other zwave sensors have many parameters including reset in milliseconds but the scale for trigger interval on the Monoprice is a number. From the factory this was set to 3. I changed it to 1 (it does not allow zero) to see if it would reset quicker. No difference has been noticed. I turned the LED off and that worked. I also set it to sensitivity to ‘highest’ which also seemed to make little difference.

In spite of all of the above, I’ve continued to attempt to use this sensor. I decided to try it in the bathroom for a couple reasons. The first reason is in the bathroom a shorter range of detection will matter less. (the bathroom is a small room) Also the matter of the long reset matters less because usually you don’t spend hours in the bathroom. The Monoprice also has a humidity sensor and I have visions of the sensor being able to detect a rise in humidity and therefore trigger openHAB to signal I am in the shower and adjust the automation accordingly.
I’m happy to report the sensor does seem to report humidity but after getting influx and grafana working in order to see if the output is something usable for detecting a shower running, I’m not sure it will work quick enough to be of use.
The Monoprice is apparently the same exact product as the Zooz. I actually tried to buy the Zooz on amazon and it was unavailable. When I tried to order the Zooz motion sensor on amazon a little pop up box said amazon was not currently selling the product because to many members had reported problems. I ordered the Monoprice instead.

Over all I’m not thrilled with the Monoprice but I haven’t thrown it out or tried to return it yet either

habmin rocks for zwave!

Do your monoprice sensors report battery level ok? I’ve never been able to get mine to report anything but 0 for some reason

Sorry, I meant to add that to my post about the Monoprice, yes it does report battery level (which is currently listed as 100%)

Oliver, I followed the link in your post and checked out the Neo online. They actually show two different versions of PIR sensors. What is funny to me is both sensors look very much like the fibaro and dome sensors which themselves also look very similar to one another.
I had noticed the Fibaro and the Dome look very similar. The biggest difference is the Dome has a magnet mount in the back which attaches to a swivel and the Fibaro instead offers a small plastic clip. The LED is different and the case is slightly different but I had wondered if they perhaps were made by the same manufacturer. Rebranding these devices seems common. What is odd is the two models sold by Neo, one closely resembles the Fibaro with a clip mount and the other resembles the Dome with the magnetic mount
How does your Neo motion sensor work?

Does this device require I have the “Hue Hub” to make it work… or if I install the Hue Binding into my openHAB2… it will work without the HUB?
Thanks! Dave

Well…another big issue I realize… the Hue system is ZigBee-based… and this will directly interfere with normal 2.4Ghz WiFi. Yikes. I have Ubiquiti Unifi WiFi Access Points throughout my house… and if I add any ZibBee stuff… they will directly interfere with my WiFi.

WiFi’s three non-overlapping channels (1, 6, and 11) use the exact same frequencies as ZigBee channels 11-22. I’ve now read that ZigBee channel 26 is usually relatively unaffected by WiFi, but many ZigBee devices do not support it.

Can you specifically select the frequency (ie Channel 26) to be used by these ZigBee Hue sensors?

I’m not sure I want to get into the issues of my WiFi not working or the Hue stuff not working reliably… Hmm.

What is the experience out in openHAB land of mixing ZigBee and WiFi???


Definitely an interference issue when installing ZigBee in a standard 802.11n (2.4 Ghz) environment. Hmmm. I think it will be only safe if I can force ZigBee Channel 26 to be used.

I use the Hue binding with a Hue bridge and hue bulbs, dimmer remote and motion sensor. I also have a zigbee dongle and several other zigbee devices. I also have lot of WiFi connections, laptop, Lifx bulbs (which run on wifi) WiFi plugs ect. and no interference problems.

That’s wonderful, Andrew. Do you know what WiFi channels your Access Points or WiFi Router is using?

Maybe in your situation you are not using all the WiFi bandwidth… and your ZigBee devices are using open frequencies… which would be great.

I know in my setup, I am using WiFi channels 1, 6, 11 for my 3 Access Points, which provide excellent WiFi coverage throughout. I am very hesitant to disable one of the channels and have to go to something like this:

So I am curious about how others make ZigBee work properly/reliably with WiFi.
Thanks for your reply.

Just wanted to check back in and say that it seems my sensors do report battery state after all, because I finally had some completely stop responding and when I replaced the battery they reported 100% again. The problem seems to be that their scale must be nowhere near correct because my sensors worked for months at “0%” (so long that I thought the channel was just broken) before they actually died. I think that may explain some of the reviews reporting poor battery life too, because if you’re going strictly by the reported battery percentage you only get a few months out of them but mine lasted well over 6 months of regular use as presence detection and what I feel is fairly aggressive temperature/light logging set at reporting at 3 degree (down from the default of 10) and 5%(? not sure what their percent translates to - but down from the default of 10) changes.

I saw several folks report same on amazon, I think voltage range is wacked

Hey Andrew, where have you landed after your extensive testing?

I’ve been testing the Aeotec Multisensor 6. I like that it can be powered by an included USB cable (so it never goes to sleep), but as someone else noted the motion detection range and sensitivity is not very good. It’s supposed to be five metres at max sensitivity, but I can stand directly in front of it well within that range and not trigger it.

I’m tempted to try the Fibaro, and have a Zooz that I need to experiment with a bit. I just wish they didn’t use CR123A batteries.

First, I had never used zwave, only zigbee, and I’m impressed with zwave. Seems much more reliable and greater configuration

My choice of the three zwave motion sensors I’ve tried would be the Dome. Does everything the fibaro does for half the price. Dome has nice mount options, fibaro has little plastic clip and one screw. In fact I’m probably going to order a couple more. People warned me the Aerotec 6 motion sensor was a little flaky at motion and motion was my main criterion. I did really like the idea of main power instead of batteries though.
Also, I needed a door contact and went with the Aerotec 5 door/window switch and like it a lot.

pass on the Zooz/ Monoprice motion sensor, no fast reset, clunky, slow

But I was happy with the smart things and iris motion sensors for the first 4 months. The real important thing in my book is how long they last. All arrived with batteries reporting full charge. All still reporting full charge (100%) at 4 months

Thanks! Unfortunately for me, Dome doesn’t have a temperature sensor and that’s one of my criteria, along with motion and light. I might just have to figure out a better spot for the Aeotec and live with its motion limitations.

I also have an old Wemo Motion sensor that still works (and has great motion sensitivity), which I was trying to replace. It’ll work great for months, then give me a few weeks of headaches with constant disconnects.

Correction:… I have got the Phillips Hue and Monoprice motion sensors working again with fresh batteries.

Both use two AAA batteries and they seem to last 5 - 6 months

The Dome and Fibaro are both still working at roughly the 5 or 6 month mark. Both use the cr123 battery and both are still reporting 100% battery levels