Your module apparently causes the i2c scan to slow down signficantly if the sensor disappears or another sensor is added after the bme280 sensor disappears? about node-red-contrib-bme280 HOT 2 OPEN

I have to test this scenario. Possible is due constant retries to contact with the missing sensor. At some point it should stop retrying and inactivate the node until new deployment.

from node-red-contrib-bme280.

Yes, I only discovered it, because I happen to be changing sensors in and out, and discovered this odd slow down side-effect. I changed my flow, adding a gate, so that the bme280 node never receives a message, unless I enable said flow. What I want to do, is somehow scan the i2c bus and only open the gate if a bmp280 or bme280 is present. Maybe your solution could be enhanced to try to initialize the sensor only if the sensor is present on the bus? Log error if sensor not found type of thing? I have 8 different sensors, across 12 devices, that report temperature, pressure, humidity, so in my python scripting I validate which sensor is present before attempt to use same. A good method for BMP/BME sensors is to query for the serial number of the sensor, if BMP do X, of BME do Y, for other sensors, search for device at the appropriate address, if MCP9808 do A, if Si702 do B, if SHT3X do C, etc., etc., if none of the above report no ambient sensor found.

from node-red-contrib-bme280.