control_device
ChatGPTControl any device through its advertised capability.fields. Discover list_devices first; send only supported field names and exact types/ranges/enums. No vendor-specific tools. A live execution route is required; queued is not confirmed. Keep request_id for an identical retry; query get_control_result without replaying uncertain writes.
delete_intent_plan
ChatGPTDelete a user-selected shared plan at its current revision, retaining audit history. Never silently delete conflicts.
get_control_result
ChatGPTRead the result of an existing command without resending. Only confirmed=true proves device acceptance.
get_profile
ChatGPTIdentify the authenticated Dropair account. Identity comes from the connection, never tool arguments.
get_schedule
ChatGPTRead the shared Dropair plan, generation and provenance before editing. Bridge plans include delivery receipts. Native thermostat plans are shared Cloud plans, NOT the vendor-native schedule; cloud_saved is never device application. Native execution requires a verified bound Bridge; initial pairing/provisioning uses the App; capable Bridges synchronize subsequent revisions through authenticated MQTT and execute without a phone timer. confirmed means plan installation only; last_occurrence_state reports a separate temperature transition. For Matter thermostats, remind the user to disable and clear the thermostat’s own schedule in the original app or on the device before using Dropair Schedule to avoid conflicts. Missing vendor schedule data does not prove it is cleared. Native entries preserve UUID id (generate a UUID for a new entry); weekday Sunday=1; Bridge day_mask Sunday=bit0. Times use the returned timezone.
get_schedule_result
ChatGPTRead an existing schedule operation without resending. For native thermostats, confirmed=true means exact plan installation on the Bridge; last_occurrence_state separately reports a temperature transition. Queued or stale data does not prove physical execution.
list_devices
ChatGPTList devices, actual observations, supported execution routes and capability limits. A device listed without an execution route is read-only.
list_history_streams
ChatGPTDiscover actual retained history streams before querying; do not guess stream IDs.
list_home_energy_history
ChatGPTDiscover already retained Home energy reports, complementing device sensor streams. Read-only: never contacts a provider or queues a fetch. Continue next_before with the returned binding_id and binding_generation. Report fetch times are not observation coverage.
list_homes
ChatGPTList authorized Dropair Homes and rooms.
list_intent_changes
ChatGPTRead the latest 50 immutable versions of a shared plan, including deleted versions. Restoration uses save_intent_plan at the latest revision as a new change.
list_intent_executions
ChatGPTRead retained trigger and real action results for an automation. Unknown is not success and must not be retried as a new action.
list_intent_executors
ChatGPTDiscover actual resident automation owner IDs and last-seen times before enabling. Online alone does not prove a source or target is supported.
list_intent_plans
ChatGPTRead shared visible Scene and Automation objects before editing; use existing schedule tools for thermostat schedules. Blocked plans are NOT running. Never infer HomeKit synchronization.
list_schedule_changes
ChatGPTRead bounded immutable schedule changes, authenticated actor/source, before/after plans, and delivery results for the current owner. Legacy unaudited changes may be unavailable.
query_device_history
ChatGPTQuery a stream returned by list_history_streams. Sensor streams return original measured temperature/humidity and other supported samples, bounded to 288 time buckets and 31 days; empty buckets are gaps. Thermostat event streams return control/setpoint history, at most seven days and fifty events per page. Missing records are unknown, not zero. Never infer energy or runtime from temperature.
query_home_energy_history
ChatGPTRead a retained energy report discovered by list_home_energy_history. Preserve quality, report interval boundaries and time_semantics_verified. Unknown is not zero. Summaries cover the whole report. Use next_offset with the returned revision to page consistently; never infer consumption from missing power. No collection or provider fetch.
read_device_state
ChatGPTRead actual reported device state and sample times. Stale/missing observations are not current values.
restore_intent_plan
ChatGPTRestore an audited automation revision as a NEW disabled revision. Does not replay historical actions. Use current expected_revision and stable request_id.
restore_schedule
ChatGPTRestore an audited prior generation as a NEW change, keeping history. Requires current expected_generation, stable request_id and expiry. Only act on user-requested restoration. Pending is not device success.
save_intent_plan
ChatGPTSave a user-requested Scene or typed occupancy, property-edge or daily-time Automation as a visible draft, preserving its original intent. Reuse an existing plan_id for corrections, use expected_revision and a stable request_id. Saved does NOT mean enabled or executed. Scenes may be run manually in the foreground App only when its actual local drivers support every target; enable through set_intent_plan_enabled only on explicit user intent; active requires exact resident acknowledgement and supported sources/targets. Property-edge scenes use a pinned same-home scene_id and scene_revision. Discover actual device IDs first; never invent sensor or lighting capabilities. Schedule edits use update_schedule.
set_device_target
ChatGPTSet only requested standard target fields. Use a fresh 32-character lowercase hexadecimal request_id for a new intent; retain it for an identical retry. Lighting fields require an advertised lighting execution route. Pending is not success; use get_control_result. Never resubmit uncertain writes automatically.
set_intent_plan_enabled
ChatGPTEnable or pause a user-selected automation at its current revision. Enabling requires the selected resident execution_owner ID. Deployment pending is not active; a pause may wait for an offline owner acknowledgement. Never enable old drafts in bulk.
update_schedule
ChatGPTSave a user-requested schedule edit. For a Bridge send complete schedules; for a native thermostat send native_plan from get_schedule, preserving untouched entries and timezone. Send exactly one format, expected_generation, stable request_id and expiry. For Matter thermostats, remind users to disable and clear the device’s own schedule first to prevent conflicts; never claim it is cleared without evidence. Native edits request installation on a verified bound Bridge. Initial provisioning uses the paired App; capable Bridges synchronize later edits automatically, while legacy firmware needs foreground App synchronization. Only bridge_installed confirms installation, never all future transitions. Do not claim a queued plan is running. On revision_conflict re-read and ask about conflicting edits; never overwrite blindly. Pending is not applied; query get_schedule_result. Provenance is assigned by the server, not arguments.