Setup and usage of Aeotec MultiSensor 6

Scott847 · August 8, 2015

Anyone using this as a light sensor?

I've thought about having a light in my hallway triggered by a motion sensor at night, but it can also be dark there during the day if it is really gloomy outside.

Was thinking maybe something like this that can tell how dark it is would help me with this.

Any thoughts?

That should work pretty well if you can plug it in so it's USB-powered. If it's battery powered it will only report light levels every 59 minutes.

Following is a chart of light levels for a south-facing room today. Setup parameters for the USB-powered MultiSensor 6 producing this data are P40/S1 = 1 (enable change-based reporting), P43/S2 = 10 (lux), P111/S4 = 259 (report changes at least every 5 minutes).

.

KeviNH · September 5, 2015

Recently bought the latest Aeon Labs Aeotec Z-Wave Multi-Sensor 6. As expected, it shows up with several devices. Unexpectedly, one is listed as "Glass Break" sensor. Anybody know if this is actually an acoustic glass break sensor? I've tried the obvious tests (dimes in a soda can, drop a ring of keys, etc), and it never registers as "On"

Also, I am powering off the USB cable so I can use this as a Z-Wave repeater. In order to repeat secure Z-Wave signals, do I need to follow the procedure to add the multisensor as a security device?

fryfrog · September 9, 2015

Recently bought the latest Aeon Labs Aeotec Z-Wave Multi-Sensor 6. As expected, it shows up with several devices. Unexpectedly, one is listed as "Glass Break" sensor. Anybody know if this is actually an acoustic glass break sensor? I've tried the obvious tests (dimes in a soda can, drop a ring of keys, etc), and it never registers as "On"

Also, I am powering off the USB cable so I can use this as a Z-Wave repeater. In order to repeat secure Z-Wave signals, do I need to follow the procedure to add the multisensor as a security device?

For secure repeater, I'm 99% sure you need to be usb powered and bound in secure mode. I believe it says so right in the manual. I bound all of mine normally first, then had to re-do them. Blech!

I don't think there is an actual glass break sensor, that is probably just the tamper sensor showing up as something weird. On mine, I'd bind them fairly still and it wouldn't show up. Then I'd give them a little shake and it'd appear.

fryfrog · November 25, 2015

Has anyone updated the firmware on one of these yet? I got a Gen5 Z Stick to do it... but I'm not looking forward to excluding and including ~12 sensors 2-3 times.

oskarw · April 2, 2016

Hi Michel,

I've come across the attached document, which is a bit different than the Aeotech-MS6-Config-Params.pdf you have linked to above. I've queried my Multisensor 6 default parameters, specifically the Parameter 4, and it shows a value of 5, matching this new document.

Oskar

MultiSensor-Documentation.pdf

Michel Kohanim · April 3, 2016

Hi Oskar,

Thanks so very much. Updated the link.

With kind regards,

Michel

MustangChris04 · May 11, 2016

When querying parameter #41, I get a popup that says "Z-Wave command Failed ZWave 28 Query Config ZW008_1 param 41" Does anybody get this?

When querying parameter #42, I get a size of 1, and a value of 0, but in the manual it says the size is 2 and value is 10. Does anybody see that discrepancy?

Thanks!

Broyd · May 18, 2016

I get:

parameter: 41 size: 2 value:20

parameter: 42 size: 1 value:10

KeviNH · August 13, 2016

I couldn't find the MultiSensor 6 manual on the Aeotec website but found it here: http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1390/MultiSensor%206%20manual%20(3).pdf

Link to PDF manual above is dead, try these

(found by googling multisensor 6 manual.pdf)

rafarataneneces · August 13, 2016

Just got one of the new Aeotec MultiSensor 6's. Added it, looks like I'm getting "status", temperature, humidity, uv light, luminance, battery level, motion, tamper and "binary" sensor. It kind of seems like it might just work.

Looks like it'll also add in secure mode too.

So the temperature was read in Fahrenheit no problem?

I have the Fibaro Motion Sensor FGMS-001 and the temperature is only reported in Celsius!

Scott847 · August 14, 2016

So the temperature was read in Fahrenheit no problem?

I have the Fibaro Motion Sensor FGMS-001 and the temperature is only reported in Celsius!

Yes, it can report in Fahrenheit.

rafarataneneces · August 14, 2016

Yes, it can report in Fahrenheit.

Is that a Z-Wave property or a simple configuration or is that the default value?

