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
I noticed with current version from TestFlight that certain (see images) nodes cannot be DM'd over MQTT despite being only a single hop away while other nodes multiple hops away can be DM'd. This is only with new app builds, older versions actually do successfully DM nodes over MQTT so this appears to be an artificial limitation or a limitation that doesn't 100% work/not work as expected.
Expected Behavior
Here is the CMRG ECHO on iOS version 2.5.14 (1327) - successfully DM'd over MQTT
Current Behavior
Here is the same node with the same conditions with version 2.5.15 (1337) - no direct message available, but you can see that channels do reach it and it responds.
Participation
I am willing to submit a pull request for this issue.
Additional comments
Adding an example of another bot that is more hops away and DM is available which doesn't make sense.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
One note also - this is a private broker MQTT server, this is not the public MQTT server
Xaositek
changed the title
🐞 [Bug]: Some Nodes Over MQTT Cannot Be DM'd by Build 2.5.15 (1337)
🐞 [Bug]: Some Nodes Over MQTT Cannot Be DM'd in recent iOS app builds
Jan 22, 2025
Firmware Version
2.5.18
What did you do?
I noticed with current version from TestFlight that certain (see images) nodes cannot be DM'd over MQTT despite being only a single hop away while other nodes multiple hops away can be DM'd. This is only with new app builds, older versions actually do successfully DM nodes over MQTT so this appears to be an artificial limitation or a limitation that doesn't 100% work/not work as expected.
Expected Behavior
Here is the CMRG ECHO on iOS version 2.5.14 (1327) - successfully DM'd over MQTT
Current Behavior
Here is the same node with the same conditions with version 2.5.15 (1337) - no direct message available, but you can see that channels do reach it and it responds.
Participation
Additional comments
Adding an example of another bot that is more hops away and DM is available which doesn't make sense.
Code of Conduct
The text was updated successfully, but these errors were encountered: