adam/LoRa_APRS_iGate
1
0 Fork 0
mirror of https://github.com/richonguzman/LoRa_APRS_iGate.git synced 2026-10-30 18:41:58 +01:00
Code Issues 55 Packages Projects Releases Wiki Activity

display stays "connected!!, loading..." #217

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

Recently I changed the wifi to another AP.
Now the display says:

Connected!!
Loading ...

No other data is displayed.
Wifi is connected and web UI accessible.

When I revert to the old ssid the display restores

note: the old AP runs Unifi, the New AP runs Mikrotik. Another I-gate connects fine with a different Mikrotik AP.

Recently I changed the wifi to another AP. Now the display says: ``` Connected!! Loading ... ``` No other data is displayed. Wifi is connected and web UI accessible. When I revert to the old ssid the display restores note: the old AP runs Unifi, the New AP runs Mikrotik. Another I-gate connects fine with a different Mikrotik AP. <!-- github-sync-id:3434412398 -->
adam commented 2026-10-05 05:50:36 +02:00
Author
Owner
Copy link
Copy source

Hi

Is the configuration on both WIFI AP the same but the ssid and password?

Hi Is the configuration on both WIFI AP the same but the ssid and password? <!-- github-comment-id:3312249754 -->
adam commented 2026-10-05 05:50:37 +02:00
Author
Owner
Copy link
Copy source

both mikrotik have the same configuration. btw. wifi itself works fine: I can access the WebUI of the gateway with the hanging message.

both mikrotik have the same configuration. btw. wifi itself works fine: I can access the WebUI of the gateway with the hanging message. <!-- github-comment-id:3312260124 -->
adam commented 2026-10-05 05:50:37 +02:00
Author
Owner
Copy link
Copy source

is on both the WPA2 enabled? yesterday i was talking with another OP who fighted with his iGate and this was the hole missing part to solve

is on both the WPA2 enabled? yesterday i was talking with another OP who fighted with his iGate and this was the hole missing part to solve <!-- github-comment-id:3312410422 -->
adam commented 2026-10-05 05:50:38 +02:00
Author
Owner
Copy link
Copy source

WPA2 PSK yes

WPA2 PSK yes <!-- github-comment-id:3312458220 -->
adam commented 2026-10-05 05:50:39 +02:00
Author
Owner
Copy link
Copy source

can your board connect to the other "working" microtik ?

can your board connect to the other "working" microtik ? <!-- github-comment-id:3312473460 -->
adam commented 2026-10-05 05:50:39 +02:00
Author
Owner
Copy link
Copy source

That one is now running remote and accessible with the same configuration

That one is now running remote and accessible with the same configuration <!-- github-comment-id:3312478111 -->
adam commented 2026-10-05 05:50:40 +02:00
Author
Owner
Copy link
Copy source

sorry , i did not follow:

"igate board 1" connects to "microtik1"
"igate board 2" connects to "unify1" and not to "microtik2". But can it connect to "microtik1" ?

sorry , i did not follow: "igate board 1" connects to "microtik1" "igate board 2" connects to "unify1" and not to "microtik2". But can it connect to "microtik1" ? <!-- github-comment-id:3312484513 -->
adam commented 2026-10-05 05:50:41 +02:00
Author
Owner
Copy link
Copy source

1: "igate board 1" connects to "microtik1"
2: "igate board 2" connects to "unify1" and not to "microtik2"
3: "microtik1" and "microtik2" have exactly the same config.

1: "igate board 1" connects to "microtik1" 2: "igate board 2" connects to "unify1" and not to "microtik2" 3: "microtik1" and "microtik2" have exactly the same config. <!-- github-comment-id:3312502954 -->
adam commented 2026-10-05 05:50:41 +02:00
Author
Owner
Copy link
Copy source

1: "igate board 1" connects to "microtik1" 2: "igate board 2" connects to "unify1" and not to "microtik2" 3: "microtik1" and "microtik2" have exactly the same config.

can you download both iGateConfiguration.json on the "igate board 1" and "igate board 2" to compare them ?

