Z-wave motion sensorSenses: Motion, Temperature, Humidity and Light and reports all the information back to a Z-wave Controller. *

Cost: ~$52 from Amazon, ~$54 from eBay

Notes: The multisensor comes with everything you need to set it up including a micro usb cord and 4 x AAA batteries.  Before associating it with your network controller (in my case I used an Aeon Labs Z-Stick S2), I recommend upgrading the firmware.  The upgrade is super easy but requires a windows computer.  The firmware is an executable file found at: http://aeotec.com/partner/z-wave-firmware/viewcategory/7-multisensor (please note – they are country specific).  The site seems to go offline a lot – if you need the US version of the multisensor firmware upgrade, send me an email.  To install the upgrade, plug in the usb under the motion sensor where the batteries are normally located.  Then plug the other side, not connected to your sensor, to you Windows PC.  You should hear the normal hardware install “bing”.  After the “bing” launch the firmware executable and hit “update”.  The process should take less than a minute at which point you are ready to pair the multisensor with the controller.   The pairing processes is like most Z-wave devices.  Put the controller in pairing mode by hitting the big center button.  It will flash with a blue light, then press the pair button on the back of the multisensor to the right of the sensitivity knob.  The Z-Stick 2 blue light blinking should speed up and then go solid.  After about a second of solid light on the Z-Stick controller, the device has been paired and it will return to “pairing mode” and start flashing again.  To stop this, push the big button on the Z-Stick or you can go directly to pairing another device.

The Z-wave multisensor can also control up to 6 other devices.  I have not tried that feature yet.

*With some controllers, only the motion detection is supported.

Output: Using my server and debug client application, I took a look at the raw values that I received from the Aeotech Multisensor.

Routing Binary Sensor

Node Number: 6
Node Name: Undefined
Node Group:
Node Properties:

  • Wake up 10 minutes when batteries are inserted=0
  • On time=240
  • Enable Motion Sensor=1
  • Command Options=1
  • Reset #101-103=0
  • Group 1 Reports=0
  • Group 2 Reports=0
  • Group 3 Reports=0
  • Reset #111-113=0
  • Group 1 Interval=720
  • Group 2 Interval=720
  • Group 3 Interval=720
  • Reset to default=False
  • Library Version=6
  • Protocol Version=3.28
  • Application Version=1.18
  • Minimum Wake-up Interval=240
  • Maximum Wake-up Interval=2678400
  • Default Wake-up Interval=0
  • Wake-up Interval Step=240
  • Relative Humidity=52
  • Battery Level=100
  • Wake-up Interval=0
  • Sensor=True
  • Temperature=24.8
  • Luminance=73

The 4 “orange” items are the default sensed values.  I have no way to accurately test the luminance and relative humidity.  The temperature seems to be a little off but I will have to do more testing with that later.  I have not tried to dial in the sensor sensitivity with the sensitivity control.  When plugged in, I would get the results faster by default but I would also get more jitter on the temperature.  Sometimes I would see as low as 4 and as high as 40340344 (melting my face off).


Software: I fully expect that the new ‘simple’ client will properly handle this sensor within the next few weeks.  I will update when available.

Overall Review:

Aeon Labs Aeotec Z-Wave Multi-Sensor

November 20, 2013

4/5 stars

A great addition to your home automation setup. You get measurements for Motion, Temperature, Humidity and Light from this sensor.


  1. cs -

    HI Thomas, I have been trying to make the Aeotech multisensor work with the raspberry pi for some time now – I tried using your debug script to get the output from my multisensor – but that did not work. All i got was
    DEVICE~Undefined~2~~Routing Binary Sensor~0

    Routing Binary Sensor

    Node Number: 2
    Node Name: Undefined
    Node Group:
    Node Properties:

    any idea where i am messing up – sorry NOOB here.

    • Thomas -

      Sorry to respond with questions instead of answers –
      1. What controller are you using? Z-stick?
      2. Are you using the latest Server and Client files with the latest OZW library?
      3. Can you share your OZW log?
      4. Have you force the sensor to wake up by pressing the pairing button on the sensor (I think 3 times)?

  2. cs -

    hi, thanks for the response, I am indeed using the Z-Stick from Aeotech and a raspberry pi running an image i downloaded from your site – (openZwavePi-12-12-12.7z). I just saw you have a newer image (dated february- ill try that as well – are you referring to something newer?) . heres whats inside ~/open-zwave-read-only/cpp/examples/linux/OZW_Log.txt

    2012-06-27 18:04:07:277 mgr, Added driver for controller -p
    2012-06-27 18:04:07:280 Opening controller -p
    2012-06-27 18:04:07:283 Trying to open serial port -p (attempt 1)
    2012-06-27 18:04:07:285 ERROR: Cannot open serial port -p. Error code 2
    2012-06-27 18:04:07:287 ERROR: Failed to open serial port -p
    2012-06-27 18:04:07:288 WARNING: Failed to init the controller (attempt 0)
    2012-06-27 18:04:12:290 Opening controller -p
    2012-06-27 18:04:12:291 Trying to open serial port -p (attempt 1)
    2012-06-27 18:04:12:292 ERROR: Cannot open serial port -p. Error code 2
    2012-06-27 18:04:12:292 ERROR: Failed to open serial port -p
    2012-06-27 18:04:12:293 WARNING: Failed to init the controller (attempt 1)
    2012-06-27 18:04:17:294 Opening controller -p
    2012-06-27 18:04:17:295 Trying to open serial port -p (attempt 1)
    2012-06-27 18:04:17:296 ERROR: Cannot open serial port -p. Error code 2
    2012-06-27 18:04:17:296 ERROR: Failed to open serial port -p
    2012-06-27 18:04:17:297 WARNING: Failed to init the controller (attempt 2)


    • Thomas -

      If you type ‘ls /dev/ttyUSB*’ do you see anything? If you do not see /dev/ttyUSB0, you should try a Raspberry Pi firmware update. The newest edition is the ‘simpleChristmas’ version (Client found at http:///Client. It should automatically start the server.


Leave a Reply