-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Broadcastify System ID string/number config.json issue #858
Comments
Here is my config.json:
Here is my output when running trunk-recorder:
|
james-coder
added a commit
to james-coder/trunk-recorder
that referenced
this issue
Nov 12, 2023
robotastic
pushed a commit
that referenced
this issue
Nov 12, 2023
This was not fixed by #859 for me |
@e850205 if you are getting an error, please share. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've recently compiled trunk-recorder on a WSL2 Ubuntu 20.04 system. (Using usbipd.)
I used a previously working config.json from another computer where
"broadcastifySystemId": "86753"
(Notice the quotes around the number.) This was working fine for me with no errors.When I compiled it for the WSL2 Ubuntu 20.04 system, I get the error:
Which leads me to think it wants a int there instead instead of a string. I change it to be
"broadcastifySystemId": 86753
, but then I get this error:So basically, I getting one error message that says it should be an integer (in SYSTEMS), I change it to an integer, then I get another error message saying it should be a string (in PLUGINS).
The documentation at https://github.com/robotastic/trunk-recorder/blob/master/docs/CONFIGURE.md#system-object says:
broadcastifySystemId: if broadcastifyCallsServer is set System ID for Broadcastify Calls (this is an integer, and different from the RadioReference system ID)
The broadcastify plugins code is in https://github.com/robotastic/trunk-recorder/blob/47460b1582ec5187ed99eac0df93ae41ab93017f/plugins/broadcastify_uploader/broadcastify_uploader.cc
The text was updated successfully, but these errors were encountered: