Stuck after "Invalid advertisement data" error. about ruuvitag-sensor

[Lalufu]

That doesn't look like a ruuvitag advertisement (it doesn't look like a valid BLE advertisement at all unless there's some data getting lost somewhere). From the code, this should just cause the sending MAC to be blacklisted, but the process as a whole should move on.
How many tags do you have? Are you losing data from all of them after this?

[eRazeri]

Thank you for your reply!
I have only one tag in that location.
This was happening before and after upgrading the firmware of the ruuvitag to the latest.
So if it blacklists the MAC, then I understand that it stops to read data from this tag.
For now I just restart the container manually and all seems to work after it.
Could I somehow set the process to restart, exit the process or to crash the container when this happens?

[ttu]

Hi @eRazeri!

This sounds like a docker / system specific problem, so I wouldn't add any custom functionality for this case.

We can utilize Python log's custom handlers to make the process to exit when specific MAC is blacklisted. Handler will listen for all log events and will exit when we receive a log message that matches the condition.

from ruuvitag_sensor.ruuvi import RuuviTagSensor
import ruuvitag_sensor.log

from logging import StreamHandler

class ExitHandler(StreamHandler):

    def emit(self, record):
        if (record.levelname != "DEBUG"):
            return
        msg = self.format(record)
        if "Blacklisting MAC AA:BB:CC:DD:EE:FF" in msg:
            exit(1)


#ruuvitag_sensor.log.enable_console()

exit_handler = ExitHandler()
ruuvitag_sensor.log.log.addHandler(exit_handler)

if __name__ == "__main__":
    RuuviTagSensor.get_data_for_sensors()

Let me know if this solution solves your problem. I will close this issue, but if this solution doesn't work, please reopen the issue.

[eRazeri]

Hi @ttu!

Thank you very much!
Sorry for the long delay in answering, it took me a long time to verify because the error is very random.
With your code as base, I was able to catch the error and restart the container.
I did change your code a little to work for me. I'm checking for the "Invalid advertisement data", because I never encountered this "Blacklisting MAC" message in my enviroment.

[Lalufu]

I'm still confused as to how we get this data in the first place, as it doesn't seem to conform to the specification for BLE messages. Maybe parsing the output from hcitool goes wrong somewhere?
If you can turn up the debug level in your application to debug you should get some useful output. Unfortunately it'll be a lot of output, so I'm not sure whatever system you're using can store this.