Changelog¶
Installers are on the releases page. Versions before 1.0 were previews. The page keeps the newest versions only; an older one can still be built from its tag. Versions before 1.15.1 have security flaws that 1.15.1 fixes: update to it or a later one.
Unreleased¶
- No more packages for macOS. HADA is not signed with an Apple developer certificate, so a Mac does not open the disk images downloaded from a release. They are no longer published, the releases from 1.13.1 to 1.15.1 no longer carry them, and the website and these pages no longer offer them. The page for Linux is now Linux; Linux stays a preview.
1.15.1¶
Security fixes, from a review of the whole app. A stable version, first published as a preview the day before; everyone should update to it.
- The installer no longer asks for a folder: HADA always goes to
C:\Program Files\HADA. In a folder elsewhere, a drive's root for instance, every signed-in user could change the files of the service, which runs as SYSTEM, and so run anything with its rights. A folder named on the command line (INSTALLFOLDER=…) now gets rights of its own instead of those of where it is. A copy installed elsewhere moves to Program Files with the update. - The installed service never takes itself for a portable copy. A
HADA.portablefile next to its folder would have moved its settings to an unprotected folder. - The tray app and the window trust only a service pipe made by SYSTEM or an administrator. Before, they also took one made by their own user, so that any program of that user could, while the service was not running, pose as it and have the tray app start programs and press keys. A portable copy's still accept their own user's, as their service is a process of that user.
- MQTT without TLS only on your own network. As with a Home Assistant connected to directly, HADA no longer connects without TLS to a broker at a public address, where the password and everything the computer reports would travel in the open. The Overview page says so. Turn TLS on, or tick Connect to this broker without encryption on the Connections page if the way there is encrypted by something else.
1.15.0¶
Seven new entities: keep the computer awake, idle time, the network's traffic, a full-screen app, dark mode and signing out, with more about the battery; and a fix for the direct connection. A stable version. On Linux and macOS the new entities are untested by hand, like the packages.
- Keep awake: a switch with which Home Assistant keeps the computer from going to sleep by itself, e.g. through a long download. Sleeping on purpose still works, and the screen may still turn off. It is off whenever HADA starts.
- Idle time: how long nobody has used the keyboard or mouse, in minutes, beside
user_active. - Network download and upload: how fast data comes in and goes out over the connection the computer routes through, in kB/s.
- The battery's details, as attributes of
battery_level: the time left, its health, its cycle count and the power going in or out, where the battery's driver tells them. - Full-screen app: on while a game, a film or a slide show fills the screen, to dim the lights by. On Linux only in an X11 session; not on macOS.
- Dark mode: a switch for the dark and the light look of Windows, GNOME, KDE and macOS.
- Sign out: a button that signs out whoever is at the computer. Off until switched on, like the power buttons.
- Fixed: on the direct connection, a reading, the list of entities, an event or the answer to a command could be lost when HADA sent it at the same moment as something else. Home Assistant ignores a message numbered lower than the one before it, the two could go out in the wrong order, and nothing sent the lost one again.
1.14.0¶
The Settings page without Unlock editing, and your own settings in the administrator window. A stable version.
- The update switches no longer need Unlock editing. Check for updates automatically and Offer test versions too on the Settings page are changed by anyone signed in, in the window opened from the tray icon, and apply at once, with no Save. They decide only what HADA asks GitHub, never what is downloaded or installed; installing still asks for administrator rights. Saving the other settings leaves them as they are.
- Your own settings can be changed in the administrator window too, the one Unlock editing opens: Start with Windows, the language, the dashboards, the time until
user_activeturns off, the browser for notifications and New window (preview). Before, they were read-only there. They stay read-only when the window runs as another account, as when a standard user typed an administrator's name and password into the prompt: changed there, they would be that account's.
1.13.1¶
Fixes, and the documentation brought up to date. A stable version.
- Fixed: on Windows, for a moment after a window or a portable copy's service had ended, HADA could still take it to be running, so that showing the window or stopping the service right then could reach nobody.
- Windows Server no longer gets the Silence notifications switch: setting the quiet hours there crashes the service that also shows notifications. The
do_not_disturbsensor stays. - Updates on Linux and macOS: the window no longer offers Download and install there, nor speaks of a portable ZIP. What is new opens the release page, and the window says what to do with the package from it. On Windows nothing changes.
- The documentation was checked against the program: wrong and stale pages are corrected, the settings of the direct connection are listed, and a new page, Linux and macOS, says what the untested packages do and how they differ from Windows. Updating a portable copy now means replacing its
appfolder too, which the page and the window say.
1.13.0¶
A switch for Do not disturb, and the quick actions' shortcuts on Linux and macOS. A stable version, which also brings everything new in the previews 1.6.0 to 1.12.0 to those who use stable versions: the new window, the same on every system, and HADA for Linux and macOS, whose packages are still untested by hand.
- Silence notifications: a switch to turn Do not disturb on and off from Home Assistant. On Windows it works as the switch in the notification settings does; on Linux it switches GNOME's notification banners off, and holds KDE's notifications back for as long as HADA runs. macOS keeps its Focus to itself, so there is no such switch there.
- The quick actions' keyboard shortcuts now work on macOS, and on Linux in an X11 session; Wayland does not let apps listen for keys meant for others, and X11 keeps Ctrl+Alt with F1 to F12 for switching to a text console. The tray icon's menu shows them next to the actions.
- Fixed: a custom sensor could be given the id of the media player, of "Restart required" or of the screen's brightness.
1.12.0 (pre-release)¶
More of what Linux and macOS lacked. Their packages are still untested by hand, which their names say. On Windows nothing changes. A pre-release, so that it gets tried before a stable version carries it.
- On Linux: whether the screens are on, and buttons to turn them off and wake them: through GNOME on Wayland and X11, through KDE (which switches them, but does not say how they are), and on other X11 desktops.
- On macOS:
- Whether the screens are on, and the buttons to turn them off and wake them. With the Mac set to ask for the password at once, turning the screens off locks it too.
- The brightness of the Mac's own screen, which Home Assistant can also set.
- Whether the microphone and the camera record. macOS does not say which app.
- Buttons that press keys, and play/pause, next and previous buttons, which press the keyboard's media keys. macOS lets HADA press keys once it is allowed in System Settings → Privacy & Security → Accessibility; until then nothing is pressed, and the log says why. A Mac's keyboard has no stop key, so there is no stop button; what plays macOS keeps to itself, so there is no playback sensor or media player.
- Not yet on macOS: Do not disturb, the pictures and buttons of notifications, and keyboard shortcuts for quick actions.
- The word that HADA goes on running comes each time the window is closed, until Don't show this again is ticked.
1.11.1 (pre-release)¶
A fix for the window, and a word the first time it is closed. A pre-release, so that it gets tried before a stable version carries it.
- Fixed: on Windows, the buttons at the top right of the window, to minimize, maximize and close it, did nothing: a click on them was taken for one on the title bar. The buttons HADA draws itself on Linux and macOS get the same fix.
- The first time the window is closed, it says that HADA goes on running in the background, and where to find its icon to open it again or to end it.
1.11.0 (pre-release)¶
HADA for macOS, a first preview: disk images for Apple silicon and Intel that nobody has tried on a Mac by hand yet, which their names say. On Windows and Linux nothing changes. A pre-release, so that it gets tried before a stable version carries it.
- HADA on macOS, untested.
HADA-1.11.0-macos-arm64-untested.dmgfor Apple silicon and…-x64-untested.dmgfor Intel, for macOS 14 Sonoma or newer. Drag HADA into Applications. The app is not signed by an Apple developer, so the first time macOS refuses to open it: allow it under System Settings → Privacy & Security → Open Anyway. Once someone has tried them, the same images come without-untested.- The same window as on Windows and Linux, and an icon in the menu bar, from which the window is opened and HADA is ended. HADA has no icon in the Dock; closing the window leaves it running in the menu bar.
- The service runs as you, started by the app and ending with it. To have it start when you sign in, turn on Start when you sign in on the Settings page; System Settings then lists HADA under Login Items.
- What arrives in Home Assistant: CPU load, memory, battery and charger, last boot, the signed-in user, whether the screen is locked, the disk's usage, the IP address and the Wi-Fi network, the lid, the GPU load, connected USB devices for custom sensors, whether you are active, an external display, the app in front, the volume, the audio device and the microphone's mute; buttons to lock the screen, sleep, shut down and restart (off until switched on). Volume, mute and the microphone's mute can be set from Home Assistant.
- The Wi-Fi network's name is shown only to apps that may know the location; without it, the sensor says
connected. - Quick actions and the Home Assistant dashboard, which opens in the browser, are in the menu of the menu bar icon. Custom buttons can start a program, and custom sensors run their commands with
sh, as you. - Notifications from Home Assistant appear in Notification Center, with their title and text. Their pictures and buttons do not, yet.
- The first time Home Assistant shuts the Mac down or restarts it, macOS asks whether HADA may control the login window.
- Not yet on macOS: whether the camera or the microphone records, media, buttons that press keys, Do not disturb, the screen's brightness, turning the display off and on, and keyboard shortcuts for quick actions. A Mac cannot hibernate on demand, so it has no such button.
- Fixed: on Windows, a signal between HADA's own processes could, for a moment after it was closed, still be reached.
1.10.0 (pre-release)¶
Most of what HADA on Linux still lacked. The packages are still untested by hand, which their names say. On Windows nothing changes. A pre-release, so that it gets tried before a stable version carries it.
- New on Linux:
- Network: the IP address of the connection in use, and the Wi-Fi network with its signal strength.
- The lid, the screens and the brightness: whether the lid is open and whether an external display is connected. Also the brightness of a laptop's screen, which Home Assistant can set as well.
- Do not disturb on GNOME and KDE, and the GPU load of AMD cards, and of NVIDIA's through their driver.
- The active window and its program, in an X11 session. Wayland does not tell apps which window is in front.
- Media: what plays in any player that the desktop's own media controls show, and the media player with its buttons, so Home Assistant can play, pause, skip, stop and set the volume.
- The audio device in use, and whether the microphone is muted.
- Quick actions in the menu of the tray icon, and the Home Assistant dashboard, which opens in the browser. Set the dashboard up on the Settings page.
- Custom buttons that start a program or press keys. Keys are pressed in an X11 session only, as Wayland does not let apps type into others. Custom sensors of a connected USB device. Commands of custom sensors and buttons run with
sh, as you. - Not yet on Linux: the display's sensor and the buttons that turn it off and on, and keyboard shortcuts for quick actions.
- The window says what Linux does where it differs from Windows: on the Entities page, on the Custom entities page and in the dashboard's setting.
1.9.0 (pre-release)¶
HADA for Linux, a first preview: packages for x64 and arm64 that nobody has tried on Linux by hand yet, which their names say. And a fix for all systems. A pre-release, so that it gets tried before a stable version carries it.
- HADA on Linux, untested. An AppImage to run as it is, a .deb for Debian and Ubuntu, an .rpm for Fedora and openSUSE, each for x64 and arm64:
HADA-1.9.0-linux-x64-untested.AppImageand so on. They were built and checked by machines only; once someone has tried them, the same packages come without-untested. GNOME and KDE are both meant.- The same window as on Windows, and an icon in the system tray, from which the window is opened and HADA is ended. Closing the window leaves HADA running in the tray. On GNOME the icon needs the AppIndicator extension, which Ubuntu has.
- The service runs as you, started by the app when you sign in and ending when you sign out: turn on Start when you sign in on the Settings page. Your settings are your own; nothing needs unlocking. Saved passwords and tokens are sealed with a key only you can read.
- What arrives in Home Assistant: CPU load, memory, battery and charger, last boot, the signed-in user, whether the session is locked, whether a restart is due, the usage of each disk (
disk_root_usage,disk_home_usage), whether you are active, whether the camera or the microphone records and for which app, the volume, and buttons to lock the screen, sleep, hibernate, shut down and restart (off until switched on). Volume, mute and the microphone's mute can be set from Home Assistant. - Notifications from Home Assistant appear as the desktop's own, with a picture and buttons; a pressed button goes back to Home Assistant as on Windows.
- Not yet on Linux: the active window, media, the dashboard window, quick actions and their shortcuts, the network and Wi-Fi, the display and the lid, the external display, Do not disturb, the screen's brightness, the GPU. They come with later versions.
- Fixed: right after connecting directly to Home Assistant, a sensor could be registered as an entity twice.
1.8.0 (pre-release)¶
The new window takes over: it has every page now, and the tray icon opens it. A pre-release, so that it gets tried before a stable version carries it.
- The tray icon opens the new window, and so do HADA in the Start menu and starting HADA again. As before, there is one window: started again, the open one comes to the front.
- Every page is in the new window. Besides the Overview and Connections:
- Entities, each with its switch, and a note when the connections you use do not carry all of them.
- Custom entities: sensors, buttons and quick actions of your own.
- Settings: updates, and what is yours alone, such as the language and starting with Windows.
- Logs: the service's messages by level, to copy or clear, following the newest.
- Back to the previous window with New window (preview) on the Settings page, for as long as both come with HADA. The new window stays at hand as HADA (new window, preview) in the Start menu.
- Unlock editing opens the window as administrator at the page you were on.
- Fixed: Start with Windows, turned on in the new window of a portable copy, registered the window instead of HADA itself to start when you sign in. Turn it off and on again if you turned it on in 1.7.0.
1.7.0 (pre-release)¶
A first look at the new HADA window, which is to be the same on Windows, macOS and Linux. It comes beside the window you know, which stays as it is and is what the tray icon opens. A pre-release, so that it gets tried before a stable version carries it.
- The new window, a preview. Open it with HADA (new window, preview) in the Start menu, or New window (preview).cmd in a portable copy. It has the Overview and Connections pages so far; the other pages say they are still to come, and are in the window you know.
- The Overview has a card for each way of connecting that you use, MQTT or directly, with a row for each server and its state. A notice says when a connection needs attention; close it, and it comes back with the next problem. Manage leads to the Connections page, and a server's row to that server.
- Connections lists your servers by the way they connect. A server opens with its state and all of its settings, to test, change or remove. Add a connection takes three steps: the way to connect, with what each gives and needs, the address and signing in, and a check that saves it and says what the connection does now.
- The sidebar can be folded to its icons, and stays so.
- On Windows it looks like a Windows 11 app, in the light or dark colours and the accent colour you chose.
- Both windows now say in your language, before saving, that two servers are the same broker or the same Home Assistant as the same device, which would make them throw each other off. Before, saving was refused with an English message from the service.
- Stopping a portable copy closes the new window too.
1.6.0 (pre-release)¶
Little to see: this version changes how HADA is built inside. The settings window, the tray app and the service work as before. A pre-release, so that it gets tried before a stable version carries the change.
- Fixed: the service of a portable copy, told to stop while it was still starting, ended with an error instead of stopping.
- Fixed: when HADA stopped right after its first reading of a sensor, a Home Assistant connected to directly could be sent that sensor once more as a new entity, only to show it as unavailable.
1.5.1¶
- Fixed: Sign in through Home Assistant opened a window of files instead of the browser when it was chosen in the window unlocked for editing, which is where it is chosen in an installed HADA. The browser is now sent to Home Assistant by way of an address on the computer itself, which works however the browser is opened.
- While waiting for the sign-in, the window shows that address, to open by hand should no browser come up.
1.5.0¶
More for a Home Assistant connected to directly: the computer as a media player, signing in instead of pasting a token, a local address for the networks you call home, and a refusal to send the token unencrypted over the internet. The app now says which of your connections carries what. A stable version, which also brings everything new in 1.3.0 and 1.4.0 to those who use stable versions. The media player needs version 0.4.0 of the HADA integration.
- No unencrypted connection over the internet. A Home Assistant connected to directly at an
http://address is refused when the address is a public one, as the access token could be read on the way; the Overview page says so. Addresses of the computer's own network work as before, andhttps://ones always do. The refusal can be lifted per server on the Connections page, which now also says under the address whether the connection is encrypted. See Security. - Signing in through Home Assistant. Instead of making a long-lived token and pasting it, choose Sign in through Home Assistant on the Connections page: the browser opens Home Assistant's own sign-in page, and HADA keeps what comes back. It can be withdrawn in your Home Assistant profile, under Refresh tokens. A pasted token works as before. See WebSocket engine.
- Another address on your home network. A Home Assistant connected to directly can have a second address, used while the computer is on the networks you name as home: the short way, without going out to the internet and back. Anywhere else the main address is used and the local one is not tried at all. The Connections page lists the networks the computer is on, to add with a click. See WebSocket engine.
- A dashboard for every Home Assistant. Each Home Assistant connected to directly has a dashboard in the tray icon's menu by itself, at the connection's address; on the Settings page each can be switched off or given an address of your own. The address typed there before still works, as Another address. With several dashboards the menu lists them by name, and the one window shows whichever is chosen. See The dashboard window.
- The computer as a media player. Through the HADA integration the computer is a media player in Home Assistant: what is playing, play, pause, next, previous, stop, volume and mute in one entity. It is a new entity on the Entities page; the media buttons, the volume slider and the playback sensor stay as they are, and are what MQTT and a connection without the integration have. Needs the HADA integration from its next version on. See Controls.
- What works through which connection, in one table: Which connection to choose.
- Two more entities.
restart_requiredis on while Windows waits for a restart to finish installing updates.screen_brightnessshows the brightness of a laptop's screen and lets Home Assistant set it. Both work through MQTT and through the HADA integration; a connection without the integration shows the brightness without the slider. - The Entities page says what does not arrive. A connection that carries less than the list offers is named there with what is missing: a direct connection without the HADA integration has no buttons, switches or sliders to click in Home Assistant, for instance.
- Quick actions with any user's token. What happens on the computer reached Home Assistant only with an administrator's token, unless the HADA integration was used. With Notifications on, or sensors sent as entities of the device, it now arrives with the token of an ordinary user too.
- Readings sent together. What several sensors report at the same moment reaches a Home Assistant connected to directly in one message, through the HADA integration and as entities of the device alike, instead of one message each; and only the newest reading of a sensor is sent when Home Assistant is slow to answer. Nothing to set up.
- An integration that is behind says so. When the HADA integration in Home Assistant is older than HADA and leaves entities out for not knowing their kind, the Overview page says that it wants updating.
- Fixed: a button pressed in Home Assistant in the very moment the computer connected to the HADA integration could be lost.
1.4.0 (pre-release)¶
Home Assistant without a broker: notifications as on a phone, and the computer as a device with entities of its own, through Home Assistant's mobile_app integration or through the new HADA integration. A pre-release, so that it gets tried before a stable version carries it. MQTT works as before.
- Help with choosing a connection. The Connections page says in plain words what MQTT, a direct connection and a direct connection with the HADA integration each need and give, and so does a new page of the documentation, Which connection to choose.
- Entities through the HADA integration. A third way for the sensors of a Home Assistant connected to directly: the HADA integration, installed in Home Assistant with HACS, makes the computer a device whose entities follow the computer's, are removed when it no longer has them, and are unavailable the moment it goes away. Its buttons, switches and numbers are real ones, to press and set in Home Assistant as with MQTT, without a broker. Notifications have the action
hada.notify, with all a phone's notification may carry, and quick actions areevententities. See WebSocket engine. - Sensors as real entities without MQTT. A Home Assistant connected to through the WebSocket API can get the sensors as entities of a device, with a unique ID: they can be renamed and managed in Home Assistant, survive its restarts, and need no administrator's token. New connections do this; existing ones keep writing states until changed on the Connections page, as the entity IDs differ. See WebSocket engine.
- Notifications as on a phone. With Notifications switched on for a Home Assistant connected to through the WebSocket API, the computer registers with the
mobile_appintegration and Home Assistant has the actionnotify.mobile_app_…, with a title, a picture and buttons; a pressed button firesmobile_app_notification_action. Works next to MQTT, with Entities set to Off for that connection, and with the token of an ordinary user. See Notifications. - More in a notification, through
mobile_appand through MQTT alike:tagto replace a notification andclear_notificationto take it back, an address opened when it or one of its buttons is pressed,stickyandsilent. Throughmobile_app, a picture may be one that needs signing in at Home Assistant, such as a camera's. Which browser the addresses open in can be chosen on the Settings page. See Notifications. - Several Home Assistants through the WebSocket API: as with MQTT servers, up to eight, each with its own name, address and access token, connected at the same time. Each has its own card on the Overview page. The one Home Assistant set up before stays as the first server. See WebSocket engine.
- Stopping a portable copy, with Exit in the icon's menu or with Stop HADA.cmd, closes its windows too. Before, a window left open kept the program's files in use, and the folder could not be replaced or deleted.
1.3.0 (pre-release)¶
Nothing new to see: this version changes what HADA is built on, and is a pre-release so that it gets tried before a stable version carries it.
- HADA runs on .NET 10, the long-term release, instead of .NET 9, whose support ends in November 2026. The installers and the portable version bring it along, as before.
- What is specific to Windows is kept apart from the rest, as groundwork for macOS and Linux versions. Those do not exist yet.
1.2.0¶
A stable version, which also brings everything new in 1.1.0 to those who use stable versions.
- Several Home Assistants at once: any number of MQTT servers, up to eight, each with a name of its own, connected at the same time. Each has its own card on the Overview page; the buttons of a notification answer the Home Assistant that sent it.
- Broker names that stand for several addresses, as
.localnames do, are tried address by address, IPv4 first, and the one that answered is remembered. The log says what a name stands for, and why a name could not be found. - A server that cannot be reached is mentioned in the log once, not at every retry.
- Portable version: a ZIP to unpack and run, without installing and without administrator rights. It keeps everything in its own folder and can run next to an installed HADA.
HADA.Tray.exe --exittells the running tray app to exit.- Security: the service checks who owns
%ProgramData%\HADAbefore reading anything from it. A folder someone other than an administrator made is set aside instead of trusted. See Security.
Settings saved by earlier versions are taken over: their one MQTT server becomes the first of the list, with its password. The tray app and the service of 1.2.0 work only with each other.
1.1.0 (pre-release)¶
- Quick actions: entries in the tray icon's menu, optionally with a global keyboard shortcut, that show up in Home Assistant as triggers of the device.
- Notifications with a picture and buttons. A pressed button is reported back to Home Assistant.
- Button: press keys, a custom button that presses a key combination on the desktop.
- Dashboard window: a small window showing a Home Assistant address, opened from the tray icon's menu.
gpu_loadsensor, and the adapter'smac_addressas an attribute ofip_address.
1.0.0¶
The first stable version. It is 0.5.0 with one change:
- Test versions (pre-releases) are no longer offered as updates unless Offer test versions too is turned on. An installation that saved its settings with 0.5.0 keeps what it had.
From here on, settings and MQTT topics stay compatible from one stable version to the next.
0.5.0¶
- Settings page: the installed version, what the last update check found and a Check now button; switches for checking automatically and for counting test versions; and personal settings that need no administrator rights: start with Windows, language, and the idle time after which
user_activeturns off. - The status cards on the Overview page open the page where what they show is set up.
- Whether the daily update check runs is a setting of its own; it used to follow the
update_availableentity's switch.
0.4.1¶
- Download and install an update from the window: the installer is downloaded, compared with its published checksum and started.
0.4.0¶
- Control from Home Assistant: volume and mute, media keys, display off and wake, sleep, hibernate, shut down and restart (off until switched on), and notifications.
- Custom buttons that run a PowerShell command or start a program.
- New sensors: signed-in user, IP address, Wi-Fi network, disk usage, default audio device, media playback, do not disturb, update available.
- With several users signed in, only the one at the computer is reported.
- A daily check for a newer version.
- MIT license.
0.3.0¶
- Custom sensor type Device is connected, e.g. for a USB-C dock.
external_displaybinary sensor.
0.2.2¶
- The window runs as a process of its own and is drawn in software, which brought the tray app from about 335 MB after opening the window down to about 20 MB.
0.2.1¶
- Start with Windows switch.
- The service recovers when another copy of it held the pipe or shared its MQTT client ID.
0.2.0¶
- Custom sensors: fixed text, program running, PowerShell command.
- More built-in sensors: memory, battery, display, lid, session lock, last boot, user activity, microphone and camera in use, microphone muted.
- MSI installers for x64 and ARM64.
- The window follows the dark theme; entities turn unavailable when their source is away.
0.1.0¶
- First preview: the service, the tray app with its settings window, the MQTT and WebSocket engines, per-entity switches.