Donovan Buck

Can you share your code?

I can't test (I'm at work), but I suspect initializing a sensor on that pin will reset it to a normal input. Have you tried setting the pin mode after...

That's my fault. PR #1690 was submitted, and I updated the docs, but the PR was never merged because tests were failing. It's a good change, so I'll see if...

@Jenesius Johnny-Five doesn't have support for the nRF24, and I doubt it ever will. Even the [Nordic site](https://www.nordicsemi.com/products/nrf24-series) recommends using Bluetooth for new projects. I always hate when someone responds...

Since Johnny-Five requires a host computer running node, it's probably easier to have a radio (or bluetooth or wi-fi) connection to each Arduino in parallel rather than relaying from on...

My only concern is that this doesn't solve things for the auto-addressing of multiple HT16K33s across multiple boards. What if we stored addresses in a WeakMap with boards as keys?...

There are a couple of things I'm noticing. First, when running `npm test` locally, my machine reports a failure on the sip.js IMU -- BNO055 data test. By the time...

Regarding the first issue, the first firing of i2cReadOnce comes from sip. The others are coming from the proximity.js SRF-10 read callback (line 100).

That totally makes sense, and thanks for the quick reply. I'll see if I can figure out a good way to distinguish calls to i2cReadOnce between sip and proximity.

This is interesting. Here's what I think is happening... The HT16K33 is an addressable I2C device. Both of yours start at 0x70, which I believe is the default value. If...