> 1: "igate board 1" connects to "microtik1" 2: "igate board 2" connects to "unify1" and not to "microtik2" 3: "microtik1" and "microtik2" have exactly the same config. can you download both iGateConfiguration.json on the "igate board 1" and "igate board 2" to compare them ? <!-- github-comment-id:3312509837 -->
adam commented 2026-10-05 05:50:42 +02:00
Author
Owner
Copy link
Copy source

Working config:

{"wifi":{"AP":[{"ssid":"bbbbbbbbbbbb","password":"aaaaaaaaaa"}],"autoAP":{"password":"1234567890","timeout":10}},"callsign":"PI1APD-10","aprs_is":{"active":false,"passcode":"17070","server":"rotate.aprs2.net","port":14580,"filter":"m/10","messagesToRF":false,"objectsToRF":false},"beacon":{"comment":"LoRa APRS de Mheen","interval":15,"latitude":52.222,"longitude":5.993,"overlay":"L","symbol":"a","sendViaAPRSIS":false,"sendViaRF":false,"path":"WIDE1-1","gpsActive":false,"gpsAmbiguity":false},"digi":{"mode":0,"ecoMode":0},"lora":{"rxFreq":433775000,"txFreq":433775000,"spreadingFactor":12,"signalBandwidth":125000,"codingRate4":5,"power":20,"txActive":true,"rxActive":true},"display":{"alwaysOn":false,"timeout":30,"turn180":false},"battery":{"sendInternalVoltage":false,"monitorInternalVoltage":false,"internalSleepVoltage":2.900000095,"sendExternalVoltage":false,"externalVoltagePin":34,"monitorExternalVoltage":false,"externalSleepVoltage":10.89999962,"voltageDividerR1":100,"voltageDividerR2":27,"sendVoltageAsTelemetry":false},"wxsensor":{"active":false,"heightCorrection":0,"temperatureCorrection":0},"syslog":{"active":false,"server":"lora.link9.net","port":1514},"tnc":{"enableServer":false,"enableSerial":false,"acceptOwn":false},"other":{"rebootMode":false,"rebootModeTime":6,"rememberStationTime":30,"backupDigiMode":false},"ota":{"username":"admin","password":"xxxxxxxx"},"personalNote":"","blacklist":"","webadmin":{"active":true,"username":"admin","password":"xxxxxxxx"},"ntp":{"gmtCorrection":0},"remoteManagement":{"managers":"","rfOnly":true}}

failing config:

