@Jons1001 Do you think it could be a damaged o2 connector or loom if it's an intermittent problem? Maybe it could be that every 3 weeks or so you are hitting a bump just right that is momentarily breaking the connections/causing funny readings? Those codes would recorded but would not affect driving. It would allow you to clear them but they would reappear as soon as the loom gets jogged again. All three codes are related to the O2 sensors, so you have one code for sensor 1 Saying the engine is running lean, and another saying the same sensor is stuck rich and cannot be reached? If the sensor can't be reached, then surely it cannot tell if the engine is running lean or not?
My logic is that if these cause a CEL and you can clear it with out physically changing anything on the car, and it doesn't re appear immediately then the car is not actually running lean and the exhaust is not rich as per the codes, meaning it must be an intermit sensor/loom issue.
Can you read live data with your app? Maybe run the car and see if you can read data from the O2 sensors and see if you are getting signals?
I want to stress though that I am not a professional mechanic, I'm just using my experience from working with sensors at work. If anyone knows more than me I am happy to be educated!
Sent from my moto g(
plus using Tapatalk