So I’ve got a T-Beam v1.1 connected via bluetooth to my iPhone. A couple of days ago it worked fine, I could send and receive messages. But now I can only send, but not receive. I can see that the messages I’m sending from another device, is being received by the T-beam as they show up in the display. But the message never shows up on my phone. Not messages in global nor direct messages.
I’ve tried rebooting the t-beam, rebooting the iPhone, forgetting the bluetooth connection and establishing it again, and even entirely deleting the Meshtastic app and all saved data, and reinstalling it.
I’ve had the same with a T3S3 and both iOS and MacOS apps - the app would (sometimes) send a message ok but never receive. I did see one reply on the device, but never in the app. This is a new T3S3, just flashed with the latest stable beta, iOS and MacOS apps deleted and reinstalled.
Also, perhaps related, the device has no GPS so I used the fixed option where the phone should set the location but the device display never gave the compass reading. I have now switched to wifi (to see if messages will work), told the device where it is via the Python CLI and now the compass display is there. It’s as if before it had no idea of location despite the app supposedly sending the location of the phone.
So… now I am running it on wifi (so no iOS or MacOS app possible because switching to wifi stops BLE) I noticed a message come in on the device screen and also via the Python API but it did not appear in the Meshtastic web app display. So I sent a message via the web app, it does not get an ack but I did get a reply, again in the API data, not the app. If it comes in the data stream from the T3S3 how can it not end up in the app? I feel like I am missing something obvious!
I just installed the latest version (Heltec V3 - v. 2.2.24 stable) and iOS app (v 2.2.26) on 2 devices, and messages show up on my device (Heltec) but not on my iOS app. Even when connected via USB to my Mac, messages only sometimes show up.