get_schedules
Retrieve schedules configured for a specific node, including trigger conditions and actions. Returns support status and schedule count.
Instructions
Get schedule information for a specific node. Returns the schedules configured for the node if any exist, along with support status.
Response includes:
schedules_supported: Whether the node supports scheduling
schedules: Array of schedule objects with trigger and action details
schedule_count: Number of configured schedules
Each schedule object contains:
id: Unique schedule identifier
name: Human-readable schedule name
enabled: Whether the schedule is active
triggers: Array of trigger conditions (format explained below)
action: What the schedule will do when triggered
TRIGGER FORMAT GUIDE (for understanding schedule responses):
"m": Minutes since midnight (0-1439). Example: 480 = 8:00 AM, 1110 = 6:30 PM
"d": Day bitmap for which days to trigger:
31 = Weekdays (Mon-Fri)
96 = Weekends (Sat-Sun)
127 = Every day
0 = One-time only
Individual days: 1=Mon, 2=Tue, 4=Wed, 8=Thu, 16=Fri, 32=Sat, 64=Sun
"dd": Day of month (1-31)
"mm": Month bitmap (4095 = all months)
"rsec": Relative seconds from creation time
"ts": Exact Unix timestamp when schedule was created or will trigger
Example: {"m": 1110, "d": 31} means "6:30 PM on weekdays"
NOTE: Schedule actions use device type names (like "Light") not display names. See get_node_details for the mapping between device types and their display names.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| node_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |