I have a Danfoss Room Thermostat (or better: a Devolo MT-2649).
You can set the setpoint temperature with up and down keys. If you manage to press the “LED Button” you can set a “timed heating period” for 1h up to 24h what is really a cool feature… BUT i can’t get openhab or the zwave binding to get this value.
This device doesn’t just send the plain new setpoint value and x hours later the former value again - it uses the command class schedule for sending so there is no change for the temperature setpoint channels in openhab.
Any idea how to get these values / value changes or how to make the device send the changes via default setpoint value?
OK, let’s start with the basics.
What version of OpenHAB & Z-Wave binding?
That item was last updated last month which means you likely need 2.5M3 version of the binding. 2.5M2 may be new enough. I am not sure.
I have been trying to update the database. removing obvious errors.
Does your manual show some configuration parameters that we may have missed? Sometimes finding the necessary information can be quite a challenge, especially on older devices.
I just added configuration command class SCHEDULE
The change will need to be reviewed and then it will be in the next binding version published.by @chris
The binding receives the command class SCHEDULE but doesn’t know what to do with it?
Any idea how to get these commands as raw values as a string or sth. similar?
BTW: where and how could I find (or handle) this payload?
only three bytes are changing for this “schedule”:
06 = this is the hours for how long the overwritten schedule shall be used… 06 = 6 hours
01 18 = this is the setpoint times 10 01 18 = 280 -> 28 deg 00 C8 = 200 -> 20deg 00 FF= 255 -> 25.5 deg
so maybe there’s someone with an idea how to process these in openhab? or maybe @chris could give me a hint how to get this message for further processing?
If you really wish to pursue this I recommend filing an issue on GitHub with a link to this thread.
I think this should be a lower priority than some other pressing issues.
Chris needs to get his development environment working with the new system so he is able to make binding changes.
I know of one pending change where users cannot use their devices (Doorbells and Sirens) with OpenHAB until changes are made.
Thank you for your patience.
I can really only point back at the statement I’ve already made (that @Bruce_Osborne referenced a few posts back). It’s not super easy to see how this can be incorporated into OH as there is no item time linked to schedules, and it’s not something that is regularly requested.
You could try and hack something together, but to implement this properly is quite a lot of work given we’d need to also look at how to integrate it to the OH core system.
Probably compiling the binding yourself with debugging turned on
Good luck with that since @chris the expert is not successful with his dev environment yet.
Me tracking this thread also…
Wouldn’t be possible to implement @akrabisuggestion from the referenced thread?
A switch to receive the ON command when the schedule is activated and a number with the duration…