Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setenv does not work properly with non-nebra fleets #123

Closed
shawaj opened this issue Feb 5, 2023 · 3 comments · Fixed by #126
Closed

Setenv does not work properly with non-nebra fleets #123

shawaj opened this issue Feb 5, 2023 · 3 comments · Fixed by #126

Comments

@shawaj
Copy link
Member

shawaj commented Feb 5, 2023

Originally reported by @hellrc5 here NebraLtd/helium-rak#19 (comment)

packet-forwarder Error: Cannot set FREQ variable.
packet-forwarder VARIANT variable is already set as COMP-RAKHM.
packet-forwarder Error: Not all required parameters have been set. Container will be reset after 5 sec.

Interestingly the diagnostics container detects the correct FREQ plan:

diagnostics INFO:hw_diag.utilities.hardware:Found the following LTE Devices: []
diagnostics INFO:root:Frequency: EU868
@shawaj
Copy link
Member Author

shawaj commented Feb 5, 2023

Relates-to: NebraLtd/hm-diag#444
Relates-to: NebraLtd/hm-diag#468

@MuratUrsavas
Copy link
Contributor

The best way to fix this, is to make FREQ parameter optional, not mandatory.

@shawaj
Copy link
Member Author

shawaj commented Feb 6, 2023

Closed by #126

@shawaj shawaj closed this as completed Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants