Koen Vervloesem

Wait, we didn't have a TheengsDecoder package then, ignore that suggestion 🙂

No I'm curious now that it's under testing whether something in a recent Decoder release leads to your issue.

Ok, I think you'll need to investigate the core dump. Are you able to do that? You need to install the `python3-dbg` package on the same machine and then run...

Do you see whether this segfault always occurs after decoding a specific Bluetooth device? Or is it random? What's the latest decoding you see as an MQTT message or in...

By the way, can you try running with log_level set to INFO instead of DEBUG to see whether that makes a difference?

Can you try to disable the RDL52832 devices, e.g. by removing their battery? If the gateway doesn't crash after this, then the segfault is probably triggered by the RDL52832 decoder.

Do you see something odd in the logs with `journalctl -u TheengsGateway`? Maybe change the log level to INFO first to see more.

And what did you change between the working and not working state? Update Theengs Gateway? Update the operating system?

> One payload went trought : Wait, so it *does* work? Did something else change so the BLE receivers are less receptive maybe? Antenna orientation, obstacles between the antenna and...

Now that I'm looking at your `theengsgw.conf` file, this looks odd: ``` "ble_time_between_scans": 100, ``` This means that your gateway is waiting for 100 seconds between every scan. I would...