This part of the troubleshooting only tells you what to look out for. but doesn't tell you how to solve it. How do I solve it? I have been using AlertTicker-Card for quite a some time (sometimes you just don't realize things like push notifications did not work properly for a few months) and I didn't notice that I needed this automation to exist. Once I realized that, I read the troubleshooting section, opened up my automations and sure enough, there are no AlertTicker automations created there. What is my next step? I tried uninstalling and reinstalling and recreating my alerts from scratch with push notifications enabled and still don't see the automation created. |
Replies: 1 comment
|
Hi @thewan056 — I checked the code carefully and I owe you a correction. The card does not create any server-side automations. There are no How push notifications actually work:
This is a fundamental limitation of browser-side Lovelace cards — they have no way to run code when the browser is closed. To get push notifications when the browser is closed, you need a native HA automation: alias: My alert push notification
trigger:
- platform: state
entity_id: binary_sensor.your_entity
to: "on"
action:
- service: notify.your_notify_service
data:
title: "Alert"
message: "Your alert message"The card's built-in Sorry for any confusion the old documentation may have caused! |

Hi @thewan056 — I checked the code carefully and I owe you a correction.
The card does not create any server-side automations. There are no
[AlertTicker] TTSor[AlertTicker] Push Notificationsautomations, and no REST API calls to HA's automation engine. That description — wherever you read it — was inaccurate, and it no longer appears in the current README.How push notifications actually work:
The card calls
notify.<your_service>directly from your browser using the Lovelace frontend API (callService). This means:This i…