# I2C flakiness when using battery-powered Notecarrier A with Raspberry Pi **URL:** \ **Category:** Hardware\ **Created:** [April 14, 2025, 8:03pm UTC](https://discuss.blues.com/t/i2c-flakiness-when-using-battery-powered-notecarrier-a-with-raspberry-pi/2987 "2025-04-14T20:03:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![NeilT](https://avatars.discourse-cdn.com/v4/letter/n/4bbf92/32.png) [@NeilT](https://discuss.blues.com/u/NeilT)\ **Post date:** [April 14, 2025, 8:03pm UTC](https://discuss.blues.com/t/i2c-flakiness-when-using-battery-powered-notecarrier-a-with-raspberry-pi/2987/1 "2025-04-14T20:03:11Z")
Hi, I’m using a Notecarrier A (housing a NOTE-NBGLN) connected to a Raspberry Pi Zero 2W. I2C connections are over the Pi GPIO 2/3 to SDA/SCL on the Notecarrier, plus a common GND. (I’m using the Notecarrier A instead of the Notecarrier Pi as I would like to keep the notecard powered on, even when the Pi is shut off) When the Notecarrier is powered by USB, the Pi detects the Notecard. i2cdetect shows the expected address and everything works. However, if the Notecarrier is powered by a battery (I’m using a 3.7v 18650 connected to the LiPo JST connector), I2C only works intermittently. I’ve tried various configurations: 1. Notecarrier and Pi both powered by same USB source feeding into their respective USB inputs (works) 2. Notecarrier connected to USB power source, Pi connected to battery (works) 3. Notecarrier and Pi both connected to the battery (flaky) 4. Notecarrier to battery and Pi to USB (flaky) So the problem appears to be the Notecarrier being powered by the battery. However, events and status updates to notehub are being sent by the notecard as expected while on battery power (I’m running it on continuous mode for now); it’s the I2C connection that’s misbehaving. Is the notecarrier very picky on the type of battery it works with? I’m using a 4-cell version of this (which give me around 10k mAh) [https://www.18650batterystore.com/products/epoch-18650-2600mah-8a-protected-button-top-battery](https://www.18650batterystore.com/products/epoch-18650-2600mah-8a-protected-button-top-battery) Or is this some kind of bus timing issue? Are there additional connections/pull-ups I need to provide for this config to work? Or connect battery directly to V\_in? Notecard details: NOTE-NBGLN, Firmware version 7.5.2.17004 + Notecarrier A (non-legacy) Thanks! ---
**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\ **Post date:** [April 15, 2025, 1:27pm UTC](https://discuss.blues.com/t/i2c-flakiness-when-using-battery-powered-notecarrier-a-with-raspberry-pi/2987/2 "2025-04-15T13:27:47Z")
Hi @NeilT and welcome to the Blues community! Unfortunately I2C on the Pi is [notoriously flaky](https://cdn-learn.adafruit.com/downloads/pdf/raspberry-pi-i2c-clock-stretching-fixes.pdf), so in these situations we recommend connecting to the Notecard/Notecarrier via TX/RX (GPIO 14/15) instead of I2C. Here’s a link to our example in the note-python repo: > Hope that helps! Thanks, Rob ---
**Author:** ![NeilT](https://avatars.discourse-cdn.com/v4/letter/n/4bbf92/32.png) [@NeilT](https://discuss.blues.com/u/NeilT)\ **Post date:** [April 16, 2025, 11:58pm UTC](https://discuss.blues.com/t/i2c-flakiness-when-using-battery-powered-notecarrier-a-with-raspberry-pi/2987/3 "2025-04-16T23:58:00Z")
Hi @RobLauer, thanks for the pointers. I’ll try out the serial option and report back how it goes. Do you also recommend this route when using the Notecarrier Pi? I haven’t had any issues in that setup. ---
**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\ **Post date:** [April 17, 2025, 1:30pm UTC](https://discuss.blues.com/t/i2c-flakiness-when-using-battery-powered-notecarrier-a-with-raspberry-pi/2987/4 "2025-04-17T13:30:50Z")
Hi @NeilT, Personally I’ve never had trouble with a Pi 4 or Pi 5 when using I2C and a Notecarrier Pi. And then a colleague was unable to get his Pi 5 to communicate at all?! At this time there is so much confusion online about whether clock stretching has been “fixed” that we just don’t have any firm guidance right now. Definitely something we continue to monitor though. Rob