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.
With rtl_433 did you still have WeeWX running? Perhaps there was a zombie WeeWX process that still held the USB port used by your sdr. Have a look at the list of running WeeWX processes using something like: $ ps -aux|grep weewx and kill any that are still there. Then try rtl_433. Does WeeWX run without error as a daemon if you disable the BME280 service and just run your sdr driver? Gary On Friday, 6 August 2021 at 21:23:34 UTC+10 wxwatching wrote: > And just in case this helpful, here's my i2c output: > > sudo i2cdetect -y 1 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- 76 -- > > > >> >> -- 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/7fbda9d8-71f2-4fd1-8d08-ffde356baaabn%40googlegroups.com.
