Closed andypiper closed 2 years ago
I've started to document what I've discovered about it in my repo fork here.
My fork issue #3 depends on knowing more about how the AQ data is sourced.
Also issue #4 in my fork wants to improve the geolocation accuracy (right now my Newt thinks it is ~140 miles away from its actual location). If I could stand up an HTTP/MQTT server to be an alternate for the main one I could experiment with improving accuracy of some of these data points.
Also, enabling multiple or alternative backends in general would be useful - could be a backup if the main server is down or inaccessible, or provide different data.
I've been thinking a lot about how to make the source data more transparent for end users.... the quick and dirty thing to do is to get to source code available for people to look at. I'll try to handle that this weekend.
Thanks - sorry for the deluge of issues / discussion - as you can tell, I’m excited to get hands-on and help here 🙂 for now I have a series of issues as tasks and ideas on my fork, but could bring them over here if you are interested.
Documentation and Link to source code (just the nodeJS code - not the libraries) https://github.com/Phambili-Tech/Newt_Display/wiki/MQTT-API-Summary
Just starting documentation... so it'll evolve over time
Uploaded to github with required documentation
At the moment, this code depends on a server-side HTTP and MQTT service. Could the code for this be published?