-
Notifications
You must be signed in to change notification settings - Fork 75
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
binascii.Error occasionally #35
Comments
This is already handled in the library code, so it might be that error is just written to stdout, but the execution continues. Is there anything else in the log file? I wonder why RuuviTag broadcasts https://ruu.vi/#w? Maybe there is something wrong with the conversion of hex data. |
Ok, I'll update when the new version appears in pypi. No, just those tracebacks. Perhaps those are just interference in radio wavers or something? |
I forgot to mention: all RuuviTags are in high precision mode so they are not broadcasting URL. |
Then it seems that there is something wrong with the data conversion. Could you add a print statement before this line and keep it running until it crashes? With that I could try to check what is wrong with the conversion function. |
I got this after running the script several hours: "Z^Y*I`^X" I guess And this is also in the error log:
|
Sorry, my bad, I gave a bad guidance. Could you add this line |
I get the same issue, here is the result from print(ble_data[1]) on line 160:
|
Can't reproduce this error anymore. Decoder and payload handling has been updated after this issue was opened. If this error appears again, let's open a new issue. |
I use RuuviTagSensor in my own script and it seems to crash every now and then in call
datas = RuuviTagSensor.get_data_for_sensors(macs, timeout_in_sec)
(macs is [], timeout is 4) with traceback below:
I'm trying to avoid this (from now) by catching this exception in my code, but I think this should be handled in RuuviTagSensor library, which could raise a custom exception or something.
What do you think?
The text was updated successfully, but these errors were encountered: