PhanTomiZ Posted April 22, 2017 Posted April 22, 2017 Finally received my Z Stick and a couple more Multisensor 6. First thing after getting the Multisensors, was to update the firmware with 1.07. I have them both updated to 1.07. Quite easy and painless procedure. I'm able to access most of the configuration parameters except for anything regarding temperature. Like upper/lower limit value of temperature sensor and temperature calibration. The only temperature parameter that I can make changes to is Parameter 64 to change from °F to °C and back. This doesn't really seem like a problem, but the temperature for both sensors is off by about 1°C. Anyone else have these same results? What versions of firmware are you running with these Multisensors and why? PhanTomiZ P.S. Here are the parameters I do not have access to: Parameter number: 8 Set timeout of awake after the wake up CC is sent out 9 41 Threshold change in temperature to induce an automatic report 49 Set upper limit of temperature sensor 50 Set lower limit of temperature sensor 57 Set recover limit value of temperature sensor 201 Temperature calibration (the available value range is [-128,127] or [-12.8℃, 12.7℃]).
Broyd Posted April 22, 2017 Posted April 22, 2017 Did you see this Aeotec posting for temperature calibration using v.1.07? https://aeotec.freshdesk.com/support/solutions/articles/6000120736-calibrating-offsetting-temperature-on-multisensor-6-excel-easy-sheet-included
PhanTomiZ Posted April 22, 2017 Author Posted April 22, 2017 Did you see this Aeotec posting for temperature calibration using v.1.07? https://aeotec.freshdesk.com/support/solutions/articles/6000120736-calibrating-offsetting-temperature-on-multisensor-6-excel-easy-sheet-included No, I didn't see this. Got it now. I can't believe this temperature calibration parameter has to be so complicated. Using the spreadsheet fixed the problem. So for a -1.2°C offset requires a parameter value of 62466. For the previous versions, it was somewhat intuitive, but this is ridiculous. While trying to access parameter 41, I still get a "Z-Wave Command Failed". That's probably the only other parameter which I'm interested in changing. Thanks PhanTomiZ
Broyd Posted April 22, 2017 Posted April 22, 2017 According to the Aeotec documentation for v1.07, parameter 41 is a 3 byte parameter (as well as two other parameters, 49 and 50). For parameter 49 the documentation says: Threshold change in temperature to induce an automatic report. Note: 1. The unit is Fahrenheit for US version, Celsius for EU/AU version. 2. High byte is the threshold value. Low byte is the unit (0x01=Celsius, 0x02=Fahrenheit). 3. The threshold value (high byte) contains one decimal point. E.g. if the value is set to 20 (0x001401), the threshold value =2.0 ℃ (EU/AU version) or if the value is set to 20 (0x001402), the threshold value= 2.0 ℉ (US version). When the current temperature is changed more then 2.0, which will induce a temperature report to be sent out. See: http://www.cd-jackson.com/zwave_device_uploads/355/Engineering-Spec---Aeon-Labs-MultiSensor-6-V1-07.pdf You are supposed to be able to set Z-Wave parameters using the Z-Stick and the aeotec zensys-tools but I don't know how to do this. The ISY only lets you select parameter lengths of 1, 2, or 4. I have one MS6 at firmware 1.06 and the other is at 1.07. The ISY reads parm 41 fine from 1.06 but also gets the error from 1.07. I haven't yet run a diagnostic to see if I can get more info from the 1.07 unit when trying to read or set parm 41. I suspect that the parameter length is actually 3 bytes, thus causing the error.
PhanTomiZ Posted April 23, 2017 Author Posted April 23, 2017 According to the Aeotec documentation for v1.07, parameter 41 is a 3 byte parameter (as well as two other parameters, 49 and 50). For parameter 49 the documentation says: Threshold change in temperature to induce an automatic report. Note: 1. The unit is Fahrenheit for US version, Celsius for EU/AU version. 2. High byte is the threshold value. Low byte is the unit (0x01=Celsius, 0x02=Fahrenheit). 3. The threshold value (high byte) contains one decimal point. E.g. if the value is set to 20 (0x001401), the threshold value =2.0 ℃ (EU/AU version) or if the value is set to 20 (0x001402), the threshold value= 2.0 ℉ (US version). When the current temperature is changed more then 2.0, which will induce a temperature report to be sent out. See: http://www.cd-jackson.com/zwave_device_uploads/355/Engineering-Spec---Aeon-Labs-MultiSensor-6-V1-07.pdf You are supposed to be able to set Z-Wave parameters using the Z-Stick and the aeotec zensys-tools but I don't know how to do this. The ISY only lets you select parameter lengths of 1, 2, or 4. I have one MS6 at firmware 1.06 and the other is at 1.07. The ISY reads parm 41 fine from 1.06 but also gets the error from 1.07. I haven't yet run a diagnostic to see if I can get more info from the 1.07 unit when trying to read or set parm 41. I suspect that the parameter length is actually 3 bytes, thus causing the error. Now that you mention 3 byte parameter, I do recall reading something about this a few months ago. It seems you are correct and all parameters that are 3 bytes in size are inaccessible by the ISY. I updated the firmware to these two MS6 because I wanted them to report in °C. I now have to ask myself what I want more, to report in °C or to induce a report depending on temperature change. As it stands, I have 4 MS6 with unknown firmware version and 2 MS6 with V1.07. I do have a Z-Stick, but haven't done anything with it other than update firmware for the MS6 and Smart Switch. With your V1.06, can you use parameter 64 to change from °F to °C? PhanTomiZ
Scott847 Posted April 23, 2017 Posted April 23, 2017 According to the Aeotec documentation for v1.07, parameter 41 is a 3 byte parameter (as well as two other parameters, 49 and 50). ... I have one MS6 at firmware 1.06 and the other is at 1.07. The ISY reads parm 41 fine from 1.06 but also gets the error from 1.07. I haven't yet run a diagnostic to see if I can get more info from the 1.07 unit when trying to read or set parm 41. I suspect that the parameter length is actually 3 bytes, thus causing the error. Now that you mention 3 byte parameter, I do recall reading something about this a few months ago. It seems you are correct and all parameters that are 3 bytes in size are inaccessible by the ISY. ... Aeotec has an "unofficial" firmware 1.08 for the MultiSensor 6. It's at https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016- It includes a fix for the 3-byte parameter 41: "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."
Broyd Posted April 23, 2017 Posted April 23, 2017 Thanks Scott847 for the heads up. I was aware of this firmware update. BUT it has some consequences ... There are a few changes that may lead to some surprise which is why the firmware was pulled down temporarily. The V1.08 firmware version should only be used if you do not plan on having the sensor reports too rapidly (<10 minutes intervals).
Broyd Posted April 23, 2017 Posted April 23, 2017 With your V1.06, can you use parameter 64 to change from °F to °C? PhanTomiZ No, that doesn't work; I couldn't query that parameter without an error in v1.06. v1.07 was released to allow users to change C<->F regardless of which continent they are on. And it seems as if the 3 byte length might be an error anyway. (Thanks Scott).
Scott847 Posted April 23, 2017 Posted April 23, 2017 Thanks Scott847 for the heads up. I was aware of this firmware update. BUT it has some consequences ... There are a few changes that may lead to some surprise which is why the firmware was pulled down temporarily. The V1.08 firmware version should only be used if you do not plan on having the sensor reports too rapidly (<10 minutes intervals). Just did some further checking... looks like contrary to the 1.08 firmware note a query to parameter 41 still doesn't work and there's an error message when setting that parameter. However, I believe (but didn't check) for the 1.08 firmware you can set parameter 41 (size = 2) even though an error appears on the automatic query that's done afterwards as part of setting the parameter. Anyway, I have a few on firmware 1.08 on USB power and they seem to report back data OK on six minute intervals (I think the warning you highlighted about < 10 minute intervals applies when it's battery powered). The settings I'm using are: - P40/S1 = 0 (enables time interval based reporting) - P111/S4 = 360 (report every 360 seconds) One of the main reasons I went to 1.08 is the ability to stop the blue LED indicator from lighting when it senses motion (P81/S1 = 1).
PhanTomiZ Posted April 24, 2017 Author Posted April 24, 2017 Just did some further checking... looks like contrary to the 1.08 firmware note a query to parameter 41 still doesn't work and there's an error message when setting that parameter. However, I believe (but didn't check) for the 1.08 firmware you can set parameter 41 (size = 2) even though an error appears on the automatic query that's done afterwards as part of setting the parameter. Anyway, I have a few on firmware 1.08 on USB power and they seem to report back data OK on six minute intervals (I think the warning you highlighted about < 10 minute intervals applies when it's battery powered). The settings I'm using are: - P40/S1 = 0 (enables time interval based reporting) - P111/S4 = 360 (report every 360 seconds) One of the main reasons I went to 1.08 is the ability to stop the blue LED indicator from lighting when it senses motion (P81/S1 = 1). I forgot that this was another parameter I was interested in changing (P81/S1=1) Blue light. I didn't update the firmware to V1.08 because I wanted a tighter time interval and 10 minutes seemed quite long. If 360 seconds works, maybe 120 Seconds will also work? Is there a parameter PDF for V1.08.? Can't find it on their website. Thanks PhanTomiZ
Scott847 Posted April 24, 2017 Posted April 24, 2017 I forgot that this was another parameter I was interested in changing (P81/S1=1) Blue light. I didn't update the firmware to V1.08 because I wanted a tighter time interval and 10 minutes seemed quite long. If 360 seconds works, maybe 120 Seconds will also work? Is there a parameter PDF for V1.08.? Can't find it on their website. Thanks PhanTomiZ Are you using it USB-powered? Did some further testing of firmware 1.08 when powered this way.... If you try to change the interval reporting (P111/S4) to something like 120 seconds, it will override your change to 240 seconds (4 minutes), which is the minimum interval. But you can have both time interval and change-based reporting at the same time. For example, if you set P111/S4 to 240 seconds it will report any changes every 240 seconds. In addition, if you set P41/S2 to 3 (0.3 degrees), any time there is a temperature change of >= 0.3 from the last temperature change report, it will immediately report that change. Although ISY will report an error when setting P41/S2 it appears that the change takes effect on the multisensor. I haven't run across an updated parameters doc for 1.08. Links to latest info: - Info about firmware 1.08 including some info about configuration parameter changes: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016- - Configuration Parameters for firmware 1.07: https://aeotec.freshdesk.com/helpdesk/attachments/6028954764 FYI following is an example of a program that logs the multisensor data to Initial State at least every 4 minutes: *************** PROGRAM Sensor AMS6-2 Log If 'Master Bedroom / ZW 039 Multilevel Sensor' Temperature > 0.0°F Or 'Master Bedroom / ZW 039 Multilevel Sensor' Humidity > 0% Or 'Master Bedroom / ZW 039 Multilevel Sensor' Luminance >= 0 lux Or 'Master Bedroom / ZW 039 Motion Sensor' Status is On Or 'Master Bedroom / ZW 039 Motion Sensor' Status is Off Then Wait 30 seconds Repeat Every 4 minutes Resource 'Initial State MBR Sensor' Else - No Actions - (To add one, press 'Action')
PhanTomiZ Posted April 25, 2017 Author Posted April 25, 2017 Are you using it USB-powered? Did some further testing of firmware 1.08 when powered this way.... If you try to change the interval reporting (P111/S4) to something like 120 seconds, it will override your change to 240 seconds (4 minutes), which is the minimum interval. But you can have both time interval and change-based reporting at the same time. For example, if you set P111/S4 to 240 seconds it will report any changes every 240 seconds. In addition, if you set P41/S2 to 3 (0.3 degrees), any time there is a temperature change of >= 0.3 from the last temperature change report, it will immediately report that change. Although ISY will report an error when setting P41/S2 it appears that the change takes effect on the multisensor. I haven't run across an updated parameters doc for 1.08. Links to latest info: - Info about firmware 1.08 including some info about configuration parameter changes: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016- - Configuration Parameters for firmware 1.07: https://aeotec.freshdesk.com/helpdesk/attachments/6028954764 FYI following is an example of a program that logs the multisensor data to Initial State at least every 4 minutes: *************** PROGRAM Sensor AMS6-2 Log If 'Master Bedroom / ZW 039 Multilevel Sensor' Temperature > 0.0°F Or 'Master Bedroom / ZW 039 Multilevel Sensor' Humidity > 0% Or 'Master Bedroom / ZW 039 Multilevel Sensor' Luminance >= 0 lux Or 'Master Bedroom / ZW 039 Motion Sensor' Status is On Or 'Master Bedroom / ZW 039 Motion Sensor' Status is Off Then Wait 30 seconds Repeat Every 4 minutes Resource 'Initial State MBR Sensor' Else - No Actions - (To add one, press 'Action') All 6 of my MS6 sensors are USB powered. I like having the ability of inducing an automatic report based on temperature, so it looks like V1.08 will be the version for me. P111/S4 at 240 seconds will be sufficient, but not necessary providing I can have change based reporting (Temp, Hum, Lux, UV or Tamper). As long as the ISY only reports the error for P41/S2. V1.07 won't allow query of the parameter. "Resource 'Initial State MBR Sensor'" this must be a V5.xx option or module I'm not familiar with? Thanks for all the info. This post should help all with setting up this Aeotec Multisensor 6. Again, providing one has the Z-Stick. PhanTomiZ P.S. Have to go away for a few days, but when I get back I'll be running my spare MS6 through its paces with V1.08 firmware. P.P.S. One final thought...If an Insteon motion sensor has 3 nodes, how many does this MS6 eat up?
Scott847 Posted April 28, 2017 Posted April 28, 2017 ... "Resource 'Initial State MBR Sensor'" this must be a V5.xx option or module I'm not familiar with? ... "Resource 'Initial State MBR Sensor'" is an ISY network resource action that logs the multisensor data to Initial State, which is a cloud-based data logging/analysis site (www.initialstate.com). Below is a "tile" showing the temperature data for the past couple of days and the ISY network resource config (ISY 5.0.8 but I think should also work on 4.5.4 or 5.0.10).
wolffe Posted May 20, 2017 Posted May 20, 2017 I am experiencing the 3 byte parameter issue with zw100 firmware v1.0.8 and isy994i v4.5.4 with Z-Wave fw v4.55 Is the new 5 series isy994i firmware having this issue?
Chris Jahn Posted May 22, 2017 Posted May 22, 2017 Hi Guys, The reason we don't support 3-byte parameters is that the Z-Wave specification makes it very clear that the only valid parameter lengths are 1,2 and 4 bytes, and that any other length must not be used (i.e. you aren't even allowed to support them if you want to).
Recommended Posts
Archived
This topic is now archived and is closed to further replies.