When in the RPT admin/guest area theres should be an area for the data for the Regions configurations (allowed / blocked scopes). Also taking into account the hierarchy of the regions.
There should be an area for the regions information, that clearly shows the hierarchy (if it exists) and if they are allowed or blocked.
be aware of possible data trunck if there are a lot of regions
Project Version: v3.15.2 wrapped has an app in HomeAssistant OS 18.0 (Core 2026.6.4)
💡 Possible Solution
Additional context
Add any other context about the problem here.
## 📝 Description
When in the RPT admin/guest area theres should be an area for the data for the Regions configurations (allowed / blocked scopes). Also taking into account the hierarchy of the regions.
* https://docs.meshcore.io/cli_commands/?h=airtime+fact#region-management-v110
* https://docs.meshcore.io/cli_commands/?h=airtime+fact#dump-all-defined-regions-and-flood-permissions
## 🚦 Current Behavior
There is no data zone for the regions information
## 🎯 Expected Behavior
There should be an area for the regions information, that clearly shows the hierarchy (if it exists) and if they are allowed or blocked.
be aware of possible data trunck if there are a lot of regions
## 📋 Steps to Reproduce
NA
## 📸 Screenshots / Logs
https://gessaman.com/meshcore/regions/#how-regions-work-in-meshcore
<img width="727" height="390" alt="Image" src="https://github.com/user-attachments/assets/e33063c1-acfd-4042-9bb9-4ab4dca2cb89" />
## 💻 Environment Information
- **OS:** Windows 11
- **Browser/Version:** Edge 149.0.4022.80 (Official build) (64-bit)
- **Project Version:** v3.15.2 wrapped has an app in HomeAssistant OS 18.0 (Core 2026.6.4)
## 💡 Possible Solution
---
**Additional context**
Add any other context about the problem here.
<!-- github-sync-id:4763584321 -->
Added this in the most recent commit; lemme know how it works for you.
Works great, has expected. With hierarchy nice...
> Added this in the most recent commit; lemme know how it works for you.
Works great, has expected. With hierarchy nice...
<img width="623" height="440" alt="Image" src="https://github.com/user-attachments/assets/b2387c25-5666-4877-8434-5e63b15e4a5f" />
<!-- github-comment-id:4939283364 -->
But there is some way to "discover" the RPT regions (in a simpler non-full info), Liam and other apps do this, but this discovery feature when offered might nned to go to the client Radio settings where is the regions config.
Also on Guest access RPT the information is good.
<img width="618" height="196" alt="Image" src="https://github.com/user-attachments/assets/0ad2e3ab-cf09-47ab-8aad-ece4c6512749" />
But there is some way to "discover" the RPT regions (in a simpler non-full info), Liam and other apps do this, but this discovery feature when offered might nned to go to the client Radio settings where is the regions config.
<img width="714" height="660" alt="Image" src="https://github.com/user-attachments/assets/81b50411-6ad1-41e8-911a-a7eedfaab892" />
<img width="978" height="456" alt="Image" src="https://github.com/user-attachments/assets/ebeaba90-f4b9-4b50-baa0-49a4ece81414" />
<!-- github-comment-id:4939328333 -->
:( did not work, at least my own repeater that has a bunch of regions should had answered
> <img alt="Image" width="1490" height="490" src="https://private-user-images.githubusercontent.com/2365891/620274487-df7765cb-79f0-4d96-a604-0789ff3715a3.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODM3NTMxMzksIm5iZiI6MTc4Mzc1MjgzOSwicGF0aCI6Ii8yMzY1ODkxLzYyMDI3NDQ4Ny1kZjc3NjVjYi03OWYwLTRkOTYtYTYwNC0wNzg5ZmYzNzE1YTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDcxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjA3MTFUMDY1MzU5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjA4NGZlZDgzOTkwM2MxZDFiMTBhNDEzMGU2YTA4OGNkM2YwN2RhMjFlZDFiOTg5ZmY3ZDNlMDNlYTg5Y2VjZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmcmVzcG9uc2UtY29udGVudC10eXBlPWltYWdlJTJGcG5nIn0.y7dn1aWOVulN400MBWHShlV9wXL3Sm64HJKN7u2r2WA">
> Leme know how it works.
:( did not work, at least my own repeater that has a bunch of regions should had answered
<img width="1018" height="508" alt="Image" src="https://github.com/user-attachments/assets/08f62adc-fc75-4876-81e1-f15e68628f49" />
<!-- github-comment-id:4943259810 -->
Yes, now it is working as expected.
<img width="981" height="304" alt="Image" src="https://github.com/user-attachments/assets/5631ff58-e1e1-49fa-877a-8e6f49b5416f" />
<!-- github-comment-id:5048153163 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📝 Description
When in the RPT admin/guest area theres should be an area for the data for the Regions configurations (allowed / blocked scopes). Also taking into account the hierarchy of the regions.
🚦 Current Behavior
There is no data zone for the regions information
🎯 Expected Behavior
There should be an area for the regions information, that clearly shows the hierarchy (if it exists) and if they are allowed or blocked.
be aware of possible data trunck if there are a lot of regions
📋 Steps to Reproduce
NA
📸 Screenshots / Logs
https://gessaman.com/meshcore/regions/#how-regions-work-in-meshcore
💻 Environment Information
💡 Possible Solution
Additional context
Add any other context about the problem here.
Yeah this sounds reasonable; I'll take a look.
Still not in the v3.16.0, correct?
I do not see it in the RPT area
Added this in the most recent commit; lemme know how it works for you.
:( build please
I've pushed an updated image.
Works great, has expected. With hierarchy nice...
Also on Guest access RPT the information is good.
But there is some way to "discover" the RPT regions (in a simpler non-full info), Liam and other apps do this, but this discovery feature when offered might nned to go to the client Radio settings where is the regions config.
Leme know how it works.
:( did not work, at least my own repeater that has a bunch of regions should had answered
Yes, now it is working as expected.