Events and topics

The same wires, from the integration's side; the app's side is under Connection.

MQTT topics

Published by the Windows client, consumed by this integration:

hass.agent/devices/{serialNumber}                # discovery + capabilities
hass.agent/system/{serialNumber}/state           # Windows service status
hass.agent/sensors/{serialNumber}/state          # sensor values
hass.agent/update/{serialNumber}/state           # app update state
hass.agent/media_player/{serialNumber}/state     # media player state
hass.agent/notifications/{serialNumber}/actions  # notification action events
hass.agent/hotkeys/{serialNumber}/pressed        # hotkey presses (client 10.9.0+)

Published by this integration (commands):

hass.agent/notifications/{serialNumber}          # outgoing notifications
hass.agent/media_player/{serialNumber}/cmd       # media player commands
hass.agent/buttons/{serialNumber}/cmd            # system command buttons
hass.agent/system/{serialNumber}/cmd             # service-routed commands

Home Assistant events

When using the HA API (WebSocket) transport, the Windows client fires events into Home Assistant's event bus instead of MQTT topics (see HA API (WebSocket) above). The integration also sends commands back to the client through the hass_agent_command event:

{
  "serial_number": "device-serial-number",
  "command_type": "button_command",
  "payload": {
    "command": "restart",
    "force": true,
    "time": 30
  }
}

A hotkey pressed on the PC (client 10.9.0+) reaches the device's Hotkeys event entity on either transport, and the entity fires hass_agent_hotkey_pressed on the event bus with the hotkey's name in hotkey.