I've noticed that with the Alexa.ThermostatController Interface, a hold duration is sent correctly by Alexa in the directive for SetTargetTemperature, but not for AdjustTargetTemperature. The example utterances dictate that it should work then too. ('Alexa, make it warmer in here until 10 PM'). The endpoint has the supportsScheduling field set to True in the Discovery.Response so that's not the culprit. Is this anomaly a documentation error or a bug?
Also, the hold duration is supposed to be specified in the directive as a timeinterval object with start and duration values. I'm only seeing duration in the directive and no start field. Not the end of the world because the start is assumed to be now anyway, but still wrong. Same question: Is this a documentation error or a bug?