-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
Add APRS device tracker component #22469
Conversation
Yeay! First(?) hamradio component for HA! :-) |
I'm trying to figure out how to pass the |
Codecov Report
@@ Coverage Diff @@
## dev #22469 +/- ##
==========================================
- Coverage 94.09% 93.78% -0.31%
==========================================
Files 452 449 -3
Lines 36795 36618 -177
==========================================
- Hits 34623 34343 -280
- Misses 2172 2275 +103
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## dev #22469 +/- ##
==========================================
- Coverage 94.29% 93.78% -0.51%
==========================================
Files 458 449 -9
Lines 37203 36618 -585
==========================================
- Hits 35079 34343 -736
- Misses 2124 2275 +151
Continue to review full report at Codecov.
|
I don't quite get what's going on here with codecov. I've rebased onto the latest dev branch but it says I've changed all these files that I haven't touched in my commit(s). |
I just wanted to drop by and add some support for this component. I was just thinking about APRS and telemetry and thought "wouldn't it be cool for Home Assistant to be able to receive and transmit telemetry on the APRS-IS network!?" Sure enough, I come to find that the community is already working on this! Thanks! @PhilRW! |
Long-term we could send locations and messages to the network, but I'm starting simple with a device tracker component. |
Perhaps some additional developer documentation is needed when adding a codeowner. |
This component keeps open a connection to the APRS-IS infrastructure so messages generated by filtered callsigns can be immediately acted upon. Any messages with certain values for the 'format' key are position reports and are parsed into device tracker entities.
@syssi Now that I finally have it passing CI, could you take another look? 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok to merge when tests converted from class functions to standalone functions and PlatformNotReady
replaced with error logging.
Fixed. |
Description:
This new APRS component keeps open a connection to the APRS-IS infrastructure so messages generated by filtered callsigns can be immediately acted upon. Any messages with certain values for the 'format' key are position reports and are parsed into device tracker entities.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#9056
Example entry for
configuration.yaml
(if applicable):Checklist:
tox
. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
REQUIREMENTS
variable (example).requirements_all.txt
by runningscript/gen_requirements_all.py
.