What are the various radio and MLAT status sensors? The number aircraft currently being received for those methods or?
Do you know if they expose a way to get a list of all tails by distance? It’d be nice to be able to filter by distance and show details for say the 3 closest or within x miles
What are the various radio and MLAT status sensors? The number aircraft currently being received for those methods or?
Right now the radio sensors just show radio health: red for can’t talk to radio, amber for radio’s there but no traffic, and green for radio’s there and there’s traffic. MLAT is the same: is MLAT synced or not.
Do you know if they expose a way to get a list of all tails by distance? It’d be nice to be able to filter by distance and show details for say the 3 closest or within x miles
The aircraft lists are probably too long and complicated for using the simple method I’m using above. For that I think a custom component will be required. I’m working on building the library, but it’s probably going to take awhile.
Hey mate, I’m interested in pulling in my piaware into as well, but I’m still a little new to home assistant, is there a certain type of card this is nested into? Or could you share the entire card’s yaml? Thank you so much, excited to add this and sorry if I’m overlooking something!
No specific card. The rest block of code above creates sensor.piaware_* entities. Then you can use standard HA cards to display them. The screenshot I posted above is showing a History Graph Card set to display the entities.
Oh, are you adding the above code into your config yaml? Maybe that’s where I just got lost, where to put the code itself. I’ll try config yaml, but let me know if its somewhere else. Thanks for the reply!
Is the resource xx.xx.xx.xx/status.json still working for you?
My previously working installation which has been untouched is no longer returning data from status.json (I am receiving a 404 error when trying to access from a browser). The file does exists in /var/run/piaware/ on the local machine.
The xx.xx.xx.xx:8080/data/aircraft.json is still working correctly.