1 回答
- 最新
- 投票最多
- 评论最多
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.
已回答 2 个月前
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前