ami2ha 0.1.1

Makes it installable. 0.1 shipped no icons at all, so there was nothing to
double-click — while the ReadMe and the guide both told you to double-click
Install. And the Shell fallback, Installer Install, fails on AmigaOS 3.2,
where the Installer lives in SYS:System and isn't on the command path.

Several people reported this and assumed their Installer was at fault. It
wasn't — both were my mistakes. Thank you for saying so.

What's fixed

• Real Workbench icons: the drawer, the program, and Install — whose
  default tool is spelled out, so double-clicking actually reaches the
  Installer.
• The documented commands are correct, and the manual copy route is given
  equal weight, since it needs no Installer at all and so can't break.
• The installer copes with being run from the drawer you unpacked it into.
  That's what accepting the defaults does, and it used to fail halfway through
  with "object in use".
• A worked example in the guide, start to finish — and a plain statement of
  what belongs in the icon's tool types versus the configuration file, which
  is the thing people found most confusing.

Nothing changed in the program itself. If 0.1 is already running, you don't
need this — though the icon is nicer.

Installing

Unpack and double-click the Install icon. From a Shell, name the Installer
in full:

SYS:System/Installer Install

Or skip it — it's one program. Copy ami2ha.020 (or ami2ha.000 on a 68000)
wherever you like and read ami2ha.guide.

Requirements are unchanged: AmigaOS 3.0+, a TCP/IP stack offering
bsdsocket.library, and MUI 3.8+ for the dashboard.

Tested on a PiStorm A600 running a fresh AmigaImager image, installed the way
a stranger would rather than by pushing files in over the wire — which is how
all of the above got found.

ami2ha 0.1

A native AmigaOS client for Home Assistant.
Read your sensors and flip your switches from a real Amiga.

First release. Everything here has been run on AmigaOS 3.2 against a
live Home Assistant, not just against tests.

Install

Unpack ami2ha-0.1.lha and double-click Install, or from a Shell
inside the drawer:

Installer Install

The archive contains both a 68000 and a 68020 build; the installer picks
the one that matches. ami2ha.guide is the manual — open it with
MultiView.

You will need

• AmigaOS 3.0 or newer
• a TCP/IP stack offering bsdsocket.library — Roadshow, AmiTCP, Miami,
  or UAE's own emulation
• MUI 3.8 or newer for the dashboard; the command line modes work without it
• a long-lived access token from Home Assistant: click your user name at
  the bottom left, open Security, and create one under Long-lived
  access tokens

Keep the token in a file. Never pass it on a command line, where your
shell history would remember it, and remember it travels over your
network in the clear — fine on your own LAN, not fine over the internet.

What it does

• sensors, gauges, toggles and buttons on a MUI dashboard
• choose which entities appear by giving them a label in Home Assistant,
  so you can change the Amiga's display without touching the Amiga
• a settings window for grouping, ordering, labelling and choosing how
  each entity is shown
• an ARexx port, so the rest of your Workbench can read your house and
  control it
• reconnects on its own when the link drops, backing off up to a minute
• starts from Workbench, with its settings in the icon's tool types

Memory follows the size of your dashboard, not the size of your Home
Assistant: measured against an installation with 2079 entities, a dozen
entities cost 1.3 KB rather than 960 KB.

Not yet

• HTTPS (AmiSSL). Your server must be reachable over plain HTTP, which on
  most home setups it is, on port 8123 from inside the network.
• drag-and-drop reordering; Up and Down work today

If something breaks

Project -> About shows which server that copy is actually talking to,
which answers the first question more often than you would think. The
"When it breaks" section of the guide covers the common messages.

Bug reports welcome: https://github.com/evil4dmin/ami2ha/issues