Plugin Name
homebridge-peloton
Link To GitHub Repo
https://github.com/arodbuilds/homebridge-peloton
Plugin Icon (Optional)
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
馃煝 Yes
The plugin successfully installs and does not start unless it is configured.
馃煝 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
馃煝 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
馃煝 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
馃煝 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
馃煝 Yes
More Information
homebridge-peloton turns Peloton workouts into HomeKit sensors so automations can run when a workout starts or ends, for example dimming the lights when a ride begins. It supports several Peloton accounts in one household, with triggers set for one person or anyone in the household (Peloton account) and filtered by class type and device (Bike, Tread, Guide, Apple TV, phone or tablet app). An optional fast polling switch catches workout starts within seconds while keeping standby polling light.
No verified plugin integrates with Peloton, and I found no other Peloton plugin on npm.
I sign in to Peloton directly and store tokens only under the Homebridge storage path (homebridge-peloton/accounts, files 0600). Passwords are optional after the first sign-in. The plugin contacts only Peloton's own sign-in and member API hosts, with no analytics, relay service or third-party client library. Setup happens entirely in the settings page, including a browser sign-in fallback. The only runtime dependency is @homebridge/plugin-ui-utils.
The plugin is not affiliated with Peloton Interactive. The icon is my own dumbbell mark, with no Peloton logo or brand colors.
Plugin Name
homebridge-peloton
Link To GitHub Repo
https://github.com/arodbuilds/homebridge-peloton
Plugin Icon (Optional)
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
馃煝 Yes
The plugin successfully installs and does not start unless it is configured.
馃煝 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
馃煝 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
馃煝 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
馃煝 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
馃煝 Yes
More Information
homebridge-peloton turns Peloton workouts into HomeKit sensors so automations can run when a workout starts or ends, for example dimming the lights when a ride begins. It supports several Peloton accounts in one household, with triggers set for one person or anyone in the household (Peloton account) and filtered by class type and device (Bike, Tread, Guide, Apple TV, phone or tablet app). An optional fast polling switch catches workout starts within seconds while keeping standby polling light.
No verified plugin integrates with Peloton, and I found no other Peloton plugin on npm.
I sign in to Peloton directly and store tokens only under the Homebridge storage path (homebridge-peloton/accounts, files 0600). Passwords are optional after the first sign-in. The plugin contacts only Peloton's own sign-in and member API hosts, with no analytics, relay service or third-party client library. Setup happens entirely in the settings page, including a browser sign-in fallback. The only runtime dependency is @homebridge/plugin-ui-utils.
The plugin is not affiliated with Peloton Interactive. The icon is my own dumbbell mark, with no Peloton logo or brand colors.