# Piaware 2.1-5

**URL:** <https://discussions.flightaware.com/t/piaware-2-1-5/17787>\
**Category:** ADS-B Flight Tracking\
**Created:** [December 24, 2015, 4:34pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787 "2015-12-24T16:34:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [December 24, 2015, 4:34pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/1 "2015-12-24T16:34:15Z")

</div>

Piaware 2.1-5 is available. If you have autoupdates enabled, you should be upgraded to this release soon.

This is a maintenance release with no particular new features. Main changes from 2.1-3:

- Update the certificates used to secure the connection between piaware and FlightAware’s servers.
- Reconnection after network outages or connection validation errors should be more reliable.

As usual the [full changelog](https://github.com/flightaware/piaware_builder/blob/v2.1-5/changelog) and [detailed changes](https://github.com/flightaware/piaware/compare/v2.1-3...v2.1-5) are available on github.

If you are upgrading from 2.1-2 or earlier, please also see the [2.1-3 release information](https://discussions.flightaware.com/t/piaware-2-1-3-released/17363)

---

<div class="post-metadata">

**Author:** ![N456TS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/n456ts/32/88612_2.png) [@N456TS](https://discussions.flightaware.com/u/N456TS)\
**Post date:** [December 24, 2015, 5:43pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/2 "2015-12-24T17:43:15Z")

</div>

Seamless upgrade. Thanks!

---

<div class="post-metadata">

**Author:** ![MW50C3](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mw50c3/32/128763_2.png) [@MW50C3](https://discussions.flightaware.com/u/MW50C3)\
**Post date:** [December 24, 2015, 7:13pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/3 "2015-12-24T19:13:23Z")

</div>

Worked like magic here. Upgrade complete, logs are clean, traffic is flowing.

---

<div class="post-metadata">

**Author:** ![schweboo](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/schweboo/32/94439_2.png) [@schweboo](https://discussions.flightaware.com/u/schweboo)\
**Post date:** [December 24, 2015, 8:19pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/4 "2015-12-24T20:19:09Z")

</div>

Upgrade seems to have gone like a dream here too…

---

<div class="post-metadata">

**Author:** ![beckerm13](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/beckerm13/32/115529_2.png) [@beckerm13](https://discussions.flightaware.com/u/beckerm13)\
**Post date:** [December 24, 2015, 8:40pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/5 "2015-12-24T20:40:03Z")

</div>

I upgraded and I am now seeing these statements:

[2015-12-24 14:37 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

I returned to v2.1-2 and the messages went away.

Marty

---

<div class="post-metadata">

**Author:** ![elpipila](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/elpipila/32/111945_2.png) [@elpipila](https://discussions.flightaware.com/u/elpipila)\
**Post date:** [December 24, 2015, 8:50pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/6 "2015-12-24T20:50:51Z")

</div>

> [@beckerm13](#):
>
> I upgraded and I am now seeing these statements:
> 
> [2015-12-24 14:37 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
> [2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
> [2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
> 
> I returned to v2.1-2 and the messages went away.
> 
> Marty

upgrade your dump1090

---

<div class="post-metadata">

**Author:** ![beckerm13](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/beckerm13/32/115529_2.png) [@beckerm13](https://discussions.flightaware.com/u/beckerm13)\
**Post date:** [December 24, 2015, 10:19pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/7 "2015-12-24T22:19:19Z")

</div>

> [@elpipila](#):
>
> > [@beckerm13](#):
> >
> > I upgraded and I am now seeing these statements:
> > 
> > [2015-12-24 14:37 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
> > [2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
> > [2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
> > 
> > I returned to v2.1-2 and the messages went away.
> > 
> > Marty
> 
> upgrade your dump1090

I am running the latest dump1090-mutability v1.15~dev, so there is nothing to upgrade.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [December 24, 2015, 11:10pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/8 "2015-12-24T23:10:25Z")

</div>

That is a change that dates back to 2.1-3. You need to either reconfigure dump1090 to listen on port 30104 for beast mlat data, or reconfigure piaware to feed to a port of your choice. See [ads-b-flight-tracking-f21/piaware-2-1-3-released-t36047.html](https://discussions.flightaware.com/t/piaware-2-1-3-released/17363)

---

<div class="post-metadata">

**Author:** ![karlrobbins](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/karlrobbins/32/75001_2.png) [@karlrobbins](https://discussions.flightaware.com/u/karlrobbins)\
**Post date:** [December 24, 2015, 11:33pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/9 "2015-12-24T23:33:39Z")

</div>

Upgrade to 2.1-5 completed, restarted and running nicely without issue 😃

Merry Christmas Oliver.

---

<div class="post-metadata">

**Author:** ![anon42605198](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@anon42605198](https://discussions.flightaware.com/u/anon42605198)\
**Post date:** [December 25, 2015, 4:08pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/10 "2015-12-25T16:08:56Z")

</div>

hello all, so i got a 5" touch screen for my piaware, can’t wait to get it up and going.( need a larger sd card)… can someone direct me to some info in regards to installing it with flightaware/ dump1090… i seen afew vids on it but they don’t explain much… thanks

---

<div class="post-metadata">

**Author:** ![elpipila](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/elpipila/32/111945_2.png) [@elpipila](https://discussions.flightaware.com/u/elpipila)\
**Post date:** [December 25, 2015, 6:23pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/11 "2015-12-25T18:23:02Z")

</div>

> [@mainescanner](#):
>
> hello all, so i got a 5" touch screen for my piaware, can’t wait to get it up and going.( need a larger sd card)… can someone direct me to some info in regards to installing it with flightaware/ dump1090… i seen afew vids on it but they don’t explain much… thanks

Installation instructions

[flightaware.com/adsb/piaware/build](http://flightaware.com/adsb/piaware/build)

---

<div class="post-metadata">

**Author:** ![blueskyspotter](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/blueskyspotter/32/77729_2.png) [@blueskyspotter](https://discussions.flightaware.com/u/blueskyspotter)\
**Post date:** [December 25, 2015, 11:24pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/12 "2015-12-25T23:24:21Z")

</div>

Did not encounter any issues upgrading to the latest version.

---

<div class="post-metadata">

**Author:** ![anon42605198](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@anon42605198](https://discussions.flightaware.com/u/anon42605198)\
**Post date:** [December 26, 2015, 12:06pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/13 "2015-12-26T12:06:35Z")

</div>

> [@elpipila](#):
>
> > [@mainescanner](#):
> >
> > hello all, so i got a 5" touch screen for my piaware, can’t wait to get it up and going.( need a larger sd card)… can someone direct me to some info in regards to installing it with flightaware/ dump1090… i seen afew vids on it but they don’t explain much… thanks
> 
> Installation instructions
> 
> [flightaware.com/adsb/piaware/build](http://flightaware.com/adsb/piaware/build)

there is no info there for what i asked …

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [December 26, 2015, 12:29pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/14 "2015-12-26T12:29:24Z")

</div>

That link tells you how to build a piaware install running on a Pi. If that’s not what you’re looking for, what are you trying to build?

---

<div class="post-metadata">

**Author:** ![dschaper](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dschaper/32/59633_2.png) [@dschaper](https://discussions.flightaware.com/u/dschaper)\
**Post date:** [December 26, 2015, 6:52pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/15 "2015-12-26T18:52:30Z")

</div>

I think they might be asking for instructions on how to display the information on the touchscreen?

---

<div class="post-metadata">

**Author:** ![dgates](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dgates/32/41481_2.png) [@dgates](https://discussions.flightaware.com/u/dgates)\
**Post date:** [December 27, 2015, 1:42am UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/16 "2015-12-27T01:42:41Z")

</div>

Seems to be using less CPU than 2.1-3 did, a Good Thing.

---

<div class="post-metadata">

**Author:** ![anon42605198](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@anon42605198](https://discussions.flightaware.com/u/anon42605198)\
**Post date:** [December 27, 2015, 11:49am UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/17 "2015-12-27T11:49:48Z")

</div>

looking for instructions on ruining the touch screen with piaware running dump1090…i know i have to install the software for the screen and piaware. just not sure what i will need to tweak to make it work.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [December 27, 2015, 12:41pm UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/18 "2015-12-27T12:41:40Z")

</div>

I guess you will need to configure X to use the touchscreen, and start a web browser to point at the dump1090 map. Not sure how useable that will be.

---

<div class="post-metadata">

**Author:** ![cy80rg](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/cy80rg/32/94033_2.png) [@cy80rg](https://discussions.flightaware.com/u/cy80rg)\
**Post date:** [December 31, 2015, 8:01am UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/19 "2015-12-31T08:01:34Z")

</div>

Morning all,

Noticed over the Christmas period that

a) The new Station Stats UI now show MLAT vs ADSB vs Other stats  
b) My daily stats have plummted, from c2900 birds per day, to c800

Just updated to PiAware 2.1-5 - now Mut shows zero aircraft, and the console in the Station Stats on FA shows Mut isnt sending anything to FA…

"  
[2015-12-31 07:55 GMT] 0 msgs recv’d from dump1090-muta (0 in last 5m); 0 msgs sent to FlightAware

"

The BEAST port change required for 2.1.3 was done some weeks ago, and showed some (if reduced) birds before upgrade to 2.1.5.  
I take it the “Send command to device \> Upgrade and restart PiAware” wont have reset this, it shouldnt have done anything to mut?

Also, running Mut 1.14 - can someone point me at upgrade instructions for 1.15 etc?

Thanks - and an early Happy New Year! 🙂

---

<div class="post-metadata">

**Author:** ![cy80rg](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/cy80rg/32/94033_2.png) [@cy80rg](https://discussions.flightaware.com/u/cy80rg)\
**Post date:** [December 31, 2015, 9:43am UTC](https://discussions.flightaware.com/t/piaware-2-1-5/17787/20 "2015-12-31T09:43:37Z")

</div>

Hi all,

So, upgraded to PiAware 2.1-5 succesfully.

Upgraded (via Build) Mutability to 1.15 dev.

My earlier query regarding drop in reports is no doubt due to the changes in the stats as reported by Obj earlier.  
(2900 down to 800 birds/day??)

However, Mut’s still not showing any aircraft… ?

(I went through Mut’s config again, and as Obj mentioned elsewhere, the updated BEAST port for pA is now the default, so shouldnt be that).

Will wait and see if any birds appear (sure there’s a song there somewhere… 😉 ) .

[Next page](https://discussions.flightaware.com/t/piaware-2-1-5/17787.md?page=2)
