-
Notifications
You must be signed in to change notification settings - Fork 4
Brokers
This page serves as a register for implementation specifics. Please keep the broker list in alphabetical order.
Amazon deviates from the standard on several significant points.
Configure the mqtt.Client
with AtLeastOnceMax
and ExactlyOnceMax
each set to either 0
or 1
, to prevent seemingly random connection errors.
🛫 ReadSlices
may encounter mqtt: broker closed the connection (EOF); CONNECT not confirmed
during daemon startup shortly.
👻 The broker sometimes drops messages from batches as small as 100 sequential messages, with “exactly once” delivery [QoS level 2].
🛫 ReadSlices
may encounter mqtt: broker closed the connection (EOF); CONNECT not confirmed
during daemon startup.
👻 The broker sometimes drops messages from batches as small as 100 sequential messages, with “exactly once” delivery [QoS level 2].
✅ No problems were found.
🛫 ReadSlices
may encounter mqtt: broker closed the connection (EOF); CONNECT not confirmed
during daemon startup shortly.
🛫 Subscribe
may encounter mqtt: broker failed 1 topic filters
during daemon startup shortly.
🛫 Publish
may encounter mqtt: broker closed the connection (EOF)
during daemon startup shortly.