Platform
Android App
What happened?
Bug: Repeater management login does not appear to transmit over LoRa
This is occurring on the latest firmware available as of approximately two hours ago.
I am now able to navigate to repeater management on my Heltec running the power-saving firmware. However, when I open the repeater management screen, the Route field is empty. The repeater should be directly reachable, so I am not sure whether the companion is failing to determine the route.
Steps to reproduce
- Open repeater management on the Heltec companion running the power-saving firmware.
- Select the repeater.
- Observe that the Route field is empty.
- Enter the repeater management password.
- Click the button to log in/connect.
Observed behavior
Nothing appears to actually be transmitted over LoRa when attempting to connect.
My companion has an LED that illuminates whenever it transmits a LoRa message. When I attempt to log in to the repeater, that LED does not illuminate at all.
The logs also only appear to show Bluetooth activity. I do not see anything indicating that a LoRa message was created or transmitted as part of the repeater-management connection attempt.
Comparison with the regular MeshCore app
As a control test, I switched to the regular MeshCore app and attempted to manage the same repeater using the same password.
That worked as expected:
- The app sent the repeater-management connection message.
- The companion's transmit/status LED illuminated when the message was sent.
- I was able to manage the repeater normally.
This suggests that the companion and repeater themselves are functioning correctly, and that the issue is specific to the repeater-management connection attempt from this firmware/app path.
Possible cause
One possibility is that the empty Route field is related. If the software does not know the route to the repeater, it may be declining to construct or transmit the management message at all.
Since this repeater is directly reachable, I would expect either a direct route to be selected automatically or for the connection attempt to still result in a transmitted LoRa packet.
The most significant symptom is that clicking login appears to result in no LoRa transmission whatsoever.
How bad is it?
Low - Minor issue
Platform
Android App
What happened?
Bug: Repeater management login does not appear to transmit over LoRa
This is occurring on the latest firmware available as of approximately two hours ago.
I am now able to navigate to repeater management on my Heltec running the power-saving firmware. However, when I open the repeater management screen, the Route field is empty. The repeater should be directly reachable, so I am not sure whether the companion is failing to determine the route.
Steps to reproduce
Observed behavior
Nothing appears to actually be transmitted over LoRa when attempting to connect.
My companion has an LED that illuminates whenever it transmits a LoRa message. When I attempt to log in to the repeater, that LED does not illuminate at all.
The logs also only appear to show Bluetooth activity. I do not see anything indicating that a LoRa message was created or transmitted as part of the repeater-management connection attempt.
Comparison with the regular MeshCore app
As a control test, I switched to the regular MeshCore app and attempted to manage the same repeater using the same password.
That worked as expected:
This suggests that the companion and repeater themselves are functioning correctly, and that the issue is specific to the repeater-management connection attempt from this firmware/app path.
Possible cause
One possibility is that the empty Route field is related. If the software does not know the route to the repeater, it may be declining to construct or transmit the management message at all.
Since this repeater is directly reachable, I would expect either a direct route to be selected automatically or for the connection attempt to still result in a transmitted LoRa packet.
The most significant symptom is that clicking login appears to result in no LoRa transmission whatsoever.
How bad is it?
Low - Minor issue