Security & safety
Bosch Indego Mower
sander1988/Indego · v6.2.0
HACSCloud polling
Home Assistant Custom Component for Bosch Indego Lawn Mower
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
camera | Camera | Needs its own HomeKit Bridge in accessory mode |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
vacuum | Vacuum (as a switch) | |
lawn_mower | Lawn mower (as a switch) | |
button | Button (as a switch) |
What people report
Bosch Indego mowers work through the Bosch cloud and need a SingleKey ID login; the Bosch cloud sometimes blocks or errors. A lawn mower entity was added in 2024.
- Works12
- Not working1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Bosch Indego 1000 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 10C | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 1100 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 1200 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 13C | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 350 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 400 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego 500+ | Works Cloud | Support added via pyIndego updateSaved copyNew version of pyIndego with support for new mower modell Indego 500+ Excerpt saved from GitHub on 2026-10-23. | PR #138 · 2021-07 | |
| Bosch Indego M+ 700 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego S+ 350 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego S+ 400 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego S+ 500 | Works Cloud | Listed as supported mowerSaved copySupported devices: Indego 1000, 1100, 1200; Indego 10C, 13C; Indego 350, 400; Indego S+ 350 (1st & 2nd Gen); Indego S+ 400 (1st & 2nd Gen); Indego S+ 500; Indego M+ 700 (1st & 2nd Gen). Limitations: A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow) Can be disabled/removed after initial setup The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!") Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure … Excerpt saved from the README on 2026-10-23. | README | |
| Bosch Indego mowers (account) | Not working Cloud | 'No mowers found' in Bosch account after cloud API changeSaved copy… [code] So, remove all mower entity, remove component, remove Chrome extension. After that install component, install Chrome extension and while installing Bosch Indego Mower integration got only "No mowers found in this Bosch Indego account!". But there is my mower in Bosh Indego account. In logs still "403 Forbriden" message: `403, message='Forbidden', url=URL('https://api.indego-cloud.iot.bos Excerpt saved from GitHub on 2026-10-23. | Issue #186 · 2023-06 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 206 (0.03%) |
|---|---|
| GitHub stars | 105 |
| Latest version | 6.2.0 (2026-10-09) |
| Set up in the UI | Yes |
| Maintainers | @sander1988, @whylev, @kimzeuner |
| License | Apache-2.0 |
Devices listed in its README
- Indego 1000, 1100, 1200
- Indego 10C, 13C
- Indego 350, 400
- Indego S+ 350 (1st & 2nd Gen)
- Indego S+ 400 (1st & 2nd Gen)
- Indego S+ 500
- Indego M+ 700 (1st & 2nd Gen)
Limitations from the README
- A Chrome extension is required to complete the authentication setup (Bosch SingleKey ID OAuth flow)
- Can be disabled/removed after initial setup
- The Bosch Cloud (Azure) may occasionally block the integration: HTTP 4XX errors ("The connection to the Bosch Indego API failed!")
- Workaround: Try changing the user agent during setup or in Settings → Devices & Services → Bosch Indego Mower → Configure
- HTTP 5XX errors typically indicate temporary Bosch Cloud unavailability (often occurs once daily)
- These are temporary and resolve automatically
- Sending impossible commands (e.g., docking while already docked) may cause temporary HTTP 5XX errors from Bosch
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/sander1988/Indego
- Source code: https://github.com/sander1988/Indego
- Issues: https://github.com/sander1988/Indego/issues
- HACS: https://hacs.xyz
