You set up an automation that sends a notification to your phone when the front door opens. You leave the house. The door opens behind you (delivery, kid, spouse). You expect a notification. You never get one. The automation seems to be running (the lights it controls did update), but the notification did not reach your phone.
The notification chain
A smart home notification reaches your phone through this chain:
- Event occurs (door opens)
- Hub detects event
- Automation triggers and initiates notification
- Notification is dispatched to the platform’s notification service
- Platform notification service sends to Apple or Google push service
- Push service delivers to your phone
- Your phone shows the notification
Any link in the chain can break.
Verify the automation fired
Did the automation actually fire? If the same automation has other actions that you can observe (lights change, sound plays), check whether those happened. If yes, the automation fired and the notification specifically failed. If no, the automation did not fire and you have a trigger issue.
Check the app’s notification settings
Most likely cause: the smart home app’s notifications are disabled in your phone’s OS settings.
iPhone: Settings, Notifications, scroll to the app, verify Allow Notifications is on, verify Show on Lock Screen and Show in Notification Center are on.
Android: Settings, Apps, the app, Notifications, verify all categories are enabled.
App-side notification settings often have categories (general, security, alerts). Verify the specific category for your automation is enabled.
Battery optimization on Android
Android battery optimization can prevent the smart home app from running in the background, which means it cannot receive notification triggers.
Settings, Battery, Battery Optimization, find the smart home app, set to Not Optimized.
This is a common cause of intermittent notifications: the app works for a while, then Android puts it to sleep, then notifications stop.
Focus or Do Not Disturb modes
If your phone is in Focus mode (iPhone), Do Not Disturb, or a similar quiet mode, notifications may be silenced.
Check your current Focus state. Some Focus modes silence all notifications; others allow specific apps through. Smart home apps may be silenced even in Focus modes you set up months ago.
The notification grouping
If many notifications arrive close together, your phone may group them. The first arrives visibly, subsequent ones go into a stacked group that you may not notice unless you expand it.
If your hub fires multiple events (a door open and motion at the same time), all notifications may be grouped under one banner.
The platform delivery delay
Notification delivery is not instant. Even healthy systems have a 1-5 second delay. If your test was “open the door and immediately check the phone”, the notification may not have arrived yet by the time you looked.
Wait 30 seconds after the trigger before concluding the notification did not arrive.
The cloud incident
If the platform’s notification service is having issues, all notifications from that platform may be delayed or dropped. Check the status page.
Alexa: status.amazon.com
Google Home: status.cloud.google.com
Apple Push Notification Service: apple.com/support/systemstatus
Cloud incidents are usually self-resolving but can affect your setup for hours.
The Wi-Fi versus cellular path
If your phone is on Wi-Fi at home but not connected to the internet (a captive portal you have not logged into, a router with broken DNS), push notifications cannot arrive. Switch to cellular to bypass the broken Wi-Fi.
Phone reboot fixes many issues
If notifications stopped arriving for many apps simultaneously, your phone’s notification service may have hung. Reboot the phone. Notifications usually resume after.
The duplicate device problem
If you have the same smart home account signed in on multiple phones (yours and a tablet), notifications may go to one device but not another, or may be silenced on one because they were read on another.
Verify each device that should receive notifications has the app installed and the account signed in.
The specific user filter
Some automations send notifications to specific household members rather than everyone. If the notification is filtered to your spouse and you are checking your phone, you would not see it.
Check the automation’s notification recipient setting.
The custom message issue
If your automation includes a custom notification message, verify it is well-formed. Some platforms reject notifications with empty messages or with characters that violate their content policies.
Simplify the message to plain text and test if it then arrives.
The cooldown filter
Some platforms silently suppress repeated notifications of the same type within a cooldown period. If your automation has already fired several notifications today, additional ones may be dropped.
Check the platform’s notification quotas. Usually undocumented but discoverable through community discussion.
Test with a manual trigger
To verify the notification path is functional, manually trigger an automation that includes a notification. If the manual trigger sends a notification successfully, the issue is upstream (the trigger condition was not met). If even manual trigger fails to send, the notification path itself is broken.
The IFTTT and third-party path
If your notification goes through IFTTT or another third-party service, that service can be the failure point. Verify the service is healthy and your applet is active.
The privacy-respecting notification
iPhone has a setting that lets notifications arrive but not show content on the lock screen. If you only see banners on lock screen, security-sensitive notifications may be configured to hide content. Open the app to see the actual notification.
When notifications work for some triggers but not others
If notifications from one automation arrive and notifications from another do not, the difference is in the automations themselves. Compare them:
- Same recipient?
- Same notification category?
- Same notification service (some hubs have multiple notification paths)?
The difference identifies the broken path.
The notification test routine worth keeping
Build a standing notification test routine that you can fire on demand: a button or voice command that sends you a notification. Use it whenever you suspect notifications might be broken. It takes thirty seconds to confirm or rule out the notification path.
This eliminates the ambiguity of “is my real notification missing or did the event never fire?” The wider topic of notification fatigue and routing is in our notification fatigue guide.
