You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see some use-cases in being able to manage automations from openHAB:
It would be useful if openHAB could turn these automations on or off.
I imagine exposing each automation as a Switch channel. These channels could be on the Bridge thing, since there would be only once instance of them, and they do not represent any physical devices. This would be similar to automations on the Hunter Douglas PowerView Hub. They should belong to a channel group, and they could be marked as advanced.
The resource type representing these automations is behavior_instance.
Getting all instances: GET https://{{host}}/clip/v2/resource/behavior_instance
(also included in GET https://{{host}}/clip/v2/resource)
I see some use-cases in being able to manage automations from openHAB:
It would be useful if openHAB could turn these automations on or off.
I imagine exposing each automation as a
Switch
channel. These channels could be on the Bridge thing, since there would be only once instance of them, and they do not represent any physical devices. This would be similar to automations on the Hunter Douglas PowerView Hub. They should belong to a channel group, and they could be marked as advanced.The resource type representing these automations is
behavior_instance
.Getting all instances:
GET https://{{host}}/clip/v2/resource/behavior_instance
(also included in
GET https://{{host}}/clip/v2/resource
)Example for enabling an automation:
PUT https://{{host}}/clip/v2/resource/behavior_instance/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Payload:
The text was updated successfully, but these errors were encountered: