Issue with AeoTec Multi Sensor 6 on HassIO

Hi all,
I am very new to all this, and thanks everybody for creating this wonderful resource.

I have HassIO (latest upgrade) on an Rpi with a ZStick Gen 5. I have a Fibaro Switch 2, and an AeoTect RGBW LED strip both working at a very basic level (changing colour, switching on/off in home screen and a single timed at automation). I decided it was time to get a sensor and test triggering on movement. I purchased an AeoTec HW100 Multi Sensor 6.

Now when I connected it, pairing took a few goes. Eventually it pairs, the LED goes green, red, green and then sits dark. I can shake it and the green LED comes on. Not once have I been able to trigger on movement sitting like this.

If I then connect my ZStick back to the Pi and reboot, the HassIO state screen detects the sensor, adds humidity, luminosity, and temperature, and they have reasonable values. They don’t seem to change, which I gather might be ok as I haven’t configured polling. The movement “icon” never changes state. This is all HassIO automated detection, I have done nothing up to this point.

Now however, if I look at the sensor, it is sitting doing the rainbow fade, as if it has not been paired. If I re-pair and repeat the process (pair, restart HassIO), it does the same thing. Reads once, then seems to lose the pair (or factory reset). AeoTec support say the green/red/green on pairing is normal (although the manual disagrees, doesn’t mention red). AeoTec Support have suggested changing the following:

The best I think would be to set these parameter settings:
Parameter 3 [2 byte dec] = 10 //set PIR sensor timeout to 10 seconds
Parameter 4 [1 byte dec] = 5 //set maximum sensitivity for PIR sensor
_Parameter 5 [1 byte dec] = 2 //set binary sensor report to be sent instead of basic report.

My first question is, what do I use to change these settings? OZWCP on HassIO? How?

Next question is, can an incompatibility with HassIO cause it to un pair on first query?

Dealer has offered to swap it under warranty, but I am now unsure if it is actually faulty. Anyone played with these and can confirm?
Oh, one other thing, using the AeoTec OTA app, I can see that every time it does this, it leaves behind a phantom node and I have to clean them up by resetting my ZStick. It also behaves differently adding a node via OTA than using the action button. OTA successfully upgrades (or downgrades) the sensor firmware after several tries at adding the node.

Any comments or opinions gratefully received.
Cheers,
Glenn.

Have you never found this page …


From here you can manage your nodes …

I would think that the motion sensor should be set for binary mode otherwise HA won’t work with it.

Thanks Keith. I have seen that page, but I didn’t realise I could modify node settings from there. I will check it out further after work.

1 Like

I’ve read here that you should use Hassio to pair the device. i.e. don’t unplug the z-stick.

Thanks Tom. Will try that in case it makes a difference.

Thanks everybody. I have learned a lot over the last 3 days of playing with this sensor.
After being shown where to play with nodes (Doh!), I did even more tinkering last night. I can add the node successfully and the sensor behaves, but still no movement led. If I change a setting in the node, say the movement sensor timeout which defaults to 240 seconds, it changes, then changes back after a few seconds. If I reboot the Pi, the sensor goes back to its factory default state and I have to re-add it. I can only conclude that it is faulty.
Oh well, 3 days down but at least I learned a lot.

If it’s in battery mode that’s expected behavior you need to wake it up before any settings will stick, to do this there is usually a button or a hole somewhere (you only get 20s or so to do any changes), if it’s in usb power mode it should always be awake, so then it might be faulty.

Thanks Keith. I should have mentioned it is USB powered at present.

New sensor arrived today. Worked straight up. Smarthome in Aus was fantastic to deal with.

1 Like