Notifications not appearing in Windows 11
Just installed on my Win11 machine, just wanted to have a notification sent to my desktop. I see my desktop in HA as "notify.desktop", but cant get even the test notification to appear in the windows app.
I went through the documentation and I believe I am setup correctly. Suggestion to try or need more info?
troubleshooting section might need some frequent-problems section, as I feel that might be what I have https://www.hass-agent.io/latest/getting-help/
...
getting a lot of MQTT errors in HA logs...
eg.
this is just one of many. literally every sensor or command has this same error message attached to it in the logs. I was able to find a post on the community site that references this. Hopefully this information posted helps, thanks for keeping this going!
https://community.home-assistant.io/t/psa-mqtt-name-changes-in-2023-8/598099...
2024-01-25 03:15:29.082 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'icon': 'mdi:window-maximize', 'unique_id': '9437ba0c-a2df-4f1a-9761-76ee4169028b', 'object_id': 'BRYAN-PC_activewindow', 'availability_topic': 'homeassistant/sensor/BRYAN-PC/availability', 'device': {'identifiers': ['hass.agent-BRYAN-PC'], 'manufacturer': 'HASS.Agent Team', 'model': 'Microsoft Windows NT 10.0.22631.0', 'name': 'BRYAN-PC', 'sw_version': '2.0.1', 'connections': []}, 'name': 'BRYAN-PC_activewindow', 'state_topic': 'homeassistant/sensor/BRYAN-PC/BRYAN-PC_activewindow/state', 'force_update': False, 'enabled_by_default': True, 'availability_mode': 'latest', 'payload_not_available': 'offline', 'payload_available': 'online', 'qos': 0, 'encoding': 'utf-8'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_activewindow'
2024-01-25 03:15:29.082 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'icon': 'mdi:window-maximize', 'unique_id': '9437ba0c-a2df-4f1a-9761-76ee4169028b', 'object_id': 'BRYAN-PC_activewindow', 'availability_topic': 'homeassistant/sensor/BRYAN-PC/availability', 'device': {'identifiers': ['hass.agent-BRYAN-PC'], 'manufacturer': 'HASS.Agent Team', 'model': 'Microsoft Windows NT 10.0.22631.0', 'name': 'BRYAN-PC', 'sw_version': '2.0.1', 'connections': []}, 'name': 'BRYAN-PC_activewindow', 'state_topic': 'homeassistant/sensor/BRYAN-PC/BRYAN-PC_activewindow/state', 'force_update': False, 'enabled_by_default': True, 'availability_mode': 'latest', 'payload_not_available': 'offline', 'payload_available': 'online', 'qos': 0, 'encoding': 'utf-8'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_activewindow'
Solution:
Cjheck out the server guide for a help page on this.
Also available here: #entity-names...
Sensors become unavailable after a while but all green status in HASS.agent
Hey,
running 2.0.1 and this happens where it says its connected to mqtt and HA but sensors are unavailable. Have the last logs if needed.
Restart of HASS.Agent, fixes it. ...
Powershell command not running
I have several audio outputs (namely speakers, headphones and home cinema) and used HA to switch between them. This used to work yesterday (old HASS.Agent, switching using index) and is not working today (using ids). I copied the command from HASS.Agent and ran it directly in powershell and the output changed, however nothing happens when I press the button associated with the command in HA (no logs are written to the best of my ability to find them).
The command in question is:
Set-AudioDevice -id "{0.0.0.00000000}.{9a3730ee-fb93-41c1-bd3b-d255652cf07b}"
Is there something I'm missing or is the powershell command really not running at all?...
Hass agent not connecting to mqtt
i have tried to install hass agent for the first time and it is refusing to connect with mqtt the most notible things i could find in the log at a glance are
please escuse me as im new to all this i belive i have set up mqtt correctly? as i have got it running for frigate i got it running for a bit but after a home assistant restart it refuses to connect again
here is my log i am unsure whats what or any specifics so ill throw the whole thing here any help is appreciated...
Solution:
I would restart all network equipment. Had issues with my mesh where it lost connection from tiem to time.
Adding image from Nest Doorbell to Notification
Hey folks,
Thanks for running this Discord, help for dummies like me is always appreciated!
I've got HASS Agent all setup, and I'm able to send notifications when my doorbell goes to my Windows desktop. All that works beautifully. I like the fancy option of adding an image and I've been trying to get it working without muck luck and I'm wondering if someone can point me in the right direction. ...
Notification with images?
Hi. How do we get images in notifications?
Solution:
Okay so to add an image all you need to do is add an image property to the notification followed by the url.
Also, whenever you are posting code, make sure to paste it between 3 backticks at the top and bottom, like this:
```...
Info on Integration
so, one thing is unclear to me, is it necessary to add the new fork repository to hacs or is it still """"dangerous"""" use the new one and should I keep the old one?
Doesn't open
i download the new version from "https://www.hass-agent.io/latest/getting-started/installation/" but it doesnt open the istaller. i tried it as admin and also closed the old version.
Solution:
can you launch cmd/powershell as administrator and then run
HASS.Agent.Installer.exe /LOG="install.log"...
Can't find "SetAudioOutput" command
As mentioned in this post https://discord.com/channels/1173033284519862392/1173033285845266515/1195371878450216980 you can change your audio output, but I cant find the command. I presume it should be available in the command section. The audio sensor is working. I am running version 2.0.1. Does anyone know what is going on?
Solution:
Fixed in 2.0.2
backing up stable before switching to beta
Hey, If I want to backup in case I want to switch back to stable is it enough to get the folder, or should I backup the registry as well?
Solution:
Just to make sure I'm understanding correctly, so since I just need my commands&sensors the config should be all I need? I have the actual config e.g ha api, mqtt details & client id & etc stored so I don't care about those
2.0.1 crashes when switching virtual desktops
Running 2.0.1, checking the windows event log I'm seeing evt 1000
```Faulting application name: HASS.Agent.exe, version: 2.0.1.0, time stamp: 0x65310000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x00007fff868b668c...
Solution:
@luma @Findel please check this version 😄
https://github.com/hass-agent/HASS.Agent/releases/tag/2.0.2-beta2...
how to get started - migration?
hello!
I've read the docs but not sure about a couple of things. At the moment, I have the old HASS.agent service and satellite running with Win10 computer and HA(HAOS). Do I have to uninstall the Windows program and use the new beta? do I have to remove the HA integration also and replace that, also? thanks...
Solution:
From a simple point of view, to test the 2.0.1 version:
1. backup your current "config" folder (there's never enough backups)
2. run the installer, select "migrate" option at the end
3. done...
Problem installing Windows App Runtime
Hello there. While trying to install the 2023.11.1-ubeta of Hass.Agent and following the manual installation steps provided here
https://github.com/amadeo-alex/HASS.Agent/blob/main/README.md, I am running into the Issue, that I get the Error Message, that Windows App Runtime Version 1.3 is required.
What I've tried so far:
- Installing Windows App SDK 1.4.3, 1.4,2, 1.3.3 and 1.3.0...
Satellite service crash when adding gpuload sensor
When I add the gpuload sensor, the service crashes. On restart, the gpuload sensor is not included as a sensor. Attached is the satellite log. Interestingly, it states "Processing 10 received sensor(s)", but only 9 sensors are written to the log before the crash.
Also attached is two events from the Windows Event Log that correlate with the crash....
Solution:
Error adding custom command
Specs
Version:
2023.11.1-ubeta
The friendly name of commands is copied from the actual name always, therefore it is not modifiable.
...Solution:
ok, I have a fix for this and in the meantime found 2 more bugs 😄
Command friendly name not working
Specs
Version:
2023.11.1-ubeta
The friendly name of commands is copied from the actual name always, therefore it is not modifiable.
...Access to Global path is denied in the app during startup
Specs
Version:
2023.11.1-ubeta
During startup of HASS.Agent immediately after the [INTERNALSENSORS]
are ready HASS.Agent spits out an error to the extended logs. Full log file is attached, the main error code is below
```...Solution:
Not a bug then, FTLs are also exceptions which are cought and handled down the line by code