Feature Request/Issue: RPT guest access retrieved info issue/improvement #220

New Issue

2026-10-05T02:04:13+02:00

adam commented

2026-10-05 02:04:13 +02:00

📝 Description

In the MeshCore Liam app, when you enter into a RPT has guest, you can retreive the owner info and it retreives not only the owner, but also the firmware version, in RemoteTerm4MC I cannot get that with Guest access (the firmware is on the Radio settings data window, and with guest this gets always empty values.

🚦 Current Behavior

No data is populated in the Owner info (Guest or admin access).
To be thrufly I have tested many, many, many times to refresh OwnerInfo (And I know that it has data because I can get it via the Liam app, and tested at odd hours of the day to not be blocked by RPT airtime stress), but it always returns empty data.

🎯 Expected Behavior

More or less replicate the output from Liam MeshCore App
Deprecate the "Owner info" and populate the following info in the "Node Info" area (ReadOnly values that can be pulled with just guest access):

Name
Lat / Lon
Clock (UTC)
Firmware
Owner info text
have the firmware version info in the owner info area when you pull it.

📋 Steps to Reproduce

refresh the "Owner Info" and "Node Info" areas.

📸 Screenshots / Logs

💻 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

💡 Possible Solution

Additional context
Add any other context about the problem here.

## 📝 Description In the MeshCore Liam app, when you enter into a RPT has guest, you can retreive the owner info and it retreives not only the owner, but also the firmware version, in RemoteTerm4MC I cannot get that with Guest access (the firmware is on the Radio settings data window, and with guest this gets always empty values. ## 🚦 Current Behavior No data is populated in the Owner info (Guest or admin access). To be thrufly I have tested many, many, many times to refresh OwnerInfo (And I know that it has data because I can get it via the Liam app, and tested at odd hours of the day to not be blocked by RPT airtime stress), but it always returns empty data. ## 🎯 Expected Behavior More or less replicate the output from Liam MeshCore App Deprecate the "Owner info" and populate the following info in the "Node Info" area (ReadOnly values that can be pulled with just guest access): - Name - Lat / Lon - Clock (UTC) - Firmware - Owner info text have the firmware version info in the owner info area when you pull it. ## 📋 Steps to Reproduce refresh the "Owner Info" and "Node Info" areas. ## 📸 Screenshots / Logs <img width="608" height="209" alt="Image" src="https://github.com/user-attachments/assets/6764d712-0b58-45b0-9cd3-ade14311bc42" /> <img width="962" height="248" alt="Image" src="https://github.com/user-attachments/assets/6010116a-ec7b-46d8-aa18-f260fecc971a" /> ## 💻 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 ## 💡 Possible Solution --- **Additional context** Add any other context about the problem here.

adam closed this issue

2026-10-05 02:04:13 +02:00

adam commented

2026-10-05 02:04:14 +02:00

Hmm we don't alter what we ask for when authenticated as a guest, and owner info should be globally accessible regardless. Is it maybe just a big field that isn't always reliable fetched?

Hmm we don't alter what we ask for when authenticated as a guest, and owner info should be globally accessible regardless. Is it maybe just a big field that isn't always reliable fetched?

adam commented

2026-10-05 02:04:14 +02:00

Hmm we don't alter what we ask for when authenticated as a guest, and owner info should be globally accessible regardless. Is it maybe just a big field that isn't always reliable fetched?

From my testings its not about the field size, if you see the attached image of the owner info on Liam MC app, its something like 6char text string.
And I have tryed many several RPT where I have guest access and the RemoteTerm4MC output is always the same.
(and do not forget the RPT firmware version feature request :D )

> Hmm we don't alter what we ask for when authenticated as a guest, and owner info should be globally accessible regardless. Is it maybe just a big field that isn't always reliable fetched? From my testings its not about the field size, if you see the attached image of the owner info on Liam MC app, its something like 6char text string. And I have tryed many several RPT where I have guest access and the RemoteTerm4MC output is always the same. (and do not forget the RPT firmware version feature request :D )

adam commented

2026-10-05 02:04:15 +02:00

Hmm okay I'll dig into this further. I don't have any repeaters near me with guest access but let me give some ideas a shot blind and you can let me know if they work for you.

Hmm okay I'll dig into this further. I don't have any repeaters near me with guest access but let me give some ideas a shot blind and you can let me know if they work for you.

adam commented

2026-10-05 02:04:16 +02:00

I've set up some test changes on the branch alternate-repeater-detail-fetch. Are you up for checking that out and letting me know if that fixes your issues?

I've set up some test changes on the branch `alternate-repeater-detail-fetch`. Are you up for checking that out and letting me know if that fixes your issues?

adam commented

2026-10-05 02:04:16 +02:00

I've set up some test changes on the branch alternate-repeater-detail-fetch. Are you up for checking that out and letting me know if that fixes your issues?

Yes shure, just let me know how to do this on my enviroment that builds it from the dockerfile

# Define the base image argument here instead of relying on build.yaml
ARG BUILD_FROM=jkingsman/remoteterm-meshcore:3.16.0

FROM ${BUILD_FROM}

# Install dependencies (jq and tini are standard for supervisor addons)
RUN apt-get update \
    && apt-get install -y --no-install-recommends jq tini \
    && rm -rf /var/lib/apt/lists/*

# Copy the startup script
COPY run.sh /run.sh
RUN chmod +x /run.sh

# Entry point configuration
ENTRYPOINT ["/usr/bin/tini", "--"]
CMD ["/run.sh"]

# Labels required by Home Assistant Supervisor
LABEL \
    io.hass.type="addon" \
    io.hass.version="3.16.0" \
    io.hass.arch="amd64|aarch64" \
    org.label-schema.schema-version="1.0" \
    org.label-schema.name="RemoteTerm for MeshCore" \
    org.label-schema.description="Web UI + backend for MeshCore mesh radios"

> I've set up some test changes on the branch `alternate-repeater-detail-fetch`. Are you up for checking that out and letting me know if that fixes your issues? Yes shure, just let me know how to do this on my enviroment that builds it from the dockerfile ```dockerfile # Define the base image argument here instead of relying on build.yaml ARG BUILD_FROM=jkingsman/remoteterm-meshcore:3.16.0 FROM ${BUILD_FROM} # Install dependencies (jq and tini are standard for supervisor addons) RUN apt-get update \ && apt-get install -y --no-install-recommends jq tini \ && rm -rf /var/lib/apt/lists/* # Copy the startup script COPY run.sh /run.sh RUN chmod +x /run.sh # Entry point configuration ENTRYPOINT ["/usr/bin/tini", "--"] CMD ["/run.sh"] # Labels required by Home Assistant Supervisor LABEL \ io.hass.type="addon" \ io.hass.version="3.16.0" \ io.hass.arch="amd64|aarch64" \ org.label-schema.schema-version="1.0" \ org.label-schema.name="RemoteTerm for MeshCore" \ org.label-schema.description="Web UI + backend for MeshCore mesh radios" ```

adam commented

2026-10-05 02:04:17 +02:00

@jkingsman I just found out that the RPT Owner info and name can be requested in an unathenticated manner.

Maybee this can be somehow added in RemoteTerm4MC (somewhere) so we didn't have to pass thru the login first.
Nevertheless to add the firmware this needs to be done after login (admin or guest)

@jkingsman I just found out that the RPT Owner info and name can be requested in an unathenticated manner. <img width="1279" height="145" alt="Image" src="https://github.com/user-attachments/assets/8deadb3e-7bf7-4250-959e-38a5a98a20d5" /> Maybee this can be somehow added in RemoteTerm4MC (somewhere) so we didn't have to pass thru the login first. Nevertheless to add the firmware this needs to be done after login (admin or guest)

adam commented

2026-10-05 02:04:18 +02:00

I've pushed an updated image.

I've pushed an updated image.

adam commented

2026-10-05 02:04:18 +02:00

Going to close this as presumptively fixed; please reopen if you still see issues.

Going to close this as presumptively fixed; please reopen if you still see issues.

adam commented

2026-10-05 02:04:19 +02:00

Going to close this as presumptively fixed; please reopen if you still see issues.

Thanks, it works has expected.

> Going to close this as presumptively fixed; please reopen if you still see issues. Thanks, it works has expected. <img width="610" height="259" alt="Image" src="https://github.com/user-attachments/assets/d44f0b11-f048-422c-8d70-006162e61761" />

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#220