Issue with Sense HAT in combination with PiSugar 2 Pro

[Gerald-Dicker]

When I install the PiSugar 2 Pro in combination with Sense HAT on my Raspberry Pi 4 Model B, none of them work anymore.

When I run "i2cdetect -y 1", it returns all 128 possible addresses with both devices installed. However, with only Sense HAT installed on the Pi "i2cdetect -y 1" correctly returns: 1c, 46, 5c, 5f, 6a, and with only the PiSugar installed, it correctly returns: 32 and 75.

According to what I found on the internet, Sense HAT uses GPIO pins 2 and 3 for the SDA and SCL signals. Apparently also PiSugar2 Pro uses these two pins for SDA and SCL, but not sure which pin (2 or 3) for which signal...

Does anybody have an idea of the potential problem and solution?

Regards, Gerald

[JdaieLin]

@wlmh110

[eplamers]

I'm running into this issue as well. Interested to find a solution, will start digging through PiSugar & SenseHat code

[Gerald-Dicker]

Hi, the PiSugar team already know what the problem is and will fix it with their Version 3, expected in H1 this year. Hope this helps

On 7 Apr 2021, at 16:56, eplamers @.***> wrote:

I'm running into this issue as well. Interested to find a solution, will start digging through PiSugar & SenseHat code

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSugar/PiSugar/issues/32#issuecomment-814982692, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARRO4N4B5IN4NYF5JR6FEMTTHRXARANCNFSM4XZ66USA.

[Jdec2004]

I'm having the exact same problem with the yahboom cooling hat. Is this a problem with the code or the hardware?

[lmf-github]

Any update on if this issue with the SenseHat was solved (and what is referred to in the above post- Version 3 of what, the driver?). Have an issue with another Hat, and wondering if the solution to this SenseHat issue will fix this too, and if so how to apply the fix?.

[RedHandShepard]

Yeah i would love an update as well. V3 of what? Is it software? or did i waste 60 bucks just to have to buy another newer version they didn't botch the hardware on? If its a hardware thing witch one works?

[RedHandShepard]

Just realized these others asked their questions months ago and didn't even het an answer. That's sad. Guess the pisugar team doesn't care that they sold us garbage advertised as leaving the gpio free for projects. As far as im concerned yall owe us refunds

[wlmh110]

Any update on if this issue with the SenseHat was solved (and what is referred to in the above post- Version 3 of what, the driver?). Have an issue with another Hat, and wondering if the solution to this SenseHat issue will fix this too, and if so how to apply the fix?.

@RedHandShepard

Sorry, this question is the same as another issue and has not been answered in time Please contact the after-sales team at the following email address for assistance pisugar.zero@gmail.com

[joemeaux22]

Hello. Sorry to dredge up a dead issue. Did the questions above ever get answered? The response above mentioned it is the same as another issue, can someone point me to that issue?

[RedHandShepard]

Not solved. Waiting on new version of product.

On Sat, Mar 19, 2022, 12:26 AM joemeaux22 @.***> wrote:

Hello. Sorry to dredge up a dead issue. Did the questions above ever get answered? The response above mentioned it is the same as another issue, can someone point me to that issue?

— Reply to this email directly, view it on GitHub https://github.com/PiSugar/PiSugar/issues/32#issuecomment-1072937428, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMSTVMFLPNNLL2T5DB6NHVLVAVJQFANCNFSM4XZ66USA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[joemeaux22]

Thank you for the reply. I'll keep an eye out for next version.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.