Looking for Homey instead of Home Assistant and/or if you need more detailed information on how to get your credentials, @wdool created Stromer for Homey using information in this repo but has extensive information on how to connect. Very nice that Homey users can now also track and automate their favorite bike(s).
Home Assistant 2026.10 or newer. If you are on an older Home Assistant version, use v0.4.3 or earlier.
A Stromer bike that has "Mobile phone network" connectivity. This excludes the standard ST1 without the "Upgrade" (see Stromer Connectivity). ST2, ST3, ST5 and ST7 come standard with the required connectivity.
See How to install? below if you prefer to add the repository manually.
The setup flow asks for:
- Your Stromer username (i.e. the e-mail address you use in the Stromer app)
- Your Stromer password
- The Client ID of the Stromer app
- The Client Secret of the Stromer app, optional: only needed for older (APIv3) client IDs, leave it empty if your client ID starts with
4P
Stromer does not offer a public API or a way to request API credentials. The official Stromer app logs in using its own (app-specific) Client ID, and this integration has to present that same Client ID to talk to the Stromer API. It is not shown anywhere in the app or on the Stromer website.
The way to retrieve it is to intercept the traffic between the Stromer app on your phone and the Stromer API using a man-in-the-middle (MITM) proxy such as mitmproxy and read the Client ID (and Secret, if present) from the app's login/authorization requests. If you don't know how to do this or what it implies, ask someone who can help you with it or do not use this integration. Stromer for Homey has a detailed walkthrough, and helpful users can be found on the Dutch Stromer forum.
In the current state it retrieves bike, status and position from the API every 10 minutes.
There is an early implementation on toggling data on your bike, light and lock can be adjusted.
Do note that the switches do not immediately reflect the status (i.e. they will when you toggle them, but switch back quickly).
After your 'switch' command we do request an API update to check on the status, pending that update the switch might toggle back-n-forth some time.
Depending on your bike type the Light switch will switch on/off or between 'dim and bright'.
As with the switch implementation a button is added to reset your trip_data.
Multi-bike support (see #81 / #82 for details). The config-flow will detect if you have one or multiple bikes. If you have one, you can only select it (obviously). When multiple bikes are in the same account, repeat the 'add integration' for each bike, selecting the other bike(s) on each iteration.
Basically you'll have to trigger (through automations) the updates yourself. But it's the correct way to learn Home Assistant and the method shown below also saves some API calls to Stromer. Basically this will determine if the bike is unlocked and if so start frequent updates. The example will also show you how to add a button to immediately start the more frequent updates. And yes, I'm aware we can make blueprints of this, but I'll leave that for now until we have a broader user base and properly tested integration.
-
-
Create a
switch(i.e. input-boolean) namedStromer Frequent Updates(i.e. becominginput_boolean.stromer_frequent_updates. Feel free to name it otherwise, but this is what will be referred to below. -
-
Create a new automation, click on the right-top three dots and select 'Edit as YAML'. Don't worry, most of it you will be able to use the visual editor for, it's just that pasting is much easier this way. Do note that you'll have to change the
stromerpart of the bike (or after pasting, select the three dots, go back to visual editor and pick the correct entity).
alias: Stromer cancel updates when locked
description: ''
triggers:
- trigger: state
entity_id: binary_sensor.stromer_bike_lock
to: 'on'
- trigger: template
value_template: >-
{{ has_value('sensor.stromer_last_status_push') and now().timestamp() - as_timestamp(states('sensor.stromer_last_status_push')) > 600 }}
conditions: []
actions:
- action: homeassistant.turn_off
data: {}
target:
entity_id: input_boolean.stromer_frequent_updates
mode: single- Create another automation, same process as above
alias: Stromer start updates when unlocked
description: ''
triggers:
- trigger: state
entity_id: binary_sensor.stromer_bike_lock
to: 'off'
- trigger: template
value_template: >-
{{ has_value('sensor.stromer_last_status_push') and now().timestamp() - as_timestamp(states('sensor.stromer_last_status_push')) > 600 }}
conditions: []
actions:
- action: homeassistant.turn_on
data: {}
target:
entity_id: input_boolean.stromer_frequent_updates
mode: single- And the final one, actually calling the updates (example every 30 seconds). We'll only point to bike speed, but it will update the other sensors
alias: Stromer update sensors
description: ''
triggers:
- trigger: time_pattern
seconds: /30
conditions:
- condition: state
entity_id: input_boolean.stromer_frequent_updates
state: 'on'
actions:
- action: homeassistant.update_entity
data: {}
target:
entity_id: sensor.stromer_bike_speed
mode: single- Final step is adding a button to your dashboard if you want to trigger updates right now. Do note that your bike must be unlocked before triggering, otherwise it will 'cancel itself' :) In a dashboard, click the three buttons right top, and add a
button-card, throughview code editorpaste, switch back to visual editor and customize the below to your taste. Again pointing at bike speed but it will refresh if the bike is unlocked and trigger the updates helper.
show_name: true
show_icon: true
type: button
tap_action:
action: perform-action
perform_action: homeassistant.update_entity
data: {}
target:
entity_id: sensor.stromer_bike_speed
entity: ''
hold_action:
action: none
name: Start Stromer updates
icon: mdi:bike
show_state: falseEven though available does not mean it's stable yet, the HA part is solid but the class used to interact with the API is in need of improvement (e.g. better overall handling). This might also warrant having the class available as a module from pypi.
- Location
- It inherits zones, but you could also plot your location on a map
- Sensors
- Like motor and battery temperature
- Two speed sensors:
Bike speed(reported by the bike) andGPS speed(derived from the position, so it may show small values while parked)
- Binary Sensors
- Light-status and Omni-lock status and theft status
- Use HACS
- Navigate to the
Integrationspage and use the three-dots icon on the top right to add a custom repository. - Use the link to this page as the URL and select 'Integrations' as the category.
- Look for
StromerinIntegrationsand install it!
For each bike you will have to add it as an integration. Do note that you first have to retrieve your Client ID (see Why do I need a Client ID (and MITM)?).
- In Home Assistant go to
Settings->Devices & services - Hit the
Add integrationbutton in the right lower corner - Search or browse for 'Stromer e-bike' and click it
- Enter your e-mail address, password and the Client ID (and Secret, if needed)
If you change your Stromer e-mail address, password or client ID/Secret, use Reconfigure from the three-dots menu of the integration entry. If the Stromer API rejects your credentials, Home Assistant will ask you to re-authenticate.
You can adjust these in Settings -> Devices & services -> Entities (e.g. https://{Your HA address}/config/entities)
Just click on the device and adjust accordingly!
Please note that you can also click the cogwheel right top corner to rename all entities of a device at once.
I'm on Discord and used to frequent the Dutch Stromer forum more often, but feel free to add a Bug through the Issues tab on Github.
It works on my bike and Home Assistant installation :) Let me know if it works on yours!
