How to down grade remote terminal version and also upgrade #197

New Issue

2026-10-05T02:02:58+02:00

adam commented

2026-10-05 02:02:58 +02:00

Hello, can I get a how to for downgrading fimrware and also the correct way to upgrade.

Thanks for your help. I have a need to down grade and test. Cant seem to find instructions.

Hello, can I get a how to for downgrading fimrware and also the correct way to upgrade. Thanks for your help. I have a need to down grade and test. Cant seem to find instructions.

adam closed this issue

2026-10-05 02:02:58 +02:00

adam commented

2026-10-05 02:02:59 +02:00

Hello! Sorry, I'm not super clear on what you're looking for. Are you meaning radio firmware? You should just be able to flash an older firmware via the same method you used to flash a new one (https://meshcore.io/flasher is a good place to start).

RemoteTerm doesn't really have a concept of firmware, but if you're talking about using an older version of RemoteTerm, you can either specify a specific revision via docker, or use git to checkout an older version.

Hello! Sorry, I'm not super clear on what you're looking for. Are you meaning radio firmware? You should just be able to flash an older firmware via the same method you used to flash a new one (https://meshcore.io/flasher is a good place to start). RemoteTerm doesn't really have a concept of firmware, but if you're talking about using an older version of RemoteTerm, you can either specify a specific revision via docker, or use git to checkout an older version.

adam commented

2026-10-05 02:03:00 +02:00

How to down grade remote terminal. I want to go back to 1.12 and test. sorry for not being clear.

how to down grade version and how to best upgrade commands please and thanks allot

I tried to ask AI and didnt get very far. So for us not so smart folks, if a simple command list could be shown for down grade and upgrade that would be awesome.

How to down grade remote terminal. I want to go back to 1.12 and test. sorry for not being clear. how to down grade version and how to best upgrade commands please and thanks allot I tried to ask AI and didnt get very far. So for us not so smart folks, if a simple command list could be shown for down grade and upgrade that would be awesome.

adam commented

2026-10-05 02:03:01 +02:00

How are you running it right now? Docker or straight from source?

How are you running it right now? Docker or straight from source?

adam commented

2026-10-05 02:03:02 +02:00

straight from source. Not docker. Install path 1

straight from source. Not docker. Install path 1

adam commented

2026-10-05 02:03:02 +02:00

So, we don't have a release 1.12; I think maybe you're talking about your radio firmware, which is separate from your RemoteTerm install. You'll need to use the MeshCore flasher to go down to 1.12.

So, we don't have a release 1.12; I think maybe you're talking about your radio firmware, which is separate from your RemoteTerm install. You'll need to use the MeshCore flasher to go down to 1.12.

adam commented

2026-10-05 02:03:03 +02:00

3.12.0 Sorry typo

3.12.0 Sorry typo

adam commented

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

git ls-remote --tags origin | grep 3.12.0
4a6235855fe08d40c811fd477bbdfa7fb591daea	refs/tags/3.12.0
d6e12188882af580beb6d427b379e3d6d7064ff4	refs/tags/3.12.0^{}

So that'll be git checkout 4a6235855fe08d40c811fd477bbdfa7fb591daea to jump back to that version.

``` git ls-remote --tags origin | grep 3.12.0 4a6235855fe08d40c811fd477bbdfa7fb591daea refs/tags/3.12.0 d6e12188882af580beb6d427b379e3d6d7064ff4 refs/tags/3.12.0^{} ``` So that'll be `git checkout 4a6235855fe08d40c811fd477bbdfa7fb591daea` to jump back to that version.

adam commented

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

let me try that right now. again thank you for the help. just the top git command or all 3?

will that also keep my settings or blow them out? I have a couple of python scripts

let me try that right now. again thank you for the help. just the top git command or all 3? will that also keep my settings or blow them out? I have a couple of python scripts

adam commented

2026-10-05 02:03:05 +02:00

just the git checkout 4a6235855fe08d40c811fd477bbdfa7fb591daea; the command above was just showing you how to convert a version tag to a commit you can check out.

Don't forget to rebuild your frontend!

I would strongly recommend backing up your remoteterm.db file before doing anything with versions; I can't guarantee that newer database versions will work with older application version. 3.12 is pretty recent so you might not have issues, and an older rev shouldn't do any damage to a newer database (other than refusing to boot if it's incompatible), but backups are always wise.

just the `git checkout 4a6235855fe08d40c811fd477bbdfa7fb591daea`; the command above was just showing you how to convert a version tag to a commit you can check out. Don't forget to rebuild your frontend! I would strongly recommend backing up your `remoteterm.db` file before doing anything with versions; I can't guarantee that newer database versions will work with older application version. 3.12 is pretty recent so you might not have issues, and an older rev shouldn't do any damage to a newer database (other than refusing to boot if it's incompatible), but backups are always wise.

adam commented

2026-10-05 02:03:05 +02:00

let me ask this first, I run a script that gets telemetry for my 31 repeaters that are all line of sight to each other. I do this over night. with the new version, its does not run the entire script. was a limit / token added?

let me ask this first, I run a script that gets telemetry for my 31 repeaters that are all line of sight to each other. I do this over night. with the new version, its does not run the entire script. was a limit / token added?

adam commented

2026-10-05 02:03:06 +02:00

This is just using the API?

This is just using the API?

adam commented

2026-10-05 02:03:07 +02:00

yes (i think thats right) it builds a CSV and then my HA server hits that and updates.

yes (i think thats right) it builds a CSV and then my HA server hits that and updates.

adam commented

2026-10-05 02:03:07 +02:00

Certainly nothing that would be truncating your script. If it's just directly hitting the API, but there are parts of your script that aren't getting run, that points more directly to a bug in the script anything else.

Certainly nothing that would be truncating your script. If it's just directly hitting the API, but there are parts of your script that aren't getting run, that points more directly to a bug in the script anything else.

adam commented

2026-10-05 02:03:08 +02:00

The script calls each repeater for Volts and that works fine. but after about half or so it stops for almost and hour and then continues with the remaining repeaters. before, I updated, it ran all of them at once until completion, script has not changed.

my thought was to go back a couple of revisions and test.

The script calls each repeater for Volts and that works fine. but after about half or so it stops for almost and hour and then continues with the remaining repeaters. before, I updated, it ran all of them at once until completion, script has not changed. my thought was to go back a couple of revisions and test.

adam commented

2026-10-05 02:03:09 +02:00

so I run,
git checkout 4a6235855f

then

cd frontend && npm install && npm run build && cd ..

is that all?

so I run, git checkout 4a6235855fe08d40c811fd477bbdfa7fb591daea then cd frontend && npm install && npm run build && cd .. is that all?

adam commented

2026-10-05 02:03:09 +02:00

Yeah that should be sufficient! What specifically is it stopping at? Is the request to the API taking a long time or something else?

Yeah that should be sufficient! What specifically is it stopping at? Is the request to the API taking a long time or something else?

adam commented

2026-10-05 02:03:10 +02:00

@jkingsman to upgrade to the next revision that you release. what would be the proper way of doing this. I'm saving all this before I begin my test.

@jkingsman to upgrade to the next revision that you release. what would be the proper way of doing this. I'm saving all this before I begin my test.

adam commented

2026-10-05 02:03:11 +02:00

Just some random remarks:

For checking out a specific tagged release, git checkout 3.12.0 will do as well ;-)

And you may need to do git stash first.

Just some random remarks: For checking out a specific tagged release, `git checkout 3.12.0` will do as well ;-) And you may need to do `git stash` first.

adam commented

2026-10-05 02:03:11 +02:00

I thank everyone for their help. Downgrading fixed the issue of my script stopping about 3/4 the way through. It "seemed" like a timeout condition (token) for how many transmit segments I have.

I thank everyone for their help. Downgrading fixed the issue of my script stopping about 3/4 the way through. It "seemed" like a timeout condition (token) for how many transmit segments I have.

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#197