mirror of
https://github.com/house-of-abbey/GarminHomeAssistant.git
synced 2025-12-15 10:38:16 +00:00
Amended "BatteryReporting" to "BackgroundService". Augmented TroubleShooting.md to remind people how to verify their JSON schema. Amended wording of some of the settings.
1.5 KiB
1.5 KiB
Home | Switches | Actions | Templates | Background Service | Trouble Shooting | Version History
Actions
A simple example using a scene as a `tap`` menu item.
{
"entity": "scene.telly_watching",
"name": "Telly Scene",
"type": "tap",
"tap_action": {
"service": "scene.turn_on"
}
},
Any menu item with an action (tap, template, or toggle), may have a confirmation view added. For consistency this is always done via the tap_action JSON object, even though for a toggle menu item there will only ever be a single field inside. For the toggle menu item, the confirmation is presented on both on and off directions. There is no option for asymmetry, i.e. only in one direction.
"tap_action": {
"confirm": true
}
For example:
{
"entity": "switch.garage_door",
"name": "Garage Door",
"type": "toggle",
"tap_action": {
"confirm": true
}
}
Note that for notify events, you must not supply an entity_id or the API call will fail. There are other examples too.
{
"name": "Message",
"type": "tap",
"tap_action": {
"service": "notify.mobile_app_on_phone",
"data": {
"title": "This is a title",
"message": "This is the message"
},
"confirm": true
}
}