JianBo He

@zmstone Need your reviews Because you made a comment last time: > the 'connected' state should be set as early as possible because a lot of the following logic depend...

Hi, @ruijf Thanks for your suggestion here. We will take a team discussion later :)

Thanks for your feedback, this is very helpful feature. We've documented it and maybe released it in the next few releases.

First, the `zone.external.ignore_loop_deliver = true` option is meaning that the PUBLISHER client does not receive messages from itself. However, in this scenario, the duplicated message is sent by another connection...

@imkos Do both logs correspond to the same client? I see that their prefixes are not the same? ( `DA(1.0.15)..` and ` DA(1.1.23)..`) @zmstone In a node, it is synced....

But, it is a different client for emqx. The better design is that they should have the same `clientid` whatever firmware version is. btw, another possible reason is that the...

Hi @hydaizd Thanks for your point out it here. Maybe we need to add some fields to this structure about `properties` or something like that, i.e: ```protobuf // exhook.proto, exproto.proto...

This seems to be a failure to parse the MQTT protocol. Can you reproduce it consistently? Or provide a tcpdump of the network packet capture file.

It looks like a bug in the underlying HTTP library(cowboy). We will check it later :) Thanks for your feedback. @tangtangsara

This is an unavoidable situation. It just temporary changes by dashboard or cli The database of emqx (named Mnesia) will be reset after joining or leaving a cluster. Because we...