I recently upgraded (?) an RPi4 to the latest and greatest (?) Raspberry Pi
OS, which is based upon Debian 13.1 (Trixie). I have been using a program called "radoneye" (https://github.com/sormy/radoneye) to monitor a Radoneye RD200 detector.

Now when I get the software to talk to the RD200 (via Bluetooth), it often times out and spits out 50 or so lines of whinage. Sometimes the whinage
is after the desired output, sometimes there is no useful output at all.

I can still use an RPi4 running the previous version of Raspberry Pi OS to access the RD200 (with this radoneye software), so I know the device is
still working.

I don't know whether this is an issue with the newer Python (3.13.5
vs. 3.11.2), with the Bluetooth implementation in Trixie, the software has
a bug which wasn't an apparent bug in Python 3.11.2, or something else yet.


My question (and I do have one): is there anyone here using Bluetooth via Python3 on an RPi who can comment on whether all is good for them on Trixie?

(FWIW, this software is not using bluepy.)

Thanks.
Jim

--- PyGate Linux v1.0
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, 13 Oct 2025 14:01:11 -0300, Jim wrote:

Now when I get the software to talk to the RD200 (via Bluetooth), it
often times out and spits out 50 or so lines of whinage. Sometimes the whinage is after the desired output, sometimes there is no useful output
at all.

Is this <https://github.com/sormy/radoneye/issues/5> you?

Looking down the posted traceback, the error seems to be coming from
the dbus-fast package, specifically this line <https://github.com/Bluetooth-Devices/dbus-fast/blob/cf34de432a4c51cbe7a605f453076cb0223a2b4a/src/dbus_fast/_private/unmarshaller.py#L393>.

I see python3-dbus-fast is a standard Debian package, so perhaps the
problem is down to a new version of that?

--- PyGate Linux v1.0
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025-10-13 at 18:48 ADT, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:

On Mon, 13 Oct 2025 14:01:11 -0300, Jim wrote:

Now when I get the software to talk to the RD200 (via Bluetooth), it
often times out and spits out 50 or so lines of whinage. Sometimes the
whinage is after the desired output, sometimes there is no useful output
at all.

Is this <https://github.com/sormy/radoneye/issues/5> you?

It is. I guess that means you doxxed my github account. ;-)

Looking down the posted traceback, the error seems to be coming from
the dbus-fast package, specifically this line
<https://github.com/Bluetooth-Devices/dbus-fast/blob/cf34de432a4c51cbe7a605f453076cb0223a2b4a/src/dbus_fast/_private/unmarshaller.py#L393>.

I see python3-dbus-fast is a standard Debian package, so perhaps the
problem is down to a new version of that?

It might be. As you might have seen, the radoneye author has suggested
some debugging steps which I haven't had a chance to try yet.

I found out today that the software is also having the same issues with the Debian 12 version of Raspberry Pi OS, but far less often than with Debian
13. My Debian 12 system was reliable a number of times when I tried it interactively from a terminal, but when I created a cron job to grab the
data, I have got a lot of errors. Interestingly, it has (so far) always retrieved the sensor data before dying a painful death.

On Debian 12 I get whinage ending with a couple of lines like this:

File "/home/<user>/.python-virtual-environment/lib/python3.11/site-packages/bleak
/backends/bluezdbus/manager.py", line 644, in get_services
await self._wait_for_services_discovery(device_path)
File "/home/<user>/.python-virtual-environment/lib/python3.11/site-packages/bleak/backends/bluezdbus/manager.py", line 779, in _wait_for_services_discovery
raise BleakError("failed to discover services, device disconnected") bleak.exc.BleakError: failed to discover services, device disconnected

or this

File "/home/<user>/.python-virtual-environment/lib/python3.11/site-packages/radoneye/client.py", line 51, in status
return await self.__get_interface().status()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/<user>/.python-virtual-environment/lib/python3.11/site-packages/radoneye/interface_v1.py", line 225, in status
result = await asyncio.wait_for(future, self.status_read_timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/asyncio/tasks.py", line 492, in wait_for
raise exceptions.TimeoutError() from exc
TimeoutError

Given that I see it not working well with my Deboan 12 RPi, I am surprised no-one else has reported issue on the github page. I wonder if I'm the
only person using this on a Pi.


The system that was working (apparently) flawlessly was an RPi running a
Debian 10.13 system. Which, ironically, I upgraded because 10.13 is abandonware, and hasn't had any updates for a while. So much for my
"upgrade".

Cheers.

Jim

--- PyGate Linux v1.0
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)