Work · Community report
Troubleshoot phone notifications
@Joey_vm_Ware says Muse found and fixed a problem with notifications to their phone, and the screenshot they posted traces stuck Reolink camera alerts to a script calling an old phone notify service. This page shows how to troubleshoot phone notifications on both the phone and the system sending them.
What you can get
- Prepare
Phone model, operating-system version and affected app
- Ask and review
Pick one alert that should have arrived and note when it was triggered and whether it ever showed up.
- Check the result
A reproducible notification test and change log, rather than an undocumented claim that all alerts are fixed.
The source case
@Joey_vm_Ware reports working through phone-notification problems with Muse and says it found and fixed the issue. The attached screenshot shows the agent's own account: Reolink camera alerts were not arriving because a watcher script still called an old, deregistered phone notify service, and it changed the script. The post does not name the phone model, operating system or platform, or show a test of the fix.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
This is why I like @Muse so far. This is true AI self help. I was working some issues with notifications to my phone and it found the issue for me and fixed it. https://t.co/PlJxVLuTgz
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Phone model, operating-system version and affected app, An example of a notification that should have arrived, Current notification and quiet-mode settings. Source community report, checked 2026-10-08.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- Phone model, operating-system version and affected app
- An example of a notification that should have arrived
- Current notification and quiet-mode settings
How to try it
Editorial, not from the source
- Pick one alert that should have arrived and note when it was triggered and whether it ever showed up.
- Check the phone side: the app's notification permission, Focus or Do Not Disturb modes, and on Android, battery optimisation for that app.
- Check the sending side: the app's own alert settings, or the automation or script that sends the notification, and whether it targets the current device.
- Approve one change at a time, and keep a note of what was changed.
- Send a test alert and confirm it arrives once, on time, then watch the next real one.
What the screenshot shows
@Joey_vm_Ware's post is short: they were working through issues with notifications to their phone, and Muse found the issue and fixed it. The screenshot attached to the post carries the detail. It shows a message reporting that two Reolink motion alerts from around 8:40 got stuck retrying because a watcher script still called an old, deregistered phone notify service. The message says the dead call was removed, both alerts reprocessed, a gallery sensor was updating again, and duplicate notifications came from a manual run overlapping the service loop. It ends 'Nothing you need to do.' By that message's account, the fault was in the system sending to the phone, not the phone itself.
Two halves: the phone and the sender
A missing notification can fail on either side. On the phone, check the app's notification permission, Focus or Do Not Disturb schedules, notification summaries on iPhone, and battery optimisation on Android, which can stop background apps receiving alerts. On the sending side, check the app's own alert settings or, in a home-automation setup, the automation that sends the alert. In systems such as Home Assistant, a phone's notify service is named after the device, so reinstalling the companion app or renaming the phone can leave automations calling a service that no longer exists. That matches the kind of fault in the screenshot, though the post does not name the platform.
Prove the fix
'Fixed' should mean a test alert arrives once and on time, and the next real one does too. Ask for a log of what was changed, such as which script line was removed, so it can be undone. Duplicates point to two senders, such as a manual run and a scheduled loop, or two automations for the same event. An agent that can edit your automations can also break them, so approve changes before they are made, even if the result is the 'Nothing you need to do' kind of message.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- Device, operating system, affected platform and a verification test are not given; the script change is known only from the agent's own message in the screenshot.
- The screenshot was read for this guide, but the persistence of the reported fix was not checked.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
If it goes wrong
Editorial, not from the source
- Alerts stopped after a new phone or app reinstall
- Check whether automations or scripts still target the old device's notify service, and point them at the current one.
- Alerts arrive late or in a batch
- Check Focus modes, notification summaries and, on Android, battery optimisation for the app.
- The same alert arrives twice
- Look for two senders: duplicate automations, or a manual run overlapping a scheduled loop.
Common questions
Can Muse fix phone notification problems?
One user says it found and fixed theirs. The screenshot shows the fix was to a script sending camera alerts, not a phone setting.
Why do my camera alerts stop reaching my phone?
Common causes are phone settings (permissions, Focus modes, battery limits) or the sender targeting an old device after an app reinstall or phone change.
Why am I getting duplicate notifications?
Usually two things send the same alert, such as two automations or a manual run overlapping a scheduled one, as the screenshot describes.
What does the source not show?
The phone, the operating system, the platform running the script, and whether the fix held.
Next
More in Work
Get recurring task recommendations — ask your own agent to check for relevant updates.