2.2.0/2.1.2: Notifications and Shutdown not work

[GerdRuetten]

Hello everyone,

I switched to the forks of HASS-Agent and HASS-Agent Integration.

Since then, notifications no longer work and I also can't shutdown the PC.

Absolutely nothing happens.

No error message.
No entry in the log.

It seems as if no MQTT data is being sent at all during any action.

My versions:

HASS-Agent: 2.2.0
HASS-Integration: 2.1.2
HA version: 2026.2.2 (HA OS)
Windows: Win 11 Home, 25H2

The integration was installed via HACS.

In MQTT i can see:

The Test-Notification under HASS-Agent / Windows works

I using mosquitto outside from HomeAssistant.

In the mqtt-Log i can see:

1771111608: New client connected from 10.24.2.4:33014 as mqttjs_f9547860 (p2, c1, k60, u'uptime-kuma').
1771111608: Client mqttjs_f9547860 disconnected.
1771111618: Client d7b504c8 disconnected.
1771111618: New connection from 10.24.10.10:35563 on port 1883.
1771111618: New client connected from 10.24.10.10:35563 as 34ba2799 (p2, c1, k15, u'hass-agent').
1771111626: Client 41e84b17 disconnected.
1771111631: New connection from 10.24.10.10:36743 on port 1883.
1771111631: New client connected from 10.24.10.10:36743 as 41e84b17 (p2, c1, k15, u'hass-agent').

I would appreciate support.

Thank you in advance!

Best regards,
Gerd

[amadeo-alex]

Just to confirm we have a mqtt send/receive issue, if you enable debug logs, there are no mentions of notification/shutdown after you do the action on HA side?

In the mqtt logs, does the connected/disconnected logs repeat constantly? If you've migrated there is a chance both original and fork use the same clientid for connection and are "fighting" for it.

[GerdRuetten]

if you enable debug logs, there are no mentions of notification/shutdown after you do the action on HA side?

No, there are no mentions
Here the debug log fro Hass-Agent (Windows) after fresh start and after send notification

2026-02-16 20:17:13.085 +01:00 [INF] [MAIN] HASS.Agent version: 2.2.0
2026-02-16 20:17:13.091 +01:00 [INF] [MAIN] Extended logging enabled
2026-02-16 20:17:13.096 +01:00 [INF] [SETTINGS] Config storage path: C:\Users\gerdr\AppData\Local\HASS.Agent\Client\config
2026-02-16 20:17:13.204 +01:00 [INF] [SETTINGS] Configuration loaded
2026-02-16 20:17:13.208 +01:00 [INF] [LOCALIZATION] Selected UI culture: [en] English
2026-02-16 20:17:13.520 +01:00 [DBG] [RADIOMGR] Initialization started
2026-02-16 20:17:13.580 +01:00 [INF] [RADIOMGR] Radio management permission granted
2026-02-16 20:17:13.580 +01:00 [DBG] [RADIOMGR] Enumerating proximity/NFC devices
2026-02-16 20:17:13.609 +01:00 [INF] [RADIOMGR] Ready
2026-02-16 20:17:15.661 +01:00 [INF] [INTERNALSENSORS] Ready
2026-02-16 20:17:15.909 +01:00 [INF] [VIRTDESKT] Virtual Desktop Manager initialized
2026-02-16 20:17:15.910 +01:00 [DBG] [AUDIOMGR] initializing
2026-02-16 20:17:15.932 +01:00 [INF] [AUDIOMGR] initialized
2026-02-16 20:17:15.960 +01:00 [INF] [SETTINGS_QUICKACTIONS] Loaded 0 entities
2026-02-16 20:17:15.991 +01:00 [INF] [SETTINGS_COMMANDS] Loaded 1 entities
2026-02-16 20:17:15.999 +01:00 [INF] [SETTINGS_SENSORS] Loaded 0 entities
2026-02-16 20:17:16.171 +01:00 [INF] [HOTKEY] Completed bind for global quickaction hotkey
2026-02-16 20:17:16.171 +01:00 [INF] [LOCALAPI] Disabled
2026-02-16 20:17:16.173 +01:00 [INF] [MQTT] Identifying as device: PC-WOHNZIMMER
2026-02-16 20:17:16.185 +01:00 [INF] [MQTT] Connecting ..
2026-02-16 20:17:16.194 +01:00 [INF] [SERVICE] Local install path: C:\Program Files\HASS.Agent Satellite Service\Service\
2026-02-16 20:17:16.252 +01:00 [INF] [MEDIA] Ready
2026-02-16 20:17:16.276 +01:00 [INF] [MQTT] Connected
2026-02-16 20:17:16.278 +01:00 [WRN] [MEDIA] No MediaSession active
2026-02-16 20:17:16.284 +01:00 [INF] [HASS_API] Home Assistant version: 2026.2.2
2026-02-16 20:17:17.992 +01:00 [INF] [HASS_API] System connected with http://10.24.2.1:8123/
2026-02-16 20:17:18.054 +01:00 [INF] [NOTIFIER] Ready
2026-02-16 20:17:18.190 +01:00 [INF] [MQTT] Initial registration completed

Here the log from mosquitto after start HASS-Agent (Windows).
I give a new Client-ID
10.24.10.10 is the correct IP from the Windows PC

1771268806: New connection from 10.24.10.10:26455 on port 1883.
1771268806: New client connected from 10.24.10.10:26455 as hass-agent-1 (p2, c1, k15, u'hass-agent').

This is the yaml-Code from Homeassistant to send the notification

action: notify.pc_wohnzimmer
data:
  message: Das ist eine Test-Message
  title: Titel für Test-Message

In the HomeAssistant-Log i can see nothing.

And this, what i can see in the mqtt-explorer

[amadeo-alex]

Looks like the image got borked with the quote :D

[GerdRuetten]

Looks like the image got borked with the quote :D

fixed

[amadeo-alex]

Yeah, that's almost certainly something off with mqtt.
After calling that service, or "action" how it's called now we should see something like this on your side (the "notifications" part):

Which is missing on your screenshot. Now we enter the stupid questions phase :D
Are you certain both HA and HASS.Agent are talking to the same MQTT broker?

[GerdRuetten]

Yes they talking to the same MQTT-Broker ... but ...

I using acl on mosquitto-Side.

The homeassitant-user from mosquitto looks like:

# Home Assistant
user homeassistant
topic read #
topic write homeassistant/#
topic write zigbee2mqtt/#
topic write shellies/#

and that's the problem .... the user must have readwrite to hass-agent/# ... correct?

Is this acl for the hass-agent user correct?

# hass-agent
user hass-agent
topic readwrite homeassistant/#
topic readwrite hass.agent/#
topic read $SYS/#

[amadeo-alex]

I'll be honest with you, thanks to that message of yours I've just learned the mosquitto has ACL. Makes sense actually, but I never actually though of it.

My educated guess is that HA is missing write permissions for "hass.agent/#" - i.e. you call a service on HA side and no message is seen on MQTT broker.