Having switched to a newer API key I found several json field names and value types/formats to have been altered and needed adjusting in my evohomeclient code. Just last week I discovered I missed at least one as a cancel override returned 0°C as the current setpoint (for which the front-end references the schedule because the update in the web portal is not instant). As my own installation does not contain a DHW device I am unable to verify what changes might have occurred to that particular device, particularly the schedule info.
I'd appreciate it very much if somebody could supply me (partial) schedule info of his/her DHW device, using either watchforstock's python library or the schedule backup/restore demo app from my C++ implementation at https://github.com/gordonb3/evohomeclient
I'd appreciate it very much if somebody could supply me (partial) schedule info of his/her DHW device, using either watchforstock's python library or the schedule backup/restore demo app from my C++ implementation at https://github.com/gordonb3/evohomeclient
Comment