Hey @esmathews
So … after debugging no planes on skyaware anywhere with someone who asked me, turns out his computers clock was running 2 minutes late or so resulting in a message rate being displayed but no planes on the map as they are all considered stale.
This seems to have the root cause that unlike the /dump1090-fa interface the websocket data fetcher uses the computers local time to calculate plane.seen in for the object that is then passed to processReceiverUpdate().
While this isn’t necessarily a bug … i’d say in the long term it will save you complaints to use server time instead of browser time in that data fetcher