HASS.Agent is a Windows-based client application for Home Assistant, developed in .NET 4.8.

Click here to download the latest installer, or click here to download the latest zip package.

Need help? Visit the dedicated HA forum thread or join on Discord.

Developing this tool takes up quite a bit of time. It's completely free, and it'll stay that way without restrictions.
However, like most developers, I run on caffeïne - so a cup of coffee is always very much appreciated!

• Why?
• Functionality
• Screenshots
• Installation
• Configuration
• Usage
• Updating
• Wishlist
• Error Reporting
• Usage Summary
• Credits and Licensing

The main reason I built this is that I wanted to receive notifications, including images, on my PC and to quickly perform actions (i.e. to toggle a lamp). There weren't any software-based solutions for this, so I set out to build one myself.

That's also the premise of this project; it's built to solve problems I encountered (or perhaps I should use the word "nuisances"), so it may not work for you. If that's the case, feel free to open a ticket so we can discuss!

Summary of the core functions:

• Notifications: receive notifications, show them using Windows builtin toast popups, and optionally attach images.

  • This requires the installation of the HASS.Agent Notifier integration.

• Quick Actions: use a keyboard shortcut to quickly pull up a command interface, through which you can control Home Assistant entities - or, assign a keyboard shortcut to individual Quick Actions for even faster triggering

• Commands: control your PC (or other Windows based device) through Home Assistant using custom- or built-in commands.

• Sensors: send your PC's sensors to Home Assistant to monitor cpu, mem, webcam usage, wmi- and performance counter data, etc.

• All entities are dynamically acquired from your Home Assistant instance.

• Commands and sensors are automatically added to your Home Assistant instance.

Notification examples:

This is the Quick Action window you'll see when using the hotkey. This window automatically resizes to the amount of buttons you've added:

You can easily configure a new Quick Action, HASS.Agent will fetch your entities for you:

The sensors configuration screen looks like this:

Adding a new sensor is just as easy, with an information panel on the right:

You have the option to download an installer or a .zip package - they both contain the same, and the installer doesn't do any configuring. It's just easier, especially for updates.

HASS.Agent uses an entry in your user account's registry to launch on login. You'll be offered to enable this during onboarding, but you can always disable/enable using the Configuration window.

To use notifications, you'll need to install the HASS.Agent Notifier integration. This can be done through HACS or manually.

You'll also need to open the configured port in the firewall of the receiving PC (default 5115). During the onboarding process (or when using the Configuration window), HASS.Agent will offer to do it for you. If you want to do so manually, you can run this command in an elevated prompt:

netsh advfirewall firewall add rule name="HASS.Agent Notifier" dir=in action=allow protocol=TCP localport=5115

Optionally change 5115.

The port has to be reserved in order for HASS.Agent to use it. Again, this'll be done for you by the onboarding process (or when using the Configuration window), but if you want to do it manually, run this command in an elevated prompt:

netsh http add urlacl url=https://+:5115/ user=%USERDOMAIN%\%USERNAME%

Optionally change 5115.

When you first launch HASS.Agent, you'll be taken to the onboarding process. This will guide you through configuring step-by-step, and HASS.Agent will offer to perform some tasks for you.

If you don't want this, or if you want to change something later on, you can use the configuration screen:

Configuring HASS.Agent is split into different pages:

To use quick actions, you have to configure your instance's API. Normally the default URI should work, unless you've changed the port or mdns name. You can get a long-lived API token following this doc.

Make sure the integration has been installed and configured in Home Assistant, and actually works (I used a test automation). In the configuration screen, check the 'accept notifications' box and change the default port if needed.

After changing the port (or enabling/disabling), HASS.Agent will perform the port binding and create/modify the firewall rule as soon as you save your changes. This requires elevation, so you'll be shown an UAC prompt.

Enter your MQTT broker configuration. This is only required if you want to use commands (triggered from Home Assistant) or sensors (sent from your PC).

Gives the option to enable/disable running HASS.Agent when you login.

This is optional, and can be used to pull up the Quick Actions window at any time.

If you want, HASS.Agent can check for updates in the background. This works by checking the latest release on GitHub. When a new release is found, you'll be notified and given the chance to open the release page.

Enables you to manage how local storage is handled.

HASS.Agent provides extended logging options (see Error Reporting), you can easily manage them from this page.

Remember you need to restart HASS.Agent before they become active.

HASS.Agent resides in the system tray. Make sure it's always visible and not hidden in the overflow, otherwise notifications may not get shown. As a tip, you could drag the icon right next to your clock.

You can double-click to open the Home screen:

From here, you can easily use & configure the various parts of HASS.Agent:

Shows the various application configuration options (as discussed above).

Manage your quick action buttons. Use the 'add new' button to create your first action. All entities are dynamically acquired from your Home Aassistant instance. If they won't show up, make sure you've configured 'HASS api' in the configuration screen. Use the 'preview' button to check if it's working for you.

Manage which sensors you want to publish to your Home Assistant instance. There are some ready-to-use sensors available, but you can also use your own WMI query. This requires MQTT to be configured.

Most sensors are single value, but some are multi-value sensors. These sensors are configured as one entity, but will create multiple entities in Home Assistant. For instance, the storage multi-value sensor will create label, total size (MB), available space (MB), used space (MB) and file system entities for all present non-removable disks. When adding a new sensor, the information panel on the right will tell you if the selected type is multi-value.

Note: WMI can be a pain, and also make sure you don't update your queries too often. Keep an eye on your CPU load.

Manage which commands should be accepted from your Home Assistant instance. Aside from the builtin commands, you can use your own custom command (you can test your command by typing it into a console), or a key command which will emulate key presses. This requires MQTT to be configured.

Example configuration of a shutdown command in Home Assistant, used in combination with wake-on-lan:

- platform: wake_on_lan
  name: "TEST_W10_x64_01"
  mac: "00-00-00-00-00-00"
  host: 10.0.0.5
  broadcast_address: 10.0.0.255
  turn_off:
    service: switch.turn_on
    data:
      entity_id: switch.test_w10_x64_01_cmd_shutdown

Apart from the automatic update checker, you can check for new updates from the main window or rightclicking the systray icon and selecting 'check for updates'. If there's an update, you will be offered to download the .zip package from GitHub.

If you're using the installer, it'll launch HASS.Agent for you when it's done. But if you've updated manually, just doubleclick HASS.Agent.exe.

List of things I want to add somewhere down the road (basically a personal to-do notepad):

• Notifications: ability to add commands (i.e. 'yes/no' or 'activate alarm')
• Notifications: add 'critical' type to attract more attention
• Notifications: history window
• Notifications: use our own method of showing instead of Windows toast, for added versatility
• Notifications: show a videostream for x seconds with size y (small/normal/fullscreen) on position z (bottom right, center screen, etc)
• Quick Actions: show current state in window
• Quick Actions: ability to change button size (small/medium/large)
• Quick Actions: ability to define custom mdi icons, and/or fetch icon from Home Assistant
• Quick Actions: add pages as tabs instead of one form, i.e. one tab with 'lights', one tab with 'switches'
• Sensors: implement library plugin system for more powerful custom sensors
• Commands: command to open URL on default browser
• Updater: give HASS.Agent the option to update itself 100% automatically
• General: a built-in way to show a Home Assistant dashboard
• General: switch to being a 'native app' so mqtt/integrations are no longer needed

If you have any other wishes, feel free to submit a ticket.

This type of application is prone to errors (due to fetching data from WMI, systemwide keybindings, etc). To manage exceptions, I use the excellent Coderr platform. However, this does mean that exception information will be sent to their servers. This is disabled by default.

If you'd like to help out, please enable exception reporting from the configuration window. No telemetry or periodic info will get sent.

If you're experiencing bugs, please enable extended logging from the configuration window. Restart HASS.Agent and wait for the bug to occur. Afterwards, please attach the relevant logfile from the Logs subfolder in your ticket.

Remember to disable afterwards to prevent your logs from growing too large. Note that if you only enable this option, nothing will get sent to Coderr.

Checklist to start using HASS.Agent:

• Install and configure HASS.Agent Notifier integration if you want notifications
• Download & run the latest release's installer
• HASS.Agent will launch and show you the onboarding process
• Configure the parts you'll be using
• HASS.Agent will restart to activate your configuration
• Start adding Quick Actions, commands & sensors!

Stuck? Create a ticket or join on Discord.

First: thanks to the entire team that's developing Home Assistant - such an amazing platform!

Second: I learned a lot from sleevezipper's HASS Workstation Service. Thank you for sharing your code & hard work!

And a big thank you to all other packages:

HADotNet, CoreAudio, Grapevine, HotkeyListener, LibreHardwareMonitor, Microsoft.Toolkit.Uwp.Notifications, MQTTnet, Newtonsoft.Json, Serilog, Syncfusion, TaskScheduler, Octokit, CliWrap and Coderr.

Please consult their individual licensing if you plan to use any of their code.

HASS.Agent and HASS.Agent Notifier are released under the MIT license.