Skip to content

docs: add Swiss Mesh Pro to number allocations table#2182

Open
ssozonoff wants to merge 1 commit intomeshcore-dev:devfrom
ssozonoff:docs/add-swiss-mesh-pro-allocation
Open

docs: add Swiss Mesh Pro to number allocations table#2182
ssozonoff wants to merge 1 commit intomeshcore-dev:devfrom
ssozonoff:docs/add-swiss-mesh-pro-allocation

Conversation

@ssozonoff
Copy link
Copy Markdown

No description provided.

@ripplebiz
Copy link
Copy Markdown
Collaborator

We have re-adjusted the data-type ranges. So, please use an ID starting from 0x0100

@ssozonoff ssozonoff force-pushed the docs/add-swiss-mesh-pro-allocation branch from 289782b to 32716aa Compare March 30, 2026 09:22
@ssozonoff ssozonoff force-pushed the docs/add-swiss-mesh-pro-allocation branch from 32716aa to 336ebde Compare March 30, 2026 09:25
@ssozonoff
Copy link
Copy Markdown
Author

ok thats fixed thx

@ripplebiz
Copy link
Copy Markdown
Collaborator

Could you add some info in the Contact column about where to get info about the project?

@ssozonoff
Copy link
Copy Markdown
Author

There is not much to add at the moment. I have some prototype stuff (weather station) which is currently running and was/is using Group Data before you guys further refined the protocol. Hence its not currently conforming to the official protocol and its my understanding that in order to confirm to the protocol I need to register and ID in the allocation table.

@liamcottle
Copy link
Copy Markdown
Member

There is not much to add at the moment. I have some prototype stuff (weather station) which is currently running and was/is using Group Data before you guys further refined the protocol. Hence its not currently conforming to the official protocol and its my understanding that in order to confirm to the protocol I need to register and ID in the allocation table.

For now, I would recommend using any ID within the 0xFF00 to 0xFFFF range. These are reserved for testing and development use. You have access to ~256 unique IDs in this range, so the potential for clashes with other users in your area is probably very low at this time.

Once you have a production app ready, for example something being released to the Apple App Store, or Google Play Store, you could then request a unique ID to be reserved by us to avoid clashes with other users/apps on public mesh networks.

But since you're just tinkering/testing, you don't really need a globally unique ID at this time :)

We will need to update the docs so this is more apparent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants