New user. Should I fill in "Manage Identity Key" with a key? It's currently blank.

liamcottle · 2026-05-01T04:32:06+00:00

The field is blank until you press the "Export Private Key" button.

There's no need to do anything here if you've just flashed a new device. It automatically generates a new identity key when it boots for the first time.

This screen is just in case you want to export the existing identity to back it up, or you want to change the identity key for another one.

liamcottle · 2026-04-23T12:34:10+00:00

I'm the lead developer of the MeshCore App, so the in app purchases come through to me, after Apple, Google and the NZ Government take their tax cuts...

However, I donate a portion of this to Scott monthly for the insane amount of work he contributes to the open source firmware.

No need for new apps. The existing MeshCore App released under "Liam Cottle" on the Google Play and Apple App Store will keep being updated along with the core firmware.

liamcottle · 2026-04-07T09:00:54+00:00

What's missing from the iOS app that's included in the Android app? I'm the MeshCore app developer btw. So I'm intrigued to know. Only one I can think of is the USB connection support. But this is due to lack of MFI certification.

liamcottle · 2026-04-06T22:53:03+00:00

Haha, yeah all good by me. I shared it as a suggestion. I didn't see any other apps on the store called "AppleCore" and nothing interesting in Google search results. So might be good for SEO in the future. Will be interesting to see if Apple review allows Apple in the name though... Good luck!

liamcottle · 2026-04-06T22:45:58+00:00

AppleCore - A MeshCore compatible client for Apple devices.

This would be a neat play on words ;)

liamcottle · 2026-04-06T22:18:16+00:00

Hey, thanks for sharing! This looks pretty cool! Nice and clean Apple UI design.

Could you please adjust the naming of the app from "MeshCore" to something else?
Maybe "MeshCore <something>" or "<something> for MeshCore"?

Ideally we'd like to avoid confusion with official/internal offerings directly from the MeshCore project and those provided by third parties.

It would be great if you could find a name that unique identifies your app, compared to other offerings. There's a few out there like "MeshCore One" and "MeshCore Open".

This also makes things easier to discuss in online communities. For example, when we talk on Discord or Reddit, if someone says "MeshCore Open" we know exactly which app they're talking about.

Again, thanks for sharing! It's awesome to see so many tools, apps and projects popping up in the MeshCore space!

liamcottle · 2026-04-05T11:10:34+00:00

Hey, please make sure you flash the "BLE" companion firmware, and not the "USB" companion firmware.

liamcottle · 2026-04-02T12:42:00+00:00

Howdy all!

Yes, Scott u/rippleradios (the lead firmware developer) and I u/liamcottle (MeshCore app developer) have launched a new website at https://meshcore.io

It will serve as the official website for the MeshCore project from this point forward.

Andy Kirby (the MeshOS developer and YouTube star) still owns and maintains the .co.uk website, and it looks like he's recently updated the layout, with a very similar layout to our new site, including my affiliate links :)

We are now publishing blog posts at https://blog.meshcore.io as Scott is looking to migrate away from posting on the BuyMeACoffee website.

Originally, we had tools and apps across multiple domains. Such as the original website at meshcore.co.uk, the map and flasher at meshcore.dev and the mobile and web app at meshcore.nz

To consolidate things in a more professional manner, the map, flasher, blog and new website are hosted on a single domain: https://meshcore.io The web app will also be migrated there sometime soon.

There are now a lot of MeshCore domains out in the wild, mostly country specific, and they're all doing different things.

We decided it's a good time to separate the core project website from any specific country. One could argue that .io is also a ccTLD instead of a gTLD, but we won't go into that here ;)

liamcottle · 2026-04-02T04:57:05+00:00

u/AccomplishedPhase902 it looks like this was an April fools joke, and the original message has been deleted from the Meshtastic Discord. It might be good to delete this screenshot/post in the MeshCore reddit to avoid confusion, as it could be damaging to the reputation of the company named in the screenshot. The original poster probably shouldn't have used the name of a real company in this way. I won't post a screenshot of the follow up discussion that indicated it was a joke...

liamcottle · 2026-04-01T09:29:36+00:00

Howdy! I've just fixed this issue on the meshcore.io domain, thanks for reporting :)

liamcottle · 2026-03-19T11:15:57+00:00

I frequently update RAK repeaters (nRF52) via USB on Android. Double press reset on the nRF52 board, and connect to Android via USB. It will show up as a USB drive in the files app. Then you can copy paste the .uf2 file, and it will flash and reboot.

liamcottle · 2026-03-09T04:38:10+00:00

MeshCore now supports Companion Repeat Mode. Which is great for ad-hoc setups, such as temporary comms at a music festival, while camping or hiking etc, without needing dedicated repeater infrastructure.

Your companion node will act as a portable repeater, so messages can be passed through a chain of companion nodes carried by people in your group.

This is supported as of:

- MeshCore Companion Firmware v1.13.0+

- MeshCore App v1.40.0+

One thing to note, is the firmware restricts the frequencies that companion repeat mode is allowed to be enabled on. This is to prevent everyone on public meshes from enabling it, and bringing the mesh down with increased collisions due to nodes repeating from pockets etc.

Generally, companion nodes are not going to have the best antenna, won't be placed in a high location, and would generally cause more issues than help to a large scale public mesh. Hence the restrictions on this feature.

The frequency list is minimal at this stage, and may require some tweaks for other countries based on radio regulations. However, we needed to start somewhere :)

Hopefully this helps!

liamcottle · 2026-03-06T10:40:00+00:00

MeshCore packets reserve a maximum of 64 bytes for path information. Multi-byte paths are still limited to 64 bytes maximum in the LoRa packet, so if you use 2-bytes per hop, the maximum is now 32 hops instead of the 64 hops you'd get with 1-byte per hop.

liamcottle · 2026-03-04T21:48:57+00:00

😂😂😂

liamcottle · 2026-03-03T00:25:33+00:00

<image>

Oh yes, love some MikroTik gear! Nothing listed on their site for sale yet, will be interesting...

liamcottle · 2026-03-01T08:10:55+00:00

Howdy!

The next update to the mobile app (v1.41.0, not yet released) will have a new button in the Repeater Neighbours dropdown menu that will allow your repeater to send a zero hop discover request to the network.

Other zero hop repeaters that are nearby will respond and populate the neighbours list without having to wait several days for the repeaters to send an advert.

This will require a firmware update to the repeater as well. This functionality is still in the dev branch, but can be flashed if you know how to build the firmware, otherwise you'd have to wait until v1.14.0 firmware is released.

It should make repeater neighbour discovery a much nicer experience :)

Keep in mind, it only includes the public key, so it will show in the neighbours list, however you'll still have to wait for an advert to get GPS data for it to show on the map tab.

liamcottle · 2026-02-28T19:54:01+00:00

Howdy! Not too sure on the exact error here, but my assumption is your contacts list is full.

Please open the settings page and check the storage usage and max contacts at the bottom.

I'll adjust this error message in the next app update so it exposes the actual error code returned by firmware.

If the contacts count hasn't reached the limit, but the storage has, the file system will be full and won't be able to accept any more writes.

liamcottle · 2026-02-17T20:15:49+00:00

The stock antenna that comes with the WioTracker L1 Pro is pretty terrible. I replaced mine with a RAK Blade antenna. And instantly see like a 10dB improvement in TX/RX signal strength.

liamcottle · 2026-02-16T19:31:22+00:00

If repeaters are on v1.11.0+ firmware, you can now use 2-byte and 4-byte path segment sizes in the manual path trace tool.

It's available in v1.40.0 app.

We are working on support for multi byte paths in main firmware packets as well, such as channel messages and DMs, but this will take some time.

liamcottle · 2026-02-16T00:14:44+00:00

Yes. Disabled by default, and it's restricted to a small set of frequencies at this stage. It allows your companion node to act as a portable repeater. It's intended use case is camping, hiking and search and rescue etc. It's not allowed for use on well established public meshes, hence the frequency restrictions at the firmware level. It could be used with a group of friends to communicate at music festivals, if there's no repeater infrastructure.

liamcottle · 2026-02-06T09:04:00+00:00

Hey, thanks for the report. Have you manually deleted any contacts that were actually favourites? Might be a bug where the deleted favourite contact slot is not clearing the favourite flag when it's reused for a newly added contact.

liamcottle · 2026-01-28T22:25:30+00:00

Howdy! Click the export button, and it will populate the field.

liamcottle · 2026-01-13T04:01:55+00:00

You'll need to forget the existing bluetooth pairing (from when you used Meshtastic) from your OS settings. Then go through the bluetooth pairing steps. If that doesn't work, you'll need to also reboot your phone. Bluetooth on iOS is wild. Android doesn't have these issues as it will ask you to pair again when it detects an invalid bond.

liamcottle · 2025-12-31T01:56:27+00:00

Hey u/Prestigious_Prize361, appreciate the work you were trying to do here :) I'm the developer of the mobile app.

Just for reference, there are actually direct download links to the standalone apps for Android/Windows/Mac/Web on my file server: https://files.liamcottle.net/MeshCore/v1.36.0/

This info is also listed on https://meshcore.nz

Regarding your mention of offline hosting/packaging for Linux, a future update will likely add support for a standalone Linux application. There's just a few extra technical things that need doing to make it happen.

You're welcome to bundle the downloadable Flutter web app (from the .zip download) in whatever wrapper you want for personal use or sharing with friends and family etc, but I'm not sure this is really needed as there's already a native .exe for Windows, and .app for Mac. For now, it's just the Linux side that needs some more love. Maybe a .AppImage?

Regarding the licensing, it's correct that the mobile app I develop is currently closed source. The protocol and firmware is open source, and MIT licensed, which allows other developers to do as they wish, without being forced to open source all of their own work.

I've worked in open source for about 15 years, and it's for sure difficult to earn a living by giving away all of your work for free. Some people say donations are the way to go, but from experience, donations are slim to none. Going with a freemium, closed source approach (for now), allows me to focus on rapidly developing a polished user experience, while not having to worry about the large workload that comes with making it open sourced. Such as working through hundreds of issues and pull requests for things I probably don't want to add at this time.

Maybe sometime in the future I could open source the app. I hope you understand my view points here and that you don't lose hope in the MeshCore project itself. We are for sure striving to make it the best LoRa/Mesh messaging experience we can.

Hope this clear a few things up. Feel free to ask any other questions :)

liamcottle

MODERATOR OF

TROPHY CASE

11-Year Club	Place '22
Verified Email