Now I can retrieve what I believe to be schedule data, my next challenge is to decode it. The first 14 nibbles look to be very similar to the payload of the request. Based on the Evohome_schedule_backup.py on GitHub, I think these 14 nibbles should be removed and the remaining data is the useful schedule data. Can anyone confirm this? It's the part at the start of the data that looks like '00200008000100'.