Set Configuration Parameter Fails in UI works in REST

[brockp]

I recently picked up an Aeotec Z-Wave color change bulb.  I'm running firmware 4.5.4 and zwave dongle 4.55.

 

I found this wonderful excel sheet that calculates your parameter values for you from the vendor.

 

I found though that changing the parameter via the UI  device->z-wave->Set Configuration Parameter

 

If I enter a value and hit set it always gets set to 0. 

 

If I set using the REST system using hex or decimal it works like a charm.  Following that thread I now control things via the network module and look forward to 5.x going stable.

 

Now where the bug really gets, not only can you not set the parameter correctly via the UI.  After I set it with the REST interface, if I go back to the UI things go bad if you query the value you get nonsenical values back

 

eg

#set value with rest request using hex 0x0163005E
#also works with decimal 23265374
http://192.168.1.5/rest/zwave/node/ZW010_1/config/set/37/0x0163005E/4

Sat 02/11/2017 09:40:59 PM : [UZW-CMD 29      ] Set Config : ZW010_1 37/4/23265374

Open console and Z-Wave Configration Parameters window and query parameter 37

#reported values
Parameter Number 37
Parameter Size 4
Parameter Value 16777215

That value matches nothing.  If you hit set now the bulb goes white, but the parameter should not change.  If I now query the same parameter again I get a new value 6488158 which now never changes.

 

A lot of unexpected behavior.  Is this expected?

[Chris Jahn]

Hi brockp,

 

There is a bug related to this where the UI cannot set or display the value correctly if it is large integer.  This may be what you are experiencing here.

[Broyd]

I don't know where the problem lies but obviously something is not right. Are you setting the parameters from a browser OR are you using the network module to issue the http URL?

 

What results do you get when you use REST to query parameter 37 instead of using the UI.

 

You can use a browser to do the query or you can set up another network resource and then run it by pressing the test button in the panel where you created the resource.

 

Ah. I see Chris Jahn provided the answer. That is a pretty serious bug if you need to set a large value. Hopefully it is fixable. Still curious, what does the REST query show?

[brockp]

Broyd,

 

If I do a query the XML fragment has the correct value.

[Broyd]

Broyd,

 

If I do a query the XML fragment has the correct value.

Thanks for telling me this. At least there is a way to set and check those large values!