Open badazz91 opened 9 years ago
I'm looking into it. Most likely a problem with that specific version of the I2C library on your pi. Hopefully I'll post a fix in a few days.
Thanks!
Hey @isaaczinda, did you get around to finding a fix?
Peer, What model of raspberry pi are you using? My code has only been tested on the raspberry b+, as this is the only one available to me. I am traveling now, but when I return home I'll try an install on my system and try to reproduce your problem. However, I might not be able to get around to it for a while, so maybe try to look into another solution. Best,-Isaac Zinda
On Mon, Apr 11, 2016 at 1:48 AM -0700, "Peer Jüttner" notifications@github.com wrote:
Hey @isaaczinda, did you get around to finding a fix?
You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/seattleacademy/mcp9808/issues/2#issuecomment-208234968
Isaac, I'm using the rpi2. I've been looking for an alternative but havn't found a good one yet, so I might write one myself... Thanks for the info! Peer
Hi Isaac,
I am hitting the same issue on RPI3 with the latest Raspbian Jessie. The issue seems to be that you are using an older i2c version. Switching to the latest one ("i2c": "^0.2.3") fixes the problem. Do you want to address this on your side or you want me to submit a pull request?
-Nash
@nashneshev I think it would be easiest if you submit a pull request with those changes, and I will merge. Thanks for the suggestion!
Hey,
I'm trying to use it with my raspberry pi Modell B+. But I get this error when installing it via npm.
Is this a bug? Or am I doing something wrong? Thx.