So, installed the replacement sensors, and first full charge showed an uneven drain again. Charged then for about 12 hours and I got 40 hours or so of even drain, before it went to yellow.
Charged third time and within 5 hours of riding, left pedal was in the yellow. This is crazy. I am sure it has to be a software issue that they can rectify?!
I’m guessing this would have come up in troubleshooting so far, but if not, it’s worth confirming the left pedal is not hanging on to a connection with your phone or something. I had the left drain issue and it was because my iPhone wahoo fitness app - which I connected to once before I got the bolt and then forgot about - was persistently connected and wouldn’t let the pedal sleep. Give away was left pedal only draining and LEDs still blinking and pedal listed in the Bluetooth menu even though trainer road app and favero app were closed.
My pedals were recently returned by Favero after they replaced the right sensor because of the battery drain issue. I also think this is a software issue as i was getting drain in both pedals but Favero insisted that there was only an issue with the right sensor. My pedals were shipped back to me with firmware 3.30 which i have not bothered to update as that was running well for me from March 2018 to November before i upgraded the pedals to the latest firmware. I completed a full 12 hour charge cycle when i received them back and am experiencing the expected, consistent, drain over both pedals as per the 50 hour battery time - so no issues at the moment.
Got an email that Firmware 4.0 is out which adds pedaling dynamics. Not as interested in that as much as if it fixed the power/cadence freezing issue when using Bluetooth. Anyone tried it yet? If not I have a ride planned for tonight and will report back.
I’ve had my pedals a couple of months now and they’ve been running flawlessly. No dropouts, battery life is great. Been running on v3.0 firmware the whole time.
I just downloaded the v4.0 firmware (4.04) and intend to give them a spin tomorrow.
Great to hear. I’m so tired of having to use the ANT+ iPhone adapter.
Yippee for me. 4.04 solved the freezing for me with BLE. I could reproduce this every time by going to the pairing screen and winding up to 200+ watts and then stop. The watts would drop maybe to 50 watts less and just get stuck there. With the new firmware it drops to zero in 4 to 3 seconds. Maybe a second longer when I pair with ANT+.
Hi guys,
I have been following this thread for awhile and read all the recommendations with regards to the battery drain on favero assioma PM. i tried the same method suggested by the favero representative and have mixed results too, working sometimes but goes back to quick draining after awhile. But when i chanced upon the autosleep function on the app, i tried to change from 5mins to 30mins, then 30mins back to 5mins again, just for trial and error. To my surprise, the battery drain issue never ever happened again for an entire week. While it is a little too early to say it ‘works’, i will continue to monitor for the next week and update this forum if it happened again. Hope this helps.
Cheers
Just posting here to note that I have the power drain issue. First issue with the pedals in the year or so I’ve had them. Went to ride today, no signal - iPhone couldn’t find them, PC, Garmin Fenix, nothing. The lights on the pedals were blinking, but no apps (Assioma app, TR, Zwift etc) could see them, even after confirming no other connection issues (other device already connected etc.).
I assumed batteries weren’t an issue - I had fully charged them over the past weekend, and had only used the pedals - with no issues - for about three hours. Plugged them in anyway, and surprised to see the left pedal battery was almost dead, right pedal was almost full green.
Tried to charge them up - and the left pedal refuses to charge.
Will contact support to see what they say.
Update - Assioma said the firmware update would fix the issue - it hasn’t. Still getting battery drain issues, random dropouts with the right pedal not connecting unless the battery charger is connected (no issues with left pedal), no power or cadence.
Very disappointing. Assioma is clearly aware of this widespread issue but seem unable to address it.
Another Assioma Duo owner here. No more issues with “freezing” and I have only had the battery drain problem a couple of times, both times I suspect maybe my laptop stayed connected to the pedals for a long time? My biggest issue is constant dropouts over BT. Thought it was my Garmin head unit and I don’t really care about dropouts while I’m outside, but after hopping back on the trainer for the winter I have been having dropouts ever 2-3 minutes that last only about 1 second. I don’t think it is interference because my Kickr and HRM are both using BT and never have any issues. It also seems to happen more frequently when I transition between sitting up and leaning over, or if my pedal stroke changes slightly.
Does anyone else experience these constant dropouts?
I get occasional dropouts when out on the road, and dropouts use ANT+ FE-C on the trainer. I’d rather use ANT+ outdoors to get the pedal analytics, but I still have issues with the power never dropping to 0. Using bluetooth, the L/R reporting is reversed too.
@Lezyne Any updates coming to fix these issues?
I actually noticed when using the Windows application and Bluetooth, my Duos are left-only and it is doubling the power. Switched to ANT+ and no more dropouts, full L/R functionality.
I did experience dropouts early on and it was because my Garmin 935 seemingly randomly connected to them via Bluetooth one day rather than the usual ANT+. Took me a frustrating while to figure that out, but once I switched back to ANT+ things were good again (it also made me realize why the extra cycling dynamics type stats weren’t showing up on Connect anymore, which also had me scratching my head). It also seemed to drop out on TrainerRoad which should have been connected via ANT+, if I’m remembering right (or maybe it was just my Garmin dropping out…). Anyway, that was approaching 2 years ago though, but sounds like it could still be an issue - - maybe try the ANT+ connection with your Garmin and see if things persist?
Sorry to hear things haven’t been fixed for you. The one time it happened to me they gave me a test firmware build and that worked and I haven’t had an issue since (*knockonwood) even putting them in/out of travel mode a couple times (which I didn’t do before). It’s definitely a strange issue.
I’m seeing this on Zwift - running on iPad connected via BLE. Fave to Assioma uno…power freezes for approx 4 seconds when I stop pedalling suddenly on the upward part of my pedalling motion, a gradual slowing or drop in power is picked up fine.
New update out from Lezyne on December 6. I’ve only done a very short test with it, but it seems to have resolved the issue of power and/or cadence freezing. Chime in if you see improvements (or not!).
Recently developed the power drain issue (after a year of flawless usage) which, after logging a support ticket and receiving a very speedy response from Marco Z (thanks), resulted in v4.21 firmware being pushed to my DUO.
Sadly, that’s when the real issues have started which have basically rendered my TR/indoor training setup unusable as every device drops and/or freezes (Tickr, Kickr, power). I’ve also noticed that the TR app initially only showed the Assioma as BT (i.e. not Ant+), then later I saw it listed as a second device (one as BT, another as Ant+). I’ve done multiple t’shooting (restart, disconnect, forget devices, etc. etc) to no avail. Nothing else in my setup (other devices/connections, etc.) has changed, i.e. that might cause an issue/conflict.
After sending a follow-up to Favero/Marco v4.23 was pushed and it performed the update successfully… problems still there though.
Outdoor riding (DUO connected to Wahoo Bolt) seems fine with no issues to report over an 8hr ride yesterday. However on the indoor today all the issues persisted.
Wanted to see if others had similar issues… Or anyone using v4.21 and/or v4.23 with no issues.
For now I’ve asked Marco to reset to v4.04 which was stable for me for a long time (barring the recent battery hiccup), however the rollback had not worked (got an email on a Friday saying it should be triggered in the backend, but I haven’t seen it when connected via Assioma app several times this weekend).
Mine show up on TR desktop app as separate devices (one for BT and one for ANT+). I know that TR will preference BT and push you towards that automatically (not something you can control. Do you need to have your ANT+ connected to TR?
(Since the FW upgrade) It shows consistently as a BT device and only occasionally as a separate Ant+ device … However the Ant+ version/device doesn’t show any power, only cadence numbers.
