You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found some peculiar behaviour with MQTT and I'm not sure what is causing it.
EMS-ESP is correctly subscribing to the topic ems-esp/thermostat/# as shown in the Mosquitto verbose logs. But when I publish to ems-esp/thermostat/hc1/seltemp it does not get picked up by EMS-ESP.
I thought at first something with the base/basename change I did, but that looks ok. For some reason, the callback onMessage(callback) is not triggered.
No, have not realized it before, my esp32 with dev.2 (2.12.23) is working good. The S3 with actual software do not call onMessage.
Don't know what it is, made some tests. If i register a callback within MqttSettingsService and call mqtt::onMessage from there (like onMqttConnect, onMqttDisconnect), it works and structure is more clear. I'll make a PR.
MichaelDvP
added a commit
to MichaelDvP/EMS-ESP32
that referenced
this issue
Dec 12, 2023
Found some peculiar behaviour with MQTT and I'm not sure what is causing it.
EMS-ESP is correctly subscribing to the topic
ems-esp/thermostat/#
as shown in the Mosquitto verbose logs. But when I publish toems-esp/thermostat/hc1/seltemp
it does not get picked up by EMS-ESP.I thought at first something with the base/basename change I did, but that looks ok. For some reason, the callback
onMessage(callback)
is not triggered.@MichaelDvP have you seen this before?
The text was updated successfully, but these errors were encountered: