# RV3028 BreakoutRTC - Pico 2W + Breakout Garden - device not recognised

**URL:** <https://forums.pimoroni.com/t/rv3028-breakoutrtc-pico-2w-breakout-garden-device-not-recognised/29034>\
**Category:** Support\
**Created:** [August 5, 2026, 9:55am UTC](https://forums.pimoroni.com/t/rv3028-breakoutrtc-pico-2w-breakout-garden-device-not-recognised/29034 "2026-08-05T09:55:58Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![hel](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/hel/32/6075_2.png) [@hel](https://forums.pimoroni.com/u/hel)\
**Post date:** [August 5, 2026, 4:45pm UTC](https://forums.pimoroni.com/t/rv3028-breakoutrtc-pico-2w-breakout-garden-device-not-recognised/29034/8 "2026-08-05T16:45:56Z")

</div>

Thanks!

I think I’ve figured it out - it’s a problem specific to our C++/MicroPython driver so didn’t show up on our tests as production test breakouts using big Raspberry Pis.

Turns out newer RV3028 chips have a different hardware identification number (0x44 instead of 0x33) so we’ll need to update the driver to accommodate this.

I created an issue here if you want to follow it: [RV3028: `BreakoutRTC: breakout not found when initialising` · Issue #1135 · pimoroni/pimoroni-pico · GitHub](https://github.com/pimoroni/pimoroni-pico/issues/1135)  
and some fixed builds here (just RP2040 boards at the moment):  
[rv3028: add new chip ID/version · pimoroni/pimoroni-pico@73bfb7f · GitHub](https://github.com/pimoroni/pimoroni-pico/actions/runs/31024951781)

---

_[View the full topic](https://forums.pimoroni.com/t/rv3028-breakoutrtc-pico-2w-breakout-garden-device-not-recognised/29034)._
