Subscribing to messages using Homie.getMqttClient() is not reliable: topic is truncated #526
Conversation
|
I tested it, seemed correct. Unfortunately I do not have any test environment nor something with robust tests; I just tested with some code examples |
…topic is truncated (#526) * Declare _mqttTopicCopy in BootNormal.hpp * Using _mqttTopicCopy to manage subscribed topics * Removed leading spaces
|
Updated my environment (develop-v3) with this change and OTA updates started to encounter very inconsistent watchdog timer errors. With this change backed out, I can once again reliably update. I believe the extra copy causes enough of a delay to make the script unstable. If others have encountered problems recently with OTA updates, I would be curious if this change is suspect. Sorry I do not have an alternative fix to the original problem. |
|
A few more details if this helps anyone. I'm not sure the right issue to be updating, so apologize if this is in the wrong place. My hardware is ESP8266 based MakerFocus D1, Mini, which seems to be very similar to the Wemos D1 Mini. Since backing out this change I have been very successful with OTAs (about 12 tests with no failures). It also appears the boards are more reliably keeping up MQTT connections to the broker. While I do not have another code solution for the original problem, I'm happy to help test if someone has a proposed fix. Thanks for the awesome library. |
It is not possible to subscribe to MQTT messages in general using Homie framework, as BootNormal::_onMqttMessage() truncates the topic.
Issue #524
With this change, topics can afterwards be intercepted by any other subscribed function, without loosing functionality