New plugin for BME280 temperature/humidity/pressure sensor

atus

I wrote a new plugin for the BME280 sensor using the node-bme280 driver.
The code is here:https://github.com/atus/pimatic-bme280
The package is here: https://www.npmjs.com/package/pimatic-bme280

This is my first contact with coffee script and publishing an npm package so let me know if something needs fixing.

The plugin works for me, but if you find issues, please let me know on atus/pimatic-bme280#issues or submit a pull request.

leader21

Very nice!! Thx a lot for your efforts!!

atus

Thanks @leader21, let me know if I need to do anything else to get this into the official plugin list.

mwittig

@atus said in New plugin for BME280 temperature/humidity/pressure sensor:

let me know if I need to do anything else to get this into the official plugin list.

It’ll be added automatically, but it apparently the updater has not been run since last Sunday for some reason. We’ll look into this asap.

I have briefly reviewed your plugin and I have a few comments:

Please be so kind to add a proper README to your plugin project. Thanks!
Using setInterval() for requestValue() updates may cause problems in case the callback functions triggered by sensor.begin() and/or sensor.readPressureAndTemparature() are deferred for some reason. In this case requestValue() callouts may pile up. Use setTimeout() instead and re-schedule the task within the inner callback function. You should also add better error handling. i.e. check the “err” parameters of the outer and inner callback functions.
As part of the device config schema you should also set the extension “xAttributeOptions” in addition to “xlink”. This way, users will be able to hide an attribute’s sparkline or value from display.

atus

Readme - DONE
xAttributeOptions - DONE
and pushed, patched npm

the setInterval() and error handling is on my TODO, I have to get some time to test it.

is this proper error logging?

env.logger.error "Error in AnswerPredicateHandler:", error.message
env.logger.debug error

mwittig

@atus Excellent! Meanwhile the update script is back to normal, but for some reason it did not find you plugin. I’ll check again if sopmething is missing and get back to you.

atus

@mwittig Still not seeing this in the list of plugins. Is there anything I should do?

leader21

We’re still investigating what the issue is. Stay tuned for more …

sweetpi

@atus Good new: I was able to solve the Problem: We used a deprecated npm registry endpoint to get the package list (http://blog.npmjs.org/post/157615772423/deprecating-the-all-registry-endpoint). I migrated the plugin update script to a the new endpoint. Your plugin is now listed. Thanks for your patience.

S O

I think this should include at least “processingTemp”: “$value” as BME280 tend to show couple of degree too high, so it could be calibrated correctly.

https://github.com/atus/pimatic-bme280/issues/1

atus

There’s a pull request to fix most things mentioned here. @mwittig please review. Others are also welcome to review.

@mwittig said in New plugin for BME280 temperature/humidity/pressure sensor:

Using setInterval() for requestValue() updates may cause problems in case the callback functions triggered by sensor.begin() and/or sensor.readPressureAndTemparature() are deferred for some reason. In this case requestValue() callouts may pile up. Use setTimeout() instead and re-schedule the task within the inner callback function. You should also add better error handling. i.e. check the “err” parameters of the outer and inner callback functions.

If you still care about this, please point me to an example. I haven’t noticed issues with the current approach so far.

S O

BME280 need to have possibility to calibrate. It is notorious for overheating issues, and I dont trust humidity as well…