{"wifi":{"AP":[{"ssid":"bbbbbbbbbbbb","password":"xxxxxxxxxx"}],"autoAP":{"password":"1234567890","timeout":10}},"callsign":"PI1APD-10","aprs_is":{"active":true,"passcode":"17070","server":"rotate.aprs2.net","port":14580,"filter":"m/10","messagesToRF":false,"objectsToRF":false},"beacon":{"comment":"LoRa APRS","interval":15,"latitude":52.222,"longitude":5.993,"overlay":"L","symbol":"a","sendViaAPRSIS":true,"sendViaRF":false,"path":"WIDE1-1","statusActive":false,"statusPacket":"","gpsActive":false,"gpsAmbiguity":false},"personalNote":"","blacklist":"","digi":{"mode":0,"ecoMode":0},"lora":{"rxFreq":433775000,"txFreq":433775000,"spreadingFactor":12,"signalBandwidth":125000,"codingRate4":5,"power":20,"txActive":true,"rxActive":true},"display":{"alwaysOn":false,"timeout":30,"turn180":false},"battery":{"sendInternalVoltage":false,"monitorInternalVoltage":false,"internalSleepVoltage":2.900000095,"sendExternalVoltage":false,"externalVoltagePin":34,"monitorExternalVoltage":false,"externalSleepVoltage":10.89999962,"voltageDividerR1":100,"voltageDividerR2":27,"sendVoltageAsTelemetry":false},"wxsensor":{"active":false,"heightCorrection":0,"temperatureCorrection":0},"syslog":{"active":false,"server":"lora.link9.net","port":1514,"logBeaconOverTCPIP":false},"tnc":{"enableServer":false,"enableSerial":false,"acceptOwn":false},"mqtt":{"active":false,"server":"","topic":"","username":"","password":"","port":1883},"ota":{"username":"","password":""},"webadmin":{"active":false,"username":"admin","password":""},"remoteManagement":{"managers":"","rfOnly":true},"ntp":{"gmtCorrection":0},"other":{"rebootMode":false,"rebootModeTime":6,"rememberStationTime":30,"backupDigiMode":false}}
Working config: ``` {"wifi":{"AP":[{"ssid":"bbbbbbbbbbbb","password":"aaaaaaaaaa"}],"autoAP":{"password":"1234567890","timeout":10}},"callsign":"PI1APD-10","aprs_is":{"active":false,"passcode":"17070","server":"rotate.aprs2.net","port":14580,"filter":"m/10","messagesToRF":false,"objectsToRF":false},"beacon":{"comment":"LoRa APRS de Mheen","interval":15,"latitude":52.222,"longitude":5.993,"overlay":"L","symbol":"a","sendViaAPRSIS":false,"sendViaRF":false,"path":"WIDE1-1","gpsActive":false,"gpsAmbiguity":false},"digi":{"mode":0,"ecoMode":0},"lora":{"rxFreq":433775000,"txFreq":433775000,"spreadingFactor":12,"signalBandwidth":125000,"codingRate4":5,"power":20,"txActive":true,"rxActive":true},"display":{"alwaysOn":false,"timeout":30,"turn180":false},"battery":{"sendInternalVoltage":false,"monitorInternalVoltage":false,"internalSleepVoltage":2.900000095,"sendExternalVoltage":false,"externalVoltagePin":34,"monitorExternalVoltage":false,"externalSleepVoltage":10.89999962,"voltageDividerR1":100,"voltageDividerR2":27,"sendVoltageAsTelemetry":false},"wxsensor":{"active":false,"heightCorrection":0,"temperatureCorrection":0},"syslog":{"active":false,"server":"lora.link9.net","port":1514},"tnc":{"enableServer":false,"enableSerial":false,"acceptOwn":false},"other":{"rebootMode":false,"rebootModeTime":6,"rememberStationTime":30,"backupDigiMode":false},"ota":{"username":"admin","password":"xxxxxxxx"},"personalNote":"","blacklist":"","webadmin":{"active":true,"username":"admin","password":"xxxxxxxx"},"ntp":{"gmtCorrection":0},"remoteManagement":{"managers":"","rfOnly":true}} ``` failing config: ``` {"wifi":{"AP":[{"ssid":"bbbbbbbbbbbb","password":"xxxxxxxxxx"}],"autoAP":{"password":"1234567890","timeout":10}},"callsign":"PI1APD-10","aprs_is":{"active":true,"passcode":"17070","server":"rotate.aprs2.net","port":14580,"filter":"m/10","messagesToRF":false,"objectsToRF":false},"beacon":{"comment":"LoRa APRS","interval":15,"latitude":52.222,"longitude":5.993,"overlay":"L","symbol":"a","sendViaAPRSIS":true,"sendViaRF":false,"path":"WIDE1-1","statusActive":false,"statusPacket":"","gpsActive":false,"gpsAmbiguity":false},"personalNote":"","blacklist":"","digi":{"mode":0,"ecoMode":0},"lora":{"rxFreq":433775000,"txFreq":433775000,"spreadingFactor":12,"signalBandwidth":125000,"codingRate4":5,"power":20,"txActive":true,"rxActive":true},"display":{"alwaysOn":false,"timeout":30,"turn180":false},"battery":{"sendInternalVoltage":false,"monitorInternalVoltage":false,"internalSleepVoltage":2.900000095,"sendExternalVoltage":false,"externalVoltagePin":34,"monitorExternalVoltage":false,"externalSleepVoltage":10.89999962,"voltageDividerR1":100,"voltageDividerR2":27,"sendVoltageAsTelemetry":false},"wxsensor":{"active":false,"heightCorrection":0,"temperatureCorrection":0},"syslog":{"active":false,"server":"lora.link9.net","port":1514,"logBeaconOverTCPIP":false},"tnc":{"enableServer":false,"enableSerial":false,"acceptOwn":false},"mqtt":{"active":false,"server":"","topic":"","username":"","password":"","port":1883},"ota":{"username":"","password":""},"webadmin":{"active":false,"username":"admin","password":""},"remoteManagement":{"managers":"","rfOnly":true},"ntp":{"gmtCorrection":0},"other":{"rebootMode":false,"rebootModeTime":6,"rememberStationTime":30,"backupDigiMode":false}} ``` <!-- github-comment-id:3312541722 -->
adam commented 2026-10-05 05:50:43 +02:00
Author
Owner
Copy link
Copy source

