- \n
- When the iron smart plug turns on, turns on a key on the NFC Deck<\/li>\n\n\n\n
- When the iron smart plug turns off, turns off that key on the NFC Deck<\/li>\n\n\n\n
- Hitting the key turns off the smart plug<\/li>\n<\/ul>\n\n\n\n
The abstract goal in this first use case is to notify when some action may need to be taken, that way the key can be activated to take the action.<\/p>\n\n\n\n
We’re going to start with two triggers in our automation. Each of these will be given a different trigger ID. One trigger for the smart plug turning on and a second trigger for it turning off.<\/p>\n\n\n\n
![\"\"](\"https:\/\/lab.rapternet.us\/wp-content\/uploads\/2024\/01\/image-8.png\")
Triggers<\/figcaption><\/figure>\n\n\n\n Now that we have our triggers with IDs setup, we want to add a choose block in the automation actions. This choose block will have two options, one for each trigger using the trigger ID. Then each of those options will have one action to toggle my notification LED.<\/p>\n\n\n\n
![\"\"](\"https:\/\/lab.rapternet.us\/wp-content\/uploads\/2024\/01\/image-9.png\")
Iron On Trigger<\/figcaption><\/figure>\n\n\n\n The on trigger is more interesting as it turns on the notification light and changes the color in one nice little action using the color name. This is using the light turn on service which let’s us change settings while turning on the LED.<\/p>\n\n\n\n
![\"\"](\"https:\/\/lab.rapternet.us\/wp-content\/uploads\/2024\/01\/image-10.png\")
Iron On Trigger Action<\/figcaption><\/figure>\n\n\n\n The off trigger and action are straight forward, just call the light turn off service.<\/p>\n\n\n\n
![\"\"](\"https:\/\/lab.rapternet.us\/wp-content\/uploads\/2024\/01\/image-11.png\")
Iron Off Trigger<\/figcaption><\/figure>\n\n\n\n This automation built in home assistant becomes the following YAML.<\/p>\n\n\n\n
- id: '1705775063628'
alias: Master Bedroom Keypad Lighting
description: ''
trigger:
- platform: device
type: turned_on
device_id: 0914cd9c0ad011cc9c86daa3f2c4f2f0
entity_id: 1f6d2ca4d98a314408d8bb5cdfdbd5d6
domain: switch
id: Iron On
- platform: device
type: turned_off
device_id: 0914cd9c0ad011cc9c86daa3f2c4f2f0
entity_id: 1f6d2ca4d98a314408d8bb5cdfdbd5d6
domain: switch
id: Iron Off
condition: []
action:
- choose:
- conditions:
- condition: trigger
id:
- Iron On
sequence:
- service: light.turn_on
metadata: {}
data:
color_name: red
target:
entity_id: light.esphome_web_75e790_key_4_light
- conditions:
- condition: trigger
id:
- Iron Off
sequence:
- service: light.turn_off
metadata: {}
data: {}
target:
entity_id: light.esphome_web_75e790_key_4_light
<\/pre>\n\n\n\nConclusion<\/h2>\n\n\n\n
This little automation works well and was a good way to get using the new features of the NFCDeck. I’m happy with the simple results and easy to use automations around my house and this is just another way to make use of them.<\/p>\n\n\n\n
![\"\"](\"https:\/\/lab.rapternet.us\/wp-content\/uploads\/2024\/01\/pxl_20240123_0340374256898576259545801098-771x1024.jpg\")
Notification Light Active <\/figcaption><\/figure>\n\n\n\n Additional Reading on the NFC Deck<\/h2>\n\n\n\n
- \n
- NFC Deck Version 1<\/a><\/li>\n\n\n\n
- EspDeck Version 1<\/a><\/li>\n\n\n\n
- EspDeck Version 2<\/a><\/li>\n\n\n\n
- EspDeck Version 3<\/a><\/li>\n\n\n\n
- EspDeck Automations<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
Since I just finished my new EspDeck model that has backlit keys. I always intended on using these for notifying me of some state in my house so I can take action on it, ideally using the EspDeck itself. This is the first use case I had for the features so I’ll be implementing it … <\/p>\n
- EspDeck Version 1<\/a><\/li>\n\n\n\n
- NFC Deck Version 1<\/a><\/li>\n\n\n\n