mirror of
https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git
synced 2026-11-03 08:02:19 +01:00
Issues Connecting and trying to use Room Servers #215
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/Remote-Terminal-for-MeshCore#215
Reference in new issue
Block a user
Currently trying to play around a bit with room servers and noticed a few issues.
Can only ever seem to login when forcing Flood. Using a Path even the one automatically discovered login always fails.
additionally Even after successful flood to login, messages are not received if changed back to the discovered or a forced path.
Login times out after 10 seconds. Plenty for a local room server but does not seem to be enough for one further away then 2-3 hops. to receive a response of successful login back. Appears a little more successful after changing to a 30 second timeout. Might be worth making this configurable assuming issue 3 does not resolve this issue.
When logging in the console log shows "meshcore - WARNING - *** please consider using send_login_sync instead of send_login"
I am guessing send_login_sync is new and Remote Terminal just isn't supporting it yet. Not sure if it would make login work better
Even After a successful login if selecting a different channel or item, when returning to the Room Server the window does not show the message history or ability to send a message. The login button is also gone, a refresh of the page is the only way i have found to make it reappear and requires a re-login.
Additional to this if a message is sent to the room server by someone else, the room server shows up with an unread message but its not possible to confirm it read until a page refresh and re-login.
Yeah rooms are a severely untested feature. login sync shouldn't matter much at all. I'll see if I can replicate the issues around login and message retrieval.