are you using V3.1.2 on the "igate board 2" ???

are you using V3.1.2 on the "igate board 2" ??? <!-- github-comment-id:3312586263 -->
adam commented 2026-10-05 05:50:43 +02:00
Author
Owner
Copy link
Copy source

Board 2 is using 3.1.2 as it was flashed today after I encountered issues.

Board 2 is using 3.1.2 as it was flashed today after I encountered issues. <!-- github-comment-id:3312603913 -->
adam commented 2026-10-05 05:50:44 +02:00
Author
Owner
Copy link
Copy source

so lets go to the basics:

wifi connection procedure hasn't changed at all from the start so there must be a strange thing going on.

Can you just flash (and erase the board from all as a regular new board flashing) and flash V3.1.2

just add your callsign and your WiFi SSID and PASSWORD? and see if its connected to wifi or not ?

  1. if it does connect... ok lets continue
  2. if it does not.... then we have to check more on the router side
so lets go to the basics: wifi connection procedure hasn't changed at all from the start so there must be a strange thing going on. Can you just flash (and erase the board from all as a regular new board flashing) and flash V3.1.2 just add your callsign and your WiFi SSID and PASSWORD? and see if its connected to wifi or not ? 1) if it does connect... ok lets continue 2) if it does not.... then we have to check more on the router side <!-- github-comment-id:3312618922 -->
adam commented 2026-10-05 05:50:45 +02:00
Author
Owner
Copy link
Copy source

I just saw this same problem, the iGate boots up and connects to WiFi. But if the WiFi doesn't have an uplink (if Starlink is off in our case), then it never completes the start-up and stays in this Loading... state.

Ideally it should just note that APRS-IS is unavailable and boot up in digipeater / TNC mode until internet becomes available.

I just saw this same problem, the iGate boots up and connects to WiFi. But if the WiFi doesn't have an uplink (if Starlink is off in our case), then it never completes the start-up and stays in this _Loading..._ state. Ideally it should just note that APRS-IS is unavailable and boot up in digipeater / TNC mode until internet becomes available. <!-- github-comment-id:3469682119 -->
adam commented 2026-10-05 05:50:45 +02:00
Author
Owner
Copy link
Copy source

we should get a way to test about "internet connection" as a basic script then before attempting to be in working conditions, right?

we should get a way to test about "internet connection" as a basic script then before attempting to be in working conditions, right? <!-- github-comment-id:3470382295 -->
adam commented 2026-10-05 05:50:46 +02:00
Author
Owner
Copy link
Copy source

I think the right way to test is end-to-end, so see if we can establish a connection to APRS-IS. If not, operate purely as digipeater (if mode is enabled) and keep periodically trying to establish the APRS-IS connection.

There are many ways we can be unable to establish the connection:

  • WiFi is down
  • WiFi doesn't have Internet uplink
  • APRS-IS is down

From the point of view of the iGate, it shouldn't matter which of these conditions it is, we just should operate the way we can, and keep retrying to establish the (WiFi or APRS-IS) connection.

I think this would be the most robust approach, as any or all of the three might have intermittent outages in real-world usage. And even more so on an ocean-going sailboat!

I think the right way to test is end-to-end, so see if we can establish a connection to APRS-IS. If not, operate purely as digipeater (if mode is enabled) and keep periodically trying to establish the APRS-IS connection. There are many ways we can be unable to establish the connection: * WiFi is down * WiFi doesn't have Internet uplink * APRS-IS is down From the point of view of the iGate, it shouldn't matter which of these conditions it is, we just should operate the way we can, and keep retrying to establish the (WiFi or APRS-IS) connection. I think this would be the most robust approach, as any or all of the three might have intermittent outages in real-world usage. And even more so on an ocean-going sailboat! <!-- github-comment-id:3473772036 -->
adam commented 2026-10-05 05:50:47 +02:00
Author
Owner
Copy link
Copy source

