Repository navigation
Guide Security
Settings → Sicherheit shows in one place how your account is protected. Only you see it: an administrator of your household cannot open your sessions here.
Five gauges at the top, each a jump to its part:
- Password: set or not, and when you last changed it (unknown for passwords set before this page existed). Change it in your profile.
- Passkeys: how many you have. Add, rename and remove them right below, see Signing in with a passkey.
- Sign-in services: GitHub and Apple, if linked, see GitHub and Apple. MowDeck does not let you unlink the last way to sign in.
- Access tokens: your active personal access tokens for scripts, see Scripting MowDeck. You can revoke one right here.
- Devices: where you are signed in now.
Every browser and every app installation you are signed in with is one row: the browser and system (for example Firefox on Windows or MowDeck app on iOS), where it signed in from, how (password, passkey, GitHub, Apple), since when and when it was last active. This device marks the one you are using.
MowDeck asks no location service. The address is shortened to its network (203.0.113.x); addresses of your own network are shown as home network.
- Sign out ends one device. Sign out everywhere else ends all but this one.
- Both ask you to confirm with your passkey or password first (Confirming critical actions), so somebody who got hold of a signed-in device cannot throw you out.
- A signed-out device cannot renew its access. MowDeck's account functions refuse it at once; the mower functions accept the access it already has for at most 10 more minutes, then it has to sign in again.
When somebody signs in to your account from a browser or app MowDeck has not seen for you before, you get a notification Neue Anmeldung bei MowDeck / New sign-in to MowDeck: in the app's inbox and as a push message on the devices you set up for notifications, also during your quiet hours. It names the browser and system and the shortened address.
Was it not you? Tap the notification: the security page opens with that sign-in flagged. Sign this device out, then change your password.
Good to know:
- Your very first sign-in, and your first one after this feature arrived, never alert: there was no device to compare with.
- A device is recognised by a random id in a cookie, not by fingerprinting. A private window or deleted cookies make the same browser a new device again.
- The app taking over a sign-in you just made in the browser does not alert again.
- You can turn the alerts off with the switch on the security page. Turning them off asks for a confirmation, so a stolen session cannot silence them.
The last 30 days of what happened to your account, newest first: sign-ins and failed sign-ins, new devices, signed-out devices, passkeys, linked services, password changes and access tokens. Failed attempts are marked red, things worth a look amber.
Mirrored from docs/guides/security.md at commit 39f6a7b11a834ca2c25cb9bc29734489243fce8d. Edit the file in the repository, not this wiki page.
Mirrored from the docs/ directory at commit 39f6a7b11a834ca2c25cb9bc29734489243fce8d. Edit the files in the repository, not this wiki.
MowDeck documentation
- Home
- Phases
- Architecture
-
Decisions (ADR)
- Architecture decisions
- ADR 0001: OpenFGA instead of self-built authorization
- ADR 0002: Self-built Identity service in FastAPI instead of Keycloak or Zitadel
- ADR 0003: SvelteKit for the web app
- ADR 0004: Monorepo with a uv workspace
- ADR 0005: AGPL-3.0 for services and apps, Apache-2.0 for libraries
- ADR 0006: PostgreSQL for all persistence, no SQLite
- ADR 0007: NATS JetStream as event bus
- ADR 0008: Traefik as gateway
- ADR 0009: Command and event envelopes, subject naming and de-duplication
- ADR 0010: Python 3.13 for all services and libraries
- ADR 0011: Separate GPL-3.0 package for the PyMammotion adapter
- ADR 0012: Mower control interface and safety rules
- ADR 0013: Device-Gateway registry, sharding and per-mower concurrency
- ADR 0014: Authorization model, tuple ownership and the mowdeck-authz client
- ADR 0015: Tokens, sessions and key rotation
- ADR 0016: Fleet commands and authorization per command kind
- ADR 0017: Telemetry storage and retention
- ADR 0018: Realtime WebSocket protocol
- ADR 0019: Mammotion adapter transports, manual drive and secrets
- ADR 0020: Web app architecture
- ADR 0021: Browser authentication flow
- ADR 0022: Notifications: rules, recipients and delivery
- ADR 0023: Map rendering and projection
- ADR 0024: Scheduler: recurrence, rain pause and command issuing
- ADR 0025: Home Assistant integration as a pure API client
- ADR 0026: Manual drive channel over the Realtime WebSocket
- ADR 0027: Health history and theft alarm
- ADR 0028: Entitlements: plans as data and enforcement
- ADR 0029: Helm chart and release pipeline
- ADR 0030: Mowing patterns as plug-ins and the Planner
- ADR 0031: Billing with a Stripe adapter
- ADR 0032: Live camera over Agora, joined directly by the browser
- ADR 0033: Vision-assisted recovery with human approval
- ADR 0034: Linked cloud accounts and device discovery
- ADR 0035: Server-side camera frames and automatic AI analysis on errors
- ADR 0036: Native app shells with Capacitor, loading the web app from the server
- ADR 0037: Camera panorama calibration in the browser, with the AI supplying points only
- ADR 0038: Dual link per mower and firmware updates
- ADR 0039: Spot mowing by MowDeck-driven paths
- ADR 0040: Link heartbeat for online status
- ADR 0041: Spot runs from the dock: undock, transit and return
- ADR 0042: Drive calibration
- ADR 0043: Turn styles
- ADR 0044: Drive view with camera
- ADR 0045: Camera relay
- ADR 0046: Device settings as capabilities
- ADR 0047: The RTK base station as a Fleet device
- ADR 0048: Maintenance commands
- ADR 0049: Manual driving over the Mammotion cloud
- ADR 0050: Passkeys and the app login hand-off
- ADR 0051: Sign in with GitHub
- ADR 0052: Sign in with Apple
- ADR 0053: Retention and downsampling of the position track
- ADR 0054: Aerial photo under the mower map
- ADR 0055: Deploy maintenance window
- ADR 0056: Camera photo in push notifications for errors and theft alarms
- ADR 0057: Step-up re-authentication for critical actions
- ADR 0058: Theft tracking mode
- ADR 0059: iOS widgets and the mowing Live Activity
- ADR 0060: Apple Watch app
- ADR 0061: Mowing angle rotation
- ADR 0062: Setup tour for new users
- ADR 0063: Matter server (mowers in Apple Home and Google Home)
- ADR 0064: Personal access tokens and the public API documentation
- ADR 0065: Security center and new-login alerts
- ADR 0066: Cloud provider plugins and adapters for more vendors
- ADR 0067: Error code lexicon, provider independent
- ADR 0068: Public demo mode
-
Development
- Getting started
- Service template
- Shared libraries
- Cloud providers: adding a vendor
- Adding an error lexicon for a vendor
- Design: identity and authorization
- Design: fleet, telemetry, realtime
- Design: web app
- Web app
- Home Assistant integration
- Camera source bridge protocol
- Fuzzing and property-based tests
- GitHub wiki mirror
-
Operations
- Operating the Compose stack
- Operating MowDeck on Kubernetes (Helm)
- Building the Bluetooth bridge (ESPHome on a XIAO ESP32-S3)
- Releases
- Billing operations
- Telemetry: retention and position downsampling
- iPhone and Android apps
- Passkeys
- Sign in with GitHub
- Aerial photo under the map
- Sign in with Apple
- Theft tracking mode
- Matter server
- Source code offer (AGPL-3.0 section 13)
- Public demo
- Spikes
-
Guides
- Guides
- ESP32 bridge: purchase and setup
- Signing in with a passkey
- Signing in with GitHub
- Error codes in plain words
- Aerial photo under the map
- Signing in with Apple
- Confirming critical actions
- Your security page
- iPhone widgets and the mowing Live Activity
- Apple Watch
- The setup tour
- Apple Home and Google Home (Matter)
- Scripting MowDeck
- API reference
- Original plan (German)