v2.2.6

Fixes

• When fetchtv cannot list recordings, it now says why, instead of one line for every case:
  • The box does not offer a ContentDirectory service, or did not answer the request for its folders, or did not answer the request for its Recordings folder: restart the box and try again. This does not mean the box has no recordings.
  • The box lists no Recordings folder: a Fetch box that has lost its Fetch service (account cancelled or suspended, or no internet) shows its setup screen on the TV and lists no recordings until that is fixed.
  • The Recordings folder is empty: the box answered and has no recordings.
• A filter that matches nothing (--show, --exclude, --title) no longer prints the cancelled-account hint.

For programs that use fetchtv

• getFetchRecordings takes an optional onOutcome callback. It is called once with { outcome, error?, folders? }. outcome is one of ok, empty, no-content-directory, browse-failed, no-recordings-folder, or recordings-browse-failed. The exported LISTING_OUTCOME object holds these values. The return value is unchanged.

Upgrading

Run npx fetchtv@latest, or docker pull furey/fetchtv:latest. Nothing else changes.