What's new
What changed in Zero Logs Analyzer: pages you can open, numbers you read on them, files you can download, and the controls you use to publish or withhold your own data. Newest first.
Work that changes nothing you can see (parser internals, tests, infrastructure) is recorded in the engineering changelog in the source repository instead. Nothing appears on this page unless it was written for riders deliberately.
The Android app has its own version numbers and its own release notes: the newest is 0.37.1, released 15 November 2026.
You are on version 4.37.3, marked below.
What the parser decodes
Across every kind of log, 98.3% of records are read (71.5% completely) and 0.8% are of a type nobody decodes yet.
Older Zeros (SDS/FX)
Newer Zeros (FST)
Measured 21 November 2026.
How these are measured
- Fully decoded:
- every field of the record is identified and shown; a message is read to its end.
- Partly decoded:
- the record is understood, but it holds a value nobody has named yet, or a value was held back because the file overwrote it or it was impossible.
- Unknown type:
- not understood, or not accepted by its decoder.
- Corrupted:
- destroyed in the file itself. A record we merely do not understand never counts here.
- Header:
- files whose identifying details were all read from the file, never from its name. On the main board those are VIN, model, board and firmware revision; on the battery, BMS serial and pack serial. The battery serials and the older main board's model and revisions are not read yet.
- Fields, not bytes: a byte the decoder gives no meaning that is zero in at least 999 of every 1,000 records of its kind counts as padding. Counted byte by byte instead, the fully decoded shares are 70.5% on older main boards, 66.9% on older batteries, 89.0% on newer main boards, 52.6% on newer batteries.
- Older and newer Zeros are told apart by how a file's records are laid out, not by its name. Newer battery logs carry a marker every 128 bytes, written over whatever sits there. That marker is most of their corrupted share, and a property of the file.
- Every record of every file counts; a download repeats older records until the bike overwrites them.
- home.hasslers.net publishes a table like this for its own decoder; this one also counts fields rather than bytes, so the two can sit side by side. They measure different logs with different decoders, and an overwritten value is its own column there and part of “partly decoded” here.
upstream a2152d1b68ac620a · patch unknown
4.37.3
22 November 2026Currently runningReports whose AI analysis found too little to judge open again.
Fixed: Was wrong, now is not
- A report whose AI analysis found not enough evidence to judge no longer opens on an error screen. The analysis card now says "Not enough evidence".
4.37.2
21 November 2026The 2016 FX and FXS show their ABS as the manual prints it.
Fixed: Was wrong, now is not
- The 2016 FX and FXS now show "Bosch Gen 9 ABS" in their specifications, as their owner's manual prints it.
4.37.1
21 November 2026A charge recorded twice now counts once.
Fixed: Was wrong, now is not
- A charge recorded only by a Power Tank's own log is no longer used to measure the health of the motorcycle's main battery.
- A charge recorded twice, once from the motorcycle's log and once from a battery log, now shows as one charge, so your charge energy totals no longer count it twice.
- If you leave the chat while an answer is being saved, the answer is saved once and counts against your monthly AI allowance once. The connection to the AI service also closes when you leave.
- With "Read my logs" on, when a log holds more rows than the assistant can read, it now reads the errors, the tip-overs and the newest warnings first, where it used to read the oldest rows.
- A link in the assistant's "Read:" lines is no longer made from an address with hidden characters in it.
- The "Read my logs" switch now always ends showing the setting that was saved, however quickly you click it.
4.37.0
21 November 2026Each battery module of a two-module bike shown on its own, and some older battery logs read in full.
Added: New in this release
- On a motorcycle with two battery modules, the charge page, the charge list on each battery card and a log's cell charts now show one module at a time, with a switch between them. Until now they mixed both modules' cells into one figure.
Fixed: Was wrong, now is not
- After a battery log filled up and started over, some older battery firmware kept marking it as starting at its very beginning, so only the newest records were read. Those logs are now read whole: for one rider, files that showed a couple of days now hold months of records.
- Motorcycle logs whose VIN setting held something else, such as text typed in at a dealer, are now filed under the motorcycle they were uploaded to, so their rides and charges appear on that bike.
- The app's download panel and two guides no longer say the app never changes a setting on the motorcycle. It changes one only when you ask.
4.36.2
21 November 2026Small fixes to the bike pages and the motor guide.
Fixed: Was wrong, now is not
- The text versions of the bike pages now say hp instead of CV.
- Each bike page now shows the correction notes for every model year, and the year-by-year comparison shows suspension travel.
- On the motor guide's gearing chart, the two 11 kW licence versions are now drawn as separate markers.
4.36.1
21 November 2026The bike check flags fewer log errors that stopped long ago.
Fixed: Was wrong, now is not
- The bike check now asks you to keep an eye on a routine log error only if it appeared on three different days in the 30 days before your newest log. Until now any three days in the bike's history counted, so an error that had stopped months ago could still be flagged.
4.36.0
21 November 2026How the motor's turn reaches the rear wheel, on the Z-Force motor page.
Added: New in this release
- A new section on the Z-Force motor page, "From motor to wheel": what the belt's reduction does, why a Zero needs only one gear, the pulley and sprocket pairs Zero has used, and why the controller, not the gearing, sets the top speed.
- A chart of how hard each Zero can push per kilogram of bike, and a gearing explorer that applies any pair Zero fitted to the bike you pick, in your units.
4.35.0
21 November 2026Pick your units on the bike and motor pages, and a few figures corrected.
Added: New in this release
- The bike pages, the comparison and the motor and tyre guides have a units switch: metric, imperial or UK, with horsepower and torque units under "More". It starts from your browser's language, and your choice is remembered.
- When you show horsepower in hp, the bike pages use the figure Zero printed rather than a conversion.
Changed: Different from before
- The bike pages no longer call Zero's horsepower "CV", and power-to-weight is shown in your units.
Fixed: Was wrong, now is not
- The riding-data guide no longer names a controller Zero's manuals don't name, and no longer calls Zero's amp rating "phase current". The motor guide's live readout no longer turns that rating into a phase current either.
- The charging guide now gives the 2016 Charge Tank about 2.5 kW of its own, from Zero's 2016 press kit, and marks the precharge part of its diagram as a schematic.
- The battery basics guide now says its cell voltage limits are typical lithium-ion figures, not Zero's, and cites Zero's patent for the cell chemistry.
- Corrected or completed specs for several bikes: the 2014 DS rear travel, the 2014 SR rear brake (left empty with a note, because the manual misprints it), and suspension, wheel and brake details for the 2016 FX and FXS, the SR/S and the 2023 DSR/X.
4.34.0
21 November 2026More room for the 3D motor, and corrected power figures for a few bikes.
Changed: Different from before
- The 3D motor on the Z-Force motor page is much larger, with its controls beside it and the steps and live charts underneath.
Fixed: Was wrong, now is not
- The 2024 to 2026 S and DS now show their full-power figures (51 kW, 167 km/h) instead of the European A1 version's, with a note on the A1.
- The 2014 and 2015 FX now describe one version, the ZF5.7, instead of mixing its power with the smaller battery's range and weight. Older bikes also say where their power figures come from, and the 2017 to 2023 S and DS say which battery came with the smaller motor.
4.33.0
20 November 2026A new Learn page opens the Zero motor in 3D.
Added: New in this release
- A Learn page on the Z-Force motor: how an electric motor turns, and the motor in your Zero opened up in 3D, with the coils, magnets and encoder moving as you change the speed and the throttle.
- The five Z-Force motors, 75-5 to 75-10X, compared model year by model year from Zero's own manuals: power in kW, hp and CV, torque, controller current, battery voltage and top speed, each with the manual page it comes from.
4.32.1
20 November 2026A routine battery message is no longer shown as a problem.
Fixed: Was wrong, now is not
- The battery's own tally of its cell-board readings ("PL536 Read Attempts Failed") is no longer listed as a concern when it says the readings are fine: 1% of them or fewer needed a second try, and no board had an error. It now appears as "Cell-board read retries", and the concern it raised on your bike is closed.
4.32.0
20 November 2026A bike you add in the ZeroLogs app is on the site straight away, logs or not.
Fixed: Was wrong, now is not
- A motorcycle you add in the ZeroLogs app is now on your account on the site as well, before you upload any of its logs: in My Bikes, on the dashboard and in every bike selector. Until now a rider who used the app alone was told they had no motorcycle, and the app's "My bikes" button opened "Bike not found".
Added: New in this release
- On an FX, FXS or FXE, the bike's page and each ride recorded by the app ask whether the bike has one Power Pack or two, because the VIN does not say. Your answer gives every recorded ride its energy and consumption, the rides already recorded included.
- A ride recorded by the app says why it has no energy figure, where it used to show a dash.
4.31.1
17 November 2026Fixed: Was wrong, now is not
- Place names along a ride (traffic lights, crossings, towns) fill in more reliably when the public map service is busy.
4.31.0
17 November 2026Fixed: Was wrong, now is not
- On Zero models before the SR/F generation, start-up lines such as Key On and Power On now show when the bike was really switched on, not a guess that could be hours or days off, and a few nonsense rides and charges dated 1970 are gone. The method comes from cecil-t's work on the open-source log parser, and the logs you already uploaded are being read again.
4.30.2
16 November 2026Fixed: Was wrong, now is not
- Alerts about a failed upload or a new account now reach the team even when the messaging service stalls for a moment.
4.30.1
16 November 2026Fixed: Was wrong, now is not
- An upload or an AI reading no longer risks failing in the few seconds while the servers' gate to the outside world restarts after an update.
4.30.0
16 November 2026Changed: Different from before
- The servers' single gate to the outside world now refuses anything that is not one of the services the site uses.
4.29.0
16 November 2026Changed: Different from before
- The servers now reach the outside world through a single gate that knows the services the site uses, such as storage, weather, the AI models and email, which narrows what a fault or an attack could ever send out.
4.28.1
16 November 2026Fixed: Was wrong, now is not
- After you upload a log, your log list, overview and battery pages are prepared in the background again, so they open quickly the first time you look.
- Uploading the same file twice at the same moment, as the app can do when it retries a slow upload, now keeps one copy instead of two.
- The real-world figures on a model's page in the bikes catalogue no longer go missing for a minute while the site is being updated.
4.28.0
16 November 2026Added: New in this release
- When your motorcycle's logs show a different battery from the one on your Batteries page, you now get an alert, on the website and on your phone if Bike check alerts are on, as they are by default. It opens the service book, where you confirm the change.
Fixed: Was wrong, now is not
- Uploading a log file you had already uploaded twice no longer fails with a server error: it is recognised as a duplicate, as any other already uploaded file is.
4.27.4
15 November 2026Fixed: Was wrong, now is not
- On a motorcycle with two batteries, each battery's health is now measured on the same charges, the ones both batteries' logs recorded, so the two figures compare and add up to the whole pack. Each card says which years those charges are from, and says when they are old.
- When your logs show a different battery in the motorcycle from the one on your Batteries page, ZeroLogs now offers the change for you to confirm, even when the old battery fills years of the same download.
4.27.3
15 November 2026Fixed: Was wrong, now is not
- After an update of the site, a model's page in the bikes catalogue no longer keeps its real-world figures loading for half a minute.
4.27.2
15 November 2026Fixed: Was wrong, now is not
- The fix of 4.27.1 for charges counted twice now also reaches battery logs that go back several years, on motorcycles whose logs were uploaded many times.
4.27.1
15 November 2026Fixed: Was wrong, now is not
- Some motorcycles showed a charge twice, because a battery log, often a Power Tank's or a second battery's, keeps a clock apart from the motorcycle's. Each battery log is now set to the motorcycle's clock month by month, and the second copy is gone.
Changed: Different from before
- The Android app 0.37.1 is out on Google Play: your account's notifications on the phone, and Send stays above the keyboard in Report a problem.
4.27.0
15 November 2026Added: New in this release
- A To do at the top of the Notifications page: what is still open on your account, like a battery change to confirm, a phone recording waiting for its motorcycle, an email address to confirm or a log that is getting old. Each line opens the page where you settle it.
- When the Bike check finds something to act on, the app on your phone tells you once. Reminders for the To do can reach the phone too: switch them on under Notifications.
- See where you are signed in on the Profile page, and sign out any other device, or all of them at once.
Changed: Different from before
- The Profile page is organised in sections with an index, and is easier to use on a phone.
4.26.0
15 November 2026Added: New in this release
- Motorcycles with a Power Tank: the main pack and the Power Tank each get their own health on the battery page, against their own size, and a card compares them, so a Power Tank wearing faster than the main pack shows. When only one of the two logs has come, the page says how to get the other.
4.25.0
15 November 2026Added: New in this release
- Notifications: a bell at the top of every page counts what is new on your account, and the Notifications page lists it. A new phone or API key on your account, a third-party device paired, a log that is ready or could not be read, a reply to a problem you reported, your data download.
- On the same page you choose which of these reach your phone and set quiet hours. The Android app shows them from version 0.37.0, coming soon on Google Play.
4.24.1
15 November 2026Changed: Different from before
- The Android app 0.36.8 is out on Google Play and as a file on the app page.
4.24.0
15 November 2026Added: New in this release
- Motorcycles with two battery modules of the same kind, such as an FX or FXS with two power packs: each module's card now shows that module's own health, measured from its own log, with the range of its charges. A new card compares the two modules and says one holds less only when the charges show it clearly.
4.23.1
15 November 2026Changed: Different from before
- The guide to motorcycles with two battery modules now shows how the two modules are wired, how to ride an FX or FXS on one pack with the connector plug, and how to add the second one, with four new figures. It also explains the dash codes that point at a module and what a Power Tank needs to come off.
4.23.0
15 November 2026Added: New in this release
- Motorcycles with two battery modules: the charge curve, the cell-balance trend, the parking details and the log viewer now show one module at a time, with a switch between them. Before, the two modules' readings alternated on one chart.
Changed: Different from before
- The app page now says what the Android app may send to your motorcycle: a charging schedule you set, or which battery module's log to read. It used to say the app never writes to the motorcycle.
4.22.1
15 November 2026Changed: Different from before
- Signing in to the Android app no longer sends you an email saying a new API key was created. The app's keys are still listed under Devices & API, where you can revoke them.
4.22.0
15 November 2026Added: New in this release
- New guide, Bikes with two battery modules (Learn, Battery). It says which Zero motorcycles carry two battery modules, going by Zero's owner's manuals (an FX or FXS with two removable power packs, or an S, SR, DS or DSR with a Power Tank), and how to download the second module's log with the Android app.
Fixed: Was wrong, now is not
- Learn: 15 guides linked to Zero Motorcycles pages that no longer exist. Each link now opens a working Zero page, or the owner's manual the guide quotes.
4.21.5
14 November 2026Fixed: Was wrong, now is not
- Battery page: on a motorcycle with two battery modules, each module's card now shows that module's own data. Before, both cards showed the two modules mixed together.
4.21.4
14 November 2026Fixed: Was wrong, now is not
- Android app 0.36.7: on an FX or FXS with two battery modules, the request to switch to the second one now uses the same bytes as Zero's original app.
4.21.3
14 November 2026Fixed: Was wrong, now is not
- Android app 0.36.6: on an FX or FXS with two battery modules, the app now waits for the motorcycle to close the first battery's log before it switches to the second, as Zero's own app does.
4.21.2
14 November 2026Fixed: Was wrong, now is not
- The assistant in agent mode saves its answers again, and can read your logs and rides while it answers.
4.21.1
14 November 2026Added: New in this release
- The Android app 0.36.5: on a Gen2 Zero with two battery modules or a range extender, the app now downloads the second battery's log too.
Fixed: Was wrong, now is not
- Behind the scenes: a fix to the new automatic release process.
4.21.0
14 November 2026Changed: Different from before
- Behind the scenes: new versions of the site now go out through an automatic release process that checks every step and steps back on its own if something goes wrong.
Fixed: Was wrong, now is not
- Behind the scenes: the backups of our new servers now include every log and file you upload, and restoring them is tested again.
4.20.0
14 November 2026Added: New in this release
- A new Learn page, Common problems: the problems riders report most, from a download that stops early to a ride shown twice, each with why it happens and what to do.
4.19.5
14 November 2026Fixed: Was wrong, now is not
- The Android app 0.36.4 is out: on some motorcycles the battery log download no longer stops early, and on 2016 models the app says the charge level is not available instead of showing 0 %.
4.19.4
14 November 2026Fixed: Was wrong, now is not
- The "Charge against distance" and cell imbalance charts show their axis labels in full; the top of the charge axis read "00%".
4.19.3
13 November 2026Changed: Different from before
- The Android app 0.36.3 is out: scheduled charging for Gen3 bikes plans the night on your tariff's time bands, shows what tonight's charge costs, and works in a garage with no signal.
4.19.2
13 November 2026The last of the report's charts reach the trip page.
Added: New in this release
- The trip page and the ride page show how the charge fell against the distance ridden, from the bike's log and from the app's readings.
- The trip page shows your pack's cell balance over the past year, with the trip's day marked.
- On a log report with a ride open, two buttons take you to that ride's page and to its trip. Only the report's owner sees them.
4.19.1
13 November 2026Fixed: Was wrong, now is not
- On the newer Zero models, a battery log's clock is now lined up with the motorcycle's own, so its rides and charges no longer show up a second time at the wrong hour.
4.19.0
13 November 2026Changed: Different from before
- The Costs page now checks that every time band has a valid start and end time before saving.
4.18.6
13 November 2026Fixed: Was wrong, now is not
- On a Zero with Extended Range Charging, a charge to 110 % now reads 110 % in your rides, charges and charts; until now the readings above 100 % were left out, so a ride that started at 110 % showed 100 %.
4.18.5
13 November 2026Fixed: Was wrong, now is not
- The log events and the battery modules card on a trip no longer miss a line that sits just past the edge of a log file's recorded time span.
- Warnings and errors in the trip's log lists show their level as a labelled badge.
4.18.4
13 November 2026Changed: Different from before
- The ride page lists your log's warnings, errors and tip-overs under its charts, as the trip page does, and clicking one zooms the charts to that minute.
Fixed: Was wrong, now is not
- The log events card no longer says there is nothing to show when the only lines left out are ones whose time the parser had to reconstruct; it says how many there are and why.
- The battery modules card on a trip leaves out readings whose time was reconstructed after a main board reset, and counts "1 module" and "1 contactor event" correctly.
4.18.3
13 November 2026Fixed: Was wrong, now is not
- With "Read my logs" on, a long question no longer ends in a block of unreadable code instead of an answer: when the assistant has used its reading time, it now always writes its answer from what it read.
4.18.2
13 November 2026Fixed: Was wrong, now is not
- With "Read my logs" on, the assistant no longer describes the bike as still riding in the minutes after a tip-over.
- A question about your bike's history no longer stalls on a search further back than five years: the assistant reads the last five years and says so.
4.18.1
13 November 2026The chat says which ride an event happened on.
Fixed: Was wrong, now is not
- With "Read my logs" on, a warning or a tip-over the assistant reads now says which of your rides or charges it happened in, so the answer places it on the right ride.
- Asking whether something happened before, such as "was this the first tip-over?", now searches your logs from the last five years in one go.
4.18.0
12 November 2026The trip page shows what the report shows.
Added: New in this release
- The trip page and the ride page chart more of your bike's readings: pack current, the weakest cell and the cell spread, and under "More charts" the motor torque, the odometer, the air temperature at the bike, the weakest cell at rest, the power limits, instant consumption, energy used, regen recovered and an estimate of the pack's internal resistance. Each chart puts every log file of the trip and the app's Bluetooth readings on one clock.
- Warnings, errors and tip-overs from your logs are marked on the trip and ride charts at the moment they happened. A new "Log events" card on the trip page lists them, and clicking one zooms the charts to that minute.
- When your logs hold them, the trip page shows the battery modules' checks at key-on. It also links to the full log for the trip's days.
4.17.2
12 November 2026Changed: Different from before
- The Android app 0.36.2 is out: Gen3 riders can set scheduled charging from the Bike tab, the same window every day, and check it against the bike's next log.
4.17.1
12 November 2026The chat reads a crash more carefully.
Fixed: Was wrong, now is not
- With "Read my logs" on, the assistant no longer guesses whether the bike was moving or stopped at a moment your logs did not sample. It says the speed is not known and reads the phone recording or the battery readings around that moment.
- On a day with many warnings, a tip-over late in the day stays among the events the assistant reads.
4.17.0
12 November 2026Changed: Different from before
- The Bluetooth protocol page now explains the one setting the ZeroLogs app can send to a Gen3 motorcycle, its charging schedule, and how each send is checked against the bike's next log.
- "Download all your data" includes any charging schedule the app sent to your motorcycle.
4.16.0
12 November 2026The chat can read your logs before it answers.
Added: New in this release
- "Read my logs" in the chat. Turn it on and the assistant reads your own logs before it answers: events, battery and speed readings, your rides and charges, your bike check and the owner's manuals. While it works it tells you what it is reading, and under the answer it lists what it read, with links to those moments in your logs. It only ever reads your own data. Answers take longer and use more of your monthly AI allowance, so the switch starts off.
- The error catalogue explains a tip-over: what the bike writes in its log when it falls, why it cuts the throttle, and how to reset it.
Changed: Different from before
- With "Read my logs" off, the chat now also sees the warnings and safety events in the time window you are looking at, such as a tip-over on the ride you opened.
- Bluetooth captures you contribute on the help-decode page now have your bike's GPS position blanked, as its passcode and unlock keys already were.
4.15.0
11 November 2026The bike check reads every warning in its context, and the dealer report says how it knows.
Added: New in this release
- A motor and controller check: their temperatures on your rides of the last 90 days, read against the temperature outside.
- "Ask in chat" on every check and every diagnosis opens the chat on it, and the chat now sees your bike check and your latest diagnosis.
Changed: Different from before
- A warning your logs have not shown in the last 30 days counts for less. It reads "Seen before" with the date, and no longer asks you to act.
- A battery pack that ran hot is read against the temperature outside at that moment. On a day of 30 °C or more it needs no action; on a cool day it is worth a look.
- The dealer PDF is one branded page: a tile per part of the bike, how each finding is worked out with Zero's own limits quoted from the manual, and what a dealer can check on the bike.
- Diagnosis explanations and chat answers are shorter and written more plainly.
4.14.0
10 November 2026The bike check: what your logs already say about your bike, before you ask.
Added: New in this release
- A bike check at the top of Diagnoses, with one tile per part of the bike: charging, battery, cells, temperatures, parking, tyres, service book and log errors. Each tile says whether there is something to act on, something to keep an eye on or nothing, and opens to what we saw and where the numbers come from.
- It notices an onboard charger that stops before full while another charger finishes, a pack that ran hot or went very low, a bike that loses charge while parked or was left low for weeks, and a service that is due.
- Two new things to ask about: "Stops before full" and "Loses charge when parked". "Ask about this" on any check starts a diagnosis on it.
Changed: Different from before
- A diagnosis now opens with a one-sentence answer, then what explains it, what to do and the rest of your bike.
- The home page's "Needs your attention" list shows what the bike check found. Errors that are common on your model no longer appear there.
- The dealer PDF and the link for a mechanic include the bike check. The link never shows how the bike was parked, tyre pressures, or a battery percentage worked out from a pack size you typed.
4.13.0
10 November 2026A first step toward setting charging and ride modes from ZeroLogs.
Added: New in this release
- When you share a Bluetooth recording on the help-decode page, ZeroLogs can now read what the phone sent to a Gen3 bike's charge target, scheduled charging and ride modes, and to a Gen2 bike's custom mode. We use it to study how these settings could be changed safely; ZeroLogs itself still sends nothing to your bike.
4.12.0
10 November 2026Diagnoses: tell ZeroLogs what is going on, and it reads your logs with that in mind.
Added: New in this release
- Diagnoses, in the Bike menu: pick what is going on and answer a couple of questions. ZeroLogs then shows what in your logs explains it, what is normal for your bike, and what to do next.
- Every diagnosis is kept, with an explanation in plain words when you ask for one and a PDF to take to the dealer. A problem with the motorcycle points you to a Zero dealer.
- A diagnosis can be shared with a mechanic as a read-only link that expires after 7, 14 or 30 days. It shows the symptom, the verdict and what your logs showed, never your conversation or your notes.
- The console logs guide explains how version 0.37 of the Android app reads the serial console through a cable or a dongle.
Fixed: Was wrong, now is not
- Bluetooth recordings you share to help decode the protocol no longer keep a Gen3 bike's passcode or unlock keys.
4.11.0
9 November 2026Version 0.36.0 of the Android app is on Google Play.
Changed: Different from before
- The app's page, the footer and the app changelog now name version 0.36.0, which fixes log downloads on Zeros with a 2015-2016 main board and makes it easier to disconnect from the bike. On a phone without Google Play, the app's page offers the 0.36.0 file.
- The home page, the app's page and the Learn pages are now kept on servers closer to you, so they open faster.
4.10.4
8 November 2026Fixed: Was wrong, now is not
- Inside the Android app, a new account's dashboard told you to get your logs with Zero's app. It now sends you to the app's own download on the Bike tab.
4.10.3
8 November 2026Added: New in this release
- The Android app now shows which version you have, at the bottom of every page.
Fixed: Was wrong, now is not
- Bookmarking a ride or a charge now works. Until now it failed with an error, so nothing was saved.
4.10.2
8 November 2026Changed: Different from before
- Behind the scenes: groundwork so the site can later sit behind a protective network in front of our server, without interrupting the secure connection you use today.
4.10.1
8 November 2026Fixed: Was wrong, now is not
- Behind the scenes: one of the pages we use to look after the whole fleet now opens at once instead of taking about a minute.
4.10.0
8 November 2026Changed: Different from before
- Behind the scenes: the rest of the pages we use to run the site, from the support inbox to the e-mails we send, now share one design, and a new fleet health view shows which faults, batteries and chargers need attention across all bikes.
4.9.1
8 November 2026The ZeroLogs Android app is on Google Play for everyone.
Changed: Different from before
- The app's page, the footer and the app changelog now name version 0.35.0, the first one anyone can install from Google Play. On a phone without Google Play, the app's page offers the 0.35.0 file.
4.9.0
8 November 2026Changed: Different from before
- Behind the scenes: the pages we use to run the site were brought together in one design, with a map of where riders and rides are and a clearer view of the server's health, so a problem gets noticed and fixed sooner.
4.8.0
8 November 2026Changed: Different from before
- Behind the scenes: every list in the pages we use to run the site can now be sorted, filtered, searched and exported, so we find a problem you report faster.
4.7.1
8 November 2026Fixed: Was wrong, now is not
- Behind the scenes: the pages we use to run the site showed up blank in a browser with an ad blocker. They now show in full, so your tickets reach us as quickly as they should.
4.7.0
8 November 2026Changed: Different from before
- When we answer your ticket and you have not written back, you get one reminder after two weeks, and the ticket closes after a month. Replying reopens it at any time.
- The privacy page now says that the Android app's optional performance data includes how long the app stays open each time you use it.
4.6.0
7 November 2026Changed: Different from before
- Behind the scenes: answering a support ticket is quicker, because each rider's page now shows their app, their open tickets and any error they hit in one place.
4.5.0
6 November 2026Changed: Different from before
- Behind the scenes: the site now counts its own errors and slow answers, so we can see a problem before you have to report it. Addresses are kept only as a network range, never in full.
4.4.0
6 November 2026The pages we use to run the site were rebuilt, so a ticket or a problem you report reaches us sooner.
Changed: Different from before
- Behind the scenes: the admin pages now put first what needs attention, such as a ticket waiting on us or a log that failed to read. Your own pages do not change.
4.3.0
6 November 2026Your trip page now says how you rode, reads the trip for you with AI, and lines up its totals on one row.
Added: New in this release
- How it was ridden: the riding style radar from shared trips is now on your own trip page.
- An AI reading of the trip, written when you ask for it, from the trip's figures, the weather and your note.
- New gauges: how much of the available regen you took back, this trip's consumption against your usual on the same motorcycle, the charge stops with the charger they used, and the pack's health on trips with a charge stop.
Changed: Different from before
- The trip's totals now fit on one compact row, and the gauges are shorter.
4.2.0
6 November 2026Your trip page now opens with gauges: how fast, how hard and how hot, against what the motorcycle is rated for.
Added: New in this release
- "At a glance" on the trip page: top speed, motor rpm, peak power with the peak regen, an estimated peak torque, how the ride's time divided between pulling, cruising, coasting and regen, the regen recovered, and the temperatures. Each one says where it comes from and follows the zoom.
- The gauges' full scale is the motorcycle's own rated figure from Zero's manuals, and the pack's temperature limit from its owner manual. Where only the bike's log exists, a peak is marked as "at least", because the log keeps one record a minute.
- A "Join log points" switch joins the log's records on the slow charts (charge, voltage, temperatures). Charge always reads 0 to 100 %, and regen is shaded below zero on the power chart.
4.1.0
6 November 2026If you installed the Android app from the file instead of Google Play, it now tells you when a new version is out.
Added: New in this release
- Inside the Android app, the dashboard and the "This phone" page say when a newer version is out, and how to get it: Google Play updates its own copy, and a copy installed from the file is downloaded again from the app page in your phone's browser. You can close the notice for that version.
Fixed: Was wrong, now is not
- Inside the Android app, the download button on the app page did nothing. It now gives you the address to open in your phone's browser, with a button that copies it.
- When the server stops accepting an old version of the app, its message now names the app page beside Google Play.
4.0.0
6 November 2026The Android app is out of testing: get it on Google Play, or download it here for a phone without Google Play.
Added: New in this release
- The Android app has its own page, with screenshots, what it does on the motorcycle, which Zero models get what over Bluetooth, and what Android asks you to allow.
- A phone without Google Play can download the app from that page, with no account. It is the same file Google Play installs, and the page prints its checksum and signing certificate so you can check it.
Changed: Different from before
- The release notes print the 4.x releases in full. Earlier versions are grouped by major version in the list at the top: pick one to read its notes, and old links to a release still open it.
- The testers' page now leads to the new app page, and so does the app link in the footer.
- The Android app's release notes list version 0.34.1, the version going out to everyone on Google Play.
3.118.0
6 November 2026Phone data now lines up with the motorcycle's log to the second, and ride charts are easier to read and zoom.
Added: New in this release
- Each ride now works out the motorcycle's clock to the second from its speed peaks and stops, compared with the phone's Bluetooth or GPS speed. Speed, route and phone readings line up on the charts, and your own correction always wins, with an Undo.
- Charts show only the title, the axes and the data sources. Click a source to hide it on one chart, or use the source bar at the top to hide it on all of them. The rest sits in a Details tab with a link to learn more about each source.
- Trip charts squeeze the pauses between legs, can zoom on one leg, and zoom with Ctrl or ⌘ and the wheel or with a pinch. The zoom strip moved to the top bar and shows the speed.
Fixed: Was wrong, now is not
- Auto-align on a ride can now find the right offset when the motorcycle's clock is far from the phone's.
3.117.2
6 November 2026The Bluetooth protocol guide now says how a Gen3 motorcycle really sends its logs.
Changed: Different from before
- The Bluetooth protocol guide now says that a Gen3 motorcycle sends the blocks of a log in order, whatever block number the app asks for, as measured on an SR/F. Its download section, figure and advice on late answers are updated.
- The Android app's changelog lists version 0.34.0.
3.117.1
5 November 2026Android app 0.34.0: Gen3 log downloads that stop halfway now come back whole, and faster.
Added: New in this release
- Android app 0.34.0 for testers: the motorcycle connects by itself when you open the app or come back to it. A switch turns this off, and Disconnect keeps it off until you tap Connect.
Fixed: Was wrong, now is not
- Gen3: a log download that stopped halfway and then resumed could join two copies of the log and miss its newest part. The app now reads that log again from the start, and a lost request is asked again after about 1.5 seconds instead of 10.
- A battery log the motorcycle has not written yet is no longer uploaded, and the site calls such a file empty instead of corrupt.
3.117.0
4 November 2026Android app 0.33.0: a log download survives a key-off, a lost Bluetooth link and a closed app.
Added: New in this release
- Android app 0.33.0 for testers: a log download that stops halfway is no longer lost. The app keeps what it read and finishes by itself when the motorcycle is back on and parked, and on a Gen3 motorcycle it goes on from where it stopped.
Fixed: Was wrong, now is not
- A finished motorcycle log is kept and uploaded when the battery log is cut short, and Stop keeps what was downloaded.
- A log the app could only partly download is now called a partial download, not a truncated file.
3.116.1
3 November 2026Android app 0.32.0: report a problem from the app's own error screens.
Added: New in this release
- Android app 0.32.0 for testers: when a log download stops, the motorcycle is not found, the Bluetooth link fails, an upload is refused or a ride cannot be saved, Report this opens a report with the error already written, and it offers to add to your open ticket for the same problem.
3.116.0
3 November 2026Report a problem from the page where it happened.
Added: New in this release
- When a page fails, a Report this button opens a short form that already knows the page and the error. You see each detail it would send and can untick it, and nothing goes until you press Send.
- If you already reported the same problem, the form offers to add to your open ticket instead of opening a new one.
- Report a problem is in the menu on every page, and in the footer for visitors without an account.
Changed: Different from before
- A page that fails because of our server now says so and offers Report this, instead of saying the ride or charge was not found.
- The privacy policy explains what a report from a page carries.
3.115.0
3 November 2026Messages sent through the contact form now get a full conversation, with or without an account.
Added: New in this release
- A message sent through the contact form becomes a ticket with a number and a conversation. Without an account you follow it through a private link that comes with our replies, and you can delete the conversation from there.
Changed: Different from before
- Earlier contact messages and their replies are now tickets too, and their old reference numbers still work.
3.114.0
3 November 2026What a motorcycle costs to run, and problem reports from the app that carry what we need.
Added: New in this release
- On the model comparison page, type your electricity price and how far you ride in a year to see what each motorcycle costs per 100 km and per year. It also works out whether a swap pays for itself.
- A problem report from the Android app can include the app's diagnostics, and a ticket on the site can ask the app for them.
- Signing out of the Android app can also delete the app's data on the phone. The dialog first tells you what would be lost.
Changed: Different from before
- The measured consumption and range on the model pages count each motorcycle once, so one bike with many rides no longer sets the figure.
Fixed: Was wrong, now is not
- The Android app no longer closes when the phone is too full to save a problem report.
3.113.0
2 November 2026The privacy policy explains the Android app's optional performance data.
Changed: Different from before
- The privacy policy now says what the Android app's optional performance data contains, that it stays off until you say yes, and that its log lines are deleted after 14 days.
- Grafana Labs, which monitors the service from the European Union, is now listed among the providers that process data for us.
3.112.0
2 November 2026Feedback is now one ticket per conversation, with your files and rides attached.
Added: New in this release
- Feedback works as tickets. A problem, an idea, a question or an opinion gets a numbered ticket that you follow in one conversation, then mark as solved or reopen.
- Any message in a ticket can carry photos, short videos and text files, and you can link your own logs, rides, trips and charges so we see exactly what you mean.
- Tickets have a small Markdown editor with a preview. Pasting or dropping an image attaches it.
- An opinion can carry a rating from one to five stars, and the separate survey has left the feedback page.
Changed: Different from before
- Photos you send with feedback are stored without their location or camera data, and videos lose their location tag before we keep them.
Fixed: Was wrong, now is not
- Deleting your account now also deletes the files you sent with your feedback.
3.111.2
1 November 2026A ride the app recorded joins the right ride from your log.
Fixed: Was wrong, now is not
- When a motorcycle's clock was off by a few minutes, a ride the app recorded could join the next ride in your log instead of its own. The motorcycle's odometer now has to agree before the two are joined.
3.111.1
1 November 2026Regen figures for rides the app only partly heard.
Fixed: Was wrong, now is not
- When the app lost the motorcycle's readings for long stretches, the trip page still worked out regen from the part it heard and showed it as the whole ride. It now says how much of the ride the app read, and leaves the regen figures out when that is too little.
3.111.0
31 October 2026A clearer footer, and the site stays dark on every device.
Changed: Different from before
- The footer groups its links into Reference, Tools, Project and Legal, each with an icon, and on a phone every link is big enough to tap. The service status and the web and Android app versions sit on a line of their own.
- The service status in the footer now says "Status not known" when it cannot reach the server, instead of staying on "Checking" or claiming an outage it cannot see.
Fixed: Was wrong, now is not
- On a device set to a light theme, some headings and the footer were dark text on a dark page. The site is dark everywhere now.
3.110.0
31 October 2026Dates the way you read them, all your data in one download, and several log lines selected on a phone.
Added: New in this release
- Choose how dates and times are shown: day first (31/10/2026), month first (10/31/2026) or year first (2026-10-31), a 24- or 12-hour clock, and a time zone or your device's. New accounts start with the format of the country they sign up from, the home page asks once whether it looks right, and your profile changes it at any time.
- Download all your data: one ZIP with everything your account holds, requested from your profile page. It is built in the background, you get an email when it is ready, and it stays available for 7 days.
- Both log viewers now select several lines on a phone as well as on a computer: tap the lines you want, and a bar at the bottom shows how many are selected, with Clear, Select range and Explain.
- The Regen section says how many times the motorcycle's main board restarted during a ride recorded with the Android app, and how many of those happened while regenerating.
Changed: Different from before
- Dates in the PDF report follow your date format and time zone. Exported data files keep ISO dates in UTC, as other software expects.
- A GPX file whose times carry no time zone is now read in the time zone of the place where the recording starts, not as UTC. When its times disagree with your bike's log for that day, the route is not attached and the page says why.
- Every page now prints dates the same way; some printed them US style ("Oct 31, 2026").
- The Regen section weighs each motorcycle with the curb weight from Zero's manuals, the same figure as the Android app.
3.109.0
31 October 2026The Regen section learns where you stopped, and works on Gen3 bikes.
Added: New in this release
- The Regen section now says what each stop and slowdown ended at (a traffic light, a roundabout, a stop or give-way sign) and how long you waited at the lights, from OpenStreetMap. Your route is never sent: the site asks about whole areas of about 28 by 20 km.
- Gen3 bikes recorded with the Android app get the Regen section too, with the lever and throttle split the bike itself reports. Their power comes in whole kilowatts, so the page marks the figures as rough.
Changed: Different from before
- The Regen guide now gives how much weaker regen gets with a full or cold pack (about a tenth), and what the rider saw when the main board restarted on the descent in its worked example.
3.108.0
31 October 2026Regen, measured: a section on every trip recorded with the app, and a guide.
Added: New in this release
- Trips and rides recorded with the Android app have a Regen section: how much energy went back into the pack, how much of it came with the brake lever and how much with the throttle closed, and a chart of pack power and speed. It also works out what the ride would have cost without regen, and what slowing down earlier could have brought back.
- A new guide, Regen on a Zero: how regenerative braking works mode by mode, how the app and the bike's logs record it, what riders' rides measured, and how to use it on a trip to keep your range.
Changed: Different from before
- The Riding & Regen Data guide no longer quotes recovery figures it had no source for. It gives the measured ones and points to the new guide.
3.107.0
31 October 2026Android app 0.29.6.
Added: New in this release
- Android app: the ride summary says when the phone's GPS was too weak to draw the route, and whether the ride still shows on zerologs.
Changed: Different from before
- Tyre sensors: pressure is judged at the outside temperature, the way tyre makers define a cold tyre (one not ridden for 3 hours, whatever the air), so a tyre pumped up in a warm garage now reads a bit low out in the cold. The tyre card on a ride's page says which temperature it used.
- Android app: the tyre sheet has a green band of 0.1 bar either side of the target, and says "a bit low" or "a bit high" outside it.
Fixed: Was wrong, now is not
- Android app: tyre readings now reach your account on rides without GPS, or when the phone never gets a fix. Before, they were lost at the end of the ride.
3.106.2
30 October 2026Android app 0.29.5.
Fixed: Was wrong, now is not
- Android app: Gen3 motorcycles on recent firmware (the DSR/X among them) can download their logs again; the app stopped at "the log list could not be read".
- Android app: a battery log the motorcycle ends early is now shown as partial, with how many blocks arrived.
3.106.1
28 October 2026Fixed: Was wrong, now is not
- The Android app on the beta page, for phones without Google Play, now opens as it should.
3.106.0
28 October 2026The Android app for phones without Google Play.
Added: New in this release
- Phones without Google Play, and Aurora Store users, can install the Android app from the beta page once signed in. It is the same file Google Play installs, and the page shows how to check it.
3.105.1
28 October 2026Fixed: Was wrong, now is not
- A ride recorded without the phone's GPS joins its ride correctly once you upload the motorcycle's log of that day.
3.105.0
28 October 2026A ride recorded without the phone's GPS now shows up in your trips.
Added: New in this release
- A ride the Android app records from your motorcycle without the phone's GPS is now a ride in your trips. It has no map, and its distance comes from the motorcycle's odometer.
Fixed: Was wrong, now is not
- Pages you open again load faster: your browser keeps the site's images for a day.
3.104.0
27 October 2026Fixed: Was wrong, now is not
- If the cache behind the site stops answering, a page that shows several of your figures no longer waits for each one in turn. It loads in about two seconds.
Changed: Different from before
- Behind the scenes: the test copy of the site has a third server, and its pages now come from the Cloudflare location nearest to you.
3.103.0
27 October 2026Fixed: Was wrong, now is not
- If one of the services behind the site restarts, pages no longer hang waiting for it: they answer within a couple of seconds.
3.102.0
27 October 2026Changed: Different from before
- Behind the scenes: the servers of the test copy of the site now update themselves every week without interrupting it, and its configuration is backed up every night.
3.101.0
27 October 2026Changed: Different from before
- Behind the scenes: the test copy of the site is locked down further before it takes over from the current server.
3.100.0
27 October 2026Changed: Different from before
- The site runs on the newest version of the framework it is built with. Nothing should look different.
- When the site is being updated or cannot answer, you now see a short page saying it will be back in a moment, and it reloads by itself.
- Pages talk to the server sooner after they open, which saves a moment on the first load if you are far from Europe.
Fixed: Was wrong, now is not
- The bike comparison page no longer downloads pictures it does not show.
3.99.0
27 October 2026Changed: Different from before
- The site runs on a newer version of the framework it is built with. Nothing should look different.
- The service dot in the footer now checks only while the page is open in front of you, and turns red when the database is unreachable.
- Behind the scenes: the test copy of the site can move its database to another machine without any request failing.
3.98.0
27 October 2026Changed: Different from before
- Behind the scenes: the test copy of the site now runs on the database setup planned for this one, with continuous backups.
3.97.0
26 October 2026Changed: Different from before
- Every new version now runs on a test copy of the site before it reaches this one.
3.96.0
26 October 2026Changed: Different from before
- The AI analysis of your own rides reads what the app recorded every second: the cell balance at rest, the voltage drop under load and the weakest cell at peak current. It also reads your motorcycle's model, its pack's health and your earlier rides, in about 100 words.
- The analysis uses your units, miles and mph included.
3.95.0
26 October 2026Changed: Different from before
- Log data now takes about a tenth of the disk it used to, so report pages read far less from it.
- The Android app's version 0.29.1 is out on the test track: with one motorcycle on your account, one tap sends every ride recorded with the phone alone to it.
3.94.1
26 October 2026Changed: Different from before
- The Android app's version 0.29.0 is out on the test track: distances on the ride dashboard follow your units, and a ride the server refuses no longer holds back the rides after it.
3.94.0
26 October 2026Added: New in this release
- Readings the app records during a ride are kept in full for 12 months, then as 10-second summaries for as long as your account exists. The privacy policy says so.
- A ride's AI analysis and a shared trip's verdict now say what the ride shows about the battery pack, such as how much its voltage dropped under load and whether it used more energy than usual, and every number they write is checked against the data.
3.93.4
26 October 2026Fixed: Was wrong, now is not
- The bike's clock card now says when the clock was measured from your phone's GPS speed on a ride, instead of naming the battery.
3.93.3
26 October 2026Fixed: Was wrong, now is not
- A log downloaded with the Zero app keeps its note about the blocks that app loses when the log is read again.
3.93.2
26 October 2026Fixed: Was wrong, now is not
- Logs you uploaded earlier from the Zero app were read again without the repeated records, so their duplicate rows and misplaced events are gone too.
3.93.1
26 October 2026Fixed: Was wrong, now is not
- Logs downloaded with the Zero app no longer count the same records twice. The copies that app adds at the end of the file are skipped, which also stops a few events landing on the wrong day.
3.93.0
26 October 2026The Android app has its own release notes, and the site says which version is out.
Added: New in this release
- The Android app has its own page of release notes, with the day each version reached testers. The footer shows the app's newest version under the site's, and the home page and dashboard invite you to join the app's test. You can close the invitation.
Fixed: Was wrong, now is not
- Logs of the FX, FXS, FXE, S and SR uploaded before 25 October were read again with the corrected speeds, and the top and average speeds of their rides now match.
- The pages that explain log data no longer quote the old speed constants as current.
3.92.0
25 October 2026A ride recorded with the phone alone now joins the motorcycle's log, and log speeds on the FX, S and SR families are no longer 30 % high.
Added: New in this release
- If the Android app (0.28.0) cannot connect to your motorcycle, ride with the phone only: once you upload the motorcycle's log, the ride joins it. On models whose log records motor speed, this works even when the motorcycle's clock is wrong.
- Trip pages show how much you climbed and descended together, and the lowest and highest point of the trip.
Fixed: Was wrong, now is not
- Speeds read from the logs of the FX, FXS, FXE, S and SR were about 30 % too high. They now use figures measured on about 300,000 km of riders' logs, which match Zero's own gearing. Logs uploaded before today keep the old speeds until they are read again.
- When re-reading a log failed, the log was marked as failed and its rides dropped out of your totals. It now keeps its previous result.
3.91.0
25 October 2026Deep analysis works again, and the Android app now needs version 0.25.0 or newer.
Changed: Different from before
- The Android app needs version 0.25.0 or newer. Older versions could lose rides that had not been sent yet when the site signed you out; they now show a message with a button to update, and the site inside the app keeps working.
Fixed: Was wrong, now is not
- Starting a deep analysis of a log failed with an error since late September. It works again.
3.90.0
25 October 2026If the phone closes the app during a ride, the ride now continues.
Added: New in this release
- In the Android app (0.27.0), if the phone closes ZeroLogs during a ride, the same ride continues when the app comes back within 10 minutes, and the app reconnects to the motorcycle. The route has a short gap where the app was closed.
- When the motorcycle's Bluetooth link drops during a ride, the app now tries again by itself.
Changed: Different from before
- Each version of the Android app keeps working for 90 days after a newer one is published. After that, it asks you to update before it sends anything.
3.89.1
25 October 2026The motor controller's own codes now show on older Zero logs.
Fixed: Was wrong, now is not
- On S, SR, DS, DSR and FX-family logs, the motor controller's own error codes (Sevcon) were read but never shown. They now appear beside each controller message in the log viewer and count in the recurring-error history. They are shown at the level the log gives them, so a routine message at power-on does not turn into a red error.
3.89.0
24 October 2026The Android app's text is plainer, and three Learn pages now match what the logs and the manuals really say.
Changed: Different from before
- Android app 0.26.0 (testers): plainer wording throughout, and clearer messages when the phone is offline, when a log download stops early and when Bluetooth is off for the tyre sensors.
- The app's store page is now in English only, like the app itself.
- The parts each model was built with: ABS units, belts and motor controllers that the owner manuals print are now filled in, where before they showed as unknown.
Fixed: Was wrong, now is not
- Older (Gen2) logs do contain text the motorcycle writes itself, such as its own warning messages. The log anatomy and log format pages said they did not.
- The 12 V page and the charging page now agree on what a failing DC/DC converter looks like, and say plainly where Zero's manuals do not tell.
3.88.3
24 October 2026Everything on the site is now in English, and the Learn articles agree with each other and with the app.
Changed: Different from before
- The notes beside each log excerpt on the log anatomy page were in Italian. They are now in English and open by default.
- Messages from the ideas and survey pages that were in Italian are now in English.
- The Learn articles and the About page have been read through again: plainer wording, the same name for the same thing on every page, and no claim that the app's own code contradicts.
Fixed: Was wrong, now is not
- Several Learn pages disagreed with each other or with what the app does. Among them: Gen2 logs are binary records, not text; the Gen3 battery log does not record a temperature where one was listed; the weather card does have a "Look it up again" button; and a shared ride's map cannot appear later.
3.88.2
24 October 2026The last texts on the site are now plain too.
Changed: Different from before
- The feature list on the About page, the explanations next to battery health and shared links, the VIN decoder's messages and the sign-in lockout message are now rewritten in plainer English, like the rest of the site.
3.88.1
24 October 2026Every page, the emails and the Android app now say things more plainly.
Changed: Different from before
- The text across the site has been rewritten in plainer English, without changing what it says: the Learn articles, the bike and battery pages, the dashboard and the emails. The Android app's text is rewritten too, in English and Italian, and arrives with the next app update.
Fixed: Was wrong, now is not
- The DSR owner's guide gave the lowest charging temperature as 0°C (32°C). It is 0°C (32°F).
3.88.0
24 October 2026The bike clock card now notices when the clock inside your bike has changed, and checks a correction you type against what was measured.
Added: New in this release
- If two measurements of your bike's clock disagree, the clock card says when it changed and waits for one more measurement before offering a correction, because a single correction moves every log by the same amount.
- If the correction you type is far from what the app measured, the card warns you before you save. The clock on the dash is a separate clock, so its minutes are not the ones to enter.
Changed: Different from before
- On the SR/F, SR/S, DSR/X, the SR from 2022 and the S, DS and DSR from 2024, a few minutes of difference are no longer offered as a correction. Their clock is set from a phone now and then and drifts a few minutes in between.
3.87.0
24 October 2026Your bike's clock can be corrected to the minute, and the Android app keeps your rides and logs when it is signed out or the phone is full.
Added: New in this release
- On your bike's page, the clock card says how far out the clock inside the bike was measured, and offers that exact correction, to the minute. A clock that drifted by 38 minutes can now be put right, not only one set in another time zone.
- In the Android app (0.24.0), when a ride ends while you are still sharing it live, the app asks whether to stop sharing or keep it.
Fixed: Was wrong, now is not
- In the Android app (0.25.0), being signed out by the server (from another device, after a new password, or because the sign-in expired) no longer drops the logs waiting on the phone or disconnects the bike. The Bike tab says what happened, and everything is sent once you sign in again.
- In the Android app, a full phone no longer closes the app during a ride: the ride goes on and is saved as soon as there is space, and a log that could not be kept says so.
3.86.0
23 October 2026Share live works on every ride, and the app copes better with Bluetooth on the newer Zeros.
Added: New in this release
- A live ride link from the Android app (0.23.0) now shows where you are even on a ride with the phone alone, from the start of the ride.
- For the SR/F, SR/S, DSR/X, S/F and the 2024+ models, the app finds the bike by its name too and retries when the phone's Bluetooth fails to connect. These models are still being tested.
Changed: Different from before
- On a live ride page, your position is marked "Now" rather than "End", and no "Start" pin is shown where the area around your start is hidden.
3.85.0
23 October 2026Your tyre sensors follow your account, and the bike page shows each one's battery.
Added: New in this release
- In the Android app (0.22.0), which tyre sensor is on which wheel is kept on your account, so a second phone or a reinstall finds it.
- Your bike's page shows each tyre sensor, its battery and when it was last heard. A low battery turns the card amber, and a sensor silent for two weeks while you rode is flagged.
Fixed: Was wrong, now is not
- In the app, a change you make on the phone is no longer undone by an older one from another phone with its clock ahead.
3.84.0
23 October 2026The Android app's ride dashboard follows your account, and its notifications open the ride.
Added: New in this release
- In the Android app (0.21.0), the ride dashboard you arranged is kept on your account, so a second phone or a reinstall opens it the same way.
- The app's "ride sent" notification opens that ride, and the log's ride once the log has it.
- On Log Files in the app, the logs still on your phone are listed at the top, and each appears below as soon as it is uploaded.
3.83.0
23 October 2026Tell us about a problem straight from the Android app, and more tyre sensors work with it.
Added: New in this release
- In the Android app (0.20.0, in testing), "Report a problem" sends us your words as a ticket, with the app's technical log if you agree. You read the answer by email and on the Feedback page, and a log attached to a ticket shows there as a file.
- If the app closes unexpectedly, the error stays on your phone and the app offers to send it the next time it opens. Nothing goes without your OK.
- The app reads more kinds of Bluetooth tyre sensors: SYTPMS, iTPMS, FOBO, HRTPMS and TC.TPMS. If yours are not recognised, the tyre screen can record them for us.
Changed: Different from before
- The privacy policy says what a problem report from the app contains.
3.82.0
23 October 2026The Android app, in testing, now connects to Bluetooth LE motorcycles too.
Added: New in this release
- The ZeroLogs Android app (0.19.0, in testing) connects to the SR/F, SR/S, DSR/X, S/F and the 2024+ S, SR, DS and DSR. It shows the battery, charge, odometer, speed and ride mode, and downloads the bike's logs, always read-only.
- Adding a second motorcycle in the app is easier: "Use another motorcycle" is now a full button.
Changed: Different from before
- The Bluetooth protocol guide now explains how the newer motorcycles' Bluetooth LE link works, and which messages only read and which would change the bike.
3.81.0
23 October 2026If your bike's clock is set to the wrong time zone, you can now correct every time from its logs.
Added: New in this release
- On your bike's page, "The bike's clock" lets you say how far out the times on your rides are, in quarter hours. Every ride, charge and trip from that bike's logs moves to the right time within a few minutes, and logs you upload later are corrected too.
- When the app has measured your bike's clock against its own readings, the card offers that correction as a single button. Nothing changes until you press it.
3.80.0
23 October 2026Text logs saved with Zero's Log Decoder now upload.
Added: New in this release
- Log files exported as text by Zero's Log Decoder now upload and show their rides, charges, temperatures and charger readings. Before, they were refused with a message about a console command.
Fixed: Was wrong, now is not
- Battery logs from those text exports showed their times one or two hours late. They now show the real time.
3.79.1
19 October 2026On a bike that changed hands, each owner sees only the routes they recorded.
Fixed: Was wrong, now is not
- If a bike had more than one owner on zerologs, the later owner could see routes the earlier owner had recorded, on ride and trip pages and in their own shared links. Now a route is shown only to the account that recorded or uploaded it.
3.79.0
19 October 2026Download a ride: GPX, FIT, a second-by-second CSV, or every source as recorded.
Added: New in this release
- Each ride and recorded ride has a download card: a GPX with the bike's readings alongside each position, a FIT with the route for training apps, a CSV with one row per second and both clocks, or a ZIP with every source as it was recorded. Only you can download your rides.
3.78.0
19 October 2026One chart per quantity, every source on it, and a strip to zoom down to 20 seconds.
Added: New in this release
- On a ride, trip or recorded-ride page, speed, battery charge, power, voltage and temperatures each have one chart that draws every source together — the bike's log, the app over Bluetooth and the phone's GPS.
- A strip under the charts picks the stretch to look at, down to 20 seconds, where every single reading is drawn; the figure cards above then show that stretch: distance, energy, top speed and peak power.
3.77.0
19 October 2026Every chart on a ride or trip now says where its numbers come from.
Added: New in this release
- Each chart on the ride, trip and recorded-ride pages has a legend: the unit, one line on what it shows, where the readings come from (the bike's log, the app over Bluetooth, the phone or a route file) and how dense they are in the part you are looking at. A tap hides or shows each line.
Fixed: Was wrong, now is not
- Speed and torque from older bikes' logs, and figures worked out from a route such as acceleration, are now marked as computed rather than as the bike's own readings.
3.76.0
19 October 2026Tyre pressure sensors in the tyre guide.
Added: New in this release
- The tyre guide explains Bluetooth tyre pressure sensors: how they broadcast their readings, the eight types decoded by the open-source project we build on, and what the ZeroLogs Android app, now in closed test, does with type A sensors.
3.75.0
18 October 2026A beta page for riders who like to look under the hood.
Changed: Different from before
- The beta page is now where early builds land first, starting with the Android app: how its data moves, the exact list of what it may ask your motorcycle and what it never sends, which Zero gets what, and the Android permissions with the reason for each.
- Links to the beta page now show the app in their preview.
3.74.0
18 October 2026Groundwork for denser ride charts: nothing changes on the pages yet.
Changed: Different from before
- The site can now gather every reading of a ride or trip on one clock, in a single request: the app's, the phone's and the bike log's. The ride and trip charts move onto it in the next releases.
3.73.0
18 October 2026A full guide to tyres on a Zero.
Added: New in this release
- The tyre guide now explains what too little or too much pressure does, why the gauge reads higher after a ride, how much range a soft tyre costs, how compound, construction and cornering work, and how the AI ride verdict uses tyre data, with drawings that also read well on a phone.
- Zero's original tyres are shown as cards with the size, load and speed rating and the cold pressure in the unit you choose (bar, psi or kPa).
- Each model's page shows its original tyres and pressures, with a link to the tyres made in the same sizes.
- The tyre catalogue can be filtered by your Zero's sizes, category, maker and construction, with each maker's own size list.
Changed: Different from before
- The range calculator and the ride verdict now use the same published figure for how tyre pressure affects rolling resistance, so a soft tyre costs a little less range than before in the calculator.
3.72.0
18 October 2026Help test the Android app.
Added: New in this release
- A new page explains how to join the closed test of the ZeroLogs Android app on Google Play: three steps, what we ask of testers, and which Zero connects over Bluetooth today.
Changed: Different from before
- The privacy policy says how the testers group of the Android app is handled: only its managers and Google Play can see who is in it.
3.71.0
18 October 2026One cursor across a ride's charts and its map, and a clear line where a shared route is hidden.
Added: New in this release
- On a ride or trip page, pointing at any chart now moves the cursor on every chart and the marker on the map to the same moment, whether the reading came from the app, the phone or the bike's log.
- When a shared trip hides a ride's route because it changed after the link was made, the public page says so in one line instead of showing an empty map, and your shares page tells you which links are affected.
Fixed: Was wrong, now is not
- In the Android app (0.18.1), stopping a ride could close the app.
3.70.0
18 October 2026Delete your account yourself, a privacy policy that covers the app, and a tyre guide.
Added: New in this release
- You can delete your account from Profile, on the website and in the app: type your password, confirm, and the account goes with everything in it. A public page explains how, what is deleted at once, how to delete only some data, and how long the encrypted backups keep a copy.
- A new guide to tyres: the tyres and cold pressures Zero fitted to each model-year, and the replacements riders use, by category.
Changed: Different from before
- The privacy policy now describes the Android app — location only while you record a ride, Bluetooth only to your own motorcycle — and names every service that handles your data and what it receives.
Fixed: Was wrong, now is not
- Deleting an account now also removes your address from our newsletter records, and a newsletter still being sent no longer reaches a deleted account.
3.69.0
18 October 2026Tyre pressure sensors in the app, and your tyres' history on the site.
Added: New in this release
- The ZeroLogs app reads Bluetooth tyre pressure sensors (the "TPMSII" kits): pair them in the Bike tab, where front and rear are proposed from the sensors themselves. On the ride dashboard both pressures sit in one line, a tap when stopped shows each tyre, and a leak or a very low tyre goes to the banner.
- Every new tyre reading is kept with the ride. Ride pages draw the tyres over the ride, and the bike page shows each morning's pressure over the months, how fast each tyre loses air, and when it will be low.
- The AI ride verdict reads the measured pressures. It says how much they can explain of the consumption, which is small, and never more than that.
- A ride recorded with the phone alone now uploads: after the ride, the app asks which of your motorcycles it was.
3.68.2
18 October 2026The ride verdict checks your tyres against the right pressure.
Fixed: Was wrong, now is not
- The ride's AI verdict now checks your tyres against the pressure you set in your bike's profile, or, if you set none, against Zero's own owner manual for your model and year (36 psi on a 2024 S, 32/34 on an FXS). Before, a rider with no pressure set was compared with a made-up 29/32 psi.
3.68.1
18 October 2026A trip you shared keeps the map it was shared with.
Fixed: Was wrong, now is not
- A shared trip's map no longer changes after you share it. If you later add or replace the route of one of its rides, the link hides that part instead of showing the new one.
3.68.0
18 October 2026Rides from the app show up before their log, and report pages load faster.
Added: New in this release
- A ride you record with the ZeroLogs app appears in Trips and on your timeline straight away, as its own card, before the motorcycle's log is uploaded. When the log arrives, the two become one ride.
Changed: Different from before
- Report pages load their charts with one request per log instead of one per chart.
- Updating ZeroLogs no longer throws away the pages it had already worked out, so the first visit after an update is as quick as any other.
3.67.0
17 October 2026How a Zero talks over Bluetooth, explained from real recordings.
Added: New in this release
- A new Learn guide explains how a Zero talks over Bluetooth: how the link works, every command we know and what each reply holds, and how a log is downloaded block by block. Its charts and diagrams are drawn from real recordings of a 2016 FXS, and every row says whether it was measured or is not yet confirmed.
3.66.0
16 October 2026Faster report pages, charts you can zoom everywhere, and a site that fits your phone.
Added: New in this release
- The ride and trip pages' charts zoom too — drag across one, or use − and + on a phone — and every chart follows.
- Once the motorcycle's log is uploaded, a ride keeps what the app read during it, about once a second, under the log's own charts.
Changed: Different from before
- Report pages and the log viewer load much faster: they now read only the days each log covers.
Fixed: Was wrong, now is not
- The whole site no longer pauses while an AI analysis is being written.
- A photo taken from the app's ride dashboard lands on the ride it was taken during, even when the motorcycle's clock runs fast or slow.
- Pages fit a phone with a larger text size: no more page wider than the screen, and no more text squeezed into a narrow column.
- The trip page's motorcycle charts now show the time along their axis.
3.65.0
16 October 2026A ride recorded by the app opens right away, with every reading, before the motorcycle's log.
Added: New in this release
- A ride the app recorded can be opened from Trips before you upload the log: its route, battery, cells, temperatures and both speeds, about once a second.
- On that ride, the charts zoom — drag across one, or use − and + on a phone — down to every single reading.
- Maps say where a trip started and ended, at what time, and where it stopped and for how long.
- At night the weather in the app shows the moon instead of the sun.
Fixed: Was wrong, now is not
- Pages no longer break on a phone with a larger text size: titles, buttons and headings stay inside the screen.
3.64.0
16 October 2026The trip page shows what your motorcycle's own log said during each ride.
Added: New in this release
- A trip now lists what the motorcycle's log recorded during each ride — key on, contactors, current limits, warnings and errors — with repeated lines folded into one.
- Rides recorded by the app that are still waiting for their log say what only the log adds: the motor and controller, errors and events, the odometer.
- The Android app speaks Italian, has a high-contrast mode for riding in the sun, and shows the ride dashboard in two columns when the phone is mounted sideways.
Fixed: Was wrong, now is not
- The app's download panel now names the models that connect over classic Bluetooth instead of a wrong year range: the S, SR, DS and DSR up to 2023 and the FX, FXS and FXE.
3.63.1
16 October 2026Fixed: Was wrong, now is not
- Placing your recorded routes on their rides after an upload could stop half way; it finishes again.
3.63.0
16 October 2026A bike's clock drifts; your routes now follow it.
Fixed: Was wrong, now is not
- The clock correction measured from your battery now applies to the rides around the day it was measured, so older routes keep the correction that fits them.
3.62.0
16 October 2026Your routes land on the right ride, even when the bike's clock is off.
Added: New in this release
- zerologs now measures how far your Zero's log clock is from real time, from the battery's charge the app reads while you ride, and places the app's routes on their rides with that correction.
- Your bike's page shows what the motorcycle reported to the app: the firmware of every board, and how far its log's clock runs from real time.
- The Android app (in testing) downloads the battery's log too, names the motorcycle's own readings (odometer, trips, the dash's range, speedometer) and shows active faults.
Fixed: Was wrong, now is not
- Logs downloaded by the app with blank memory pages now come out whole.
3.61.0
14 October 2026A dashboard for the kind of ride you are on.
Added: New in this release
- The Android app's ride dashboard (in testing) has presets — Trip, Sport and City — shows the weather where you ride, with the wind as you meet it, and uses the units of your zerologs profile.
3.60.0
14 October 2026What a new file brought, and a dashboard you can read on the move.
Changed: Different from before
- When the Android app tells you a downloaded log is ready, it now opens that file on Log Files — what it added to what you already had — instead of the whole report.
- The app's ride dashboard (in testing) says whether you can still get back to where the trip started, in green, amber or red, and tells the pack's temperature apart from the electronics'.
3.59.0
13 October 2026A screen for the handlebar.
Added: New in this release
- The ZeroLogs Android app (in testing) gets a ride dashboard of its own, locked while you ride: the energy left and the range at your pace, consumption, the grade, the climb and the weakest cell — things the bike's own dash does not show.
- A photo taken from the ride dashboard goes onto that ride's trip on the site by itself, once the motorcycle's log of the day is uploaded.
- The phone stays awake for the whole ride, and any moment the GPS dropped out is counted and shown instead of turning up as a hole on the map.
3.58.0
13 October 2026Share a ride live, and let the app start and stop rides for you.
Added: New in this release
- Share a ride live from the ZeroLogs Android app (in testing): a link that shows where you are and the road so far, for as long as you choose. Nothing near where you start is shown, the battery only if you want, and nothing is kept once the link ends.
- The app can start and stop rides by itself: ride off with the motorcycle connected and it records; stop for a few minutes or switch the bike off and it ends.
- A ride recorded with the app appears in Trips straight away, with its route, while it waits for the motorcycle's log.
- Help decode Zero motorcycles with a Bluetooth capture of the official Zero app: only the messages with the motorcycle are kept, never the file you upload.
3.57.0
13 October 2026Help decode Zero motorcycles.
Added: New in this release
- An optional "Help decode Zero motorcycles" setting, in the Android app and on your Profile: your motorcycle's raw Bluetooth readings (never your position) help name the values nobody has decoded yet, by comparing many motorcycles. Off unless you turn it on, and you can turn it off at any time.
- Inside the app, My Bikes and the Dashboard show the motorcycle paired with your phone, one tap from its live screen.
3.56.0
13 October 2026The Android app: easier pairing, clearer choices, a real ride screen.
Added: New in this release
- In the ZeroLogs Android app (in testing): pairing guided step by step with Zero's own instructions, the bike linked to its page in My Bikes, and two clear choices — Ride or Download logs — with what the MBB and BMS logs contain.
- Rides recorded with the app get a live screen (speed, distance, battery, energy, altitude), a summary at the end, and elevation from the phone's barometer on the route.
- The app shows everything the motorcycle reports over Bluetooth, and can record a session to help decode what is still unknown.
3.55.0
13 October 2026A ride recorded with the app gets its route on the site.
Added: New in this release
- A ride recorded with the ZeroLogs Android app (in testing) adds its GPS route to the same ride from your motorcycle's log: right away if that day's log is already uploaded, or as soon as it is. One ride, never two.
- The app shows a downloaded log's upload as it happens, and tells you when a recorded ride is kept on the phone and when it has been sent.
- Phone recordings that were waiting for their ride now join it by themselves when the motorcycle's log arrives.
3.54.1
13 October 2026Log Files and the timeline, faster and readable in the app.
Fixed: Was wrong, now is not
- Log Files opens much faster in the Android app: opening the app no longer throws away the pages it had already prepared, and a new upload only recomputes the new file.
- On a phone the timeline shows your rides and charges day by day right under the figures, instead of after several other cards and a chart that was unreadable at that width.
3.54.0
13 October 2026The Android app is one app: one bar for your motorcycle and your account.
Added: New in this release
- In the ZeroLogs Android app (in testing) the motorcycle screen and the site now share one bottom bar with the site's icons, and switching never opens a new screen.
- The app can record a ride: GPS, the phone's motion sensors and, when connected, the motorcycle's battery readings. Without internet the ride waits on the phone and is sent later.
3.53.0
12 October 2026The Android app opens on your motorcycle.
Added: New in this release
- The ZeroLogs Android app (in testing) now opens on a screen for your motorcycle: pair it from the app, see its battery, cells and temperatures live, and download its log with every step shown. The rest of the site is one tap away.
3.52.0
12 October 2026Logs downloaded with the Zero app say what they are missing.
Added: New in this release
- A log downloaded with the official Zero app is marked "Gaps from the Zero app": that app loses some records around the motorcycle's pauses while it downloads. The rest of the log is read as before, and the ZeroLogs Android app downloads the complete log.
3.51.0
12 October 2026The Android app learns to read the motorcycle.
Added: New in this release
- The ZeroLogs Android app (in testing) can download the log straight from a Gen2 Zero over Bluetooth and upload it for you — read-only, it never changes a setting on the bike.
3.50.0
12 October 2026Links from our emails open the Android app.
Added: New in this release
- With the ZeroLogs Android app installed, the sign-in, verification and password-reset links in our emails, and links to your reports and dashboard, open in the app instead of the browser.
3.49.0
12 October 2026Easier to read on a phone.
Fixed: Was wrong, now is not
- On a phone, small labels and chart axes are no longer printed below a readable size, and the batteries page no longer scrolls sideways.
3.48.0
12 October 2026Uploading from the Android app, offline included.
Added: New in this release
- In the Android app, logs you pick or share to it ("Share → Zero Logs" from the Zero app or Files) wait on the phone and upload by themselves when there is a connection, even with the app closed. A notification tells you when each log has been read and what it contains, and opens the report.
3.47.0
12 October 2026The timeline reads on a phone, and the site is ready for the Android app.
Added: New in this release
- Devices & API lists the phones running the zerologs Android app on your account, and removes one in a tap: it is signed out and can no longer upload, while everything it uploaded stays.
Changed: Different from before
- On a phone, the timeline's month and week views are a list of the days you rode or charged, one readable row per ride or charge, instead of a seven-column calendar too narrow to read.
3.46.1
12 October 2026A fix for the Android app that is not out yet.
Fixed: Was wrong, now is not
- The message telling an out-of-date Android app to update now reaches it, instead of being dropped by the connection on the way.
3.46.0
11 October 2026A correction to the console-log guide, and groundwork for an Android app that is not out yet.
Added: New in this release
- The developer documentation lists the two errors the coming Android app can receive: an app too old to keep syncing, and a device that already records a different kind of data.
Fixed: Was wrong, now is not
- The console-log guide no longer says older Zeros talk Bluetooth LE: their built-in radio is classic Bluetooth serial, and Bluetooth LE is the radio of the SR/F generation.
3.45.1
11 October 2026Small finishing touches to the redesign in 3.45.0.
Changed: Different from before
- Buttons respond when you press them, and pages no longer keep moving once they have loaded.
Fixed: Was wrong, now is not
- The cookie banner no longer says we use marketing cookies — we never did, as the cookie policy already said.
- Every row in a battery's charge list can be opened from the keyboard, and screen readers get a cleaner page outline.
3.45.0
11 October 2026A cleaner, calmer site: the guides are easier to find, the home page shows a real bike, and the colours mean one thing each.
Added: New in this release
- The Learn hub starts from your question — a dash code, a log line, how to download a log — and lists every guide by topic on the first screen. Long guides have a table of contents on phones.
- The log catalog finds a line when you paste it as your bike wrote it, and shows what each problem looks like in a log.
- The home page shows the demo bike's real readings from its own logs, and links to how to download a log if you have never done it.
Changed: Different from before
- Colours have one meaning each across the site: charging is blue, riding is green, anything an AI wrote is gold. The timeline used to draw them the other way round.
- The sidebar is grouped into four sections, and each page has its own title in the browser tab.
Fixed: Was wrong, now is not
- Dash-code pages tell you first when the same number means a different fault on the other dashboard, before any "do not ride" warning.
- Reading times on the guides are now measured from their length; the old ones were well short.
- Numbers and dates use one format everywhere, and buttons and menus are announced properly by screen readers.
3.44.0
11 October 2026A health page for each bike, a warning when the onboard charger stops waking it, and a range estimate that starts from your own battery.
Added: New in this release
- The range calculator can start from your own bike: one tap sets the model, the year and your battery's measured health, instead of assuming a new pack.
- Each bike has a Health tab: one tile per part, coloured only by problems that are still active, and grey rather than green when the logs are too old to say anything.
- A new check notices when the onboard charger has stopped waking the bike while it is still being ridden and charged some other way. It comes with a five-minute test you can run before any part is replaced, and your answer counts even if you never upload another log.
Fixed: Was wrong, now is not
- The PDF export of a bike bought second-hand no longer includes the previous owner's rides or kilometres.
- The PDF now says where each number comes from — measured, estimated from the state of charge, or reconstructed between two logs — and which model wrote its verdict.
- When we re-read logs you had already uploaded, a change in battery health is now shown as our correction, not as new charges or a change in your pack.
- On small phones the Learn page no longer scrolls sideways, the model catalog shows its first bike sooner, and its pictures no longer carry the cover text of Zero's manuals.
3.43.0
11 October 2026Share your bike's valuation report with a buyer, and rides and charges that finally keep to their own times.
Added: New in this release
- Publish your bike's valuation report as a link for a buyer, with your service book beside it. It is frozen on the day you publish, expires after 30, 60 or 90 days, and the only choice is how much of the VIN it shows.
- The link opens as a printable report, and its preview card in chats names the model, year and date — never the VIN.
Fixed: Was wrong, now is not
- On Gen3 bikes a ride no longer runs through a charging stop: the battery's own log kept the ride open while the bike charged, and its window could hide a whole second ride.
- Charges that had been merged across a ride into one long session are split back into the plug-ins they were.
- A key-on that only powered the bike's own systems is no longer counted as a ride.
- The coverage section of the valuation card no longer says "Partly hidden" where it means "a few months".
3.42.0
10 October 2026Charges taken with the bike switched off now show up, and a ride and a charge no longer sit on top of each other.
Fixed: Was wrong, now is not
- A charge taken with the bike disarmed is read as a charge: its current was decoded as a large discharge, so the charge was missing and a parked bike could look like it drew 25 kW.
- Many Gen2 charges now record the state of charge they ended at, so they count towards battery health and show whether they reached full.
- Where a ride and a charge overlapped on the timeline, the charge now gives way to the ride; regeneration on a descent is no longer listed as a charge.
- Charger log lines are no longer all filed as "Charger undervoltage"; a charger over-current trip has its own entry, and the "Contactor Welded" log line is explained and told apart from the dash error 26.
Changed: Different from before
- The footer shows one service status instead of naming the systems behind it.
- The log error catalogue folds: each entry opens on a tap, and a link to an entry opens it.
- Profile fields stop at the length the site keeps, instead of being cut after you save.
3.41.0
10 October 2026A dashboard that shows everything about your bike, a service book you can hand to a buyer, and battery health over time.
Added: New in this release
- The dashboard is shaped by your garage: with one bike it leads with that bike, with several it compares them worst-first, and every section of the site has a card with its key figure and a link into it.
- Battery health over time: the battery page draws how your current pack's health has moved, says in one sentence whether it is stable or declining, and tells you when the figure changes and why.
- The maintenance page is now a service book: Zero's scheduled services in order, each stamped by your entry for it, with the next one and anything due by date marked.
- Print or save your service book as a PDF on zerologs letterhead, choosing whether costs, workshop names, notes and your name are included.
- When a battery swap also changes how many modules your bike runs, the bike page now offers to record the wiring change too.
Changed: Different from before
- "Needs your attention" only lists problems that are still current: faults from before a repair you recorded, or not seen in your logs for a month, move to a separate list of past faults.
- The bike you choose is remembered across Timeline, Trips, Charging, Batteries, the log viewer, log files and the service book, with one picker on every page.
- Adding a service entry is a short two-step form: the essentials first, the optional details after, and you can save after the first step.
- Trips and log files list which bike each entry belongs to when you have more than one.
Fixed: Was wrong, now is not
- My Bikes no longer opens empty when the page is loaded directly.
- The service book's Export now downloads a readable spreadsheet instead of an error page.
- Upload buttons on My Bikes, Reports and Log Files open the upload page instead of the home page.
- On a phone, dialogs are no longer partly hidden behind the bottom bar.
3.40.2
5 October 2026Your battery health and dashboard now count only the logs you uploaded.
Fixed: Was wrong, now is not
- If another account has uploaded logs of the same motorcycle, such as a previous owner, their charges and rides no longer enter your battery health, your dashboard totals or the battery assistant. Your own downloads still carry the battery's earlier history.
3.40.1
5 October 2026Battery health now reads the same on the dashboard, the battery page and every pack card.
Fixed: Was wrong, now is not
- A pack's own health card now counts the same charges as the battery page, including those logged before the pack's serial first appeared in a download.
- When the only pack your logs have ever shown is a replacement, charges from the battery it replaced are no longer averaged into its health.
- An FX, FXS or FXP with no pack size on file no longer shows a guessed health figure on some screens and none on others: every screen shows the measured capacity and says the pack size is not known until you declare it.
- The battery page loads quickly again on bikes where it could take minutes or fail.
3.40.0
5 October 2026Your battery page now recognises a replaced pack, a Power Tank or an unlocked capacity, and measures each battery against itself.
Added: New in this release
- My Batteries suggests what the logs show about your pack: a replacement newer than the bike, a Power Tank, or an unlocked capacity on a 2022-or-later SR, SR/F or SR/S. Nothing changes until you confirm, and a suggestion you dismiss is not offered again.
- Confirming a replacement dates the swap, and your history is split there: the old pack and the new one each get their own health figure, measured against their own capacity.
- Every battery card now says which capacity its health is measured against and when that pack was fitted.
Changed: Different from before
- A Power Tank is shown as part of the whole battery instead of being split into modules no label carries.
- Battery Health on Learn explains how a pack change is recognised and dated.
3.39.6
5 October 2026Battery health reads the same on every page again, and the Learn pages explain what we found.
Changed: Different from before
- Battery Health, Charging, Anatomy of a Log and Buying a Used Zero now explain why a used pack can read above 100%, why the main board and the battery can disagree about the same charge, and why some start-up lines in a log have no time of their own.
Fixed: Was wrong, now is not
- On bikes with more than one battery module, the dashboard and the battery page could show two different health figures for the same pack. They agree again.
- When a health figure above 100% is withheld, the explanation now says the likely reason: the pack on file is often not the one fitted, such as a replacement, a Power Tank or an unlocked capacity.
3.39.4
5 October 2026Fixed: Was wrong, now is not
- Some charges on older main-board logs that disappeared in 3.39.0 are back: the first reading of a charge could carry the state of charge from before the charger started, which made a real charge look like it added nothing.
3.39.3
4 October 2026Fixed: Was wrong, now is not
- Bikes with more than one battery module, such as an FX or FXS with a Power Tank, measure battery health from all of their charge records again: the battery's own records can describe one module only.
3.39.2
4 October 2026Battery health no longer mixes two meters, and never shows more than 100%.
Fixed: Was wrong, now is not
- Battery health on older bikes is now measured from the battery's own charge records when there are enough of them, instead of blending them with the main board's, which read the same charges 12-24% higher. Several bikes move by a few points.
- A battery health figure above 100% is no longer shown on any bike: a used pack cannot hold more than it did new, so the figure is marked as not reliable. The measured capacity is still shown.
3.39.1
4 October 2026The log files page opens faster.
Changed: Different from before
- The log files page is prepared in the background whenever your data changes, so its coverage calendar and your newest files' details are ready when you open it instead of being built while you wait.
3.39.0
4 October 2026Logs are now read with the latest community parser, rides cut in two by a misdated start-up are whole again, and the log files page shows your coverage at a glance.
Added: New in this release
- The log files page opens with a calendar of every day your logs cover, and each file shows only its own dates, how densely it logged and which measurements it carries, with a button straight to those rows in the log viewer.
- Six more fault and warning types are recognised and explained, among them a controller that failed to precharge and battery temperature limits.
Changed: Different from before
- Logs are now read with the latest version of the community log parser, so more older main-board messages come out with their proper names.
- The decode-coverage section of this page is now a set of charts per platform, with a legend you can open when you need it.
Fixed: Was wrong, now is not
- Start-up messages that carry no clock of their own no longer cut a ride in two or stretch it across a parked night, so rides that were split into pieces come back as one, with their full distance.
- A ride that never closed in the log no longer adds its distance to a real ride nearby.
3.38.0
3 October 2026Every log file now shows what it holds and how it was read, and older main-board logs that came out nearly empty are read in full.
Added: New in this release
- Each log file opens a card with what it is (board, model, firmware), how it was read, what it added that you did not already have, and a timeline of the time it covers, gaps included.
- The log viewer shows a year of your data day by day, like a contribution calendar: each day takes the colour of riding, charging or parking, with a marker on days that logged warnings or errors. Select a day to open it.
- This page now shows what the parser decodes for each kind of log, measured over every file stored here.
- The Learn pages on newer Zeros' logs go into much more detail: how each record is laid out, the bytes the battery's flash overwrites, and how this decoder compares with the community parser.
Fixed: Was wrong, now is not
- Main-board logs from older S, DS, FX and similar bikes that came out almost empty are now read in full. Thousands of rides, days and odometer readings come back, and "charges" that were really key-on messages are gone.
- Battery health is now measured from one log at a time, so a charge's energy and its state of charge always describe the same stretch of time. Several bikes' figures move, most by a few points.
- On older bikes, battery charge energy keeps the precision the battery records instead of being rounded down to whole amps.
- On newer Zeros a battery-health figure above 100 % is no longer shown; it is marked as not reliable until the measurement is understood.
- A pack replaced on a date you declared no longer has older readings mixed into its health figure, and a pack named twice in a log is no longer counted as two.
- Battery messages that were lost or cut short on newer Zeros are now kept.
- The log viewer fits on a phone screen.
3.37.0
3 October 2026Logs from newer Zeros — SR/F, SR/S, DSR/X and every 2024 or later model — are read more completely, and more honestly.
Added: New in this release
- Battery logs from newer Zeros now show every message the battery wrote; about half of them were being missed. Logs you already uploaded are being re-read with this change.
- Your bike's firmware and board revision are now read from newer logs instead of being left blank.
Fixed: Was wrong, now is not
- On newer Zeros the battery log rewrites a few bytes at fixed places in the file. Values caught there are now left out instead of shown wrong: they had produced phantom readings, phantom rides and days that never happened.
- The VIN decoder gives the right battery size for 2024 and later models, which follows the model as Zero's manuals do, and for the 2016 FX and FXS.
- Where Zero's manuals print a different rated power for Europe and for the rest of the world, the VIN decoder now shows both instead of picking one.
- The in-browser log decoder now gives the same results as your uploaded reports for newer Zeros.
3.36.0
27 September 2026Every log file now tells you what it actually added — right in your file list.
Added: New in this release
- Each file in your file list shows how its time splits between what you already had and what is new, and what its rows are: riding, charging, parked, warnings. The bars load as you scroll, so a long list stays quick.
- Open any file's breakdown from the list, or from the new "This file" tab on its report: how many days, rides and charges it brought that no earlier file of yours had, and a short list of checks on how completely we could read it. Those checks are about the file and our decoder, never a verdict on your motorcycle.
- The status page now shows your data's off-site backup, and when it last succeeded.
Fixed: Was wrong, now is not
- The report page is usable on a phone: the side panel sits above the charts instead of squeezing them to a sliver.
- Dates on a few pages followed your browser's language while everything around them was English. They now use the same format everywhere.
- Some guide and Learn pages scrolled sideways on a phone. They no longer do.
- A file processed while others were being read at the same moment could wait a full minute before trying again. It now retries within seconds.
- The status page described the servers of a setup we have not moved to yet. It now draws the one that answered your visit.
3.35.0
18 September 2026Your maintenance page now starts from what the app already knows about your bike — and the timeline draws your own work, not just Zero's plan.
Added: New in this release
- The maintenance page now offers the things the app had already worked out elsewhere and was keeping to itself: a pack change your logs show, and the battery you declared in your bike's profile. It asks you to confirm each one rather than writing it for you.
- It also says which kind of record each one is — something you typed, something confirmed from a dated record, or something your logs show but cannot date. A buyer reading your service history can tell them apart, and should be able to.
- Your own service records are drawn on the schedule timeline. Jobs done on the same day sit together as one mark you can click, and clicking it shows exactly those records below.
- The lane says how many records it drew and how many it could not. A job with no odometer reading is never placed at a guessed position — it is counted and listed instead. Readings are never taken from your logs.
Fixed: Was wrong, now is not
- The timeline had too much empty space and marks too small to hit. The marks are larger, they have a touch-sized target around them, and the top of the chart is now your own history rather than blank axis. With thirty records it stays readable on a phone as well as a desktop.
- A record offered from your logs no longer claims a date it does not have. Zero's downloads repeat old events, so the last time we saw a pack is not the day it came out — the page says so and asks you to correct it.
- The battery you declared in your bike's profile was never offered as something fitted, so a history could say two packs came out and none went in.
- A pack change found in your logs no longer puts the pack's serial number in the record title, where it would have been published on a shared page. The serial is still shown to you, on your own page, where it belongs.
- That same record was being dated from the wrong end of what the logs show — the newest download rather than the first sighting of the new pack, which on a real bike was four years out. It now proposes the earliest date the change can have happened, and still asks you to correct it.
- A shared service history now labels records the app observed in your logs, instead of showing them as if you had typed them yourself.
- Switching between your motorcycles now clears the search, the filter chips and any timeline selection, instead of carrying one bike's filter onto another.
3.34.0
17 September 2026Your warranty, read out of Zero's own manual — and a maintenance page that stops treating a used bike as neglected.
Added: New in this release
- The maintenance page now shows what Zero's manual prints as your warranty: how long the motorcycle is covered, how long the battery is, and — on 2014 to 2016 bikes — the mileage cap that can end the battery term before the years do. It names the manual and page it read, and it says "ends no earlier than" rather than a date, because the clock starts the day the bike was first sold and we only know its model year.
- It also tells you the two things nobody expects: on most model years the pack's outer case is covered for two years while the pack itself is covered for five, and the warranty follows the motorcycle rather than the owner — so it carries over when you buy or sell used, once the transfer form is filed.
- Every service record now carries an icon for what it was, so a long history reads at a glance.
- A public API for third-party devices: anyone building a Zero dongle or app can now send data in with their own key, with scopes and a per-vehicle grant so a key can only ever do what you allowed.
Fixed: Was wrong, now is not
- A bike bought used no longer looks neglected. Services nobody has recorded were being counted from zero, so a motorcycle at 20,000 km was told its 160 km break-in service was 19,840 km overdue — in red, at the top of the list, permanently. Those rows are still shown and still say they are counted from zero, but they are no longer presented as something you have failed to do.
- The page now says when a service is due on the CALENDAR, not only on distance. A yearly service more than two years late was printing how many kilometres remained, which contradicted itself.
- The first two dealer services both read "Dealer service" and nothing else. They now say which service they are, whether they have been recorded, and roughly when your bike passed that reading.
- If you read in miles you were shown some intervals rounded into figures Zero's manual does not print — 1,250 miles appeared as 1k, 3,100 as 3k. You now see Zero's own numbers.
3.33.0
17 September 2026A service book for your motorcycle: what the manual says to do, what you actually did, and a version you can hand to a buyer.
Added: New in this release
- Maintenance is a new section in your dashboard. Record what was done, when, at what reading, what it cost and who did it — against Zero's own schedule for your model, so you can see what is due and what has been done. Every Zero owner manual ends with a blank service-history form; this is that page, with the totals worked out for you.
- Parts can be picked from Zero's own catalogue — 1,010 part numbers and every battery pack — so a line in your history says exactly which part. Anything no catalogue carries, like tyres, a top box or a seat, is typed in beside it and recorded just as well.
- Your bike's own data is read for services you may not have written down. A battery in your garage with an install date, or a hardware change you have already declared, is offered as an entry for you to confirm or dismiss. Nothing is ever added without you, a confirmed entry stays marked as found-in-your-data rather than typed by you, and a dismissed one stays dismissed.
- A shared bike link can now include your service history, if you switch it on. It is meant for a buyer: dates, readings, parts, costs and your notes — never the name of your workshop. What gets published is frozen the moment you create the link, so anything you add or edit afterwards does not appear on it.
- Where the intervals fall in time, not just in kilometres. If your logs carry an odometer we show roughly when your bike passed each service point. Where the logs have a gap we show the range instead of a date, and where there is no odometer at all we say so — most Zero logs do not carry one.
- Your whole service book downloads as a spreadsheet, with everything in it.
- Two new Learn articles: “Zero's service schedule for every model”, with the intervals drawn on a distance axis and the manual page behind each plan, and “what every noise on a Zero means” — squeals, hums and creaks traced to the manuals, including the ones Zero says are normal, and why a Zero's belt is never oiled.
Changed: Different from before
- The AI now knows what you have had done before it suggests maintenance. It was recommending work you had already completed, because it had never been told.
3.32.7
17 September 2026A scary-looking error in our own logs that was never an error.
Fixed: Was wrong, now is not
- Our server logs printed a six-line error report every time a service started, from one library checking the version of another. It was caught and handled the moment it happened and nothing was ever wrong, but it sat directly above the lines that would show a real problem. It no longer prints, and genuine failures from that library still do.
3.32.6
17 September 2026Follow-up to 3.32.5: the AI's thinking room, measured properly.
Fixed: Was wrong, now is not
- The room we give the AI to think before answering was set from a handful of samples. Measured properly against real traffic, the thinking varies about sixfold from one call to the next while the answer stays the same length, so the allowance is now sized above the worst case we actually observed rather than the typical one.
3.32.5
17 September 2026The AI was being cut off mid-thought, and two safety checks were reading the silence as an answer.
Fixed: Was wrong, now is not
- The AI models we use now think before they reply, and that thinking counts against the same length limit as the answer itself. Several checks were given a limit sized for the answer alone, so the model ran out of room and replied with nothing at all — which looked like success. Every AI call now has room to think, and an empty reply is treated as a failure instead of an answer.
- The check that screens notes you write for hidden instructions aimed at the AI was one of those, and an empty reply was being read as approval. It now reads a real verdict, and refuses the note if it cannot get one.
- An AI analysis that took too long was being killed outright, leaving the report stuck on "analysing" forever with nothing to tell you it had failed. It now stops cleanly, marks itself failed and retries.
- We were asking our AI provider for a model that was quietly retired months ago; it was being answered by a different one the whole time. We now ask for what is actually served.
- The riding-style card counted a charge as complete at 95% of full, where the rest of the site uses 99% and can tell "we were not told" apart from "not full".
3.32.4
13 September 2026One more number that could be thrown out by an impossible clock.
Fixed: Was wrong, now is not
- A trip's average speed could be dominated by a single ride whose recorded duration was impossible — the kind the site already sets aside everywhere else. It now uses only the rides whose clocks can be believed, on your own pages and on a trip you shared publicly.
3.32.3
13 September 2026A sweep of the site's own self-checks, and the five things they were missing.
Fixed: Was wrong, now is not
- A trip's "moving" time could include a clock no motorcycle could have produced — on your own pages, on a trip you shared publicly, and in the preview image of that link. Trips now use the believable start-to-end window, the way the rest of the site already did.
- Charge time on the costs page could be thrown out by a single impossible stored duration, which also dragged your cost-per-hour towards zero.
- The charging-sessions view excluded unbelievable sessions from one number on the screen and included them in another, on the same screen.
- Photo, avatar, attachment and route uploads now decode a few at a time instead of all at once, and are rate-limited. Enough simultaneous uploads could previously exhaust the server's memory for everybody.
- The charts on a publicly shared trip now carry the same one-line explanation of what they plot that your own pages have — that page is read by people who were not on the ride and cannot ask.
3.32.2
13 September 2026The new link previews now reach the pages that were still missing them.
Fixed: Was wrong, now is not
- Several Learn pages kept showing the old generic preview after yesterday's change, including every one of the 170 error-code pages. They now show their own card like the rest.
3.32.1
13 September 2026Four things the browser was complaining about.
Fixed: Was wrong, now is not
- The Logs page was repeatedly failing to load the ride and charge sessions it uses to link each log line to a trip. A date was being sent in a form the server read as invalid, four times over, every time you opened the page.
- A tooltip on the Logs page had nothing to anchor to, so it could appear in the wrong place.
- On a bike with a single charge, the charging chart drew the same date five times across the bottom of the graph.
- Some leftover debugging output has been removed; it was writing your report's date range into the server log on every render.
3.32.0
13 September 2026Share a Learn page and the preview finally says which page it is.
Added: New in this release
- Every Learn page now has its own link preview. Paste one into a chat and you get that page's title, what it covers, and the one number it is known for — 170 dash codes and log conditions, 503 torque figures, 406 real log lines, 84 model-year belt specifications. Until now they all shared one generic picture, so four different links looked the same.
- A colour down the left edge says which shelf the page is on, so several links in one conversation are told apart before a word is read.
- Individual error codes and parts subsystems get their own previews too. An error-code link leads with the code itself and is tinted by how serious it is; a parts link leads with how many part numbers that subsystem holds.
Fixed: Was wrong, now is not
- The part-number total this site quotes was 1,041 in four places and is actually 1,010. Corrected everywhere, including the Learn page that republishes it.
3.31.2
13 September 2026Diagrams for the weather Learn page.
Changed: Different from before
- The weather Learn page now has drawings. Five of them: the three ways a ride gets a location and what each one is allowed to do, why the town your bike is kept in only describes short rides, how hours are answered when you name a place beside some of them, the single thing weather may do to a fault report, and your bike's own thermometer against the modelled air.
3.31.1
13 September 2026The Learn page catches up with hourly places.
Changed: Different from before
- The weather Learn page now explains how to describe a ride hour by hour, and what it deliberately will not do: no map, no line drawn between the places, no headwind figure, and no pretending that remembering several places is the same as having recorded the route.
- It also corrects what it says about your privacy. It used to say one map reference per ride leaves this site; when a ride names several places, it is one per place — still rounded to about a kilometre, still never your route and never anything that identifies the motorcycle.
3.31.0
13 September 2026Say where you were hour by hour, and each hour gets its own weather.
Added: New in this release
- A ride that passed through more than one place can now be described hour by hour. Open a ride longer than an hour, and under the weather card there is a row for each hour you were out — say where you were in each, and the reading uses that place for those hours. A coastal town and a mountain pass an hour apart are two different skies, and the temperature range will finally say which hour belonged to which.
- You never type a time. The hours come from the ride itself, so all you do is pick a place beside one of them, and "same as above" fills in the hour after without you searching again.
- Hours you did not place are shown as gaps rather than quietly filled in, and the card says how many of your hours it could describe. A place you named can stand for the hour either side of it, and where that happens the row says so.
Changed: Different from before
- Adding places does not turn a ride into a route. There is no map and no line drawn between the towns, because a line between two pins is a road you may never have ridden — and for the same reason a ride placed this way still shows no headwind figure. Only a recorded GPS track can say which way you were pointing, and the card now says that out loud instead of leaving the space blank.
- A ride placed hour by hour is still your own account of where you were, not a measurement, and it is treated exactly like a single pin everywhere it matters.
- If part of a ride could not be looked up, the card will no longer tell you the air was dry or that the bike had been sitting in the sun. Both of those need the whole ride, and the first of them is what removes the "it was probably just damp" explanation from a fault.
Fixed: Was wrong, now is not
- Rain spanning hours that were never looked up is no longer reported as one long shower. A gap in the hours, or a change of town, now ends a spell — so two brief showers in two places stay two showers rather than becoming one that never happened.
3.30.0
13 September 2026Gusts, humidity, the right clock, and a page explaining the whole thing.
Added: New in this release
- Wind now comes with its gusts. The card shows the strongest hourly wind with that same hour's peak gust beside it, because a steady 18 km/h and an 18 km/h average with 42 km/h gusts are different rides.
- Humidity is shown for the hours you were out. It is also the one weather reading allowed to affect a fault report, and only in one direction: if an isolation fault turns up on a day the air was dry, the "it was probably just damp" explanation is removed from that fault's advice. Wet weather never excuses anything.
- The sun icon is no longer drawn on a cloudy day. The reading for cloud cover is fetched and checked before anything claims the bike was sitting in the sun.
- A ride can be asked again. If you add a GPS track to a ride that already has weather from a pin or from where the bike is kept, press "Look it up again" on the weather card and it is recomputed from the better source.
- A new Learn page, "Weather on your rides", explains why a weather card is blank and the three ways to fix it, what the numbers mean and whose clock they are on, why a long ride gets nothing from the town the bike is kept in, what a shared link does and does not carry, and the things the page will never tell you however much you would like it to.
Fixed: Was wrong, now is not
- The hours on the weather card were in UTC and printed as if they were yours. A trip starting at 18:38 could be captioned "coldest at 06:00, warmest at 14:00" — hours it never covered. Times now show on your own clock, the same one as the ride's start time beside them. A reading stored before this fix is labelled UTC rather than silently shifted.
- The Heading chart could report a direction the ride never went. Averaging compass bearings the ordinary way puts the mean of "just west of north" and "just east of north" at due south; it now averages them as directions, so the figure matches the ride.
3.29.2
13 September 2026The trip page can now show its weather, and every chart says what it is.
Fixed: Was wrong, now is not
- A trip now looks up its own weather. It used to stay blank until you had opened each of its rides one at a time, which almost nobody would do.
- When a trip has no weather yet, the page asks you where it happened instead of showing nothing — and what you pick covers the whole journey, not one leg.
- The Heading chart was misleading in two ways. Its average could point the opposite way to the ride, and the line jumped from one side of the chart to the other every time you passed through north. Figures now read as a compass direction and the line breaks at north instead of drawing a jump that never happened.
- Every chart now carries a line saying what it is plotting. Some were easy to misread: the air temperature on a recording comes from your phone or GPS unit rather than from the bike, and the odometer chart is the bike's own reading rather than a total for that ride.
3.29.1
13 September 2026Two fixes to yesterday's weather, both found by using it.
Fixed: Was wrong, now is not
- Searching for a town now understands the language your browser is set to. Typing "Roma" used to offer you Romania, Spain and Lesotho before the city you meant, and adding the country made it worse rather than better.
- The demo account has a place of its own on the map. It could have shown the place a real rider had told us their motorcycle is kept, which was never anybody's intention.
3.29.0
13 September 2026Tell us once where your bike lives, and your rides get the weather they were ridden in.
Added: New in this release
- Say where your motorcycle is kept, once, on its page — and every short ride that has no GPS track gets the real wind, rain and temperature for the hours you were out. Your logs cannot see any of that, and it is often what explains a ride that drank more than usual.
- A trip now shows the weather across its legs: the temperature range with the time of each end of it, and any rain with the hours it fell. Where part of the journey has no weather, the page says so rather than quietly describing the rest.
- A shared trip link can carry its weather, if you tick it. It is off unless you ask for it, it never publishes the place you told us the bike is kept, and a link you have already handed out cannot start showing weather later.
- Your bike's own thermometer now has the modelled air temperature drawn beside it on the ride charts. When the two disagree by a lot, the bike was standing in the sun rather than the day being hot — which matters, because that reading feeds the range and battery-health estimates.
Changed: Different from before
- The AI reading of a ride is given the weather it was ridden in, and told what it may do with it: wind and rain can explain a thirsty ride, and mild weather can never soften a fault. Weather taken from where the bike is kept is background only — it is never used to judge anything.
- Weather from a declared base is used only for rides under 25 km. A longer ride could have ended anywhere, so we say nothing rather than guess, and the ride page tells you that is why.
Fixed: Was wrong, now is not
- Rides that had been opened without a location were left holding an empty weather record that could never refresh. They are cleared, and they now look up the weather properly once you say where you were.
3.28.0
13 September 2026A second parts shop is back, and a correction we owed it.
Added: New in this release
- A glossary: every term this site uses about Zero hardware and log files, defined once and linked from the pages that rely on it.
Fixed: Was wrong, now is not
- English Electric Motor Co. is listed again, with a correction published on the page. We had said its parts search found nothing, and that was our mistake: the site keeps its OEM parts in a different catalogue from its accessories shop, and every check we ran looked at the wrong one. Its catalogue holds a great many of the part numbers on this site, priced in pounds.
- Bike pages now link straight to the exploded parts diagrams for that model year. That shop cannot be searched by part number from a web address, so the link goes per motorcycle instead, and it is not offered for the bicycles and the scooter its catalogue does not cover.
3.27.0
12 September 2026What your bike is actually made of, and where to buy the piece that wears out.
Added: New in this release
- A component map: which fork, caliper, disc, belt, tyre and motor Zero specified for your exact model year, and how widely each was shared across the range. One rear brake caliper turns out to cover nine model lines from 2014 to 2026, across all three hardware generations.
- A part-number index: 1,010 Zero part numbers across nineteen subsystems, searchable by number, subsystem, model year or the catalogue's own model name, with a link that searches a Zero dealer for each one. It is the only place a part number appears on this site, because Zero's owner manuals print none.
- Your bike's page and the model comparison now list components. The comparison says what actually changed between two model years rather than which one has more parts listed — both bikes have a fork, so a difference in the count would be a fact about the manuals, not about the motorcycles.
- The buying guide gained a ledger of every component, ordered by what putting it right would cost against what the bike is worth. Seven of its twenty-four entries are invisible to every log ever written: we scanned all 363 log files in our corpus and the words "brake pad", "rotor", "caliper", "fork", "bearing" and "belt" appear in none of them.
Changed: Different from before
- Where a part number does not exist, the pages give the measurement instead. Your manual prints the thickness at which to replace a brake pad, per model year, with the page it is printed on — and unlike a dealer catalogue that figure does not go stale.
- Fitment is now shown exactly as the catalogue wrote it and is never widened. A part listed for "2015-2017" answers for 2016 and not for 2018, and a part listed under a platform name is not silently attributed to every bike on that platform.
Fixed: Was wrong, now is not
- An earlier draft of the component map explained a gap in the 2016 FX and FXS entries by saying that manual described those parts vaguely. It does not — page 122 names the fork and the shock in full, and our reading of it had missed them. Fifteen entries have been recovered from the manuals' own text, each one citing the page it came from.
3.26.0
12 September 2026A rider told us our in-browser reader called his Gen2 log a Gen3 one. He was right, and pulling that thread fixed the answers the assistant gives everyone.
Added: New in this release
- Buying used: a condition index. A new guide that reads a bike's own logs against Zero's published limits and says what shape it is in. It refuses to produce a figure when the seller has withheld what it needs, rather than quietly guessing one.
- The log reader now names the model. Drop a file on the decoder and it tells you which motorcycle the VIN describes, next to the reason it classified the log the way it did.
Changed: Different from before
- The assistant reads your bike's own manual. Zero reissues almost the same owner's manual every model year, and answers were being drawn from whichever edition happened to match the wording of your question. A 2023 S asking about winter storage was answered out of the 2019 manual, which gives a different state of charge and the opposite advice about leaving the charger plugged in. Every retrieved passage now comes from a manual that covers your model year.
- Email now comes from this site's own domain, so the sender matches the links the message carries. The messages themselves are unchanged.
- Coverage is stated as months with data, not months elapsed, so a gap in your uploads reads as a gap rather than as a bike that sat still.
Fixed: Was wrong, now is not
- Gen1 and Gen2 logs are no longer mistaken for Gen3. The in-browser reader had no way to tell them apart on a 2019-or-later VIN and produced thousands of plausible-looking rows with no rides in them. It now identifies the log correctly and says plainly that it cannot decode that family, instead of inventing an answer. The same mistake could happen server-side on the first upload for a bike that was not yet in your garage; that is fixed too.
- Four Gen3 telemetry channels were being read from the wrong place, and two temperatures were labelled as the wrong probes — motor and inverter readings were being stored as battery temperatures. Reparsed logs now carry the right values.
- Message text on some Gen3 logs was being decoded as state of charge, producing impossible battery readings.
- A trip nothing measured now reports nothing, not zero kilometres — an absent number and a zero are different claims.
- One corrupt ride window no longer discards a whole upload, and windows no motorcycle could produce are no longer created in the first place.
- Sums over an empty set report nothing instead of zero, in every place they are shown.
- The dashboard no longer serves a stale shell after an update.
- A refusal message that appeared in Italian on an otherwise English page now matches the rest of the page.
3.25.0
5 September 2026What a log actually says, shown rather than described.
Added: New in this release
- A new Learn article, "Anatomy of a Zero Log, Line by Line", shows what is really written inside a log file: real extracts from real bikes, annotated one line at a time, across switching on, riding, charging, standing parked, faults and switching off. It sets the bike computer's log beside the battery's, and the older platform beside the newer one, so you can see what each of them records and what it never records.
- The same article documents a fault that writes no fault line at all: when an onboard charger stops working, the log gains no error — it loses a line it used to write. Every VIN, serial number and firmware revision in the published extracts has been removed.
3.24.0
30 August 2026Vector maps, and the last of the security review closed.
Added: New in this release
- Maps are now drawn from vector tiles: crisper at every zoom, labels that stay readable, and a layer switcher with dark, light, Voyager and OpenStreetMap styles. Every overlay — route, stops, charges, photo pins, the hover readout — is unchanged.
- Signing in from a magic link now asks for one click ("Sign me in") instead of happening the moment the page opens, so an email scanner that pre-opens links can no longer use up your link.
Changed: Different from before
- Ten wrong passwords for one account inside fifteen minutes now pause sign-in for that account for a while (the response looks identical to a wrong password, and the reset and magic-link paths keep working).
- Passwords are limited to 72 bytes when set; the sign-in and reset forms say so before you submit. Existing longer passwords keep working.
- Deleting your account now asks for your current password.
- Each account has a storage allowance (5 GB across log files, recordings and photos; 2,000 log files). An upload past it is refused with a clear message instead of failing later.
- The AI assistant treats anything quoted from your logs and notes strictly as data; the ride-context fields (usage, climate, parking) accept only the values the editor offers.
Fixed: Was wrong, now is not
- Deleting your account now really erases what you uploaded: log files, decoded logs, recordings, photos and the bikes in your garage go with it, as the privacy policy promised. Deleting a single log file used to leave the file itself behind on the server; it no longer does.
- Exporting a report as PDF failed for any bike that had ever charged. Fixed.
- Adding a bike by hand from the garage failed with an error while the bike was in fact created; it also failed when the same bike had already been added by a previous owner. Both fixed.
- Ten wrong passwords in a row now say so: the sign-in page tells you how long to wait and points to the magic link, instead of insisting the password is wrong.
- The contact form no longer claims to have sent a message it could not prepare; if the page lost its session it asks you to reload.
- Maps still draw on browsers without WebGL (Lockdown Mode, some corporate builds): they fall back to the classic raster tiles instead of failing the whole page.
- Photos attached to a bike are now stripped of camera metadata and GPS position before they are stored, like trip photos and avatars already were.
- An upload with no sign-in, or one larger than allowed, is refused before a single byte of it is read.
3.23.0
30 August 2026The pages you share with strangers are now safe against the strangers.
Fixed: Was wrong, now is not
- A photo caption on a shared trip was inserted into the map's hover label as markup rather than as text. Captions, stop and charge labels are now always shown literally.
- A busy dashboard could sign you out when the server merely asked it to slow down. Only a real "not signed in" answer signs you out now; a temporary hiccup keeps your session.
Changed: Different from before
- The site framework moved to a current, patched release, the unused image-resizing endpoint is switched off, and the site no longer forwards API calls under its own address — every call goes straight to the API host.
- Links written by the AI assistant open in a new tab with their website shown next to them, and images in its answers are not loaded at all.
3.22.1
30 August 2026The front door gets stricter with strangers and gentler with you.
Fixed: Was wrong, now is not
- Opening a report with many charts could trip the server's per-visitor limits, which failed some charts and could even sign you out. The limits now ignore the browser's preflight requests and leave more headroom, and a trip page with a full gallery of photos loads every photo.
Changed: Different from before
- The server no longer answers requests that name a hostname it does not serve, no longer serves the image-resizing endpoint the site never used, and refuses the automated probes for PHP and credential files before they reach the application.
- Links and sign-in tokens are masked in the server's access log, so a log line can no longer be replayed as a login.
3.22.0
30 August 2026A security review of the whole service: what an upload, a shared bike or a stray photo could cost you, closed before anyone paid it.
Fixed: Was wrong, now is not
- A malformed upload request could freeze the service for everyone for close to a minute, no account needed. The library that reads uploads has been replaced with a version that is immune, and the rest of the dependencies that read your files (image decoding, the sign-in tokens) moved to current, patched releases at the same time.
- A phone recording archive that inflated to gigabytes could exhaust the server. Recordings are now checked for shape before they are opened: implausible compression, absurd column counts and oversized members are refused with a clear message, and honest multi-hour recordings still load.
- Profile avatars are now stripped of camera metadata and GPS position before they are stored, the same way trip photos already were. Transparent PNGs are flattened onto white rather than onto black.
- On a bike that has had more than one owner on this service, ride details, trip pages, photos, events, weather and the AI's history were partly readable across owners. Every one of those now shows each owner only their own data.
- The AI summary of a log no longer reads other people's reports for the same VIN when building its history.
- Names and ticket text written into the notification emails we receive are now rendered as text, never as markup; names are capped at 100 characters and ticket descriptions at 20,000.
- Changing your password now signs out every other device (they appear as inactive on the Sessions page), and the session you keep is a normal one that "Sign out" and "Log out this device" can revoke. A password reset signs out everything.
- Exporting a report as PDF failed with an error when no date range was given, and on bikes with two owners; both fixed.
Changed: Different from before
- Server logs now record the visitor's real address and a request id, and no longer contain email addresses in clear. Log retention on the server was extended so that an incident older than two days can still be investigated.
- Database backups are now readable by root only, are verified end to end before they count, and can be encrypted and copied off the server once that is configured.
- Map tiles no longer carry an "API KEY REQUIRED" watermark: the basemap provider started requiring a key on 26 August and kept serving tiles with the notice burned in.
3.21.1
28 August 2026Telling us an answer did not help now actually reaches us.
Fixed: Was wrong, now is not
- Saying that a reply did not answer your question sent us an email but left no mark in the app, so the ticket looked like any other until it was opened. It now shows as needing attention, including when you change your mind after first saying it helped.
3.21.0
28 August 2026When we answer your ticket, you can now tell us whether the answer actually helped.
Added: New in this release
- Under a reply on one of your tickets there is now a short question: did this answer it? Two buttons, and a box for what is still missing if it did not. Saying it did not reopens the ticket, so the answer goes back in front of us instead of into a statistic.
- The question appears once per reply and goes away when you have answered it, then comes back if we write again. Your earlier answers are kept, so "no, then yes" reads as what it is.
Fixed: Was wrong, now is not
- Replies sent from the contact inbox are recorded with the delivery receipt our mail provider returns, so a message that failed to go out can be told apart from one that went.
3.20.1
28 August 2026If you write to us through the contact form, the answer you get is now kept with your message.
Fixed: Was wrong, now is not
- A reply sent from the contact inbox was recorded but never shown back, so the thread you started looked one-sided from our side and a follow-up began by reconstructing what had already been said. Both halves of the conversation are now kept together.
- Replies are now stamped with the delivery receipt our mail provider returns, so a message that failed to go out can be told apart from one that went.
3.20.0
27 August 2026Your battery health figure was being measured against two different yardsticks on two different screens. Now there is one, and it is the one Zero's own warranty uses.
Changed: Different from before
- The state-of-health percentage on your dashboard and the one on your battery page disagreed by about ten points for the same pack on the same day. The dashboard was measuring against the number printed on the pack's badge — a figure no charge can ever deliver, because it counts the pack's energy at a voltage the cells only touch at the very top — so most people's figure will now read higher, and both screens say which yardstick they used.
- Because that yardstick is also the one Zero's warranty names, the "at or under the 80% line" marker on the model comparison page was flagging almost every used bike. It now compares against the same published figure the warranty text does.
- A health reading above 100% is no longer rounded down to 100. It is not extra health — it means the measurement disagrees with the pack's own specification — so it is shown as it is, in grey, with a line saying it is not a health figure.
Fixed: Was wrong, now is not
- Battery pages failed to load for anyone whose bike had recorded a real charge. Riders with no charges yet saw nothing wrong, which is why it went unreported for two weeks.
- A gap in how the battery configurator checked ownership could let one account reach another rider's bike data. It is closed, and a VIN already registered to somebody else is now refused.
- The ZF15.6 and ZF17.3 pages published the capacity figures from Zero's 2023 manuals. Zero revised both downward by 0.1 kWh from model year 2024, and the pages now carry the current figures with a note about the older ones.
- Every pack page called Zero's second capacity figure "usable". Zero never uses that word: it is the same charge measured at nominal cell voltage rather than peak, and what you can actually draw is lower than both. The pages say so now, and the badge-to-nominal step is no longer explained as a battery-management reserve, which it is not.
- The energy density shown on pack pages was worked out from weights that are the same figure repeated across packs of very different sizes, which pushed one pack to a number no production battery reaches. It is now shown only for the packs whose weight is independently sourced.
- Three places promised the cells' chemistry while the pages themselves explain that Zero does not publish it. The promises are gone; the explanation stays.
3.19.3
25 August 2026The support notice at the bottom of every page stops contradicting itself, and the error-code index finally points somewhere.
Fixed: Was wrong, now is not
- The small "supported logs" badge at the foot of every page said one range of motorcycles while the note it opens said another. They agree now, and the note is more careful about the oldest bikes: they are covered, but they are the least tested of the three generations, and it says so rather than implying otherwise.
- The error-code index listed every code and then left you there. It now explains what reading the log adds to what the dash already told you — when the fault happened, at what battery temperature and charge level, and what the minutes before it looked like — and offers the demo so you can see that before uploading anything.
- One guide's title was long enough that search engines cut it mid-phrase.
- Search engines were being told several sections of the site had not changed in weeks when they had, in some cases by nearly a month. Those dates are now worked out automatically at release time instead of being typed in and forgotten.
3.19.2
25 August 2026Page titles in search results are consistent again, and two battery packs rejoin the menu.
Fixed: Was wrong, now is not
- The name of this site was appended to page titles three different ways, and on many pages not at all — so a list of results from here looked like it came from several different places. There is one form now, and titles that were long enough to be cut off mid-sentence have been shortened to fit.
- Looking up an error code should now show you the code and the fault's name in the result itself. Before, the title was long enough that the fault's name — the half you were actually reading — was the part that got cut.
- Two battery packs, the integrated ZF6.5 and ZF7.2, were missing from the Batteries menu. Their pages existed and worked; there was simply no way to reach them from the menu, which listed twenty of the twenty-two packs.
- A few battery pages printed the same capacity figure twice in their title.
3.19.1
25 August 2026Some coloured backgrounds were missing, and every error code is now listed for search engines.
Fixed: Was wrong, now is not
- A handful of coloured backgrounds were not being drawn at all. On the front page three of the twelve feature icons sat on nothing instead of their colour, and in the log viewer the tinted bands that mark a charging stretch and a riding stretch were missing. The colours were correct everywhere they were written down; they were simply never reaching the page.
- The frequently-asked questions from the Learn index were being attached to all twenty-one Learn pages rather than just the index, which is the kind of thing search engines read as the same content repeated.
Added: New in this release
- All 170 error codes are now listed for search engines, so looking up the number your dash is showing can find the page directly instead of only through the index.
- The owner guides now carry a publication and revision date, so you can see how current one is before trusting it.
3.19.0
25 August 2026A page for every error code your dash can show you, and the catalogue pages finally link to each other.
Added: New in this release
- Every error code now has its own page. Look up the number your dash is showing and you get what it means, what to check, which motorcycles use that code table, and the codes most often seen alongside it. There are 170 of them.
- Those pages answer a question that has caused real confusion: the same number means different things on an older dash and a newer one. Code 01 is a high throttle reading on one and a throttle fault on the other; code 04 is a temperature warning on one and a serious throttle fault on the other. Your model name does not settle it either, because the S, SR, DS and DSR kept their names when they moved to the newer dash in 2024 — so each page shows you both readings and tells you which applies.
- Model pages and battery pages now link to each other. From your motorcycle you can reach the pack it carries, and from a pack you can see every model that takes it. Previously these were two catalogues with nothing joining them.
- The guides now offer a way through to the tool itself, so an article about charging or battery health tells you where to see the same thing in your own logs.
Changed: Different from before
- The one-line summaries that appear under a page's title in search results were rewritten across the site. Many were long enough that Google cut them off and wrote its own instead, which is how a page ends up described by a sentence nobody chose.
- The demo can now open directly on a particular page, so a link about charging costs lands on charging costs rather than the front of the dashboard.
Fixed: Was wrong, now is not
- A page describing how to read a log over a serial cable, and a few others, were summarised in search results by a sentence that trailed off mid-thought. They are written to fit now.
3.18.0
25 August 2026The home page now explains itself, and the footer stops telling Gen3 owners their motorcycle is unsupported.
Fixed: Was wrong, now is not
- The badge at the bottom of every page said Gen2 and Gen3 logs were supported, while the note behind it said Gen3 was not — naming the SR/F, SR/S, DSR/X and the MY22-and-later Cypher III bikes as out of reach. The badge was the right half: those motorcycles have been supported for months, and the note was left over from before that work. If you own one and had concluded this tool was not for you, it is.
- The battery catalogue described the cells in every Zero pack as a specific chemistry from a specific supplier. Zero has never published either, and the page itself says so a few lines further down — so the summary contradicted the article it was summarising. It now states only what the manuals actually give.
- On a phone, the menu called the log decoder a "VIN decoder". They are two different tools and both exist, so the one that reads a raw log now says so, and the VIN decoder has its own entry.
- Sharing a link to most pages produced a preview card with no image — including the front page, which asked for a large picture card and then supplied nothing to put in it. Links unfurl properly again.
Added: New in this release
- Every capability named on the front page now links to the page that explains it. The twelve cards described what the tool does and then went nowhere; ten of them now open the relevant guide, the battery catalogue, the demo or the in-browser decoder. Two still do not, because nothing public explains them yet — rather than send you somewhere useless.
- A "how it works" section on the front page, in three steps, with a real screenshot of a real battery page rather than an illustration. The pack in it is down to 73% of what it held when new, which for its age is close to normal — that is the kind of answer the tool exists to give.
- Six questions and honest answers on the front page: which motorcycles are supported, whether you need a dealer tool, what happens to your log file after you upload it, whether it is free, whether you can try it without an account, and whether Zero Motorcycles makes this. They were all reasonable things to want to know before handing over a file, and none of them was answered where you would look.
- The front page now says plainly that this is an independent project, not affiliated with or endorsed by Zero Motorcycles. It has always been true and was written on the About page; it was missing from the one page most people see first.
Changed: Different from before
- The contact form is now reachable from the footer of every page. It existed, and nothing linked to it.
- The footer gained a row for the parts of the site that had no route from the front page — the model and battery catalogues, the decoder, the range calculator and the changelog. The live service indicators down there are now a link to the status page they summarise.
3.17.2
24 August 2026Housekeeping behind the scenes; nothing on your pages changes.
Fixed: Was wrong, now is not
- A counting error on our own operator pages meant we had been under-reading how many log files riders upload each month — the figure sat at zero regardless of the real number. Nothing you can see, download or share was affected, and no data of yours was touched. It is recorded here because this list is meant to be complete rather than flattering.
3.17.1
24 August 2026The climb figure on a ride stays right after we re-read the recording.
Fixed: Was wrong, now is not
- When a ride's elevation gain was recalculated — because you corrected the clock on your motorcycle, re-processed a phone recording, or attached one to a different ride — the figure was replaced with the climb of the whole recording rather than of that ride. Two legs of one journey could each be credited with the entire day's climbing. Each ride is now measured over its own stretch, so the number stays the one you were shown.
3.17.0
24 August 2026A number that read differently depending on your browser.
Fixed: Was wrong, now is not
- Distances, speeds, weights and temperatures were formatted using your browser's language settings, while every other number on the same page used ours. On an Italian or a German machine that meant a distance reading 1.234 km beside a count reading 1,234 — the same number written two ways, on one screen. They agree everywhere now.
3.16.0
20 August 2026A way to reach the person who builds this, and a page explaining why it exists.
Added: New in this release
- There is now a contact form that works, and works without anyone having to publish an email address. Write to us and you get a confirmation link at the address you typed; the message arrives only after you click it, so nobody can send a message in your name and no address of ours ends up in a spam list.
- A page telling the story behind the tool: the motorcycle it was built for, what went wrong with it, and why reading your own logs turned out to matter.
- A support page, if you would like to put something towards the running costs. It is entirely optional and it buys nothing — no feature, no tier, no extra AI allowance. The tool stays free for everyone either way.
Changed: Different from before
- The About page was rewritten against what the tool actually does today: trips, revocable share links, the tools that need no account, your choice of units, and the export formats. The list of what this is not grew with it, because new features bring new limits.
- We were telling you your data was anonymised before the AI reads it. That was not true, and the page now says what really happens: an uploaded log is analysed automatically, and it goes to the model provider as it is, VIN included.
- Where the legal pages used to print an email address, they now point at the contact form.
3.15.1
20 August 2026A number that was missing from the public bike pages.
Fixed: Was wrong, now is not
- The real-world statistics on the model pages — range, efficiency and average battery health drawn from everyone's uploaded logs — were not being shown at all. They were not missing for want of data; the calculation behind them was failing on every request and the page was quietly leaving the section out.
3.15.0
20 August 2026Rides that your logs recorded but the app never showed you.
Added: New in this release
- The app now recognises a ride from the motorcycle's own movement, not only from the messages its firmware happens to write when you switch on. On our test collection this took the riding we could account for from 91.5% to 99.7% — about 260 rides and 4,500 km that were in the logs and had never appeared anywhere.
- Rides that the app had filed as workshop or diagnostic sessions are now checked against the distance you actually covered first, so a real ride is no longer hidden behind a maintenance label.
- Both of the above apply to logs read from now on, so your existing rides are unchanged until your files are read again. We do that for everyone, and nothing you already have is removed by it.
3.14.1
20 August 2026Small things, mostly about being honest with you.
Fixed: Was wrong, now is not
- The status page was naming the wrong model for the manual search, and its "Manual RAG" light was green whether or not the service behind it was answering. Both now report what is actually true, and the light can go red.
- When you share a bike or a trip, the dialog now tells you how many links you have left before the limit, and if you do hit it we say which limit and what to do.
- Photos of your motorcycle were stored under a filename you chose, which is often a place or a date. They are now stored under an anonymous name.
3.14.0
20 August 2026You can now tell us when a public page is publishing something it should not.
Added: New in this release
- Every public page — a shared trip and a rider profile — now carries a quiet "report this" link. Until now the person who published it was the only one who could take it down, and if you found something abusive there was no way to reach us. You do not need an account, and we do not store anything about you.
Fixed: Was wrong, now is not
- Text you type into your bike notes, your profile and your milestones is now checked the same way your ride notes already were. The older check could be slipped past with an invisible character, on fields that are read by the AI.
- On four motorcycles we had recorded the battery of a bike carrying one Power Pack when they carry two. The battery size was corrected earlier this week; their past rides still showed half the energy they should, and now match.
3.13.1
20 August 2026One more thing a shared link should not do on its own.
Fixed: Was wrong, now is not
- A trip you shared without a map could start showing your route later, if you uploaded a phone recording of that ride afterwards. Links now keep the map they had when you shared them, and one that had none never gains one. Nothing that was already visible has been removed.
3.13.0
20 August 2026Mostly corrections: numbers that were wrong on your pages, and what a link you shared keeps doing after you have forgotten about it.
Fixed: Was wrong, now is not
- Ride time could come out negative. One ride on one motorcycle had a corrupted end time, and that single row was enough to make the whole bike's ride hours read as a large negative number on the timeline, and as a dash on the dashboard. Every total now ignores a clock it cannot believe, and says how many it set aside.
- Energy, efficiency and cost per kilometre were computed against a guessed battery size on more than six thousand rides. They now use the pack your own charges measure. For most bikes the change is a few percent; for six it was much larger, and for one the figures were out by more than double.
- Four FX motorcycles were recorded with the battery of a bike carrying one Power Pack when they carry two, which halved every energy figure derived from it.
- Big numbers in the dashboard tiles were cut off with an ellipsis when the browser window was narrow. A cut number reads as a different number, so the tiles now give the figure room instead of trimming it.
- Revoking a shared link did not take the photos with it. They stayed reachable for up to a week after you revoked. That window is now half an hour.
- A link you had already shared could keep growing. Log lines, faults and charging stops on a published page are now fixed to the files you had uploaded when you shared it, and the activity strip on a bike recap no longer carries your whole ownership history in the page data.
- A shared page told the reader that places near your private locations were hidden. There is no such setting, so the claim is gone rather than reworded.
- The masked motorcycle number on a shared page kept its last four characters, which are the part that identifies your individual bike. It now keeps the part that describes the model and drops the rest. A bike recap shared without anonymising showed the number in full, which it no longer does.
- Published log lines carried the exact time of day, on a page that is otherwise built so nobody can tell when you were somewhere. They now show how far into the ride each line falls.
- Password reset requests were not rate limited, at either layer. They are now.
- The read-only demo account could write notes and start jobs through four routes that skipped the check.
- Charging sessions that spanned days or ended before they began no longer count towards your totals, and are repaired in place where the data allows it.
Added: New in this release
- Trips now show total climb, gathered across the legs that recorded altitude, with barometric drift filtered out rather than counted as hills. Figures already stored were corrected too.
- The decoder that runs in your browser now reads reverse and park records from Gen3 logs, so their battery and temperature readings are no longer discarded.
- We looked again at whether we can tell DC fast charging from AC, this time across every charge in the service rather than our own sample. We still cannot, honestly — the very high power readings turned out to be what the battery said it would accept, not what a charger delivered — so no such label is shown, and there is now a check that will notice the day a real one appears.
3.12.1
18 August 2026Nothing you can see — a maintenance re-run stopped charging riders for it.
Fixed: Was wrong, now is not
- Re-running the analysis across every motorcycle, which is maintenance rather than something you asked for, no longer counts against your own monthly AI allowance.
3.12.0
18 August 2026A page for charging, and a check that can finally say your charger stops short.
Added: New in this release
- A Charging section, where "Charging Costs" used to be, answering one question first: does your charger finish? Under it, every charge you have on record, and the costs page as it was.
- A check that compares your chargers against each other. If one of them habitually stops short of 100% while another finishes, it says so — and it says nothing at all when there is only one charger to look at, because with nothing to compare a low figure is just as likely to be how you charge.
- The faults your motorcycle logged during a charge, grouped by kind and ranked by how many charges each one touched, quoted in the bike's own words.
Fixed: Was wrong, now is not
- A charge that stopped at 32% was shown as "Full Charge". Completion is now read from the state of charge itself, and the shared-bike page no longer overstates how many charges finished — across all bikes it had been claiming 1,539 where the corrected count is 973.
- A charge the app had split into fragments minutes apart was counted as several charges that all stopped short. Adjacent ones now count as one attempt.
- Charging figures are shown as a lower bound, written "≥73%", because the motorcycle stops reporting once the charge current tapers off and the last level it logged is not where it finished.
- "Issues: None" on a charge page was never a measurement — nothing had ever filled that field. It has been replaced with what the logs actually hold.
3.11.1
17 August 2026The version number in the footer now names the release you are actually on.
Fixed: Was wrong, now is not
- The footer could show the previous release rather than the running one, which also made this page mark the wrong entry as current. Everything else in this release is deployment machinery with nothing to see.
3.11.0
17 August 2026This page.
Added: New in this release
- A page listing what changed in each release, reached by clicking the version number in the footer. Each release links to itself, so a particular change can be pointed at directly.
- Every release now says which version you are looking at and marks the one currently running, so it is clear whether a fix described here has reached you yet.
3.10.1
17 August 2026Phones get one navigation bar that works, and console captures get their clock right.
Fixed: Was wrong, now is not
- On a phone, two navigation bars sat on top of each other and the one that won carried fewer links. Timeline, Trips, Charging Costs, the log viewer, My Batteries, Log Files, Bookmarks, Shared Links, Feedback and Profile had no route at all from a phone; there is one bar now, with a drawer behind its last cell holding the rest.
- A fault message printed inside a badge pushed a shared trip page to 669 px wide on a 390 px screen, with the card's border ending mid-sentence. Short codes still get a badge; a sentence is now laid out as a sentence.
- Timestamps read from a console capture were stored seven hours early, because the motorcycle's console prints its own clock rather than UTC. Captures are now corrected — including short ones that carry only the capture tool's own header line — so charges and rides taken from a console dump line up with the ones from a binary log.
3.9.0
16 August 2026One rule for how big your battery is, and no impossible efficiency figures.
Fixed: Was wrong, now is not
- The pack size behind the dashboard battery gauge is measured by the same rule as the battery page, including the check that discards a charge claiming twenty points of state of charge across a one-point window. The same pack, on the same day, had been reading 3.83, 4.00 and 4.20 kWh on three pages of the app.
- An impossible efficiency is no longer published. 24 km on a three-point drop in state of charge works out at 235 km/kWh, and it was on a public page; the ceiling is now 80 km/kWh — twice the fleet's 95th percentile — which withholds 253 rides out of 9,272 rather than printing a figure nobody measured.
3.7.0
16 August 2026Trip and ride energy stop being measured against the badge on the battery.
Fixed: Was wrong, now is not
- A trip counted the same battery twice. A pack does not refill during a coffee stop but its state-of-charge reading recovers once the load comes off, so a nine-leg trip added up 68 points of drop on a pack that lost 45.
- Ride energy is measured from your pack's own charges rather than from the number on its badge. A 2016 FXS with 118 recorded charges measures 3.37 kWh against a 6.5 kWh badge, so every ride on it read about 1.7 times too high; 34 of the 66 bikes with enough charge history were over by more than 10%.
- A pack is never reported as holding more than it could when new. Four bikes had been raised past their own badge by charge energy metered at the wall, with the charger's losses counted as if they had reached the cells.
3.6.0
16 August 2026Added: New in this release
- The verdict on a published trip link can be refreshed after you write a note, without minting a new link. The address you already sent to a forum keeps working, and nothing is spent until you ask.
Fixed: Was wrong, now is not
- Clearing a note removed it from your account and left it on the public page, so a rider who changed their mind was told it was done when it was not.
- After rewriting a note, the page went on offering to refresh the verdict on every load, for ever. The offer now appears only when the verdict really is older than the note, and a refresh counts against the same monthly AI allowance as every other AI feature.
3.3.0
16 August 2026Write down what the log cannot record.
Added: New in this release
- Your own note on a ride, for the part a log cannot hold — the dash flashing, the throttle going dead after a long descent, that it happened four times. A note always reaches the AI verdict, and reaches the public page only if you tick the box.
- A photograph of the motorcycle and the outline of a route can appear on your public rider page. What is published is a separate stripped copy with no camera data and no location in it, and unticking the box deletes that copy rather than merely hiding it.
Fixed: Was wrong, now is not
- Two shared links to trips ridden out of the same town could not be told apart — both read "Formia, Italy" with the date in small grey type. A shared link now carries its place and its day together, which is what names a trip.
- The route outline drew a straight line across the area the privacy trim had just hidden. It breaks the line there now, the way the map beside it always has.
- Shared ride photo links no longer carry an internal account identifier.
3.0.0
16 August 2026A public rider page, off until you turn it on twice.
Added: New in this release
- A public rider page at a handle you choose. Two separate switches, both off until you set them: one says you have a page at all, one says a particular ride appears on it, and turning the page off clears every ride from it.
- A page carries at most three rides, and one generated sentence says how many were chosen, how many are anonymised and whether the motorcycle is named — so three rides do not read as a rider who has ridden three times.
- The year on your page is the year you started riding, declared by you. It used to be the year you signed up here, which told an owner who bought their bike used in 2019 that they had been riding since 2026.
Changed: Different from before
- A published link can be made to show less while keeping its address. Tightening a link you have already sent out no longer means revoking it and losing every reader you sent it to.
Fixed: Was wrong, now is not
- The page says why a ride cannot be listed before you tick the box, instead of failing afterwards with a message that slides away.
- Using a Gravatar on your page is a choice you make, and the page states its cost where the choice is made: the address in a Gravatar URL identifies you on every site that uses them.
2.99.0
15 August 2026Added: New in this release
- A page listing every link you have published, ranked by how much each one gives away rather than by date. The owner of this app had four live links and remembered one; among the forgotten was a bike recap serving a full VIN, the odometer and six years of ride history to anyone with the address.
Fixed: Was wrong, now is not
- A 40 km ride showed as 7 km. The log held the whole climb — odometer 33,664 to 33,704, state of charge 96 to 53 — and the report had finished with no error and no warning; across the whole 861-file test corpus this recovers 9,592 km and 886 rides.
2.98.0
15 August 2026Fixed: Was wrong, now is not
- Charging sessions of impossible length are no longer created. One session in the database ran 305 days as a single charge, with 196 more over eight hours and 43 that began and ended at the same instant.
- State of health now divides by one usable-capacity figure instead of two that disagreed by 2.3%, which is why a pack in ordinary condition could publish 102%. Every pack Zero has sold has a usable figure between 87.5% and 89.3% of the number on its badge.
2.97.1
15 August 2026Added: New in this release
- Battery telemetry from the console captures of 2020-era battery boards: cell voltages, pack voltage, temperatures and current, 4,686 samples over two months on the reference capture. Those captures carry no state of charge at all — the reading is stuck at 100 in every record — so none is shown.
Fixed: Was wrong, now is not
- The Battery State of Health card came back for six bikes that had lost it. Two of its three rungs are specifications, true whether or not anything has been measured, so the explanation should not disappear along with the figure.
- The overall battery score no longer jumps at a round number. It cost 14 points at 70.0% state of health and 25 at 69.9% — eleven points, on a figure that moves when your next charge arrives.
2.97.0
14 August 2026Fixed: Was wrong, now is not
- A 2020 battery console capture holding two months of history was refused with "no log entry table found", and its owner was told to run the dump again. It reads now: 21,148 entries.
- The battery capacity quoted by the chat assistant follows the same rule as the battery page. It had been averaging the twenty most recent charges regardless of which pack they came from, and comparing the result against the badge.
2.95.0
14 August 2026The battery page counts its evidence before it scores anything.
Added: New in this release
- A battery health guide in the Learn section: what makes a charge count, why a charge from 60% to full is worth twice an 80% top-up, and why rides draw on the chart without voting on the number.
Changed: Different from before
- Four charges are needed before a state-of-health percentage is published. Below that the tile shows how much evidence exists — "2 of 4", with a filling bar and never a percent sign, because the one thing it must not resemble is a very low state of health.
- The battery page labels its three capacity figures Badge, When new and Today, and state of health divides by what the pack gave when new rather than by the badge. That step from badge to usable was true the day the motorcycle was sold, and charging an owner for it is what makes an ordinary ten-year-old pack look ruined.
Fixed: Was wrong, now is not
- 32 bikes published a state of health of exactly 102.3%, a figure that contained no measurement at all — most modern Zeros carry no electrical telemetry to measure with. Published figures go from 118 to 56 and readings above 100% from 86 to 3.
- A motorcycle whose pack cannot be measured no longer scores 100 "Excellent" on the strength of never having been checked.
- The overall health verdict listed the same three bullet points every time, so the two deductions that dominate — a live critical fault and worn capacity — were never among them. Measured on one bike: a score of 57 above three visible bullets worth nine points between them.
- The cell-spread warning judges the sustained spread instead of the worst instant. Cells separate under hard acceleration; 53 of 124 bikes were flagged, 2 are.
2.83.0
12 August 2026Battery pages stop contradicting each other.
Added: New in this release
- Recurring battery faults are listed on the battery page. All twelve of the bikes with the most log files carry at least one recurring fault family and the page had shown none of them, ranked so that 996 failures which stopped in 2020 describe a motorcycle that was repaired.
- Each capacity reading carries the temperature it was taken at, with the weather drawn under the capacity curve on a shared time axis. Measured over 1,986 charges across 46 bikes, a pack below freezing hands over about 83% of what it gives at 22 °C.
Changed: Different from before
- The AI fleet verdict expires when new logs arrive instead of standing for ever. It is not regenerated automatically, because that would spend your metered allowance on an opinion you did not ask for.
Fixed: Was wrong, now is not
- All-time battery records could be set by a corrupt reading, so a few bikes showed an impossible cell voltage as their headline figure — one read 16,546 mV for a single cell, and 21 of 123 bikes with cell data were affected. The low end mattered more, because it drives a warning: two bikes reported minima of 384 mV and 45 mV against true minima of 3,573 and 2,801.
- A pack is no longer reported as holding more than its badge. "7.22 kWh maximum" on a 6.5 kWh pack was being admitted deliberately, by a band that ran to 15% above the nameplate.
- A replaced battery was averaged with the one you ride. 56 charges on the outgoing modules at 2.90 kWh and 34 on the incoming pack at 4.00 came out as roughly 3.0 and a headline of 52%, describing a battery that has never existed.
- The health ring read 97 "Excellent" a few centimetres above this same page's own verdict of 70%, because it scored how the pack behaves and never asked how much of it was left. "Health vs Age: 104%" had the same shape: a ten-month-old pack graded against the age of the motorcycle.
- Tyre pressure and riding mode were saved and never sent back to the page, so every reload showed empty boxes and the values looked lost.
2.82.0
12 August 2026A range calculator anyone can use.
Added: New in this release
- A public range calculator: pick a model year, a speed, a load and a gradient. It never asks you for a drag coefficient — nobody knows theirs, so it is solved from Zero's own published highway range — and the whole configuration lives in the address, so a setup can be handed to someone else.
Fixed: Was wrong, now is not
- The range calculator was absent from the menu below 1280 px and had no entry at all on a phone, which is most of the people who would use it.
- Total ascent was over-counted on a route: a 9.77 km loop that ended where it started reported 84 m of climbing against a true 68.
2.73.0
6 August 2026Phone navigation for the public pages, four new Learn guides, and battery identity read out of the logs.
Added: New in this release
- The public pages have navigation on a phone. Below 768 px there was none at all: the model catalogue, the log decoder and every Learn topic were unreachable from any page, and the de facto menu was a row of 20 px footer links.
- Four new Learn guides written from Zero's own manuals: fastener torques (503 figures from 31 manuals, including the nine specifications Zero changed between model years), the 12 V system (343 fuse rows), thermal limits, and drive-belt tension.
- Compare two model years side by side. The catalogue could compare every model and no two motorcycles, so a 2016 against a 2022 was unreachable; the comparison also states what a battery failure costs, from dealer part numbers.
- Weather for a ride whose location you told us, hourly and back to 2017. Only for a location you asserted yourself, because guessing it turns "it has been dry all week, so this is not water" into a confident wrong answer.
- Efficiency is compared against your own history as well as against the fleet. One rider's 365 rides have a median of 15.4 km/kWh against the FXS fleet's 20.5, so every trip they published read "below average" and said the same thing for ever.
Changed: Different from before
- A declared change of owner reaches the dashboard, the costs page, the AI verdict and your shared links, rather than one aggregate. History views still show everything, with a marker on the day the boundary falls, because truncating a rider's journeys at the day they bought the bike would destroy what a second-hand owner said was valuable.
Fixed: Was wrong, now is not
- A quarter of every console capture never reached the database — 5,292 rows stored out of 7,011, with nothing anywhere saying so. Separately, a capture whose terminal had wrapped every line was refused outright; one such 1.2 MB file now yields 7,015 entries over 19 days.
- Selecting a battery module did nothing: either module returned identical charts, which is worse than an absent feature because it looked like it worked. Selecting a retired pack also put the current pack's cells under the old pack's name.
- The report page showed a green "No errors or warnings" card for a motorcycle with 97 error rows, and the rows behind a ride's error count can now be opened and read.
2.59.0
3 August 2026Added: New in this release
- Photographs on a shared trip, uploaded from the trip page. The file is decoded and re-encoded before storage so no location, device or timestamp survives, and a photograph whose position falls inside the hidden part of the route is published without a pin rather than not at all.
- Photographs with no position ask you where along the route they belong, and your placement always beats the camera's.
- The data-quality panel the owner sees is on the public page too, with GPX download and Google Maps and Waze links beside it.
2.50.0
3 August 2026Added: New in this release
- Every parse now checks the raw file independently and reports when it demonstrably holds records later than anything that was read. This is the failure that keeps recurring, because nothing about it looks like an error.
Fixed: Was wrong, now is not
- A rider's most recent day of riding was missing from reports that completed without a single error. Across the test corpus this recovers 3,088 entries and 44 days on 90 files, 25 of which now reach a later date and one of which gains three months.
- Because there were no rides for that day, every phone recording uploaded afterwards was refused with "no matching ride" — a symptom of a problem two layers away from where it appeared.
2.44.0
2 August 2026The public trip page.
Added: New in this release
- A shared ride opens as a navigable layered map with its sensor charts and whichever sections the owner turned on.
- Four switches on each link: the bike's telemetry, a fault summary, the raw log lines, and the model and year. Every one is off by default, and links already handed out were not widened by the change.
- Raw log lines are published with the identifiers taken out of them — VINs, serial numbers, firmware strings, hardware addresses and coordinates written into free text. Fault codes, temperatures, voltages, currents and state of charge are kept, because a redaction that eats the fault codes removes the reason to publish a log at all.
- The page says two things out loud: that a shortened route is deliberate, and that identifiers were removed from the log lines. Otherwise both read as a broken upload.
2.43.0
2 August 2026Trips.
Added: New in this release
- Rides grouped into the journeys you remember taking. A ride ends when the bike is switched off, which is right for engineering and wrong for "show me last Sunday": stop for coffee and one outing becomes three rows.
- A trip page with a layered map, the route colourable by any channel, and one shared cursor across the map and every chart. Legs with no recording are named and counted rather than drawn across.
- GPX export with one track segment per leg, so no viewer draws a straight line across the hour you spent at lunch.
- Route privacy for public links, chosen per share from a default you set once. The trim is applied when the page is built, so your stored track is never modified.
2.42.0
2 August 2026Record a ride with your phone.
Added: New in this release
- Phone recordings are read properly, gyroscope included: yaw rate, roll rate and corner radius, from the one sensor that measures cornering directly rather than inferring it from where the bike ended up.
- Nothing from the motion sensors is published below 15 km/h. A phone cannot tell riding from carrying — ungated, a 2 km walk reported a 13° lean and a 40°/s yaw rate.
- A recording works out which ride it belongs to, and one that spans several rides is split between them. Coverage and gaps travel with every match, so a recording that died ten minutes into an hour says so instead of presenting a sixth of the ride as the ride.
- A phone telemetry guide in the Learn section, written from measurements rather than from the apps' own documentation: Sensor Logger asks Android for 100 Hz and delivers 62 Hz over 90 seconds but 15 Hz over 21 minutes.
2.41.0
1 August 2026The parser had been stopping partway through a log and saying nothing.
Added: New in this release
- Export All now exports: one ZIP for a whole upload session, with selectable parts — summary statistics, decoded log text, telemetry as CSV, rides and charges, and the original files as uploaded.
- The upload assistant names the one case that is ours rather than the motorcycle's: a thin report because we did not finish reading the file, carrying the opposite advice — re-parse what you already uploaded instead of downloading it again.
Fixed: Was wrong, now is not
- A log that appeared to cover nine days actually held ten months. One bike's file reported 42 rides over 301 km and holds 114 rides, 573 km, 12 charges and an odometer reaching 33,249 km; the report ended in a smooth ladder of identical status rows and read as uneventful.
- A single torn record no longer defines a report. Five bad rows out of 6,609 had given one motorcycle a state-of-charge range of 24% to 253%, a 1,784,914 V pack and a 2,157,131 kW discharge.
- Fake pack-voltage samples are gone. One record type never carried a voltage at all and had contributed 77,999 readings — 27% of every battery voltage figure in the database; with it removed, the two independent decoders agree on the same pack to within 0.2 V.
2.39.0
31 July 2026Fixed: Was wrong, now is not
- The decoder that runs inside your browser skipped four bikes' battery logs entirely — 1,442 records it never read. It now returns exactly what the server returns on the same files: 107,728 entries each, with no disagreement left between them.
- A report could claim more entries than it actually held.
2.38.0
31 July 2026Fixed: Was wrong, now is not
- Six logs from newer bikes were read by the decoder for the older platform, because the file's own name said so. They held 1,643 to 1,741 entries where a correctly read file of that kind holds about 2,355. The bytes decide now, not the label.
2.37.0
31 July 2026Fixed: Was wrong, now is not
- Battery current was read as half a number. The stored value wrapped every 65.5 A and inverted its sign as it wrapped, which is why a charge could read as a discharge. Checked three independent ways before it was changed: against the pack's own state of charge, where the direction now agrees on 83 of 84 charge segments instead of 49, and against internal resistance on 35 of 38 bikes.
- A current that cannot be read is recorded as unknown rather than as zero, because zero reads as an idle pack. A genuine zero is kept — it is a real reading on a fifth of all records.
2.36.0
31 July 2026Fixed: Was wrong, now is not
- One of our own decoders had been taking over from a better one and halving what those bikes recorded. The stored average fell from about 6,200 rows to about 3,500 on 29 June and nothing reported it; re-read across 191 files it goes from 3,449 to 7,191 entries on average. It now takes over only where the other decoder came back with nothing usable.
2.35.0
31 July 2026Fixed: Was wrong, now is not
- A Gen3 battery temperature that was never a temperature is withdrawn — charted, stored, documented and published on the strength of a byte that sat in a plausible range and was never checked against a second instrument. The same mistake as the accessory rail once published as an odometer, and an absent reading is better than an invented one.
2.34.0
31 July 2026Fixed: Was wrong, now is not
- A third of every uploaded log was being discarded as it arrived. Across every Gen3 file on the server, 672,818 parsed entries had become 430,222 stored rows, because the rule that drops duplicates was matching on a field none of the readings carry. Files uploaded before this still lack those rows; a re-parse recovers them.
- Dates the app was not entitled to believe: 92% of Gen3 reports claimed a span longer than two months, some starting in years before the platform existed. An impossible span is now refused rather than reasoned from, and a ring buffer's two dates are described as the oldest and newest records that survived, not as a period covered continuously.
- The warning that only the last few days before export would appear was being shown to every Gen3 owner. 91 of 259 of those reports are not ring-buffer files at all.
2.33.0
31 July 2026The app explains what happened to your upload.
Added: New in this release
- After an upload you are told what was found: the identity recovered from the bytes, why a timeline is empty, whether the export was cut short near the end of the buffer. Every observation is measured from the finished report rather than written by a model, and when your browser is not set to English they are translated — translated only, with anything invented thrown away.
- An upload no longer redirects you into an empty page. When there is something you need to see first, it stops and says it.
Fixed: Was wrong, now is not
- An upload that fails now says something you can act on. A network failure names what goes wrong there; a structured server error used to render as the literal text [object Object]; a file the picker rejected was dropped in silence, with nothing to say it had gone.
- The whole file is read in your browser when you pick it, not just the first kilobyte, so a file that cannot be read is caught while the advice is still useful.
2.32.0
31 July 2026Fixed: Was wrong, now is not
- A log renamed by hand — or by a browser adding "(1)" to it — lost the identity we had been reading out of its filename, and lost the rides inside it with no sign that anything was wrong. Eight files belonging to one owner were already affected: 0 rides became 2,199 once the identity was read from the bytes instead. Every bike-computer log carries its own VIN in a fixed place, and the upload now reads the file before it asks you anything, asking which bike it is only when neither the name nor the bytes answer.
- Some riders were placed on a "local network", which is not a place — and they were not mislabelled on the admin map so much as deleted from it. Their real addresses were recovered.
2.31.0
30 July 2026A decoder anyone can use, without an account and without uploading anything.
Added: New in this release
- A page for anyone holding a Zero log: drop the file in, read the decoded text, download it. The decoding runs inside your browser and the file never leaves your machine.
- Gen1 and Gen2 logs are recognised, identified and honestly declined there rather than half-decoded — measured coverage had we tried was under 1% of the readings that matter.
Fixed: Was wrong, now is not
- "Mask identifiers" now masks all of them. It had been redacting one field of five while the line two above it carried the filename, which on every real Zero export is the VIN.
- Zero's VIN tables are indexed by model year and ours had been flattened, so a code the factory reused across years decoded silently wrong: a 2015 SR came out with a pack Zero never sold, and that figure reaches the stored capacity and the state of health divided by it.
- Charging says what it cannot know. The split between the onboard charger and a supplemental one now has an explicit unknown, and the page states once, plainly, that DC fast charging cannot be told apart.
2.30.0
30 July 2026The Learn section, audited against the manuals and the real logs.
Fixed: Was wrong, now is not
- Onboard charger power was published from a year-blind table and understated by up to 2.2 times — the DSR/X at 3.0 kW against a true 6.6 on every manual sheet. It resolves by model year now.
- Gen3 dash codes: 19 were missing, five were wrong and two had been invented, including one published as "No Error" where the manual says a turn-signal bulb is out.
- Claims about hardware that does not exist: the SR/F described as liquid-cooled where every manual sheet says air-cooled, and a CHAdeMO row against the DSR/X.
- Claims that would mislead an owner about their own motorcycle. Gen2 owners were told their logs grow without limit and keep months of history, so there was no hurry to export; the file is a fixed-size ring buffer like everyone else's. The error-code search filtered Gen2 without the DSR or FXE and Gen3 without the S/F, so those owners filtered themselves out of their own dash codes.
- A banner told every Gen3 owner that the tool could not read their logs. It had been reading them for some time.
2.29.0
30 July 2026Gen3 bikes stop reporting an odometer, because they never had one to report.
Changed: Different from before
- SR/F, SR/S and DSR/X reports no longer show an odometer or a per-ride distance. The figure came from four bytes that were never a distance: it rose on only half of its transitions, and read between 143 and 13,440 "km" on five unrelated bikes across three families and five model years. It is a 12 V accessory rail, and is reported as one now. Gen2 and 538XX bikes carry a real odometer and keep it.
Added: New in this release
- Measured pack capacity on the battery page, read from the battery's own full-charge register — decoded and stored for a long time, and never once read back.
- A page documenting the Gen3 log format record by record, with a decoder that runs in your browser, and a VIN page with all 17 positions and the tables behind them.
Fixed: Was wrong, now is not
- Exporting a report as PDF failed on any report with more than one ride.
- Gen3 rides were vanishing from the timeline: they carry no distance and no speed, and that was being read as "not a ride". One file lost every ride it had.
- The ring-buffer retention figure was wrong by about half everywhere it appeared, including in the app's own warning. A parked Gen3 fills its buffer in about 3.2 days, not five to seven.
2.27.0
28 July 2026Changed: Different from before
- The account overview and the per-bike battery figures are cached, so the slowest page in the app stops being slow. Anything you change clears your own cached figures, so a stale number cannot outlive the edit that made it wrong.
2.26.1
27 July 2026Fixed: Was wrong, now is not
- Battery statistics were cached against the motorcycle alone, so the second owner of a resold bike could be shown the first owner's figures. Every cached figure is scoped to the account that asked for it.
2.26.0
27 July 2026Changed: Different from before
- You stay signed in. A sign-in lasted 30 days with no way to renew it, so you were signed out roughly monthly with no warning; it now renews while you are using the app.
2.25.0
26 July 2026One mark, and a green that is not the manufacturer's yellow.
Changed: Different from before
- One identity replaces four that contradicted each other, and the accent moves from yellow to green: this is a third-party tool and must not dress as Zero Motorcycles. Yellows that carry meaning were left alone — a dashboard lamp that is amber on the motorcycle is still amber here.
- Email is rebuilt on the same identity, with the name carried in live text as well as in the image, because most mail clients block remote images by default.
Fixed: Was wrong, now is not
- Every button in every email painted white text on a gradient with no fallback colour. Outlook and Windows Mail drop the gradient, so the label rendered white on white and the button read as empty space.
- The site icon and the link-preview image were declared on every page and returned nothing.
2.24.0
23 July 2026Added: New in this release
- The date a battery was installed is yours to set, and re-parsing your logs never overwrites it.
Fixed: Was wrong, now is not
- The battery date pickers rejected valid dates: a date with no time of day was refused outright by the server, and the dialogs said nothing at all when a save failed, so it looked like pressing Apply did nothing.
- Bike photos, ticket attachments and share-card images failed to load.
2.23.0
12 July 2026Shareable bike recaps.
Added: New in this release
- Public, revocable links that show one bike's recap — riding, charging and a 26-week activity calendar — with everything identifying it off unless you turn it on.
- Pasting one into a chat or a social network unfurls a card drawn for that link.
- A photograph of your own bike, which replaces the model placeholder wherever that bike appears.
Fixed: Was wrong, now is not
- A shared recap counts only the owner's own uploads, so a resold motorcycle can never blend two riders' history onto one public page.
2.22.0
12 July 2026Added: New in this release
- Metric, imperial or UK units, chosen once on your account and applied everywhere.
- For owners whose file download fails or arrives truncated: upload the serial-console capture instead, with a guide to taking one over cable or Bluetooth.
Changed: Different from before
- Bike cards show the real odometer and the distance your uploaded logs cover as two clearly separate figures, because on a ring-buffer bike they are not the same number.
2.21.0
11 July 2026Added: New in this release
- A reply to a feedback ticket became a conversation rather than a single answer: both sides can add to the thread, and the reply reaches you whether or not your address is verified — gating it would swallow the answer you are waiting for.
Changed: Different from before
- The dashboard headlines the real odometer, the highest reading in your logs, instead of the sum of the rides that survived in the file. On a ring-buffer bike the sum is always short, and it looked like the number that was wrong.
2.20.0
11 July 2026Added: New in this release
- A configurator for the hardware actually fitted to your bike — an upgraded pack, a swapped motor, a different controller, a supplemental charger — chosen from a catalogue rather than typed as free text. A declared pack sets the nameplate capacity that every other figure is measured against.
2.19.0
11 July 2026Added: New in this release
- A deep reading of the raw log, on request. The text is read in sections, each one summarised, then synthesised into a single verdict. It spends from your allowance, so it runs only when you ask for it.
2.16.0
11 July 2026Added: New in this release
- Garmin FIT export, beside CSV and GPX, so a ride opens in Garmin Connect and the tools that read FIT.
Changed: Different from before
- Signing out now signs you out. A sign-in was valid for 30 days whatever you pressed; sessions are ended on the server, and you can end one from your account.
- Campaign email carries the headers Gmail and Apple Mail use to offer their own one-click unsubscribe.
2.14.0
9 July 2026Added: New in this release
- The assistant and the diagnosis read Zero's own manuals: passages from the owner and service manuals for your model are retrieved and given to the model as context, instead of it answering from memory.
2.13.70
5 July 2026The manuals, and a public catalogue built out of them.
Added: New in this release
- A public catalogue of every Zero model: a searchable index with real photographs, a spec sheet per model covering motor, battery, charging, belt, suspension and brakes, and a comparison page with an efficiency column and the trade-offs drawn out.
- An owner's guide per model, ten sections and a dozen questions each, written from the official owner and service manuals: controls, riding, charging, maintenance intervals, torque figures and wear parts, with real figures from uploaded logs beside them.
- Every catalogued pack carries a researched weight and the energy density that follows from it, each with a note saying where the figure came from, because Zero publishes almost none of them.
- Attach a GPX from a phone, a Garmin or Strava and the ride gains a route map coloured by any channel, with the map and the charts highlighting each other, plus a clock alignment that proposes the offset by matching GPS speed against logged speed.
2.13.30
4 July 2026Added: New in this release
- A diagnosis centre that puts the rules first and the model second: what can be established from the log is established before anything is asked of a model, and the model cannot overrule it.
- A catalogue of error families behind every error and warning in the log viewer, so a line in your log links to what that family means.
- A thumb up or down on a ride or a charge, with a note, when a figure is wrong — and somewhere those reports are read.
- The model your VIN decodes to can be corrected by hand when it decodes wrong, and your correction wins everywhere.
- The savings-against-petrol figure works out litres per 100 km from your bike's own power instead of a fixed number, and you can override it.
Fixed: Was wrong, now is not
- Long log lines were being clipped twice over, once by the column that stored them and once on the way in.
2.13.7
2 July 2026Added: New in this release
- A read-only public demo: one click signs you into a shared account with real, anonymised data, and nothing in it can be changed.
- A public status page that probes what the app runs on and shows what is up.
- A catalogue of every Z-Force pack with a compatibility matrix, and a way to add a pack the logs cannot name: FXS battery logs carry no serial, so a physically swapped pack was being merged into the old one and never appeared.
Fixed: Was wrong, now is not
- A bike whose VIN does not decode falls back to its stored model and that model's specifications instead of reading "Unknown" everywhere.
- The timeline lands on your latest data instead of an empty current month.
- Model names containing a slash were being split, so "SR/F" displayed as "SR".
2.12.0
2 July 2026A dashboard for more than one bike.
Added: New in this release
- A fleet dashboard: account totals, per-bike statistics, costs and battery health in one read, with an AI verdict over all of it that you ask for rather than one that regenerates itself and spends your allowance.
- A charge has a page of its own now, with the curve behind it: state of charge, voltage, current, power, temperature and cell imbalance across the charge window. Sixteen list-to-detail paths that dead-ended go through.
Fixed: Was wrong, now is not
- Days since your last ride is counted from the last ride, not from the last session of any kind.
- The battery-swap detector needs a sustained jump during a deep charge, so ordinary noise no longer reads as a new pack.
2.11.0
1 July 2026Capacity, state of health, and the charges nobody recorded.
Added: New in this release
- Usable pack capacity and state of health on the battery page, estimated from charge energy against the state of charge gained over the clean charges, and shown against the badge and the usable-when-new figure rather than as one number on its own.
- Gen3 charge energy is measured instead of guessed. It had been an average power multiplied by a ring-buffer duration, which is how it came out empty or absurd; it is integrated sample by sample now.
- Charges the current-based detector never saw are recovered from gaps in state of charge — common on a bike that charges switched off — and marked as estimated everywhere they appear.
- Colour by activity in both log viewers: riding, charging, parked, warning, error, from one shared rule.
Changed: Different from before
- Measured and estimated energy are kept apart everywhere. The headline stays measured, with the estimate annotated beside it, because an estimate must never pass for a reading.
- A charge that is a plug tap — plugged in and unplugged straight away — is left out of the timeline, the counts, the energy totals and the costs.
Fixed: Was wrong, now is not
- The battery page took 17 to 43 seconds, almost all of it spent planning the query rather than running it: a handful of impossible timestamps had smeared the readings across 1969 to 2106, into roughly 3,300 weekly slices.
2.10.35
30 June 2026What a charge costs, and what the bike did while it was parked.
Added: New in this release
- A charging costs page: a flat rate or time-of-use bands, what each charge cost, per kilometre and per day, by charger, with export and a what-if.
- Charges are classified as onboard or supplemental. The onboard charger often stops below 100% while a supplemental brick finishes the job, which is a pack-imbalance signature worth being able to see.
- Parking sessions on the timeline, derived from the gaps between rides and charges, with the standby drain across each one.
- The worst and the average cell spread across every battery file for the bike, on one chart with the watch and high reference lines.
- The per-ride debrief reads real telemetry and the context you give it — riding mode, passenger, load, tyre pressure — instead of summary statistics alone.
2.10.18
30 June 2026Added: New in this release
- Ride energy is measured where the electrical telemetry exists: the integral of real power, net of regeneration, instead of state of charge multiplied by pack size.
- A chart computed from other channels carries a badge saying so, so a derived series is never mistaken for a sensor reading: cumulative energy, regeneration recovered, efficiency in Wh/km, internal resistance.
- Faults and warnings are marked on the charts where they happened, with a list of them above.
- A GPX uploaded onto a report draws the route with an elevation and gradient profile aligned to the log's own clock.
2.10.12
29 June 2026Fixed: Was wrong, now is not
- Some 538XX bikes were moved by a firmware update onto a log format nobody had decoded, so their files read as nearly empty. One owner's log recovers 97 rides and 654 km.
2.10.10
29 June 2026Fixed: Was wrong, now is not
- Battery charge detection was near-universally dead. A session ended at the first entry that was not a charge sample, and this firmware writes ordinary telemetry between them, so every charge fragmented into single samples and disappeared.
- A charge window is anchored to the file that actually carries the telemetry, which ends the 29-hour charges reported on FST bikes.
- Gen3 logs that were being routed to the empty path for the older platform are read properly.
2.10.2
28 June 2026Fixed: Was wrong, now is not
- Deleting a log file left its rides and charges on the timeline. The file and its readings went; the sessions built out of them stayed.
- A truncated or corrupted upload is identified as one, from the structure of the file and from the size every other export from that bike has had, rather than looking like a motorcycle that did nothing.
- The database was being killed for using too much memory, which surfaced as a connection closing unexpectedly and looked like a network fault.
2.10.0
27 June 2026A security and correctness review.
Changed: Different from before
- Sign-in, sessions, uploads and per-bike access were reviewed end to end and hardened.
Fixed: Was wrong, now is not
- A run of wrong numbers: a state of health above 100%, battery sizing by model, temperatures below zero read as positive, and 2019 timestamps on Gen3 files.
- Charts are grouped at the resolution asked for in the database, and a log download streams instead of being assembled whole, so both hold up on a large file.
2.9.0
10 May 2026Telemetry you can put on video, and the battery's modules one at a time.
Added: New in this release
- Export your telemetry as CSV or GPX for the video overlay tools — Telemetry Overlay, RaceRender, Dashware, Insta360 Studio, Garmin VIRB — with a synchronisation column, and with the bike-computer and battery files for the same ride merged into one export.
- Per-module battery diagnostics: contactor events, voltage range, imbalance and precharge for each module, and a warning when a module slot reports a serial it has not reported before, which is what a replaced pack looks like.
- Opening a bike-computer report finds the battery file covering the same days and draws its cell spread and weakest-cell readings beside it, each card naming the file it came from.
- Deleting a bike, with a preview of exactly what goes with it, and the same for a single log file.
- The upload page explains what each of the two file types holds, and says so when only one of them has been uploaded.
Changed: Different from before
- The parser reads the upstream library's structured output instead of its printed text. The text renames its fields with every upstream release, which is how a silent loss of data happened in May; the structured path gains a quarter more entries on a Gen2 bike computer, and thousands of battery readings that were being missed entirely.
Fixed: Was wrong, now is not
- A log that looked corrupt was not. A Gen3 bike parked long enough overwrites its own rides, and the app explains the ring buffer instead of leaving it to look like damage.
- A link to a session that has since been rebuilt resolves to its replacement instead of dead-ending.
2.8.0
6 February 2026The 2020-on platform is read.
Added: New in this release
- SR/F, SR/S and the bikes sharing their electronics are decoded: state of charge, speed, temperatures, pack voltage and current, out of files that until now yielded nothing.
- Every report says which generation the motorcycle belongs to, and a Learn page explains what changes between them.
2.7.4
5 February 2026Fixed: Was wrong, now is not
- A Gen3 log no longer takes the whole parse down with it. One record that could not be read used to abort the file; unreadable records are skipped and everything else is kept.
2.3.0
5 February 2026Changed: Different from before
- The pack a bike carries is worked out from the battery's own logs rather than from the model alone, which is the only way a capacity figure can be right for a bike with modules added or taken away.
2.1.0
5 February 2026Added: New in this release
- The Learn section gains a searchable catalogue of dash codes and log conditions, a page on what battery health means and how it is measured, and a timeline of the generations.
2.0.0
5 February 2026The first numbered release. Everything between this and the first version shipped without a number.
Added: New in this release
- A reading of a report and of each ride written by a model, with a monthly allowance you can see, and an assistant that can see the report you are looking at.
- Charging costs: tell it what you pay for electricity and it tells you what each charge, and each kilometre, cost you.
- A timeline across every file you have uploaded, a day opening into a session and a session into the report behind it, and saved reports and bookmarks to come back to.
- A PDF of a report with its charts, its statistics and its written reading.
- The Learn section: public pages explaining what a Zero log holds and what the numbers in it mean.
- Sign-in links, address verification and notifications by email.
Changed: Different from before
- Releases carry a version number, and a changelog, from here on.
1.0.0
9 December 2025The first version.
Added: New in this release
- Upload a Zero log file and read what is in it: rides and charges found in the entries, speed, state of charge, pack voltage, current and temperatures charted over time, and the decoded log lines beside them.
- Both exports are read together — the bike computer's and the battery's — with their clocks aligned, so one pair of files reads as one history.
- A profile for the motorcycle built out of its VIN: model, year, motor and pack, with the specifications that go with them.
- An account, so that what you upload is yours.
Releases before 4.0.0 are in the version list at the top: pick one to read its notes.
The record runs back to 1.0.0, the first version of this tool. Releases from 2.41.0 onwards were written for riders on the day they shipped; the older ones were reconstructed afterwards from the engineering changelog and the commit history, so they are shorter and list only what you would have noticed. Work that changes nothing you can see is in the engineering changelog only.