@mike.maxwell Is there a chance of getting this sensor included in the built-in drivers? It is a Motion, Light and Temperature sensor in one. It is z-wave plus. I have the parameter list and all there settings if you or anyone is interested.
It currently is running under the Neo Motion Sensor driver chosen by HE. There are a few things that are not working like the Temperature and there are some choices on the driver page that are missing. Thanks
have you tried the Fibaro Motion Sensor ZW5 driver?
You might be lucky and it is just an rebadged version.
1 Like
Can you try one of these drivers?
Dome Motion sensor
or
Fibaro Motion Sensor ZW5 (as suggested by @at9)
Thanks!
Well, considering there isn't any record of any device made by a manufacturer "hoazee" or "haozee" in the official zwave certification registry, I assume it is a rebranded device.
Figure out who the actual manufacturer is, find the zwave capability and command list in the registry, and someone could probably whip up a fully working user driver in about 15 minutes on a simple device like that.
The only hope you'll have for an in-box driver is if someone sends Mike a device, and he gets around to it. OR if there is already a driver for the OEM version of the device already.
@aaiyar, @at9 I have tried all of the motion sensor drivers that have temp, motion, etc. I haven't tried the Fibaro one yet, but I will.
One thing that has been very strange, and with all the other drivers, is that when I put it in a simple lighting rule to turn on lights based on a lux level and when that level was reached the lights flashed on and went right back off!! That part I don't know how to troubleshoot or why it would do that.
The Fibaro driver seems to work except for the parts of the driver that don't apply. But at least the lights stay on with this driver and don't do a quick On then Off!
1 Like
@JasonJoel I do have all the parameters written out and the driver page has the command classes. Does any of that help?
It looks very much like a NEO Z-Wave Plus Motion Sensor, for sure.
Same prize on Amazon too, but by chance, found 20 pcs for a better price (link below). Does this work fine with the built in driver? They look quite smart, but no idea how good they are or if they work properly with the NEO motion sensor driver. How is the community experience with these?
Only thought I get is that one usually put a motion sensor up in a corner. I like my temp sensors in chest hight, cause its much warmer by the ceeling due to hight. (If this made any sence...)
NEO Z Wave Motion-temp-light 3-in-1 for $26
RogerThat 
1 Like
@RogerThat When I first included it HE chose the Neo driver you mentioned. The temp did not work with that driver. The temp works the fibaro driver but it has options that are not related.
It definitely looks like the Neo and the definitions for both are almost identical. Temp for some reason is working now with the Neo driver. I guess it needed some time.
The biggest reason I like this besides it doing 3 things is that changes in the light levels are sent to the controller irregardless of motion change, which is not found in all sensors.
2 Likes
I have tried the Neo Motion sensor driver with the Hoazee. It sure seems to be a re-branded Neo. But when you try to use the Neo driver the bulbs (Ilumin) go On and then go right back Off.
If I use the Fibaro driver the lights do come On and stay On. What would be the reason the lights would go On and right back Off with the Neo driver if the Hoazee is in effect a re-branded Neo?
On the device page of the sensor, when motion is detected does that show up as ‘active’ ( or similar action) and stay in that state for some minutes before timing out and reverting to ‘inactive’ ??
Are you using the sensor in a rule or the Motion lighting App ??
1 Like
I am only using it for the light aspect. I have motion either turned off or set very nonsensitive.
The Fibaro driver works but has other commands not used by the Hoazee. The Neo driver works except for the on and off thing.
One thing I noticed is that if I use the Neo driver and in my event I choose a light switch to turn On instead of the bulbs by themselves it works. The light connected to the light switch comes on and stays on.
So why does the Neo driver act this way with the bulbs. They are Ilumin LZW42's. Tagging @bcopeland. Could there be something in the driver for these bulbs that is conflicting with the Neo driver?
The driver is not the issue here.. It sounds like since you are turning on by lux, when you light comes on it is affecting your lux level and triggering your automation ..
1 Like
This should be evident in your logs
1 Like
Ok, I moved the sensor to another room away from the lights where it is normally dark and positioned the sensor pointing out the window. Using the Neo driver and when the light level went below the setting the lights flashed on and back off again. The lights did the same thing with the Fibaro driver now also. It used to work with the Fibaro driver.
EDIT: After I changed the driver back to Fibaro it took a few minutes before it worked again. So the Neo driver is the problem.
Why not Just use that driver and ignore the “other commands”
I am using the Fibaro driver and as long as it works who cares. That still doesn't change the fact that the Neo driver causes the lights to turn on and back off. Staff will have to look into that one.
1 Like
