Errors¶
Errors raised by aio-rfcomm.
Errors that Bluetooth or the other device cause derive from
RfcommError, and are the same on every platform. The platform's own
error, if there is one, is kept as __cause__.
Errors caused by mistakes in your own code derive from RuntimeError
instead, so catching RfcommError never hides a bug.
Bases: Exception
The base class of every error that Bluetooth or the other device causes.
Bases: RfcommError
Bluetooth cannot be used. reason says why.
instance-attribute
¶
reason: UnavailableReason = reason
Why Bluetooth cannot be used. See Availability.
Bases: RfcommError
The device did not answer. It may be switched off or out of range.
instance-attribute
¶
address: str = address
The device that did not answer, as it was asked for.
Bases: RfcommError
The device does not offer that service, or refused that channel number.
The system's stored copy of the device's services may also be out of date.
Bases: RfcommError
The channel could not be opened, or the service could not be published.
Bases: RfcommError
The connection has ended: the other device hung up, or the connection to it was lost.
Once a connection has ended, and any bytes that arrived before the end
have been received, every call to receive
and send raises this.
Bases: RfcommError
receive_until found no delimiter within
max_bytes.
No bytes were read, so receive can still
read them.
Bases: RfcommError
The RFCOMM channel you asked to serve on is already in use.
Pick another channel, or leave it out to let the library choose.
Bases: RfcommError
This platform cannot do that. The message says what to do instead.
Bases: RuntimeError
Bluetooth was opened while it was already open.
Open it once, and pass the object to the functions that need it.
Bases: RuntimeError
Two tasks received on one channel at the same time, or two tasks sent.
One task can send while another receives.
Bases: RuntimeError
Something was used after its async with block ended.