Scott847 · August 14, 2016

Is that a Z-Wave property or a simple configuration or is that the default value?

Looks like it can't be changed and is Fahrenheit for the US version. From the engineering spec that oskarw mentioned in another thread: "The unit is Fahrenheit for US version, Celsius for EU/AU version."

See oskarw's post at http://forum.universal-devices.com/topic/18669-aeon-aeotec-multisensor-6-temperature-units/?p=184564

rafarataneneces · August 14, 2016

Looks like it can't be changed and is Fahrenheit for the US version. From the engineering spec that oskarw mentioned in another thread: "The unit is Fahrenheit for US version, Celsius for EU/AU version."

See oskarw's post at http://forum.universal-devices.com/topic/18669-aeon-aeotec-multisensor-6-temperature-units/?p=184564

Oh okay so it's Fahrenheit, that's good!

Scott847 · August 15, 2016

Looks like it can't be changed and is Fahrenheit for the US version. From the engineering spec that oskarw mentioned in another thread: "The unit is Fahrenheit for US version, Celsius for EU/AU version."

See oskarw's post at http://forum.universal-devices.com/topic/18669-aeon-aeotec-multisensor-6-temperature-units/?p=184564

Oops, just noticed I misread oscarw's post - the US version defaults to Fahrenheit but can be changed to Celsius by changing the parameter he mentioned.

gduprey · March 2, 2017

Howdy,

Just cracked open my first one of these units and ran into this same issue when trying to configure it:

When querying parameter #41, I get a popup that says "Z-Wave command Failed ZWave 28 Query Config ZW008_1 param 41" Does anybody get this?

I have been able to configure nearly all other parameters without an issue. Here's the comms log when attempting to set/query the param

Thu 03/02/2017 16:34:53 : [ZWAVE-TX ZW043_1] [010D00132B067004]...
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] ACK
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] [0104011301E8]
Thu 03/02/2017 16:34:53 : [ZWAVE-TX        ] ACK
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] [01050013A90040]
Thu 03/02/2017 16:34:53 : [ZWAVE-TX        ] ACK
Thu 03/02/2017 16:34:53 : [UZW-CMD 29      ] Set Config : ZW043_1 41/2/10
Thu 03/02/2017 16:34:53 : [ZWAVE-TX ZW043_1] [010A00132B037005]...
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] ACK
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] [0104011301E8]
Thu 03/02/2017 16:34:53 : [ZWAVE-TX        ] ACK
Thu 03/02/2017 16:34:53 : [ZWAVE-RX        ] [01050013AA0043]
Thu 03/02/2017 16:34:53 : [ZWAVE-TX        ] ACK
Thu 03/02/2017 16:34:53 : [ZWAVE-RX ZW043_1] [010D0004002B0770]...
Thu 03/02/2017 16:34:53 : [ZWAVE-TX        ] ACK
Thu 03/02/2017 16:34:53 : [UZW-CMD 28 ERR  ] Query Config : ZW043_1 param 41

And all node info:

Thu 03/02/2017 16:35:32 : [ZW-SHOW         ] ----------------------------------------------
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ] ZW043_1 uid=43 type=4.33.1 mid=134 tid=258 pid=100 model=0
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x5E  V0  ZWAVEPLUS_INFO
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x86  V0  VERSION
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x72  V2  MANUFACTURER_SPECIFIC
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x59  V0  ASSOCIATION_GRP_INFO
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x85  V2  ASSOCIATION
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x73  V0  POWERLEVEL
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x71  V3  NOTIFICATION
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x84  V2  WAKE_UP
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x80  V0  BATTERY
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x30  V0  SENSOR_BINARY
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x31  V5  SENSOR_MULTILEVEL
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x7A  V2  FIRMWARE_UPDATE_MD
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  x5A  V0  DEVICE_RESET_LOCALLY
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]    -  xEF  V0  MARK
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]   sensorType=  1  scaleMask=  3  defScale=1
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]   sensorType=  3  scaleMask=  2  defScale=1
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]   sensorType=  5  scaleMask=  1  defScale=0
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ]   sensorType= 27  scaleMask=  1  defScale=0
Thu 03/02/2017 16:35:32 : [ZW-SHOW         ] 
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ] Node  43 - New Crawl Climate has the following neighbors
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    -          - Node   1 - [This ISY]
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    -          - Node   2 - Front Door Lock
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node   5 - First Floor Thermostat
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node   7 - Second Floor Thermostat
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node   8 - Panel 1 Meter
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  35 - Doorbell
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  38 - _Crawlspace Repeater
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  39 - _Dining Room Repeater
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  40 - _Sitting Room Repeater
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  41 - _Master Gst Repeater
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    - Repeater - Node  42 - _Gym Repeater
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ] 
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ] Node  43 - New Crawl Climate has 1 association group
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]    Associations for group 001 of ZW043_1 New Crawl Climate
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ]       - Node   1 - [This ISY] 
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ] 
Thu 03/02/2017 16:35:33 : [ZW-SHOW         ] ----------------------------------------------

