Alarm integration with Home Assistant

[SilverballSlayer]

First and foremost, thank you!! This is awesome!! I have a question about Home Assistant and if a few things are possible.

First, I want to tie some home automations to the morning alarm. I can see "next alarm", but that looks to update with snooze. Is there a "next schedule alarm" or something like that? My use case is that I want to do things prior to the actual alarm. Like 30 minutes before, start slowly turning my bedroom lights on, or 5 minutes before, turn on my coffee maker.

Second, is there a way to remotely turn off alarms altogether? In other words, say I have a Mon->Fri 5:00 AM alarm. But I leave home for a few days for work and forget to turn off the alarm. Is there any entity in Home Assistant that will let me disable the morning alarms remotely?

Thanks again, I just got it installed tonight and already am having fun playing with it.

[SCHibbard]

@HuskerMinion can probably answer better than I, but I have been playing with similar ideas. With List alarms and timers, you can see all the timers currently on a device, and within it, next: will show you the time it will next go off. However, that data is not stored in Home Assistant, only the device. I created sensors in configuration.yaml that do that periodically so I can access and trigger off the data in HA. @HuskerMinion just added a new feature to Techo5 in #317 that gives the ability to turn an alarm off without deleting it. I use that in a dashboard that mimic's Amazon's alarms page to manage alarms on all devices (add, delete, turn on & off). Let me know if you need sample code & I can try to clean it up in the morning (it is still a work in progress).
---Scott---

[HuskerMinion]

Thank you, that means so much! Welcome.

Next alarm: right now it follows a snooze, like you saw. Scott's way works today: list_alarms gives each alarm's next time. I'm adding a sensor for the scheduled time that ignores snoozes, so you can trigger "30 minutes before" from it directly, and a switch that turns all of a device's alarms off and back on, for trips like yours. I'll post here when they're in.

Turning one alarm off: alarm_turn_off (by time or label) or alarm_turn_off_id switches an alarm off without deleting it, and alarm_turn_on brings it back. They're in actions.md.

Thanks for helping out, Scott!

[SilverballSlayer]

Thank you both so much for the replies! Looks like I can do what I'm trying to accomplish, which was my main driver for this project. I can't thank you enough. I've been reading about the best way to do this for a month and landed on TECHO5. Loving it!

Once I implement the above, I'll tie my lighting into the alarms. Coffee maker into the alarms. Who knows what else. Likely geofence stuff, like disable the morning alarm if I'm not home. Odds are I'm just scraping the surface of the rabbit hole. So much fun!

Thanks again!!

[HuskerMinion]

Thank you, glad it's working for you! Both are in v1.6.15:

• Next scheduled alarm (sensor.<node>_next_scheduled_alarm): a timestamp for the next alarm, leaving out snoozes and reminders. A time trigger with offset: "-00:30:00" on it runs 30 minutes before. docs/actions.md has the example.
• Alarms on (switch.<node>_alarms_on): turns every alarm off for a trip and brings back the ones that were on. Reminders still go off, and setting a new alarm while it's off turns alarms back on.

The geofence idea fits that switch well. Have fun with it.

[SCHibbard]

FYI: the following in the template: section of configuration.yaml will create a sensor that is updated every 5 seconds with the current alarms on a techo device. One needs to be added for each techo device you want to monitor. It slips the friendly name of the device into each record, as I had trouble getting the custom flex-table-card dashboard card to add a fixed field from outside a record. Three items need to be edited for use, described in comments at top. After it is installed and HA is restarted, you should see the new sensors in Settings > Tools > States by filtering on "alarms_list".

    # Sensors for techo5 alarms list dashboard.
    # Setup: set variables "techo5" to device name & 'location' to a friendly name, and sensor's 'unique_id' to include device name.
  - trigger:
    - platform: time_pattern
      seconds: "/5" # Updates the table every 5 seconds
    variables:
      techo5: <DEVICE_NAME>
      location: <FRIENDLY_NAME>
      sensor_name: "{{ techo5 }}_alarms_list"
    action:
        action: "esphome.{{ techo5 }}_alarms_list"
        response_variable:
          alarm_data   
    sensor:
      - name: "{{ sensor_name }}"
        unique_id: <DEVICE_NAME>_alarms_list
        state: "{{ alarm_data.alarms | length if alarm_data.alarms is defined else 'Unknown' }}"
        attributes:
          alarms: |-
            {% set ns = namespace(updated=[]) %}
            {% if alarm_data is iterable %}
              {% for item in alarm_data.alarms %}
                {% set new_item = dict(item, **{'device': techo5, 'location': location })%}
                {% set ns.updated = ns.updated + [new_item] %}
              {% endfor %}
            {% endif %}
            {{ ns.updated }}

[HuskerMinion]

Thanks for sharing this, a nice way to get every alarm into a dashboard table.

[SilverballSlayer]

Again, a huge thank you! For the code changes, and just for this project in general. I keep getting farther down the rabbit hole. My Google calendar is integrated. I have a highly custom alarm system - now when it triggers via frigate for a camera, it pops up the camera on the display. So super cool!

I do have one question. I'm playing with the Dashboard ("Drawn on the device") and the text for my tiles isn't wrapping. For instance, "Ceiling F..." is "Ceiling Fan". Should that text wrap? Maybe I'm doing something wrong....

[HuskerMinion]

Thanks so much, that's a great setup with the Frigate pop-up. The tile names wrap now: v1.6.17, out today, draws a long name smaller and then on two lines before it cuts anything. There's also a new Dashboard tile layout setting with a Name below choice that gives names the whole width of the tile.

[SilverballSlayer]

Updated and it's working great, thank you!!!!!

[HuskerMinion]

Glad it's working, thanks for letting me know!