gjr80 <[email protected]> writes: > I'm afraid I know little when it comes to troubleshooting i2c issues. So > running a python script to access the BME280 independent of WeeWX gives the > same error. That would seem to indicate some sort of i2c issue. Sorry, not > much help dealing with the latest error, you probably need an i2c > experienced user.
Also not an i2c expert, but a datapoint: I have a BME280 hooked up to an ESP8266 with nodemcu, and sometimes the BME280 goes out to lunch somehow so I stop getting reports. That leads to a watchdog reset after 15 minutes from not posting to MQTT (cleared in puback callback), but even on reboot I don't get temp reports. Power cycling does get it working again. I was earlier using automatic mode. I switched to forced mode, and I think I've had a failure since. I have hints that the problem is provoked by power glitches and static electricity. (The ESP8266 was powered by an old phone charger, but one that is UL listed.) I have several other ESP8266 that have Si7021 temperature/humidity sensors and those have been reliable, flaky power and crazy low humidity included. I have been thinking that my particular BME280 is damaged somehow. So I would suggest that the OP power cycle it and see if that changes anything. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/rmi35rlmviv.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
