We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
使用EMQX自动订阅成功后, 发送数据 设备接收不到, 需要删掉订阅,再重新订阅设备才可以收到数据。 这个是老版本已知BUG吗?
自动订阅成功,发送数据 能够设备接收到。 "6238":100 表示设备成功操作对应命令
No response
5.0.11
# On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here
2023-12-08T06:33:59+00:00 [PUBLISH] I0622A043677@120.133.129.213:58068 msg: publish_to, topic: r, payload: {"7110":159,"7114":12,"7121":214,"7122":159,"7159":5666,"7174":5688,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"} 2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_sent, packet: PUBLISH(Q2, R0, D0),Topic=I0622A043677/w, PacketId=18Payload= {"Control":"0206185E0064EF60"} 2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBREC(Q0, R0, D0),PacketId=18, ReasonCode=0 2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.19.213:58068 msg: mqtt_packet_sent, packet: PUBREL(Q1, R0, D0),PacketId=18, ReasonCode=0 2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBCOMP(Q0, R0, D0),PacketId=18, ReasonCode=0 2023-12-08T06:34:02+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBLISH(Q0, R0, D0),Topic=r, PacketId=undefinedPayload={"6238":100,"7110":175,"7114":10,"7121":210,"7122":175,"7133":8192,"7159":5672,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"} 2023-12-08T06:34:02+00:00 [PUBLISH] I0622A3677@120.133.1.213:58068 msg: publish_to, topic: r, payload: {"6238":100,"7110":175,"7114":10,"7121":210,"7122":175,"7133":8192,"7159":5672,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"} 2
The text was updated successfully, but these errors were encountered:
@hjy30312 please help us to reproduce the issue by providing minimal test scenario.
Sorry, something went wrong.
No branches or pull requests
What happened?
使用EMQX自动订阅成功后, 发送数据 设备接收不到, 需要删掉订阅,再重新订阅设备才可以收到数据。
这个是老版本已知BUG吗?
What did you expect to happen?
自动订阅成功,发送数据 能够设备接收到。 "6238":100 表示设备成功操作对应命令
How can we reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
No response
EMQX version
5.0.11
OS version
Log files
2023-12-08T06:33:59+00:00 [PUBLISH] I0622A043677@120.133.129.213:58068 msg: publish_to, topic: r, payload: {"7110":159,"7114":12,"7121":214,"7122":159,"7159":5666,"7174":5688,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"}
2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_sent, packet: PUBLISH(Q2, R0, D0),Topic=I0622A043677/w, PacketId=18Payload= {"Control":"0206185E0064EF60"}
2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBREC(Q0, R0, D0),PacketId=18, ReasonCode=0
2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.19.213:58068 msg: mqtt_packet_sent, packet: PUBREL(Q1, R0, D0),PacketId=18, ReasonCode=0
2023-12-08T06:34:00+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBCOMP(Q0, R0, D0),PacketId=18, ReasonCode=0
2023-12-08T06:34:02+00:00 [MQTT] I0622A043677@120.133.129.213:58068 msg: mqtt_packet_received, packet: PUBLISH(Q0, R0, D0),Topic=r, PacketId=undefinedPayload={"6238":100,"7110":175,"7114":10,"7121":210,"7122":175,"7133":8192,"7159":5672,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"}
2023-12-08T06:34:02+00:00 [PUBLISH] I0622A3677@120.133.1.213:58068 msg: publish_to, topic: r, payload: {"6238":100,"7110":175,"7114":10,"7121":210,"7122":175,"7133":8192,"7159":5672,"sign":"J","ADDR":2,"type":3,"CSQ":"31","GBASE":"460,00,891B94B,7055"}
2
The text was updated successfully, but these errors were encountered: