Skip to content
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

Thermostat Setpoints not being picked up #239

Open
thucar opened this issue Jul 12, 2018 · 2 comments
Open

Thermostat Setpoints not being picked up #239

thucar opened this issue Jul 12, 2018 · 2 comments

Comments

@thucar
Copy link

thucar commented Jul 12, 2018

I'm having a bit of a hard time here. The thermostat setpoints are not being picked up or registered by my Node-Red setup.

Not sure if this is a node-red-contrib-openzwave, node-openzwave-shared or open-zwave issue. But as I can see the packets coming in in the OZW_Log file, I'm leaning towards the former two.

This is a snip of my log file. You can see on the line 7, the setpoint packet has been successfully received.
Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x43, 0x03, 0x01, 0x42, 0x0a, 0xf0, 0x0b

However there is no Info following it and it never shows up in Node-Red. Have tested it with three different thermostats (Qubino, HeatIt, MCOHome) so far and all three have the same behavior. All other data from the thermostats is being processed correctly.

Any ideas or help would be welcome.

2018-07-12 10:47:41.762 Detail, Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x80, 0x03, 0x64, 0x15
2018-07-12 10:47:41.762 Detail,
2018-07-12 10:47:41.762 Info, Node003, Received Battery report from node 3: level=100
2018-07-12 10:47:41.762 Detail, Node003, Refreshed Value: old value=100, new value=100, type=byte
2018-07-12 10:47:41.762 Detail, Node003, Changes to this value are not verified
2018-07-12 10:47:41.763 Detail, Node003, Notification: ValueChanged
**2018-07-12 10:47:41.821 Detail, Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x43, 0x03, 0x01, 0x42, 0x0a, 0xf0, 0x0b
2018-07-12 10:47:41.821 Detail,
2018-07-12 10:47:41.878 Detail, Node003,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x03, 0x04, 0x46, 0x08, 0x00, 0x7f, 0xc7
2018-07-12 10:47:41.878 Detail,
2018-07-12 10:47:41.879 Info, Node003, Received climate control schedule override report:
2018-07-12 10:47:41.880 Info, Node003,   Override State: None:
@ekarak
Copy link
Member

ekarak commented Jul 12, 2018

if you can get me an zwave thermostat that'd be handy :) just kidding, we just need an example of how are thermostat values set using OpenZWave, then I can try modelling it using a higher level example

@thucar
Copy link
Author

thucar commented Jul 12, 2018

I'd be more than happy to provide the examples you need. I'm afraid I just might need a bit more guidance on what exactly is needed and where can I find it.

The way I usually receive data from my devices, is log the values in Node-Red when including a node, or doing a "refreshNodeInfo" on an already included node. If I need to specifically refresh some information, I can just use the valueID and do a refreshValue.

I'm going by the OpenZwave documentation here: http://www.openzwave.com/dev/classOpenZWave_1_1ThermostatSetpoint.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants