Meshtastic iOS iPhone and iPad App Beta Testing Available

81

Nope, that is not the intended behavior :grinning: I got a bunch of helpful feedback reports on this.

I found the preferred peripheral saving bug and added a timeout timer to keep track of the connection a little better and to clean things up if a connection gets stuck.

I submitted a new version 1.26.7 to beta app review, takes 2-24 hours so far.

1 Like
82

What’s the redeem code to get it on testflight?

83
1 Like
84

I figured out export, there is a button to download the log in the just published release, and I put a timer on the BLE connection. Preferred radio now saves properly and is hooked up to reconnect for BLE disconnect error 6 which happens when a device reset button is used so testing if the preferred radio is properly reconnecting in this case is pretty easy. The timers run for up to 12 seconds, the LORA32 often takes about 8.

Here is the one case I am using for preferred radio reconnecting right now, I plan on connecting to the preferred radio on load too:

https://developer.apple.com/documentation/corebluetooth/cberror/code/connectiontimeout

This is the only error for which I am automatically reconnecting to the preferred radio right now but am happy to listen to feedback on doing any of the others. Error 7 (peripheralDisconnected) is a t-beam going to sleep mostly from what I have seen.

85

Thanks. I think the error 7 must be a t-echo going to sleep - all my tbeams are sleep disabled. I cannot seem to hack my t-echos to add the sleep disabled powerFSM.ccp file!

86

It still keeps asking for a redeem code

87

You have to click the link on the iOS device after you have installed TestFlight. If it is still not showing you are probably not using iOS 15, which is a requirement.

88

Finally got it! Thanks!

89

Hey, I submitted two crash reports yesterday - and I think I may have an idea what caused them. When installing the app on a 3rd iOS device, I noticed the crash happened as the modal popup asking for location permissions appeared briefly. So my guess is that right after pairing you are asking for location, that modal popup appears, and its causing the crash. Anyways - just wanted to share the extra context in case it helps.

90

I have two t-beams running 1.2.45.
I have two iOS devices, each paired with a different radio.
The radios formed a mesh.
When I send a message from one device, I see it show up on the radio that device is paired with, and then show up on the second radio.
But the message does not show up in the app.
Same thing when messaging from the other device.

Am I doing something wrong? :slight_smile:

91

The hooking of of the subscriptions to receive data is currently kind of inconsistent currently. If you see MESH PACKET logs in the mesh log then the device is receiving and sending position, node info and message packets as they arrive, if you don’t see those logs the subscriptions are probably hung up, crash reports help, I am working through it.

92

Can you add Australia please?

Thanks

93

Australia is available, iOS 15 is required.

1 Like
94

I have been beta-testing this iOS app for a couple of weeks now and have attached some general observations below. Thank you to the devs working on this project, and thank you to all those testing it. You guys rock! As a side note I am not sure if any of my observations have been mentioned or not but here they are. Thanks again!

Test Hardware

  • Heltec ESP32 are running Meshtastic 1.2.45
  • iPhone 11 running iOS 15.0.2

Observed Issues

  • When ESP32 MCU device is connected to an External Battery Pack (EBP) (cord configuration = USB 2.0 Type A on EBP side to USB 2.0 Micro-B 5-Pin on ESP32 MCU side) the ESP32 MCU device will not stay powered. After about 10 minutes the ESP32 MCU looses power from the EBP or the EBP stops providing power to the ESP32 MCU.

    • Could this problem could be ameliorated if the ESP32 MCU had an attached battery? That is, if the ESP32 MCU would have an attached battery and then this ESP32 MCU + battery unit together would then be plugged into the EBP?
    • I have found that the only way I can keep the ESP32 MCU on while connected to an EBP is to constantly press the EBP power button/battery indicator button.
    • If I have have a Raspberry Pi connected to the same EBP (via USB 2.0 Type A on EBP side to USB 3.0 Type C —> the USB 3.0 Type C cord which has the On/Off button on it that comes with a lot of Raspberry Pi 4’s) and then have the ESP32 MCU plugged into the Raspberry Pi itself, I have observed that the ESP32 MCU will stay powered until the EBP runs out of juice.

  • After the ESP32 MCU looses power from the EBP and shuts off I can press the power button on the EBP which will turns on the ESP32 MCU connected to the EBP. When I press to the “Start Scanning” button in the Meshtastic iPhone application under the “Bluetooth” tab I have noticed that none of my ESP32 MCU devices will appear under “Available Devices” unless I “hard-close” the Meshtastic application first. Once I do hard-close the Meshtastic application though and then go back to the “Start Scanning” button the ESP32 MCU devices will appear and I can then successfully connect.

  • When my iPhone is connected to an ESP32 MCU via Bluetooth and if my iPhone goes out of Bluetooth signal range from the ESP32 MCU to which it was connected I will experience the above issue and will have to hard-close the Meshtastic iPhone application in order to reconnect my iPhone to the ESP32 MCU via Bluetooth.

1 Like
95

Is there a disconnect error in your log for the bluetooth out of range context?

2 Likes
96

Some power banks require a certain amount of current to be drawn to stay on, which sounds like what’s happening to your power bank. I’m not sure what kind of MCU board you have, but some of them do have a connector or holder for an external lipo/ion battery. Maybe use one of those if you’re looking to run off batteries.

1 Like
97

Just out of curiosity, why is there a yellow light left of the app name?

IMG_AAAED322106F-1

Cheers

98

Hi, great work for building an iOS app! you’re the hero.

I have two heltec lora 32 v2 devices both connected to a separate iphone. i can send messages from the phone and the other device receives it but it’s not showing up in the app. any idea what i’m doing wrong?

“log all mesh activity” is on but i don’t see any logs.

99

Hi and thanks for your hard work with the iOS app. I am seeing some bugs when using the app. When connecting to my T-ECHO 1.2.46 with my phone, I sometimes need to swipe and reconnect two extra times to see the assigned friendly name of my unit. This is consistent with both my phones, but now when I tried to replicated it worked without a hitch of course :slight_smile: I also have the problem that I dont get the “allow notification” message until I swipe the app to force close it, and even after that I need to remove and reinstall it sometimes to get it going. I would love to have a CLI window to be able to send commands to the T-Echo as with the Python CLI, to be able to configure the module without hooking it up to a PC. I dont see any activity in the “Mesh Activity Log” either.

100

I would try closing and re-opening the app and toggling the log toggle. Hooking up to the subscriptions and then automatically updating the ui when messages arrive is kind of unstable right now.