this exact same thing happened to me today, I just found this post while looking for some lights
this is what I have tried,
- remove the py environment used in the non working pi
- grab a requirements copy from the working pi
pip freeze > requirements
- create a new env in the non working pi
- move that requirements file to the new env
- pip install -r requirements
the issue was it was using different libraries versions, this replicates the same environment from the working to the non working pi, now it works fine
this is what I have tried,
- remove the py environment used in the non working pi
- grab a requirements copy from the working pi
pip freeze > requirements
- create a new env in the non working pi
- move that requirements file to the new env
- pip install -r requirements
the issue was it was using different libraries versions, this replicates the same environment from the working to the non working pi, now it works fine
Statistics: Posted by redstoneminer — Wed Apr 09, 2025 5:11 pm