Ben Meadors
Ben Meadors
> Thank you for your response! Of course! Give us the address! We'll send a few pieces! Always in touch for all the details and help Awesome! If you don't...
> Hello @caveman99 & @thebentern! Have you received the devices? What are our next steps, what can you say about this for the integration of meshtastic Howdy! Yes we have...
Seems like a good item for the 3.0 project board
@cshields would you be willing to create a PR for this fix? Either one of those fix options would need to be limited to the TCP consumers and leave the...
Closed by #3784 and #3259. Anything remaining can be opened in a Discussion or a subsequent Issue.
I'm unable to reproduce this on multiple T-Echos. Does rolling back to a previous release resolve the issue?
@pista01 is this link accessible? If so, can you try the uf2 in the zip? https://github.com/meshtastic/firmware/actions/runs/8071539015/artifacts/1280390603 I created a revert PR based on a suspicion given .17 was your last...
Fixed with #3304
I have seen this happen as well, and I believe @RicInNewMexico has also. I have not been able to pinpoint what's happening yet. I have a theory that there is...
Role does not change the behavior. For NRF52, you have to explicitly set bluetooth.enabled = false to turn off the BLE radio and cause this issue.