1.1.0 - Notices, refuses, stops, and says its version

• A dead connection is noticed. The relay pings every 30 seconds; a socket that has
  carried nothing for 90 seconds is closed and reopened. Until now a NAT that dropped the
  mapping left the add-on "connected" indefinitely while nothing reached Home Assistant.
• Only the nine calls Stratorama makes are relayed: GET /api/states and the light,
  switch and cover services listed in the README. Anything else is answered 403 and
  Home Assistant never sees it.
• A refusal no retry can fix - an unknown, used or expired pairing code, or a revoked
  credential with no code to fall back on - stops the add-on with one line saying what to
  do, instead of retrying every minute. A revoked credential with a pairing code in the
  configuration is forgotten and the code tried at once, so re-pairing takes one restart.
• Nothing the relay or Home Assistant sends can end the process any more: an error while
  handling a message is logged and the connection kept.
• The version is in the first log line and in every hello, so a support question can be
  answered from the relay's journal.
• Development outside Home Assistant: HA_HTTP_URL and HA_WS_URL point the agent at any
  instance; npm test runs the suite against an in-process relay.

Images: ghcr.io/stratorama/amd64-stratorama-agent:1.1.0, ghcr.io/stratorama/aarch64-stratorama-agent:1.1.0. Home Assistant offers the update from 1.0.0 after the add-on store refreshes (Settings > Add-ons > Add-on Store > menu > Check for updates).