ludiazv / node-red-contrib-bme280 Goto Github PK

this node does lose any message properties of the received message.
msg.req msg.res to be also lost, it isn't possible to use in HTTP In/Response.

Just need to clarify something, if the node reports "Sensor Init failed ->Error: , Remote I/O error" it appears the payload is never forwarded? How does on then handle errors? Looks like node only reports errors to the debug stream?

gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:219:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
gyp ERR! System Linux 4.19.75-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/.node-red/node_modules/bme280-sensor/node_modules/i2c-bus
gyp ERR! node -v v13.3.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-12-07T17_12_40_774Z-debug.log

Hi

the BME280 shows me an address validation error. NaN is not defined, despite the number being filled (0x76).

Any idea? Tried deleting the node and putting in a new one, but the issue persists.

Request that node test for presence of sensor before attempt to initialize same. Is sensor not found do not attempt to initialize sensor. Do not endlessly attempt to initialize sensor if not found as well. Suggest allow operator set the number of times node should try to initialize sensor. Suggest allow operator to select action to be taken if sensor disappears after once present, such as only search bus to rediscover sensor, or just report sensor missing.

Hello,

im looking for a way to connect a BME280 via USB-I2C to my PC (Windows).
My idea was to use something like this :
https://www.amazon.de/I2C-MP-USB-I%C2%B2C-USB-Adapter-Evaluations-Board-SMD/dp/B07VSMW6P6/ref=pd_lpo_2?pd_rd_i=B07VSMW6P6&psc=1

BME280 -> I2C-USB-Adapter -> PC -> Node-Red -> node-red-contrib-bme280

Did someone tried something like this already?
I dont need a controller since the node provides the code right?
Could this work out the way i described the idea?

best regards

Your module appears to cause the i2c scan to slow down significantly if the sensor was found, but later is not found. This should not happen, if the sensor is missing or disappears, the scan should still be quick. You can recreate this issue by adding a different sensor to the i2c bus, in place of the bme280, say a SHT3X sensor, but leave the BME280 flow in node red as is. Then run i2cdetect -y 1 and the detect scan will be horribly slow. Removing all sensors, i.e. SHT3X sensor, the scan returns to normal speed. This again can be illustrated by direct i2cdetect -y 1 from the command line. As long as your module is in an active flow, the slow down occurs, when the bme280 disappears or another sensor is on the bus other than the bme280.

In order to calculate the altitude the sea level pressure is needed.
your algorithm considers the pressure at sea level = 0 which is wrong.
Maybe it should be a parameter we can pass in so we can change that.

NR 3.0 (Node.js 16.0) fires a parameter error I2C-Address. Reason is the wrong Statement isNan() in the html-File (package node-red-contrib-bme280).
Correctly the statement is isNaN().
Nevertheless the node is working fine
Hope, it will help and please update the Code