No doubt. I’m just glad it’s no longer stuck at 100% like it was on the wired charger. I think all that’s going on is the dock is turning the coil off to let the battery drain a bit, then pulls it back up.
1 Like
Agree, but from everything I’ve read this isn’t doing anything helpful to this battery chemistry type.
1 Like
It might be letting the battery reach resting voltage and then doing passive balancing….at least that is what I hope. There should still be an 80% hold function like all modern BMSs have…
2 Likes
I can only hope that the BMS is doing what it’s supposed to do and that the sensor data isn’t being read correctly. But, I agree, there should be a hold function that the user can set and modify. IE Max charge percentage with a toggle for “auto optimized” to charge to full when the unit interprets an impending job (like a schedule about to start).
2 Likes
I’ll also add that the “auto optimized” full charge should also be a button push on the main screen for those that want to manually fill it up to 100% for a big job.
4 Likes
If that’s the case, it doesn’t need to cycle repeatedly for days, and it doesn’t look like this is happening when physically connect to the wall charger.
1 Like
I think the dock is just turning on and off to let the battery not be pegged at 100%. Since the battery percentage drop does not work with Yarbo plugged in, it makes me think the BMS capability is just there to not overcharge the battery and that’s about it.
1 Like
My suspicion is this is not at all the case with the current hardware and we’re looking at the most basic feature which is only “the BMS won’t let the battery overcharge”.
2 Likes
The claim that some sort of battery is conditioning is going on is total BS. Shocking that Yarbo marketing work push the boundaries of truth.
Sorry…. didn’t mean to beat a dead horse.
OK updated the album and added my template codes, could probably be done a bit simpler but I’m just going to leave it for now, I did tweak a couple settings just a little from what this image shows:
The HA foo is strong with this one.
1 Like
After playing with the Integration for a week, I can report that it’s not stable in its current state and will cause issues. It still has some usefulness for data logging as we’ve seen for the charging. I recommend keeping it disabled except for this. There hasn’t been any recent development progress either. Maybe Yarbo can use it as a baseline to get an authorized API in our hands.