Troubleshooting¶

Options¶

AI Agents can give very good help these days, even the free one built into Google Search.
Troubleshooting your configuration has the generic Home Assistant advice
Use the Archive to browse the existing notification
Easiest way to do this is using the Studio Code Server app for Home Assistant
Switch on debug mode to get much more detailed archives,
- debug: true can be added to a notification data section, or onto any delivery config
Supernotify has a Diagnostics bundle available from the integration page
Have a look at the What's New, including any breaking changes, and any of the known Issues or Support Discussions.
Use the Tools to call the action directly, listen to events, or view states
Since Supernotify manages Home Assistant contexts, you can see the entire history of a why a notification happened, what the original trigger was, and also downstream things like moving and zooming a camera, all laid out in the state history
Supernotify also has lots of additional actions to enquire about the internals, and offers lots of diagnostic entities
The Debugging a Transport Integration has an example of working through issues with one of the underlying notification transports

If you have a desktop or coding agent, then giving it access to Home Assistant config make it much easier to resolve issues and correct config.
Easiest way of doing that is with the Samba Share app for Home Assistant.
For example, on a Mac you can have the local /Volumes/config reading the main \config directory of Home Assistant.
Caution is due where passwords and other secrets inside the Home Assistant directory could be exposed.
The Assist integration also supports MCP for queries
For more advanced usage, the Home Assistant REPL developer shell can give easy agent access to the APIs, or deep access direct into the live internals and database with live mode. The latter is the sharpest tool available for agents.