Additional info, I just tested: if the iGate is in the Connected: loading... state, it will not recover even when Internet is switched on later. Instead, you need to reboot the device.

Additional info, I just tested: if the iGate is in the `Connected: loading...` state, it will _not_ recover even when Internet is switched on later. Instead, you need to reboot the device. <!-- github-comment-id:3474140129 -->
adam commented 2026-10-05 05:50:47 +02:00
Author
Owner
Copy link
Copy source

could you all please check for V3.1.7 available?

could you all please check for V3.1.7 available? <!-- github-comment-id:3696742365 -->
adam commented 2026-10-05 05:50:48 +02:00
Author
Owner
Copy link
Copy source

Still happens with 3.1.7, though not every time

Image

Still happens with 3.1.7, though not every time ![Image](https://github.com/user-attachments/assets/6edfad31-6d7a-43e5-b5f7-ff3ac8687f20) <!-- github-comment-id:3854309062 -->
adam commented 2026-10-05 05:50:49 +02:00
Author
Owner
Copy link
Copy source

it has a check once 30 secs for WiFi being connected... it should be fast at recovery

it has a check once 30 secs for WiFi being connected... it should be fast at recovery <!-- github-comment-id:3854321268 -->
adam commented 2026-10-05 05:50:49 +02:00
Author
Owner
Copy link
Copy source

This state persisted for at least an hour

This state persisted for at least an hour <!-- github-comment-id:3854745811 -->
adam commented 2026-10-05 05:50:50 +02:00
Author
Owner
Copy link
Copy source

so its not connected or is connected and not to the server ???

so its not connected or is connected and not to the server ??? <!-- github-comment-id:3855162217 -->
adam commented 2026-10-05 05:50:51 +02:00
Author
Owner
Copy link
Copy source

It is connected to WiFi without an active uplink (Starlink was off).

It is connected to WiFi without an active uplink (Starlink was off). <!-- github-comment-id:3855509341 -->
adam commented 2026-10-05 05:50:51 +02:00
Author
Owner
Copy link
Copy source

digiBackUpFix-plus-tactical branch has a "not finished" new way to check for also aprs-server (which is a way to check that it has internet connection)

if WiFi connected but not server... enters into DigiBackUp Mode

digiBackUpFix-plus-tactical branch has a "not finished" new way to check for also aprs-server (which is a way to check that it has internet connection) if WiFi connected but not server... enters into DigiBackUp Mode <!-- github-comment-id:3855743724 -->
adam commented 2026-10-27 16:38:56 +01:00
Author
Owner
Copy link
Copy source

Dear all,
I have the same problem too after updating the firmware yesterday.
In my case I have a Lyligo board.
The board connects to wifi satisfactory at boot and then goes into “connected! Loading…” mode and stays there forever. Nothing else comes up on the screen.

Any ideas?
Another colleague told me yesterday that he went back to the last firmware version available of 2025 and WiFi connectivity works just fine…

Best regards,
Ruben

Dear all, I have the same problem too after updating the firmware yesterday. In my case I have a Lyligo board. The board connects to wifi satisfactory at boot and then goes into “connected! Loading…” mode and stays there forever. Nothing else comes up on the screen. Any ideas? Another colleague told me yesterday that he went back to the last firmware version available of 2025 and WiFi connectivity works just fine… Best regards, Ruben <!-- github-comment-id:6376105828 -->
adam commented 2026-10-27 16:38:56 +01:00
Author
Owner
Copy link
Copy source

Hola , check just basic wifi data (ssid and password) and also update your callsign

The you can start changing other values to know what is not working on your side

Hola , check just basic wifi data (ssid and password) and also update your callsign The you can start changing other values to know what is not working on your side <!-- github-comment-id:6377904485 -->
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/LoRa_APRS_iGate#217