Describe the bug
When I sent a message to another node, using the Meshcore app,it said no delivery (failed), but when I connect to this node using meshcore app, I can see, that it has been delivered 😳
Other have the same issue ?
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
Latest version (11)
**Describe the bug**
When I sent a message to another node, using the Meshcore app,it said no delivery (failed), but when I connect to this node using meshcore app, I can see, that it has been delivered 😳
Other have the same issue ?
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
Latest version (11)
<!-- github-sync-id:4083620292 -->

Here connected to the other node
<!-- github-comment-id:4069127498 -->
And here the fail on the app connected to my t-deck
And here the fail on the app connected to my t-deck
<!-- github-comment-id:4069148673 -->
Uah, interesting. Tested it with my devices. Will dig into it, ill let you know more when i figured out whats wrong. Maybe something got smashed with the multihash integration. Had sone issues with the values to diplay. I already found small display issues. Nevertheless, it will take more time but, at least it was needed so get a release out 🙏.
Thank you for the report!!
Uah, interesting. Tested it with my devices. Will dig into it, ill let you know more when i figured out whats wrong. Maybe something got smashed with the multihash integration. Had sone issues with the values to diplay. I already found small display issues. Nevertheless, it will take more time but, at least it was needed so get a release out 🙏.
Thank you for the report!!
<!-- github-comment-id:4069707599 -->
MeshCore app / direct messages: keep app-side pending delivery waits conservative for ACK-tracked sends so flood-routed DMs are no longer reported failed before their ACK can return (#144).
fix will come with v0.9.12.1
- MeshCore app / direct messages: keep app-side pending delivery waits conservative for ACK-tracked sends so flood-routed DMs are no longer reported failed before their ACK can return (#144).
<!-- github-comment-id:4308240559 -->
Is it fixed for you, @OZ1DXQ? Then I suggest you close the issue, if not I suggest you comment that the issue still persists.
Regards!
Is it fixed for you, @OZ1DXQ? Then I suggest you close the issue, if not I suggest you comment that the issue still persists.
Regards!
<!-- github-comment-id:4606665613 -->
Yes its working now 👍
But now a very slow response, when you touch the display on the t-deck 🤯 so still using ver.9 on my other t-deck ☹️
Yes its working now 👍
But now a very slow response, when you touch the display on the t-deck 🤯 so still using ver.9 on my other t-deck ☹️
<!-- github-comment-id:4710173178 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
When I sent a message to another node, using the Meshcore app,it said no delivery (failed), but when I connect to this node using meshcore app, I can see, that it has been delivered 😳
Other have the same issue ?
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
Latest version (11)
Here connected to the other node
Message received!
And here the fail on the app connected to my t-deck
Uah, interesting. Tested it with my devices. Will dig into it, ill let you know more when i figured out whats wrong. Maybe something got smashed with the multihash integration. Had sone issues with the values to diplay. I already found small display issues. Nevertheless, it will take more time but, at least it was needed so get a release out 🙏.
Thank you for the report!!
fix will come with v0.9.12.1
Is it fixed for you, @OZ1DXQ? Then I suggest you close the issue, if not I suggest you comment that the issue still persists.
Regards!
Yes its working now 👍
But now a very slow response, when you touch the display on the t-deck 🤯 so still using ver.9 on my other t-deck ☹️