That would be possible, but I'd like to understand more about your use case -- is this just to provide safety to prevent radio corruption on disconnection?
That would be possible, but I'd like to understand more about your use case -- is this just to provide safety to prevent radio corruption on disconnection?
<!-- github-comment-id:4042784401 -->
As of right now I don't have a dedicated node for RemoteTerm, this is also my Mapping Node.
I'd like to be able to disconnect it from RemoteTerm and be able to connect it back up to my phone without shutting down the VM or command line turning off BT.
As of right now I don't have a dedicated node for RemoteTerm, this is also my Mapping Node.
I'd like to be able to disconnect it from RemoteTerm and be able to connect it back up to my phone without shutting down the VM or command line turning off BT.
<!-- github-comment-id:4042889716 -->
When you click Disconnect, it will release the connection and not attempt to reacquire it until you click Reconnect. This is in the Settings area in the Radio pane, at the top.
When you click Disconnect, it will release the connection and not attempt to reacquire it until you click Reconnect. This is in the Settings area in the Radio pane, at the top.
<!-- github-comment-id:4043045436 -->
it "seems" to work but when I pause it, it doesnt pop up on my phone to connect. If I turn off BT or turn the VM off it does, Also when I turn reconnect then it stuck at "Attempting to connect to BLE: 48:....." and doesnt reconnect. If I reboot the VM it does reconnect.
it "seems" to work but when I pause it, it doesnt pop up on my phone to connect. If I turn off BT or turn the VM off it does, Also when I turn reconnect then it stuck at "Attempting to connect to BLE: 48:....." and doesnt reconnect. If I reboot the VM it does reconnect.
<!-- github-comment-id:4043199542 -->
2026-03-12 01:09:14 - app.radio - INFO - Attempting to reconnect to radio...
2026-03-12 01:09:14 - app.radio - INFO - No serial port specified, auto-detecting...
2026-03-12 01:09:14 - app.radio - WARNING - No serial devices found
2026-03-12 01:09:14 - app.radio - WARNING - Reconnection failed: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
Traceback (most recent call last):
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 384, in reconnect
await self.connect()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 275, in connect
await self._connect_serial()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 286, in _connect_serial
raise RuntimeError("No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.")
RuntimeError: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
2026-03-12 01:09:14 - app.radio - INFO - Attempting to reconnect to radio...
2026-03-12 01:09:14 - app.radio - INFO - No serial port specified, auto-detecting...
2026-03-12 01:09:14 - app.radio - WARNING - No serial devices found
2026-03-12 01:09:14 - app.radio - WARNING - Reconnection failed: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
Traceback (most recent call last):
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 384, in reconnect
await self.connect()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 275, in connect
await self._connect_serial()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 286, in _connect_serial
raise RuntimeError("No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.")
RuntimeError: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
<!-- github-comment-id:4043220554 -->
That seemed to fix it! I did a couple disconnects and reconnects. Thank you!
One other thing I noticed. When I connected my phone back up. I dont have any channels anymore.
Not a huge deal, just noticed it.
That seemed to fix it! I did a couple disconnects and reconnects. Thank you!
One other thing I noticed. When I connected my phone back up. I dont have any channels anymore.
Not a huge deal, just noticed it.
<!-- github-comment-id:4043285280 -->
Ahh yes that will happen. Because RemoteTerm is managing all your channels for you, none are kept on the radio, and only a selection of recently used contacts live on the radio. This is how you can have thousands of contacts and channels running on a single radio, but the other side of the coin is that the app flushes out the radio. I've toyed with the idea of not clearing contacts but then it kinda defeats the purpose because at a certain point the radio can't hold anymore and then we can't get adverts, and we can't automatically manage which keys should be on there (or have the user force a key to always be on via favorites).
Channels, we probably could get by not dumping channels off the radio. The main disadvantage is that we get more spam over the connection because it's "helpfully" lobbing decrypted packets at us, which we don't need, because we do all the channel crypto serverside.
Ahh yes that will happen. Because RemoteTerm is managing all your channels for you, none are kept on the radio, and only a selection of recently used contacts live on the radio. This is how you can have thousands of contacts and channels running on a single radio, but the other side of the coin is that the app flushes out the radio. I've toyed with the idea of not clearing contacts but then it kinda defeats the purpose because at a certain point the radio can't hold anymore and then we can't get adverts, and we can't automatically manage which keys should be on there (or have the user force a key to always be on via favorites).
Channels, we probably could get by not dumping channels off the radio. The main disadvantage is that we get more spam over the connection because it's "helpfully" lobbing decrypted packets at us, which we don't need, because we do all the channel crypto serverside.
I will think on this, and update in #52.
<!-- github-comment-id:4043301400 -->
that makes sense and I can live with it for this node (or until I get a dedicated node)
But keep my eyes for the update in #52
Thanks again!
that makes sense and I can live with it for this node (or until I get a dedicated node)
But keep my eyes for the update in #52
Thanks again!
<!-- github-comment-id:4043315207 -->
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.
Would be cool if there was a button to connect/disconnect the device, whether on BT or WiFi.
That would be possible, but I'd like to understand more about your use case -- is this just to provide safety to prevent radio corruption on disconnection?
As of right now I don't have a dedicated node for RemoteTerm, this is also my Mapping Node.
I'd like to be able to disconnect it from RemoteTerm and be able to connect it back up to my phone without shutting down the VM or command line turning off BT.
Ah gotcha, that makes sense. Yeah I'll implement that later today.
Done!
When you click Disconnect, it will release the connection and not attempt to reacquire it until you click Reconnect. This is in the Settings area in the Radio pane, at the top.
it "seems" to work but when I pause it, it doesnt pop up on my phone to connect. If I turn off BT or turn the VM off it does, Also when I turn reconnect then it stuck at "Attempting to connect to BLE: 48:....." and doesnt reconnect. If I reboot the VM it does reconnect.
2026-03-12 01:09:14 - app.radio - INFO - Attempting to reconnect to radio...
2026-03-12 01:09:14 - app.radio - INFO - No serial port specified, auto-detecting...
2026-03-12 01:09:14 - app.radio - WARNING - No serial devices found
2026-03-12 01:09:14 - app.radio - WARNING - Reconnection failed: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
Traceback (most recent call last):
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 384, in reconnect
await self.connect()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 275, in connect
await self._connect_serial()
File "/home/k7oww/Remote-Terminal-for-MeshCore/app/radio.py", line 286, in _connect_serial
raise RuntimeError("No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.")
RuntimeError: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
Found a possible culprit -- give it another shot.
That seemed to fix it! I did a couple disconnects and reconnects. Thank you!
One other thing I noticed. When I connected my phone back up. I dont have any channels anymore.
Not a huge deal, just noticed it.
Ahh yes that will happen. Because RemoteTerm is managing all your channels for you, none are kept on the radio, and only a selection of recently used contacts live on the radio. This is how you can have thousands of contacts and channels running on a single radio, but the other side of the coin is that the app flushes out the radio. I've toyed with the idea of not clearing contacts but then it kinda defeats the purpose because at a certain point the radio can't hold anymore and then we can't get adverts, and we can't automatically manage which keys should be on there (or have the user force a key to always be on via favorites).
Channels, we probably could get by not dumping channels off the radio. The main disadvantage is that we get more spam over the connection because it's "helpfully" lobbing decrypted packets at us, which we don't need, because we do all the channel crypto serverside.
I will think on this, and update in #52.
that makes sense and I can live with it for this node (or until I get a dedicated node)
But keep my eyes for the update in #52
Thanks again!