Thermostat Schedule: is_override_allowed not being set properly

[byalextran]

based on my testing, when setting is_override_allowed to true on a schedule, if the current time is within the start/end range, the value saves as false (instead of true) even though the response shows it's set as true.

pp schedule = seam.thermostats.schedules.create(
  device_id: ENV['THERMOSTAT_DEVICE_ID'],
  name: 'Current Time Between Start and End',
  climate_preset_key: 'occupied',
  starts_at: DateTime.now - Rational(1, 24), # start one hour before now
  ends_at: DateTime.now + Rational(2, 24), # end two hours after now
  is_override_allowed: true
)

that command returns:

<Seam::Resources::ThermostatSchedule:0x00fcd70
  thermostat_schedule_id="REDACTED-6745-4736-8c08-6887f265c802"
  device_id="REDACTED-d02e-42fe-94ff-f328e7d42529"
  workspace_id="REDACTED-8844-4294-adb3-9989d7c7b90a"
  name="Current Time Between Start and End"
  starts_at=2025-06-14 20:25:52 UTC
  ends_at=2025-06-14 23:25:52 UTC
  climate_preset_key="occupied"
  is_override_allowed=true
  max_override_period_minutes=nil
  created_at=2025-06-14 21:25:52.779 UTC
  errors=[]>

note it shows is_override_allowed=true but when i run:

pp seam.thermostats.schedules.list(device_id: ENV["THERMOSTAT_DEVICE_ID"])

it outputs:

 <Seam::Resources::ThermostatSchedule:0x00106fc0
  thermostat_schedule_id="REDACTED-6745-4736-8c08-6887f265c802"
  device_id="REDACTED-d02e-42fe-94ff-f328e7d42529"
  workspace_id="REDACTED-8844-4294-adb3-9989d7c7b90a"
  name="Current Time Between Start and End"
  starts_at=2025-06-14 20:25:52 UTC
  ends_at=2025-06-14 23:25:52 UTC
  climate_preset_key="occupied"
  is_override_allowed=false
  created_at=2025-06-14 21:25:52.779 UTC
  errors=[]>

note is_override_allowed is now set to false.

if i create a new schedule but set the start and end times as something in the future, the override value is set to true as expected.

[byalextran]

following up on this, everything above was in a sandbox environment. i just tested in a production environment and things worked as expected. so not sure if i've set things up slightly differently in the sandbox vs production environment or something else is going on.

[razor-x]

@byalextran Thanks for the report. We are looking into this. Due to the difference in behavior in the sandbox environment we believe this issue is not directly related to the Ruby SDK.