Why use i2c-bus versus i2c?

[dachshund-digital]

Why use i2c-bus versus i2c? You mention this in the read me, usage text. Just wondering why you did it?

[aphotix]

@dachshund-digital Great question. One of the big drivers was the fact that another project (fehmer/adafruit-i2c-lcd) I was depending on also used i2c-bus. I didn't want my project to use two different i2c packages. I also considered a few ancillary reasons:

• i2c has not been updated in 4 years, whereas i2c-bus was updated 2 months ago
• i2c-bus offers a more permissive MIT license (vs BSD-3) and I wanted my project and all dependencies to be very permissive
• I found it very easy to use promises with i2c-bus (and by extension async/await) but found it more of a challenge with i2c. Granted if I tried again today I may not have the same challenges as I've learned a ton since I originally worked on this.

[dachshund-digital]

Very informative. I am just getting my feet wet with node-red, and am going to be writing a few node packages for some i2c sensors that as yet don't seem to be in npm for node-red. The bme280/bmp280 sensor is, but not the SHT3X for example. Unfortunately all my i2c experience is with python not nodejs. So I have some learning to do. Using your project as a guide, should be quite educational. I should just be able to create the node-red wrapper around your project.