MQTT error or command subscription could be skipped
See original GitHub issueIn AbstractVertxBasedMQTTProtocolAdapter.onSubscribe
the subscribe topics are iterated and when processed are put in uniqueSubscriptions
map. If a topic is already in that map it is skipped.
The map key however is based only on tenant and device id - no difference if it is an error or command subscription. So if we have subscription request for both, error and command, for the same device then one of the subscriptions would be skipped.
PS: if it is really a bug, I could implement a fix
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Resolving problem: Lost messages in an MQTT application
Resolve the problem of losing a message. Is the message non-persistent, sent to the wrong place, or never sent? A wrongly coded client...
Read more >MQTT Client Error Codes - VTScada
Error code (Decimal) Error code (Hex) Meaning
0 0x0 No Error
1 0x1 Connection Refused: Unacceptable protocol version
10 0xa Timeout waiting for SUBACK
Read more >client does not get missed messages once connected again ...
Once the client throws a WS error and reconnects it will not receive the missed messages. The same goes for MQTTlens, after it...
Read more >MQTT Connection Refused - Google Groups
I've connected to Home Assistant with MQTT Explorer and been able to publish to a test topic, so that end of things appears...
Read more >MQTT command and control (automatic subscription topics)
The data logger will issue a HTTP(s) GET to the specified URL and report success or failure on the <groupID>/state/<deviceID> topic. If successful,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
PRs for 2.0.x and 1.12.x are ready: #3322 and #3323
@avgustinmm Can you also create PRs with the changes from #3320 for the 2.0.x and 1.12.x branches?