adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-10-30 22:41:57 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Feature Request: Remove RPT login confirmation warning after an authentication action succeeds #237

New Issue
Open
opened 2026-10-05 02:05:27 +02:00 by adam · 2 comments
adam commented 2026-10-05 02:05:27 +02:00
Owner
Copy link
Copy source

📝 Problem Description

When loggin in a RPT contact (access or admin) if afterwards the user request an authenticated action and it succeeds the big yellowish warning still remains on the top of the RPT area consuming space.
This warning should disappear as soon as an authenticated action succeds.

🚦 Current Behavior

If the Admin / guest access could not be confirmed there is a big yellowish warning with the possibility for the user to retry the access login, but most of the times if the user requests authenticated data the RPT still gives it because it whas authenticated prior to the request but the RT4MC did not heard the confirmation.

🎯 Expected Behavior

This warning should disappear as soon as an authenticated action succeds.

📋 Steps to Reproduce

  1. Login to a RPT contact that the RT4MC could not confirmed that the login was successfull
  2. Request any authenticated data like Neighbors (or the new Owner Info that retrieves the Firmware version)
  3. The warning will still be there occupying space.

📡 Radio Node

  • Firmware version: Meshcore-Dev 06-Jun-2026/v1.16.0-07a3ca9
  • Hardware / board type: Xiao S3 WIO

🔌 Connection to the Radio

  • Connected directly to the radio, or through an intermediary? Directly
  • Transport: Serial (USB)

💻 Environment Information

  • OS: Windows 11 x64
  • Browser / Version: MS Edge Version 150.0.4078.48 (Official build) (64-bit)
  • RemoteTerm Version: v3.16.2·f8f6842 "wrapped" HA add-on/app

📸 Screenshots / Debug Logs

Image
## 📝 Problem Description When loggin in a RPT contact (access or admin) if afterwards the user request an authenticated action and it succeeds the big yellowish warning still remains on the top of the RPT area consuming space. This warning should disappear as soon as an authenticated action succeds. ## 🚦 Current Behavior If the Admin / guest access could not be confirmed there is a big yellowish warning with the possibility for the user to retry the access login, but most of the times if the user requests authenticated data the RPT still gives it because it whas authenticated prior to the request but the RT4MC did not heard the confirmation. ## 🎯 Expected Behavior This warning should disappear as soon as an authenticated action succeds. ## 📋 Steps to Reproduce 1. Login to a RPT contact that the RT4MC could not confirmed that the login was successfull 2. Request any authenticated data like Neighbors (or the new Owner Info that retrieves the Firmware version) 3. The warning will still be there occupying space. ## 📡 Radio Node - **Firmware version:** Meshcore-Dev 06-Jun-2026/v1.16.0-07a3ca9 - **Hardware / board type:** Xiao S3 WIO ## 🔌 Connection to the Radio - **Connected directly to the radio, or through an intermediary?** Directly - **Transport:** Serial (USB) ## 💻 Environment Information - **OS:** Windows 11 x64 - **Browser / Version:** MS Edge Version 150.0.4078.48 (Official build) (64-bit) - **RemoteTerm Version:** v3.16.2·f8f6842 "wrapped" HA add-on/app ## 📸 Screenshots / Debug Logs <img width="1269" height="539" alt="Image" src="https://github.com/user-attachments/assets/5dca3944-3b77-4517-b6e7-9a0c1d56057d" /> <!-- github-sync-id:4861232695 -->
adam commented 2026-10-05 02:05:28 +02:00
Author
Owner
Copy link
Copy source

We can't know what perm level our ACL has assumed from a repeater response other than an auth packet.

We can't know what perm level our ACL has assumed from a repeater response other than an auth packet. <!-- github-comment-id:4949625527 -->
adam commented 2026-10-05 02:05:28 +02:00
Author
Owner
Copy link
Copy source

We can't know what perm level our ACL has assumed from a repeater response other than an auth packet.

Correct, but you can know when any RPT data request succedded (because you successfuly populated the requested fetch area), right?
So if you have a successful data RPT fetch (like neighbors, or anything else that needs auth) then you can safely dismiss the confirmation warning don't you think?

Image
> We can't know what perm level our ACL has assumed from a repeater response other than an auth packet. Correct, but you can know when any RPT data request succedded (because you successfuly populated the requested fetch area), right? So if you have a successful data RPT fetch (like neighbors, or anything else that needs auth) then you can safely dismiss the confirmation warning don't you think? <img width="1274" height="791" alt="Image" src="https://github.com/user-attachments/assets/fda81bcf-f4a6-439d-b441-9bd6eae629b9" /> <!-- github-comment-id:4950587494 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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