Repository navigation
bighelp plugin 3.32.1
3.32.1: instant alerts say why they are off, and the app stops asking until they work
Release 3.32.1.
For people who run hosts
- Instant alerts say why they are off. On some hosts, the plugin could not open its notification storage, so instant alerts (while the app is open) and Quiet Hours stopped working with no reason given. Your alerts still came as normal pushes. The host log and host telemetry now name the cause, for example
notification_private_storage_required, and never a file path. - The app stops asking for what can't work. While the storage can't be opened, the host no longer lists instant alerts and Quiet Hours, so the app uses normal pushes and stops retrying.
- How to fix it: the folder
$HERMES_HOME/plugin-data/loopdy/managed-notificationsmust belong to the user that runs both the gateway and the dashboard. Set the folder to700and its files to600, and don't use a symlink. Then restart the gateway and the dashboard. Details are in docs/NOTIFICATIONS.md. - Updating: update with Settings in the app, or
hermes bighelp update. Then restart the dashboard. Older apps keep working as before.
Changes since 3.32.0
- Instant alerts name why the notification journal can't open, and are skipped until it does (#227).
🤖 Generated with Claude Code