-->September 6th, 2025<--
Thank you to GolfCharlie and Claude Code for fixing the code to work with the newly changed FAA API! They have saved a lot of time. A new image has been created and will be uploaded today and available later tonight. If you don't want or need the image, you can visit https://github.com/markyharris/livesectional and incorporate the changes into your board now.
--->September 5th, 2025<--
There has been another change to the FAA API which has again broke the map. We are currently working on this. Check back for fix. If you have the fix please post it. - Mark
Hey Mark et al,
I hope you are well! I had commented awhile back on someone else's thread about my map periodically freezing and we had a discussion about potential connectivity issues, which there may have been some of that. Anyway, in the meantime, I upgraded to 4.372 and replaced the Pi itself for good measure. The current iteration has been online since mid June and has locked up twice. Once I just tickled it (map off/map on). This time, I let it sit so we can troubleshoot if you'd like. The Pi has connectivity and has had a solid connection with no hiccups, I believe, since 6/21.
The map is sitting with a rainbow of colors like it got stuck during the refresh. Sometimes it fails with no lights on.
The current log is logging the following on repeat every 10 seconds.
Thanks!
Vance
Vance,
I've seen this happen as well. But I've not been successful in figuring out exactly why. My best guess is that there is some hiccup with the FAA api and the FAA decides not to respond, and the script doesn't catch this and just keeps trying to get new info. So I put a reboot routine in metar-v4.py that will reboot each evening. However, this is not fool proof. So I have recently changed the reboot routine to be controlled using crontab. This is working much better. It will be in the next updated image.
Thanks for the insights. - Mark