When I activate Reboot mode, any further changes to the settings are repeatedly blocked. This makes it impossible to use Reboot mode. It took me a long time to figure out why I suddenly couldn't save the settings before I found the connection to this.
Tested on TTGO V 2.1. and Heltec wireless stick lite (more boards of both)..
When I activate Reboot mode, any further changes to the settings are repeatedly blocked. This makes it impossible to use Reboot mode. It took me a long time to figure out why I suddenly couldn't save the settings before I found the connection to this.
Tested on TTGO V 2.1. and Heltec wireless stick lite (more boards of both)..
<!-- github-sync-id:3412589796 -->
I was deploying another node today (Heltec 32 V3 433MHz) with V3.1 (2025-09-09), and also had issues saving changes. Though in my case, I was trying to set initial params after flashing a device for the first time, with Reboot mode still in its default state (off).
I ended up reflashing that node with V3.0.1 to get it deployed quickly.
Ricardo - I have a couple more nodes currently unused, and would be happy to perform any tests to help debug this with them.
I was deploying another node today (Heltec 32 V3 433MHz) with V3.1 (2025-09-09), and also had issues saving changes. Though in my case, I was trying to set initial params after flashing a device for the first time, with Reboot mode still in its default state (off).
I ended up reflashing that node with V3.0.1 to get it deployed quickly.
Ricardo - I have a couple more nodes currently unused, and would be happy to perform any tests to help debug this with them.
<!-- github-comment-id:3288856415 -->
During further testing, I encountered random problems with saving (=not saving) the configuration even when Auto reboot was turned off. But when it was turned on, they occurred always .
The behavior was the same regardless of whether the configuration was set after a clean webUI flash, a flash via VSC, or from a saved .json file.
During further testing, I encountered random problems with saving (=not saving) the configuration even when Auto reboot was turned off. But when it was turned on, they occurred always .
The behavior was the same regardless of whether the configuration was set after a clean webUI flash, a flash via VSC, or from a saved .json file.
<!-- github-comment-id:3289402026 -->
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
<!-- github-comment-id:3289612269 -->
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
--
Tento e-mail byl antivirovým softwarem Avast zkontrolován na viry.
www.avast.com
Hello.
I don't use Telegram. This is a test settings for Heltec Wireless Stick Lite.
Jan, OK2ILA
From: Ricardo Guzman (Richonguzman) ***@***.***>
Sent: Sunday, September 14, 2025 5:00 PM
To: richonguzman/LoRa_APRS_iGate ***@***.***>
Cc: Jan-OK2 ***@***.***>; Author ***@***.***>
Subject: Re: [richonguzman/LoRa_APRS_iGate] Possible new WebUI configuration bug in version 25-09-09: (Issue #324)
<https://avatars.githubusercontent.com/u/69999130?s=20&v=4> richonguzman left a comment (richonguzman/LoRa_APRS_iGate#324) <https://github.com/richonguzman/LoRa_APRS_iGate/issues/324#issuecomment-3289612269>
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
—
Reply to this email directly, view it on GitHub <https://github.com/richonguzman/LoRa_APRS_iGate/issues/324#issuecomment-3289612269> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOHNY4L6RIKJYDYO5XZDNTT3SV7G7AVCNFSM6AAAAACGMXERBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBZGYYTEMRWHE> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BOHNY4MBU7XF2FQQNT34HHT3SV7G7A5CNFSM6AAAAACGMXERBWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWECN762.gif> Message ID: ***@***.*** ***@***.***> >
--
Tento e-mail byl antivirovým softwarem Avast zkontrolován na viry.
www.avast.com
<!-- github-comment-id:3289737277 -->
I noticed the V3.1.1 release, with the JSON size fix.
I deployed that to a spare node, and now see no issues saving the config.
Thank you, Ricardo!
I noticed the V3.1.1 release, with the JSON size fix.
I deployed that to a spare node, and now see no issues saving the config.
Thank you, Ricardo!
<!-- github-comment-id:3293376037 -->
lets hope more test this to have this issue solved :P
I noticed the V3.1.1 release, with the JSON size fix. I deployed that to a spare node, and now see no issues saving the config.
Thank you, Ricardo!
lets hope more test this to have this issue solved :P
> I noticed the V3.1.1 release, with the JSON size fix. I deployed that to a spare node, and now see no issues saving the config.
>
> Thank you, Ricardo!
<!-- github-comment-id:3293383209 -->
I'm uploading V3.1.2 version right now... 21Hrs UTC or less (or when you see V3.1.2 available)
this solves many issues:
OTA updates will complete the missing variables and names of new versions compared to old ones to avoid crashing or bricking the unit
saving data/config from web will be also validated to always be saved and avoid any problem
stay tuned!
PS: write me here about your results
I'm uploading V3.1.2 version right now... 21Hrs UTC or less (or when you see V3.1.2 available)
this solves many issues:
- OTA updates will complete the missing variables and names of new versions compared to old ones to avoid crashing or bricking the unit
- saving data/config from web will be also validated to always be saved and avoid any problem
stay tuned!
PS: write me here about your results
<!-- github-comment-id:3304443693 -->
Tested on TTGO V2.1. It seems to be OK!
Tomorrow, I will test the Heltec board and I believe that the problem will be solved.
Tested on TTGO V2.1. It seems to be OK!
Tomorrow, I will test the Heltec board and I believe that the problem will be solved.
<!-- github-comment-id:3313323278 -->
Tested on TTGO V2.1. It seems to be OK! Tomorrow, I will test the Heltec board and I believe that the problem will be solved.
please write back when you do
> Tested on TTGO V2.1. It seems to be OK! Tomorrow, I will test the Heltec board and I believe that the problem will be solved.
please write back when you do
<!-- github-comment-id:3313352898 -->
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.
When I activate Reboot mode, any further changes to the settings are repeatedly blocked. This makes it impossible to use Reboot mode. It took me a long time to figure out why I suddenly couldn't save the settings before I found the connection to this.
Tested on TTGO V 2.1. and Heltec wireless stick lite (more boards of both)..
I was deploying another node today (Heltec 32 V3 433MHz) with V3.1 (2025-09-09), and also had issues saving changes. Though in my case, I was trying to set initial params after flashing a device for the first time, with Reboot mode still in its default state (off).
I ended up reflashing that node with V3.0.1 to get it deployed quickly.
Ricardo - I have a couple more nodes currently unused, and would be happy to perform any tests to help debug this with them.
During further testing, I encountered random problems with saving (=not saving) the configuration even when Auto reboot was turned off. But when it was turned on, they occurred always .
The behavior was the same regardless of whether the configuration was set after a clean webUI flash, a flash via VSC, or from a saved .json file.
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
Hello.
I don't use Telegram. This is a test settings for Heltec Wireless Stick Lite.
Jan, OK2ILA
From: Ricardo Guzman (Richonguzman) @.>
Sent: Sunday, September 14, 2025 5:00 PM
To: richonguzman/LoRa_APRS_iGate @.>
Cc: Jan-OK2 @.>; Author @.>
Subject: Re: [richonguzman/LoRa_APRS_iGate] Possible new WebUI configuration bug in version 25-09-09: (Issue #324)
https://avatars.githubusercontent.com/u/69999130?s=20&v=4 richonguzman left a comment (richonguzman/LoRa_APRS_iGate#324) https://github.com/richonguzman/LoRa_APRS_iGate/issues/324#issuecomment-3289612269
could you send me over telegram a copy of the .json file of the configuration? I suspect we are reaching the size of the file where we need to increase the size on the firmware
—
Reply to this email directly, view it on GitHub https://github.com/richonguzman/LoRa_APRS_iGate/issues/324#issuecomment-3289612269 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BOHNY4L6RIKJYDYO5XZDNTT3SV7G7AVCNFSM6AAAAACGMXERBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBZGYYTEMRWHE .
You are receiving this because you authored the thread. https://github.com/notifications/beacon/BOHNY4MBU7XF2FQQNT34HHT3SV7G7A5CNFSM6AAAAACGMXERBWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWECN762.gif Message ID: @.*** @.***> >
--
Tento e-mail byl antivirovým softwarem Avast zkontrolován na viry.
www.avast.com
I noticed the V3.1.1 release, with the JSON size fix.
I deployed that to a spare node, and now see no issues saving the config.
Thank you, Ricardo!
lets hope more test this to have this issue solved :P
This is probably the same issue as I mentioned in discussions: https://github.com/richonguzman/LoRa_APRS_iGate/discussions/304 - but still no joy with 3.1.1. I tried on a TTGO Lora32 v2.1
I'm uploading V3.1.2 version right now... 21Hrs UTC or less (or when you see V3.1.2 available)
this solves many issues:
stay tuned!
PS: write me here about your results
available now!
Works for me. Thanks!
great
lets wait for @N1IOX and @Jan-OK2
Tested on TTGO V2.1. It seems to be OK!
Tomorrow, I will test the Heltec board and I believe that the problem will be solved.
please write back when you do
I confirm functionality on Heltec Wireless stick lite V3. No problem now!
Many thanks!
@Jan-OK2 Great!!!
As this has been solved, time to get into TNC's!