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

Send COMMAND_CLASS_TIME_PARAMETERS/TIME_PARAMETERS_SET? #195

Open
JonSilver opened this issue Oct 10, 2017 · 2 comments
Open

Send COMMAND_CLASS_TIME_PARAMETERS/TIME_PARAMETERS_SET? #195

JonSilver opened this issue Oct 10, 2017 · 2 comments

Comments

@JonSilver
Copy link

The TIME_PARAMETERS_SET command requires a 7-octet payload to be sent to the device.
Does openzwave-shared support this?
Is there any sample code anywhere demonstrating how this might be achieved?

@ekarak
Copy link
Member

ekarak commented Oct 14, 2017

there's a custom TimeParameters class defined in ozw which the 7-byte payload is defined:
https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/command_classes/TimeParameters.cpp#L196-L208

Judging by this line however:
https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/command_classes/TimeParameters.cpp#L217

seems that the valueType for TIME_PARAMETERS_SET is a...ValueType_Button (I'd expect this to be a ValueType_Raw).

This feature needs some work...

@JonSilver
Copy link
Author

Apropos of nothing, I found this, but nothing else:
OpenZWave/open-zwave#606

Seems nobody else is wanting to send the date & time over to locks, thermostats or anything. Or maybe they've found a way that's eluded me.

So in the meantime is there any way of getting the date & time over to these devices? :(

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

No branches or pull requests

2 participants