Skip to content

feat: push notifications for messaging events - #231

Open
andig wants to merge 4 commits into
mainfrom
feat/push-notifications
Open

feat: push notifications for messaging events#231
andig wants to merge 4 commits into
mainfrom
feat/push-notifications

Conversation

@andig

@andig andig commented Jul 18, 2026

Copy link
Copy Markdown
Member

fixes #16, pairs with evcc-io/evcc#31910, replaces #230

Real push notifications for evcc messaging events — delivered via APNs/FCM through the Expo push service, so they arrive with the app closed or in the background (addressing the feedback on #230).

  • per-server "Send notifications to this device" checkbox in the server form; enabling requests notification permission, fetches the Expo push token and registers it with that server (POST /api/push/token)
  • disabling the checkbox or deleting the server unregisters the token
  • multiple servers register independently; message delivery itself happens server-side (see paired evcc PR)
  • no in-app display logic needed — the OS shows the notification; foreground messages show as banner

TODO

  • upload APNs key and FCM service account to the Expo project (EAS credentials) — required before pushes actually deliver
  • F-Droid builds have no Play Services; token fetch fails gracefully but notifications won't work there

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
andig and others added 3 commits July 18, 2026 16:11
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Push notifications bei Ladestart/Ende/usw.

1 participant