I mean, I’d like to be able to use openHAB to automate the hub schedules (and letting the hub determine when to turn setpoints on and off etc), rather than the full blown solution of letting openHAB do absolutely everything, which requires the rooms to be in manual mode, with openHAB changing the set points itself. In the former scenario, if openHAB breaks for some reason, I know that the hub is still going to keep to a reasonable schedule, whereas in the latter scenario I could end up with everything stuck in the off state.
As it stands, the binding is perfectly usable (I think) in the full openHAB automation sense in terms of features (other than the timeout bug).
What I ideally want to be able to do is have “scenes” whereby I can set a particular room/house schedule. I.e. if either of us in on annual leave we want the house heated during the day, if one of us is on a late shift, we want the house heated in the morning, if we have guests staying we want the spare room heated etc. All this could be automated from a calendar binding, where it just triggers the correct “scene” and sends the required schedule to the hub.
Sadly not based on the json dumps you’ve provided, and my poking of the android app source. There doesn’t appear to be any OpenTherm specific data there. I wonder if it’s something that drayton will open up in the future, the hub is presumably capable of reading the data from the OpenTherm module…