johnnyt Posted July 18, 2019 Posted July 18, 2019 Am struggling to change multi byte parameters, largely related to using hex properly, I believe. For example, this screenshot shows a multi byte parameter for an Aeotec multi sensor that I want to change from 20 (0x14) to 10 (0x0A, as I understand it). (first confusing thing: it says it's size 3 but ISY returns that it's size 4. I tried both sizes but the examples below show my attempts using size 4 ) Using rest according to my understanding of: I first used the following to query the value: Then I used the following to set the value according to my understanding of sending multi byte hex value (highlighted): When I query again, the value didn't change: Same using ISY config tool to query value: What am I doing wrong? Any info would be appreciated.
jfai Posted July 18, 2019 Posted July 18, 2019 I've used the ISY Z-Wave menu to configure the device. In the "Z-Wave Configuration Parameters" dialog, click on the arrow button until you see "hex" to the right of the value input box. Then enter the desired hexadecimal value. Example: Parameter Number: 41 // Threshold for change of temperature Parameter Size: 3 Parameter Value: 202 // MSB = 0x2 = 0.2 degrees, LSBs = 0x02 = Fahrenheit Before making a change, I first query the parameter to ensure I'm working with the correct one and that the device is responding. This will retrieve the parameter size. Then I just change the parameter value. Check that the system status at the bottom of the admin screen goes back to "Ready" after each Z-Wave command. This should take no more than half a second or so. Otherwise, check the ISY logs.
johnnyt Posted July 18, 2019 Author Posted July 18, 2019 40 minutes ago, jfailenschmid said: I've used the ISY Z-Wave menu to configure the device. In the "Z-Wave Configuration Parameters" dialog, click on the arrow button until you see "hex" to the right of the value input box. Then enter the desired hexadecimal value. Example: Parameter Number: 41 // Threshold for change of temperature Parameter Size: 3 Parameter Value: 202 // MSB = 0x2 = 0.2 degrees, LSBs = 0x02 = Fahrenheit Before making a change, I first query the parameter to ensure I'm working with the correct one and that the device is responding. This will retrieve the parameter size. Then I just change the parameter value. Check that the system status at the bottom of the admin screen goes back to "Ready" after each Z-Wave command. This should take no more than half a second or so. Otherwise, check the ISY logs. Thanks for the tip about getting to hex on ISY config dialog. My sensor now reports A0200 in hex, which looks a little like the command I sent 000A02 without the leading zeros and with 2 zeroes added to the end. Another interesting thing to note. In addition to this, here's what else I learned, I think: 1) the ISY size report is <actual size +1> 2) My query command via Chrome was returning the cached results (no change) and I needed to either clear the cache or use a different browser OR 3) the sensor only took in the change when it woke up to do something 4) There are only 2 groups, the MSB and the LSB and - I'm guessing - the total size (i.e. 2, 3 or 4 bytes) has to do with the range that each of MSB and LSB has. Is that right? Thanks again
johnnyt Posted July 22, 2019 Author Posted July 22, 2019 Things are not working for me. Using the example above, I tried to set MSB = 0x2 = 0.2 degrees, LSBs = 0x02 = Fahrenheit So I tried the following 2 REST commands: (I'm really not clear on the size parameter as the manual says 3 and ISY reports 4) http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x000202/4 http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x000202/3 but when I query after each one using REST ISY reports the default value is active (nothing changed) then I used the ISY parameter config tool to first query paramater 41 then enter the following (in hex) when I press "set" it goes back to the value that was there before (nothing changed? then I try the shorter "202" in hex but when I press "set" it returns the (default) value from before. Any help would be appreciated.
Chris Jahn Posted July 22, 2019 Posted July 22, 2019 Try setting the value using parameter size 3. Size 3 is actually not allowed in Z-Wave but for some reason manufacturers decided to use it anyways so we added support for it. In some cases when a size 3 parameter is queried, the results say its size 4.
johnnyt Posted July 22, 2019 Author Posted July 22, 2019 using size 3 with ISY tool did make a change when I clicked set but returned this when I entered either 202 or 000202 or 0x0202 I can't tell what I'm getting. Why is there "0200" added after the "202" I put in." or maybe "20" added to beginning and "00" added to the end?? also why isn't the REST command using size 3 doing anything? (http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x000202/3) Thanks
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 4 minutes ago, jfailenschmid said: Version of the ISY firmware? 5.0.15A
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 16 hours ago, johnnyt said: using size 3 with ISY tool did make a change when I clicked set but returned this when I entered either 202 or 000202 or 0x0202 I can't tell what I'm getting. Why is there "0200" added after the "202" I put in." or maybe "20" added to beginning and "00" added to the end?? also why isn't the REST command using size 3 doing anything? (http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x000202/3) Thanks Try turning on the Admin Console event viewer to level 3 and then set the value again, this will show the exact Z-Wave messages being sent between the ISY and the device (post the results here).
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 Below is the event log after setting it to "202" with size set to 3. Yes, my ISY is having problems updating log (suspect SD card and waiting for new one to arrive). I left the errors in case that's somehow affecting the updating of zwave device parameters. Tue 07/23/2019 09:27:48 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [2903000202] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 09:27:48 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:27:48 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/3/514 Tue 07/23/2019 09:27:48 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:27:48 AM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 09:27:48 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:27:49 AM : [D2D EVENT ] Event [n001_ven1] [GV2] [1] uom=25 prec=0 Tue 07/23/2019 09:27:49 AM : [ n001_ven1] GV2 1 (uom=25 prec=0) Tue 07/23/2019 09:27:49 AM : [D2D-CMP 03AB] STS [n001_ven1] GV2 op=1 Event(val=1 uom=25 prec=0) is Condition(val=1 uom=25 prec=0) --> true Tue 07/23/2019 09:27:49 AM : [D2D-CMP 03AB] STS [n001_ven1] GV2 op=1 Event(val=1 uom=25 prec=0) is Condition(val=-1 uom=25 prec=0) --> false Tue 07/23/2019 09:27:49 AM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290402020200] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 09:27:49 AM : [UZW-CMD 28 ] Query Config : ZW003_1 param 41 Tue 07/23/2019 09:27:49 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:27:50 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Here it is after setting it to "0x020200": Tue 07/23/2019 09:28:02 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:28:02 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400000000] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 09:28:02 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:28:02 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/0 Tue 07/23/2019 09:28:02 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 09:28:02 AM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 09:28:02 AM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290402020200] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 09:28:02 AM : [UZW-CMD 28 ] Query Config : ZW003_1 param 41 Tue 07/23/2019 09:28:02 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a)
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 I see that 2nd one above had reverted back to size 4 (which happens on query) here is the event log capture after setting it to "0x020200" with size 3: Tue 07/23/2019 10:12:14 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [2903000000] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:12:14 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/3/0 Tue 07/23/2019 10:12:14 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:12:14 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:12:14 AM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:12:14 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:12:15 AM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290402020200] ACK,AUTO,EXPLORE From=0x03
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400000000] ACK,AUTO,EXPLORE To=0x03 This is attempting to set Parameter 41 (0x29) to value=0 size=4 Can you post the exact command you used? This is what it should look like when setting parameter 41 to 0x020200 size=4 (using /rest/zwave/node/ZW003_1/config/set/41/0x020200/4) [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400020200] ACK,AUTO,EXPLORE To=0x03
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [2903000000] ACK,AUTO,EXPLORE To=0x03 The value isn't being set correctly (its zero), what is the exact command you used to do this?
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 so version 1.1 of the engineering spec does say this is a size 4 parameter. I was quoting version 1.08 previously. What I want is for a 0.2 F change in temp to trigger report of temperature, which, according to latest version of spec should be 0x00020200. As there appears to need to be 4 pairs, I entered 0x00020200 and used size 4: Tue 07/23/2019 10:27:06 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400000000] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:27:06 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/0 Tue 07/23/2019 10:27:06 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:27:06 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:27:06 AM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:27:06 AM : [FileOpen ] Open failed for [/LOG/ERRORA.LOG] (a) Tue 07/23/2019 10:27:06 AM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290402020200] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 10:27:06 AM : [UZW-CMD 28 ] Query Config : ZW003_1 param 41 I still get the same result when I query and I'm not sure how to interpret it except to think that it's wrong.
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 1 minute ago, Chris Jahn said: [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [2903000000] ACK,AUTO,EXPLORE To=0x03 The value isn't being set correctly (its zero), what is the exact command you used to do this? I'm using the built-in ISY parameter config tool.
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 6 minutes ago, Chris Jahn said: [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [2903000000] ACK,AUTO,EXPLORE To=0x03 The value isn't being set correctly (its zero), what is the exact command you used to do this? I tried again using REST: and this time it appeared to send the right command through Tue 07/23/2019 10:39:06 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400020200] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:39:06 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/131584 but it still reports 2020200 instead of 00020200 that I would have expected (or 20200 if leading zeros dropped)
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 I'd try setting it to 140200 and see if the value gets set properly. If it does then its possible the device has a lower bound for the threshold and won't let you set it to 0.2 degrees.
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 tried to reset to default using http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x00140200/4 and it worked, i.e. it reported the default value back to me. Tue 07/23/2019 10:49:03 AM : [ZWAVE-RX ZW003_1] [31/05] CC=0x31 cmd=0x05 [1B0100] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 10:49:03 AM : [ZWAVE ZW003_1] Process value Sensor type=27 scale=0 prec=0 Tue 07/23/2019 10:49:05 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400140200] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:49:05 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/1311232 When I tried again to change to new value using http://192.168.0.251/rest/zwave/node/ZW003_1/config/set/41/0x00020200/4 Tue 07/23/2019 10:49:18 AM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400020200] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 10:49:18 AM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/131584 It reported the default value back to me - as though it didn't accept the new value. I tried querying multiple times using both config tool and REST query REST query result: <config paramNum="41" size="4" value="1311232"/>
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 Try different values for the threshold to see if they are accepted, e.g. instead of 0x14, try 0x18, 0x10 etc. and see if the value changes. I suspect it doesn't let you go as low as 0.2 degrees (0x02).
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 4 minutes ago, Chris Jahn said: I'd try setting it to 140200 and see if the value gets set properly. If it does then its possible the device has a lower bound for the threshold and won't let you set it to 0.2 degrees. I tried 0x000A0200 for 1.0 F and it didn't take. then I tried 001E0200 for 3.0 F and it worked. So it seems you're right. it's quite disappointing that threshold has to be at least 2F. That's a pretty big spread. Do I also take it from this that I shouldn't use the built in tool to make these parameter changes?
Chris Jahn Posted July 23, 2019 Posted July 23, 2019 1 minute ago, johnnyt said: Do I also take it from this that I shouldn't use the built in tool to make these parameter changes? No, the builtin tool definitely works. I've been trying to recreate that problem here but I cannot. The only thing I could do to make it fail was to enter an invalid hex number (e.g. 20G02A).
jfai Posted July 23, 2019 Posted July 23, 2019 I have 3 Multisensor 6 devices and use 0.2 degrees F as temperature thresholds. No issues setting the temperature threshold or any of the other parameters using the ISY in-built tool.
johnnyt Posted July 23, 2019 Author Posted July 23, 2019 1 hour ago, jfailenschmid said: I have 3 Multisensor 6 devices and use 0.2 degrees F as temperature thresholds. No issues setting the temperature threshold or any of the other parameters using the ISY in-built tool. Do you have the v1.08 (3 bytes) or v1.1 (4 bytes)? I'm not having any problems changing the other values I tried below using the tool, including another 4 byte parameter (49) that I tried just to see. I tried again to 1) reset param 41 to default 140200, which worked, then set it to 020200, which didn't, i.e. returned previous default value Tue 07/23/2019 01:08:26 PM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400140200] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 01:08:26 PM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/1311232 Tue 07/23/2019 01:08:26 PM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 01:08:26 PM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290400140200] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 01:08:26 PM : [UZW-CMD 28 ] Query Config : ZW003_1 param 41 Tue 07/23/2019 01:08:38 PM : [ZWAVE-TX ZW003_1] [70/04] CC=0x70 cmd=0x04 [290400020200] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 01:08:38 PM : [UZW-CMD 29 ] Set Config : ZW003_1 41/4/131584 Tue 07/23/2019 01:08:38 PM : [ZWAVE-TX ZW003_1] [70/05] CC=0x70 cmd=0x05 [29] ACK,AUTO,EXPLORE To=0x03 Tue 07/23/2019 01:08:38 PM : [ZWAVE-RX ZW003_1] [70/06] CC=0x70 cmd=0x06 [290400140200] ACK,AUTO,EXPLORE From=0x03 Tue 07/23/2019 01:08:38 PM : [UZW-CMD 28 ] Query Config : ZW003_1 param 41 I guess I will bring this to the attention of Aeotec. edit: I can set the value down to 1.0F (A0200) but not lower. I've sent a question to Aeotec about this and whether that apparent lower limit can be adjusted or eliminated.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.