Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 3: invalid continuation byte #11

Open
ZeroSebastian opened this issue May 7, 2022 · 2 comments · May be fixed by #13

Comments

@ZeroSebastian
Copy link

ZeroSebastian commented May 7, 2022

Is there a specific reason why the package has to be installed with the deprecated setup.py install way?
Whenever I try to install it with this command the package is not found afterwards (it is installed into /usr/lib/python3.7/site-packages and not into /usr/local/lib/python3.7/dist-packages and i honestly do not understand why).
Because of this, I chose to install it with pip3 install . instead.
Whenever I try to import the module in python I get this error (also when executing the examples):
from bme68x import BME68X UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 3: invalid continuation byte

Does this happen because I did not install the module with setup.py install? If yes, where did I go wrong? I followed the provided instructions video.

@ZeroSebastian
Copy link
Author

ZeroSebastian commented May 26, 2022

Edit: I tried again with the sudo python setup.py install approach and added the path where it is installed ( /usr/lib/python3.7/site-packages) to the python sys path . I still get the same issue.
Can anybody help me with this?

@ZeroSebastian ZeroSebastian linked a pull request May 26, 2022 that will close this issue
@mcalisterkm
Copy link

The BSEC library is supplied by Bosch and you have to request it, and follow the instructions from PI3G.
If you do a pip install the package is missing the BSEC library, and lots of functionality is missing.

BOSCH have patched the library and you will see this a causing other issues, due to the update name change.

What sort of PI (Zero Zero 2, 3 , 4) and what flavour of raspbian are you using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants