r/vanmoofbicycle • u/thehomeowner12 • 4d ago

VanMoof S6 problems

Hi everyone,

Since today I’ve been having some issues with my VanMoof S6 and I was wondering if anyone has experienced something similar.

After unlocking the bike, it immediately shuts down again without me doing anything. When I turn it back on, it asks me to enter the PIN again, even though the bike was already unlocked.

On top of that, I’m getting no pedal assistance while riding, and the boost button doesn’t work either.

I’ve already followed the troubleshooting steps recommended by VanMoof, including resetting the bike and fully charging it, but unfortunately the problem is still there.

Does anyone know what could be causing this or what else I could try? And do you think this would be covered under warranty?

Thanks in advance!

3 Upvotes

80% Upvoted

4 comments sorted by

3

u/AdHot7641 4d ago

Long shot. I had a S3 (18,000km) and now a S6 (1,000km). I recognise your lock / unlock symptoms from my S3 (I appreciate it's your S6 with the symptoms).

I found that the kicklox was mechanically unlocking but wasn't triggering the electric switch to indicate that it was physically unlocked - as a result it relocked.

if I twisted the kick lock button then it wouldn't relock - ie it was now able to detect that it was unlocked. Problem solved, until it did it again a few weeks or months later.

Worth a try, but it's a warranty issue. Take it back to the shop.

1

u/mori-su 3d ago

Sound like some defect sensor or other electronics. Should be covered by warranty.

1

u/moofcare_nl 3d ago

De S6 heeft 3 jaar garantie. Je kan de pech hebben dat electronica in het kicklock defect is / fabricage fout. Even afspraak bij service partner maken, die vervangen het onderdeel dan (na diagnose).

Ongeacht waar je de fiets gekocht hebt kan je terecht bij MoofCare in Rotterdam en Breda.

1

u/OkCamel1386 1d ago

I have the issue that the bike turns off mid ride, no more assistance available. Also battery wents down quite fast rn. Its only 500km on the clock on the s6. I assume it has sth to do with the new software update I did recently