Sensors
Peloton
edwork/homeassistant-peloton-sensor · v1.0.0
HACSCloud polling
A platform which allows you to get current and past ride data from Peloton into HomeAssistant
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 |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
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) | 341 (0.05%) |
|---|---|
| GitHub stars | 101 |
| Latest version | 1.0.0 (2026-10-21) |
| Set up in the UI | Yes |
| Maintainers | @edwork |
| License | Apache-2.0 |
Limitations from the README
- Peloton has no public API. The integration uses the same endpoints as
- Updates come from polling, not push, so automations react up to one polling
- Only the latest workout is shown. Earlier workouts are not imported.
- Peloton limits login attempts per IP address. After several failed logins,
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.