Based on watching reports, I actually think the parameter value was actually sent (temp reports started happening much more frequently as things changed), so I really think it's something only with the query/GET.

POSSIBLE UPDATE: Reading over the config params for the 1.7 firmware, it says that param #41 is a 3-byte value. I've never seen that and always assumed that values are 1, 2 or 4 bytes. If this is accurate, I wonder if the ISY doesn't know what to do with 3 bytes? I gleaned this from this copy of the 1.7 manual/config params. Not sure if this is accurate or what, but it stands out as at least something different about param 41.

Any ideas if this is a device issue or an ISY issue?

Gerry

gduprey · March 3, 2017

Also -- has any one had any success using the calibration parameters? My units temp sensor is within 1 degree of accurate, but about 4% low on RH. I keep setting parameter 202 to 4 and it looks like it works (I can switch to other parameters and then back and query and get 4 back), but it doesn't seem to have any impact on the actual reporting %RH (which appears unchanged, even if I test with something nuts like +30% just to see if anything would work).

Gerry

Michel Kohanim · March 3, 2017

Hi Gerry,

We'll look into it.

With kind regards,
Michel

Chris Jahn · March 3, 2017

POSSIBLE UPDATE: Reading over the config params for the 1.7 firmware, it says that param #41 is a 3-byte value. I've never seen that and always assumed that values are 1, 2 or 4 bytes. If this is accurate, I wonder if the ISY doesn't know what to do with 3 bytes? I gleaned this from this copy of the 1.7 manual/config params. Not sure if this is accurate or what, but it stands out as at least something different about param 41.

Any ideas if this is a device issue or an ISY issue?

Gerry

Hi Gerry,

The Z-Wave spec clearly states the parameter value length is limited to 1,2 or 4 bytes. When they say a 3-byte value, I would assume its only actually using 3 bytes of a 4 byte value.

Scott847 · March 4, 2017

...

Reading over the config params for the 1.7 firmware, it says that param #41 is a 3-byte value. I've never seen that and always assumed that values are 1, 2 or 4 bytes. If this is accurate, I wonder if the ISY doesn't know what to do with 3 bytes? I gleaned this from this copy of the 1.7 manual/config params. Not sure if this is accurate or what, but it stands out as at least something different about param 41.

Any ideas if this is a device issue or an ISY issue?

Gerry

This is a bug that was fixed in MultiSensor 6 firmware 1.08 according to the note describing the firmware changes:

"Fixes: Parameter 41 [2 byte] will not longer report back as a 3 byte value causing the report back value to show incorrectly under the gateway interface."

See https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016-

gduprey · March 4, 2017

I just upgraded the firmware on 2 of my ZW100-A units to the 1.08 firmware.

Good news: Humidity calibration value is now being respected!
Bad news: Param 41 is still reading with an error (however, as before, it appears to be settable and the setting does take effect).

Just for those who ever want to do this, it's relatively painless, except for the need to remove the device from the ISY, run their software under windows, make sure the software fins your ZWave stick, then use the Add Node to add the device in, click on the device and go to the firmware tab and upgrade, then remove the node when all done (about 5 minutes). I had never done any of this before and the majority of my time was getting the software to connect to the ZWave stick (if it doesn't show immediately, go to the Settings in the Categories main menu and either it will show or use the Detect button).. After that, the whole thing was pretty easy.

Gerry

P.S. The meaning/use of parameter 41 has changed (in 1.07 and 1.08) to be closer to how parameter 201 works (2 bytes, high byte being a value in tenths and low byte being 1 © or 2 (F)). Be sure to grab the 1.07 docs on config parameters if upgrading from earlier

Sign In

Setup and usage of Aeotec MultiSensor 6

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Archived

Recently Browsing

Who's Online (See full list)

Forum Statistics