v2.1.5

Changes since v2.1.4 include:

• make the required 'apply' button on stage2 setup page more obvious
• don't fail DietPi image first boot on certain IPv6 failures
• switch out DietPi images to be DietPi 9.6 based
• switch to newer Raspbian base image for Raspberry Pi
• automatically reduce memory usage for systems < 900 MB memory (no effect on micro / nano feeder)
• add support for local SDRs on a stage2 system. This reduces the need for an additional system in situations where a user wants to have two or maybe three SDRs and wants to simply reuse one of the systems as stage2 (ideally that's an RPi4 or OPi5 or some other reasonably beefy SBC)
• fix small fr24 issues, including a workaround for an FR24 bug when lon < 0.1
• allow restart and recreate for individual containers
• always use mlathub for all mlat results, also for collecting them in stage2
• fix nanofeeder data input from airspy / sdrplay / dump978
• restrict manual airspy gain to valid values
• use rbfeeder mlatresults if there are any
• pin Dozzle and alpine images to reduce unnecessary updates
• fix potential crash if the scripts cannot find a local route
• made micro/nano feeder as an app work again - it seems weird to run this as an app (on port 1099), but maybe there are people who end up doing this reusing an existing DietPi install or something
• add nano feeder mode that tries to even more reduce disk IO and footprint by turning off heatmap, replay, and graphs, as well as moving all logging to memory only (which prevents looking at logs after a crash)
• various code cleanups that resulted in more logical api names, among other things
• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.6

Changes since v2.1.4 include:

• make the required 'apply' button on stage2 setup page more obvious
• don't fail DietPi image first boot on certain IPv6 failures
• switch out DietPi images to be DietPi 9.6 based
• switch to newer Raspbian base image for Raspberry Pi
• reduce memory consumption for integrated feeders running with less than 1G of memory
• automatically reduce memory usage for systems < 900 MB memory (no effect on micro / nano feeder)
• add support for local SDRs on a stage2 system. This reduces the need for an additional system in situations where a user wants to have two or maybe three SDRs and wants to simply reuse one of the systems as stage2 (ideally that's an RPi4 or OPi5 or some other reasonably beefy SBC)
• fix small fr24 issues, including a workaround for an FR24 bug when lon < 0.1
• allow restart and recreate for individual containers
• always use mlathub for all mlat results, also for collecting them in stage2
• fix nanofeeder data input from airspy / sdrplay / dump978
• restrict manual airspy gain to valid values
• use rbfeeder mlatresults if there are any
• pin Dozzle and alpine images to reduce unnecessary updates
• fix potential crash if the scripts cannot find a local route
• made micro/nano feeder as an app work again - it seems weird to run this as an app (on port 1099), but maybe there are people who end up doing this reusing an existing DietPi install or something
• add nano feeder mode that tries to even more reduce disk IO and footprint by turning off heatmap, replay, and graphs, as well as moving all logging to memory only (which prevents looking at logs after a crash)
• various code cleanups that resulted in more logical api names, among other things
• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.5

Changes since v2.1.4 include:

• add support for local SDRs on a stage2 system. This reduces the need for an additional system in situations where a user wants to have two or maybe three SDRs and wants to simply reuse one of the systems as stage2 (ideally that's an RPi4 or OPi5 or some other reasonably beefy SBC)
• fix small fr24 issues, including a workaround for an FR24 bug when lon < 0.1
• allow restart and recreate for individual containers
• always use mlathub for all mlat results, also for collecting them in stage2
• fix nanofeeder data input from airspy / sdrplay / dump978
• restrict manual airspy gain to valid values
• use rbfeeder mlatresults if there are any
• pin Dozzle and alpine images to reduce unnecessary updates
• fix potential crash if the scripts cannot find a local route
• made micro/nano feeder as an app work again - it seems weird to run this as an app (on port 1099), but maybe there are people who end up doing this reusing an existing DietPi install or something
• add nano feeder mode that tries to even more reduce disk IO and footprint by turning off heatmap, replay, and graphs, as well as moving all logging to memory only (which prevents looking at logs after a crash)
• various code cleanups that resulted in more logical api names, among other things
• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.4

Changes since v2.1.4 include:

• always use mlathub for all mlat results, also for collecting them in stage2
• fix nanofeeder data input from airspy / sdrplay / dump978
• restrict manual airspy gain to valid values
• use rbfeeder mlatresults if there are any
• pin Dozzle and alpine images to reduce unnecessary updates
• fix potential crash if the scripts cannot find a local route
• made micro/nano feeder as an app work again - it seems weird to run this as an app (on port 1099), but maybe there are people who end up doing this reusing an existing DietPi install or something
• add nano feeder mode that tries to even more reduce disk IO and footprint by turning off heatmap, replay, and graphs, as well as moving all logging to memory only (which prevents looking at logs after a crash)
• various code cleanups that resulted in more logical api names, among other things
• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.3

Changes since v2.1.4 include:

• pin Dozzle and alpine images to reduce unnecessary updates
• fix potential crash if the scripts cannot find a local route
• made micro/nano feeder as an app work again - it seems weird to run this as an app (on port 1099), but maybe there are people who end up doing this reusing an existing DietPi install or something
• add nano feeder mode that tries to even more reduce disk IO and footprint by turning off heatmap, replay, and graphs, as well as moving all logging to memory only (which prevents looking at logs after a crash)
• various code cleanups that resulted in more logical api names, among other things
• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.2

Changes since v2.1.4 include:

• add script to more easily build our images locally - this should allow us to work around the weird GitHub Action issues with Odroid images
• deal with another random change in the airplanes.live status json; at least this change makes things more logical, so I guess I shouldn't complain
• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.5-beta.1

Changes since v2.1.4 include:

• don't unnecessarily add a '_' to the end of a micro feeder site name
• increase size of /run to make sure we don't run out of space for the containers
• add undervoltage and networking issues to the Support Info page
• remove obsolete GitHub Action, references to iob images, and the remainders of the initial attempts to build DietPi images with CustomPiOS
• add several stubs for additional services that aren't fully integrated, but allow managing a pingfail service and integrating CPU/external temperature sensor in the UI template
• fix potential 501 error on startup by avoiding a delayed start of some maintenance tasks

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.4

Changes since v2.1.3 include:

• download Odroid base images from our server (this way our builds no longer randomly break)
• make sure adsb-feeder.local continues to work on the network and allow '-' in hostname
• make sure the updated hostname is included in /etc/hosts
• more careful quoting of strings when sanitizing the log before upload

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.4-beta.1

Changes since v2.1.3 include:

• download Odroid base images from our server (this way our builds no longer randomly break)
• make sure adsb-feeder.local continues to work on the network and allow '-' in hostname
• make sure the updated hostname is included in /etc/hosts
• more careful quoting of strings when sanitizing the log before upload

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.

v2.1.3

Changes since v2.1.2 include:

• avoid potential race condition when writing config.json (which was hit quite reliably when doing an app install)
• fixup form value issue with last beta (checkbox value must be 1)
• index page: improve load time
• restarting / logstreamer pages: avoid using readystatechange listener to make sure functions don't run unexpectedly
• if a feeder has working GPS/gpsd that is accessible for the Ultrafeeder container, add option to derive location from the GPS data
• fix zerotier bring up after restore
• make network checks more robust, trying to deal with corner cases where ICMP may be blocked or have extremely high latency
• reduce image sizes some more by removing unnecessary components that were being bundled
• update SDR-E containers
• address security issues around user input potentially being executed
• new experimental Raspbian based Le Potato image that supports WiFi with many USB-WiFi adapters
• many small improvements to logging and debuggability
• set station name as hostname as well

Note

Based on the available usage information, I have significantly reduced the number of images provided here. If there's one that you need for a different SBC which is supported either by Armbian or DietPi, please post a request on the Zulip server

Warning

Images can take more than 5 minutes before the web interface is available. Please be patient.

Note

Currently the Odroid image and the default LePotato images do NOT support WiFi. For the default Raspberry Pi image (but not the new Raspbian image for LePotato), WiFi can be configured with the Pi Imager when you write the image to SD-card, DietPi based images do support WiFi, but they require editing two files on the DOS partition included with the image BEFORE the first boot. Please look at the adsb.im FAQ for details.
Alternatively, if there is no network connection detected, all WiFi enabled images will create a hotspot named adsb.im-feeder. You can then connect to that hotspot and set up SSID/password of the access point you want the feeder to connect to.

For Raspberry Pis there are multiple images available. For most users the Raspbian based adsb-im-raspberrypi64-pi-2-3-4-5-v....img.xz is likely the best choice, but there are also two DietPi based images available for those who prefer that.