ami2ha -- control your smart home from a real Amiga
===================================================

A native AmigaOS client for Home Assistant, the open-source home
automation server. Read your sensors, watch entity states and flip your
switches from a MUI dashboard, with an ARexx port so the rest of your
Workbench can join in.


WHAT IT DOES

  - sensors, gauges, toggles and buttons on a configurable MUI dashboard
  - pick which entities appear by giving them a label in Home Assistant,
    so you can change what the Amiga shows without touching the Amiga
  - a settings window for grouping, ordering, labelling and choosing how
    each entity is displayed
  - an ARexx port (AMI2HA): GET, ATTR, LIST, TOGGLE, ON, OFF, CALL,
    STATUS, so other programs can read the house and control it
  - reconnects by itself when the link drops, backing off up to a minute
  - starts from Workbench, with its settings in the icon's tool types
  - command line modes that work without MUI: LIST, GET, ON, OFF, WATCH

Memory follows the size of your dashboard, not the size of your Home
Assistant. It asks the server only for the entities you show: measured
against an installation with 2079 entities, a dozen of them cost 1.3 KB
rather than 960 KB.


REQUIREMENTS

  - 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 68020 is comfortable; a 68000 build is included and works, but
    JSON over TCP on a stock A500 is slow
  - a long-lived access token from your own Home Assistant


INSTALLING

Unpack and double-click Install, or from a Shell inside the drawer:

    Installer Install

Both a 68000 and a 68020 build are included; the installer picks the one
that matches. Full instructions are in ami2ha.guide -- open it with
MultiView.

You will need a long-lived access token: in Home Assistant, click your
user name at the bottom left, open the Security tab, and create one under
"Long-lived access tokens". It is shown once. Keep it in a file, and do
not pass it on a command line where your shell history would remember it.
It travels over your network in the clear, which is fine on your own LAN
and not fine over the internet.


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


LICENCE

MIT. Do what you like with it. Source, issues and newer versions:

    https://github.com/evil4dmin/ami2ha

Home Assistant is a separate project and nothing to do with the author:

    https://www.home-assistant.io/

 PERMSSN    UID  GID    PACKED    SIZE  RATIO METHOD CRC     STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[Amiga]                  39026   77100  50.6% -lh5- 6852 Aug  9 21:46 ami2ha/ami2ha.000
[Amiga]                  38140   73144  52.1% -lh5- 2e6b Aug  9 21:46 ami2ha/ami2ha.020
[Amiga]                   5233   12527  41.8% -lh5- 39ca Aug  9 21:46 ami2ha/ami2ha.guide
[Amiga]                    477     964  49.5% -lh5- fce1 Aug  9 21:46 ami2ha/dashboard.cfg.example
[Amiga]                   2543    7331  34.7% -lh5- 4708 Aug  9 21:46 ami2ha/Install
[Amiga]                    633    1076  58.8% -lh5- 0fa5 Aug  9 21:46 ami2ha/LICENSE
[Amiga]                    921    1795  51.3% -lh5- ea2d Aug  9 21:46 ami2ha/ReadMe
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         7 files   86973  173937  50.0%            Aug  9 22:55