David Lechner
David Lechner
I would try looking at D-Bus messages too. If BlueZ doesn't send the error over D-Bus, then there isn't a way for Bleak to know about the error.
It looks like the log is cut short and we don't see the replies from BlueZ after the long list of properties. It would be helpful to log both at...
Closing since the problem appears to be with BlueZ and not Bleak. Upgrading BlueZ may help solve the problem.
Selecting "write with response" or "write without response" depends on the device you are connecting to. Some devices may only support one or the other while some devices may support...
Same as #361?
Sometimes, BlueZ will disconnect if it receives an unexpected packet. For example, I have a device that sends a write response even when doing a write without response and this...
> can you fire a disconnect event for my case? The device was disconnected after all. Yes, that should be working in Bleak already. I've tested it many times using...
Can you supply the code to reproduce the problem?
The log starts with: > 2021-11-22 09:10:51.741 | INFO | __main__:main:114 - started main - version=0.0.50 Which is clearly not from the uart_service.py example. Please provide a minimal reproducible test...
Can you share the Windows Python code and C# code so we can see the difference?