Closed gxapplications closed 4 years ago
Someone back from holidays ? :)
Nobody on this project?
Apparently, not solvable on the OZW lib side (https://github.com/OpenZWave/open-zwave/issues/1945). Any fix or solution ?
@gxapplications for buttons I use the api setValue(valueId, value)
by use true
as value
and it works
Button is not the issue. It’s that the index variable was increased from a byte to a short. If your inputting 257 but OZW is seeing 1, then then conversion didn’t happen in the wrapper correctly.
@Fishwaldo So how to fix this?
Make sure index values in the wrapper can handle short sized integers.
@Fishwaldo https://github.com/OpenZWave/node-openzwave-shared/blob/master/src/utils.hpp#L49 should be already handled
Based on the logs provided, index 257 turned into index 1 which is a overflow!
Actually testing 1.5.10 against 1.5.0, the bug seems to be fixed between these 2 versions. Thank you !
Hello,
I have a Fibaro FGWPE/F Wall Plug Gen5, and annother Fibaro product that both supports METER command class. Since I migrate to the OpenZwave 1.6 (from 1.4) I noticed the Reset feature of METER Command Class index changed from 33 to 257. The problem is the new index is 257 in fact. So when I call zwave.pressButton(4, 50, 1, 257), I got this error : TypeError: OpenZWave valueId not found: 4-50-1-1 I'm not pressing the button at index 1, but at index 257... It should be out of 0-256 bounds maybe... I looked in open-zwave lib, and confirmed that the Reset feature is well affected at index 257: https://github.com/OpenZWave/open-zwave/blob/4478eea26b0e1a29184df0515a8034757258ff88/cpp/src/ValueIDIndexesDefines.h#L86
In ozwcache file, I have this, confirming the feature Reset at unreachable index:
How to reset a METER if we cannot use pressButton(x, y, z, 257) ???