We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Save this comment yesterday, by @tkerby and I wanted to follow up on it. I did not see any Feature Request like that, so I decided to open this.
The list of known drivers and protocols change by each firmware version, and it is also subject to customisation.
An option to "Detect Driver/Protocol" for raw files would be really practical.
No response
The text was updated successfully, but these errors were encountered:
Interestingly you can process a raw file using the CLI but not the UI. Would be great to integrate post processing in the UI
Sorry, something went wrong.
Wow! I did not realise that! Do you have a docs on that?
@ppseprus, There are brief docs in the subghz command on the command line.
subghz
To decode a raw recording use subghz decode_raw <FILE>
subghz decode_raw <FILE>
Awesome! Thanks!
Still, I think a UI feature would be practical.
#1667
skotopes
No branches or pull requests
Description of the feature you're suggesting.
Save this comment yesterday, by @tkerby and I wanted to follow up on it. I did not see any Feature Request like that, so I decided to open this.
The list of known drivers and protocols change by each firmware version, and it is also subject to customisation.
An option to "Detect Driver/Protocol" for raw files would be really practical.
Anything else?
No response
The text was updated successfully, but these errors were encountered: