1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
In researching further, this appears to be a differentiation between the MQTT 5 specification and how AWS IoT Core has implemented it. This GitHub issue appears to describe what you are seeing.
As noted by the requester, there is a workaround that may work for you too:
import { v4 as uuidv4 } from 'uuid'; // ... builder.withConnectProperties({ keepAliveIntervalSeconds: 120, clientId: uuidv4() }); // ...
Please let me know if this resolves your issue. In the meantime I'll ensure the AWS IoT Core team knows about this, either to adhere to the specification or document the difference for others.
beantwortet vor 2 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- Wie veröffentliche ich MQTT-Nachrichten von meinem Gerät auf AWS IoT Core, wenn ich Python verwende?AWS OFFICIALAktualisiert vor 3 Jahren