MSGID:  d1cad449   
   REPLY: <10cjs36$2g2r9$5@dont-email.me> f9df783f   
   PID: PyGate 1.0   
   TID: PyGate/Linux 1.0   
   CHRS: CP1252 2   
   TZUTC: 1100   
   REPLYADDR zsd@jdvb.ca   
   REPLYTO 3:633/10 UUCP   
   On 2025-10-13 at 18:48 ADT, Lawrence D?Oliveiro  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  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   
   >.   
      
   > 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//.python-virtual-environment/lib/python3.11/   
   ite-packages/bleak   
   /backends/bluezdbus/manager.py", line 644, in get_services   
       await self._wait_for_services_discovery(device_path)   
     File "/home//.python-virtual-environment/lib/python3.11/   
   ite-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//.python-virtual-environment/lib/python3.11/   
   ite-packages/radoneye/client.py", line 51, in status   
       return await self.__get_interface().status()   
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   
     File "/home//.python-virtual-environment/lib/python3.11/   
   ite-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)   
   SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700   
   SEEN-BY: 226/30 227/114 229/110 111 200 206 275 300 317 400 426 428   
   SEEN-BY: 229/470 616 664 700 705 266/512 291/111 292/854 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/10 280 414 418 420 422 509 2744   
   SEEN-BY: 712/848 770/1 902/26 2320/105 5020/400 5075/35   
   PATH: 633/10 280 229/426