Create automation rule

Creates a new automation rule. Set rule_type to 'trigger' for condition-based rules or 'schedule' for time-based rules. Each action's params object is action-specific JSON; for 'Change Temperature Control' it accepts the ATM bucket (enabled, startupMinutes, postRampMinutes, minimumProfile, maximumProfile, temperatureBuffer) plus the watt floor minimumPower (0 to remove an existing floor, otherwise a whole number of watts from 500 to 8000; the snake_case spelling minimum_power is rejected here), plus chip and water-inlet thresholds (e.g. chipHotTemperature, chipTargetTemperature, chipDangerousTemperature, waterInletHotTemperature, waterInletStartupTemperature, waterInletDangerousTemperature).

curl -X POST "https://example.com/v2/commander/automation/rules" \  -H "Content-Type: application/json" \  -d '{    "name": "Miner Overheat Alert",    "rule_type": "trigger",    "site_ids": [      "ab580781-02e2-4a18-ac1b-8fc9be2f4ad4"    ],    "filter": {},    "actions": [      {        "action_type": "Reboot"      }    ]  }'

{  "id": "r-a1b2c3d4-e5f6-7890-abcd-ef1234567890",  "url": "/v2/commander/automation/rules/r-a1b2c3d4-e5f6-7890-abcd-ef1234567890"}

{  "statusCode": 400,  "code": "FST_ERR_VALIDATION",  "error": "Bad Request",  "message": "body/end_date Required"}

{  "statusCode": 400,  "code": "FST_ERR_VALIDATION",  "error": "Bad Request",  "message": "body/end_date Required"}