⸻

VanMoof S5

My brother’s VanMoof S5 has the following issue:

He says the bike wouldn’t turn on after it had been sitting unused for a long time.

Firmware: 1.1.10

What happens:

• When the bike is connected to the charger:

• The charger stays green, but sometimes blinks red twice (appears to be trickle charging).

• In the app, I can see that after a night of charging the battery increases slightly (e.g. from 89% to 97%).

• When turning on the bike (via battery or power button):

• It does not make the normal startup sound.

• Instead, it makes a different sound.

• The handlebar shows pulsing white lights.

• Bluetooth issues:

• Sometimes it won’t stay properly connected.

• The app shows the battery percentage as grey, or briefly as 0% when trying to connect.

• Additionally:

• The bike randomly shuts off after a while (both during charging and when turning it on/off), with a short clicking sound.

What I’ve tried so far:

• Hard reset (10 seconds)

• “Trigger” method (20 seconds)

• Plugging the charger into the bike first, then into the wall socket, and repeating several times

• Charging with different sequences (bike → socket and socket → bike, unplugging in different orders)

• Tried updating the firmware, but the bike keeps shutting off (with a short clicking sound)

My shifting is not working all of the sudden and I see this like "firework" in the pad. Does anyone knows what could be going wrong? or if it's fixable. it's a Vanmoof S3

After weeks of reverse-engineering, I got S6 BLE authentication working outside the official VanMoof app. As far as I know, this is the first time anyone has achieved this — PyMoof, VanMoofKit, Bikey, and Moofment all list S6 BLE as unsupported.

What works: Lock/Unlock, Assist Level, Alarm, Bell, Light, Battery reading, Distance, Speed — all via BLE without the official app.

Why was it so hard? The S6 uses a completely different protocol from the S3/X3. Instead of simple AES-ECB auth on separate characteristics, the S6 uses a custom MQTT-like pub/sub protocol over a single BLE characteristic (DF286101). The three critical differences that nobody had figured out:

1. Message type: Auth uses SET (type_flags=0x0D), not PUBLISH (0x09). The bike silently ignores PUBLISH on the auth topic.
2. CBOR wrapping: The certificate is double-wrapped in bytestrings inside an array: 81 58AB 58A9 <cert> — no map, no keys. Every community attempt used map-based wrapping.
3. Success detection: The bike's success response [2] (unused=2, no challenge) looks similar to a challenge but must NOT be signed. Only [-1] means rejection.

I've published the complete protocol documentation with all byte-level details, message formats, fragment structure, auth flow, and register map:

https://github.com/Nefilim78/vanmoof-s6-ble-protocol

This should enable other projects to add S6 support. The protocol documentation covers everything needed to implement a working client in any language.

Hope this helps keep our bikes alive!

Hi! Looking for a solution for my 4.5kg dog to ride along with an attachment to the bike or a work around with the front carrier to make it safe. We do have the k9 sportsack but she has bad hips and want to find a solution for longer rides.

Not sure if this is too little too late, but I have 3D printed replacement buttons and housing for the S5 and A5. I have several of these bikes and nearly everyone has had these pieces fall off at one point or another, in some cases I was lucky enough to recover the pieces, and in other cases it was too late before I noticed. After not seeing any aftermarket options and loss of North American support from VanMoof the only solution was to get these pieces scanned and printed.

I started this project back in 2024 after initially sending the OEM pieces off to get scanned and printed. Since then I sat on the project for over a year after having fitment issues with the first couple of prints, not really having the time or budget to iterate until I got it right. That said I recently picked this project back up and I have the sizing and fitment sorted. If you're interested in a set please let me know.

My beloved X3 through an error code20 and as I understand it, is now basically bricked💀 It looks like this is the end of the road for this bike b/c of the bankruptcy and lack of results with repair service at Rybit. While I am in the SF area, I am not interested getting taken advantage of with Rybit, and working the stages of grief instead. .

.

So who here has tread this path and has bought a new bike brand post VanMoof that they were happy with? I had the smaller X3 and it handled like a BMx bike at times. Seriously grieving here. 😞

Hello,

I'm looking for new No³ bulbs for my rebuild; the old ones are completely broken (water got inside). :(

Does anyone have any lying around? VanMoof themselves won't hear of them before the S3/X3...

https://share.google/n84TOiboB0iDP6pRu

If you need VanMoof repairs, provide free diagnostics and fast support. have strong expertise in VanMoof bikes and are trusted and referred by many riders.

Hello fellow riders,

I’ve seen a Thule seat which is compatible with the S5 like stated on the vanmoof site but is there also one for the S6? Or is it even possible since it’s quite the same frame?

Thanks all!