-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setValue failing for me #61
Comments
bumping... hoping somebody has some ideas here. |
What i meant in the first part of the question is: When I connect i see a callback telling me a value changed. From what i can see it means node 3, class id 38 instance 1. I can't see what setValue is expecting.. any ideas would help. |
Hi there, Here is the detail of my device Then in my code :
|
@elnulo I changed quite a bit my code and I got it working. I switched to the object syntax and made sure that the data aren't strings. Hope it'll help. |
that ws it!!! thank you. |
root cause finally found: it was a silly typo, see #63 |
Hello all, Thanks! |
@elnulo please note that the changes in this branch will break your code. Does the bugfix accept plain old valueid's as in |
I'm sorry, I'm still encountering this issue. I've tried several identified solutions. What am I missing? |
Do you have a Zwave node numbered 5 to begin with? Can you paste any logs that might be helpful in assisting finding what's wrong? |
I do have a node 5 ... but it wasn't a dimmer. I changed it to node 3, which is as follows: `node3: Linear, PD300Z-2 Plug-in Dimmer Module TypeError: setValue: OpenZWave valueId not found What other types of logging are desirable? Thanks |
I suspect you're having troubles because Node.JS is booting up an older version of the addon somewhere in your system. Try running Also, there's a typo in your command (should be node_id, with an underscore) and the parseInt's are not needed anymore. The command should read: |
@cmmh is your issue resolved? |
@ekarak I am having the same issue. I have however narrowed it down a little more. setValue does not seem to work for most my nodes that are single digit. My light switch that is node 9 fails, but 10-13 work great. I am on version 1.2.0 |
Working on Raspberry Pi2
I see this value get updated:
value = {"value_id":"3-38-1-0","node_id":3,"class_id":38,"type":"byte","genre":"user","instance":1,"index":0,"label":"Level","units":"","help":"","read_only":false,"write_only":false,"is_polled":false,"min":0,"max":255,"value":99}
However, when i do:
zwave.setValue(3,38,1,0,25)
I get:
TypeError: setValue: OpenZWave valueId not found
any ideas?
The text was updated successfully, but these errors were encountered: