main

v0.1.8

Fixed

• set_reservation_custom_field now always sends the value as a string, since Guesty rejects the write when it's sent as a number — confirmed via testing that a numeric access code was being silently rejected until quoted

Improved

• Guesty API errors now include both the payload that was sent and Guesty's actual response body, not just the bare HTTP status. Applies everywhere the integration talks to Guesty (all three services, plus every sensor/coordinator poll) since it's fixed centrally in async_request. A failed write used to just say 400, message='Bad Request'; it now shows what was sent and what Guesty said back, so future failures are diagnosable from the automation trace alone