I would like to receive an iOS notification when a MeshCore message is received, even if the app is not currently open/foregrounded.
Current behavior:
If the app is closed or disconnected from the Companion, incoming messages do not trigger a mobile notification. This makes it easy to miss messages unless I manually open the app and reconnect.
Use case:
I have a fixed Companion setup that is connected 24/7 over USB to a host, and has no battery limitation. In that setup, the Companion is effectively always online and accessible via IP connection, so it would be useful for the iOS app to behave more like a normal messaging app and notify me when messages arrive.
I understand this may be different from the usual mobile/Bluetooth use case, where Companion devices are not expected to stay connected 24/7 and battery/background limits matter. But for a fixed USB/IP ("WiFi") Companion, persistent receive + notification behavior seems valid.
Possible approaches:
• If technically possible on iOS, keep/recover the Companion connection in the background and trigger local notifications for incoming messages.
• If iOS background Bluetooth limits make that unreliable, consider a “fixed Companion mode” where an always-on desktop/server Companion can relay notification events to iOS and/or Android.
Expected behavior:
When a message is received by my fixed Companion, I get a mobile notification.
Related:
This overlaps with #1181, but that issue is mainly about persistent Bluetooth after closing the app. This request is specifically about reliable incoming-message notifications for fixed/always-on Companion setups, especially USB-powered ones.
I would like to receive an iOS notification when a MeshCore message is received, even if the app is not currently open/foregrounded.
Current behavior:
If the app is closed or disconnected from the Companion, incoming messages do not trigger a mobile notification. This makes it easy to miss messages unless I manually open the app and reconnect.
Use case:
I have a fixed Companion setup that is connected 24/7 over USB to a host, and has no battery limitation. In that setup, the Companion is effectively always online and accessible via IP connection, so it would be useful for the iOS app to behave more like a normal messaging app and notify me when messages arrive.
I understand this may be different from the usual mobile/Bluetooth use case, where Companion devices are not expected to stay connected 24/7 and battery/background limits matter. But for a fixed USB/IP ("WiFi") Companion, persistent receive + notification behavior seems valid.
Possible approaches:
• If technically possible on iOS, keep/recover the Companion connection in the background and trigger local notifications for incoming messages.
• If iOS background Bluetooth limits make that unreliable, consider a “fixed Companion mode” where an always-on desktop/server Companion can relay notification events to iOS and/or Android.
Expected behavior:
When a message is received by my fixed Companion, I get a mobile notification.
Related:
This overlaps with #1181, but that issue is mainly about persistent Bluetooth after closing the app. This request is specifically about reliable incoming-message notifications for fixed/always-on Companion setups, especially USB-powered ones.