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
- dimmable lights on a slider, colour lights on a colour wheel with a
brightness strip, blinds and shutters on Open/Stop/Close, and an
on/off box beside every lamp
- lights picked by label arrive as the control they can actually use:
Home Assistant is asked what each one supports, so an RGB strip is a
colour wheel and a plain bulb stays a checkmark
- camera snapshots as tiles, fetched on a click or on a timer, scaled
by the server so a 68k only has a small picture to decode, and
saveable to disk under the name you gave the tile -- or saved larger
than the tile, at a size you choose (1280x720 unless you say
otherwise), for sending on to people with smaller screens
- media players: what is playing -- title, artist, station and volume
-- over buttons for previous, play/pause, next and volume
- pick which entities appear by giving them a label in Home Assistant,
so you can change what the Amiga shows without touching the Amiga
- groups side by side in columns, each column only as tall as what is
in it, and tabs when one page is not enough: a few groups on the
start page, the rest a click away
- a settings window with a Layout page -- tabs, columns, and each
tab's groups in order -- and an Entities page for what each group
shows, its labels and how each entity is displayed
- labelled something new in Home Assistant? Refresh entities picks it
up without a restart
- a dashboard bigger than the screen scrolls, so labelling generously
works on a small Workbench instead of failing to open
- 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,
and notices a connection that has died quietly rather than showing
stale values for hours
- talks https where AmiSSL 5 is installed, checking the certificate and
the host name, so the access token can safely leave your own network --
Home Assistant Cloud included
- 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.
By default the token travels over your network in the clear, which is fine
on your own LAN and not fine over the internet. Add the TLS switch and it
does not: see below.
HTTPS IS OPTIONAL
Plain HTTP on port 8123 remains the default and needs nothing extra --
no AmiSSL, no certificates, no configuration. Most people run ami2ha on
the same network as their server, and for them nothing has changed.
If you want it, adding the TLS switch connects over https instead. That
needs AmiSSL 5 installed, and it is only opened when TLS is actually
asked for, so it costs nothing on a plain setup. The certificate is
checked by default, both the chain and that it names the host you asked
for; a self-signed certificate needs NOVERIFY as well, which keeps the
traffic encrypted but stops proving who is answering.
It is worth it when you reach your house from somewhere else -- Home
Assistant Cloud works -- and mostly is not on a LAN, where it only costs
a slow machine time.
NOT YET
- drag-and-drop reordering; Up and Down work today
- cover art for media players; the text and the transport work today
- the `decimals` keyword is accepted and does nothing; readings show one
decimal place
- pointed at a port that is not Home Assistant, it waits rather than
giving up -- Ctrl-C stops it
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/
|
aminet net>