fibaro and problems with 65535 parameters

[Gravityz]

i currently use a couple of fibaro devices and noticed that they have problems with certain parameters which can not be set correctly

most of the time these parameters are the short type (0-65535)

i also notice that trying to set these parameters to 65535 willl not be accepted.
I can not believe that I am the only one who is noticing this

eg
fibaro motion sensor FGMS-001
parameter 66 temp offset
i can not set this parameter to 65525 (-1.0c)

fibaro wallplug fgwpe
parameter 47
65535 should disable power report but setting 65535 is not accepted (can use -1 to set it though)

i tested and 32767 is accepted as the highest number
this is 15 bits

could it be that the zwave implementation in domoticz for certain registers is 15 bits instead of 16

eg, did somebody make a mistake and calculate from bit 0 to bit 15 and mistakenly is using 15 bits instead of 16 bits.

[marcelr]

A short has a range from -32768 to 32767. Positive numbers go from 0x0 to 0x7FFF. The negative numbers are stored in the upper range (0x8000 through 0xFFFF), as their two's complement.
65525 (decimal) does not exist in that range, -10 does.

If you want a range from 0 to 65535 you should declare it as an unsigned short ...

grtz,

marcelr

[Gravityz]

that sounds exactly like the solution.

how do i declare it as an unsigned short because as far a the wiki goes it is either short or

bool - The bool type is a Boolean type, or simply either true/false, on/off or 1/0
byte - A byte can represent a number from 0 to 255 (or 0x00 to 0xFF)
decimal - A decimal is a fractional number, eg, 25.5. Could also be referred to as a float or double.
int - A integer can represent a number from 0 to 4294967295
list - A list of possible string values, with each string value identified by a number
short - A Short can represent a number from 0 to 65535
string - A String - Not often used for Config Variables.
raw - The value, represented as a series of bytes. Unbounded by the OZW in length, but the device might impose some upper limits. Should not be used unless advised by a developer.

i can tell you that all the zwave xml files are using short while i notice that this is probably not correct(eg 65535 is not accepted)

https://github.com/OpenZWave/open-zwave ... ng-Devices

also seems a really old problem where Fibaro seems not to follow the zwave specs
https://groups.google.com/forum/#!msg/o ... rtuRVVKVEJ

could we declare it an INT or would de device not accept this?