R:v1.1.2-dev1
Core:v1.1.1
Docker compose environment with Heltec v4 modem over Wifi
Switching back and forth between No TX, Monitor and Repeater mode works fine, but when restarting the service it defaults back to No TX
R:v1.1.2-dev1
Core:v1.1.1
Docker compose environment with Heltec v4 modem over Wifi
Switching back and forth between No TX, Monitor and Repeater mode works fine, but when restarting the service it defaults back to No TX
<!-- github-sync-id:5228210634 -->
Mode changes now persist to configuration instead of only changing the running state. The fix is in set_mode.
The audit exercised no_tx → forward through the endpoint, received persisted=true, and reloaded the temporary YAML to confirm forward was saved. An actual container restart was not part of that check. Please retest with a build containing this fix if the restart reversion is still occurring.
Closing this as fixed on `dev` by [PR #402](https://github.com/openhop-dev/openhop_repeater/pull/402).
Mode changes now persist to configuration instead of only changing the running state. The fix is in [`set_mode`](https://github.com/openhop-dev/openhop_repeater/blob/ab7479c55c01fb0163c0032f854e04917eedab90/repeater/web/api_endpoints.py#L2058-L2175).
The audit exercised `no_tx` → `forward` through the endpoint, received `persisted=true`, and reloaded the temporary YAML to confirm `forward` was saved. An actual container restart was not part of that check. Please retest with a build containing this fix if the restart reversion is still occurring.
<!-- github-comment-id:5588242678 -->
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.
R:v1.1.2-dev1
Core:v1.1.1
Docker compose environment with Heltec v4 modem over Wifi
Switching back and forth between No TX, Monitor and Repeater mode works fine, but when restarting the service it defaults back to No TX
Closing this as fixed on
devby PR #402.Mode changes now persist to configuration instead of only changing the running state. The fix is in
set_mode.The audit exercised
no_tx→forwardthrough the endpoint, receivedpersisted=true, and reloaded the temporary YAML to confirmforwardwas saved. An actual container restart was not part of that check. Please retest with a build containing this fix if the restart reversion is still occurring.