Removing old duplicated entities.
Hello ! I installed the old HassAgent, having only played with sensor and commands, but then migrated to V2.
Used the compat script in #entity-names , but I still have duplicated entities in my MQTT integration.
I Decided to go back from scratch, and indeed the new entities has been deleted, but I can't remove the old ones (the underdogunderdog* ones), because "Entities can only be removed when the integration is no longer providing the entities". And in truth, I see the sensor being active, but with unknown status....
Solution:
Resolved by going into MQTT explorer and clearing leftover topics from pre-migration.

Possible to switch users?
Hi everyone! Is it possible to switch / log in a user from HA?
I have an older Surface Pro which is used by all family members. I'm thinking about using it as a HA dashboard when it is not in use. My idea is, anybody can grab the computer with its own user and when the computer is idle but connected to power, The user is automatically switched to the HA dashboard user. Maybe there is another way to achieve somthing similar, but I did not find a solution yet....
Solution:
You can't change which user is logged in due to security concerns in windows. You would have to make every user logout and login to an admin/ha user when they are done unfortunately.
Can't send notifications
I deleted all of my computers from the original HASS.Agent integration and restarted HA. The integration was gone and MQTT found all of my computers. I then installed the forked version via HACS custom repository. I then hit the configure button for all of my computers. However if I try to send notifications the notify service has not been configured automatically. HA can't find service notify.PC_NAME. When I look at MQTT Explorer under hass.agent I see them under devices and media_player but nothing about notifications. I have the most current version of HASS_Agent on my pc and the notifications test is working.
Any suggestions on how to get this working are greatly appreciated....
Solution:
You are correct again. I uninstalled and re-installed and am now able to send notifications once again. Thank you for your patience in helping me get this resolved. Getting old is a bitch. I should have read the documentation steps for installing more diligently.
Jatoxo - Integration device name mismatch
@Jatoxo
Solution:
Then you need to use something like mqttexplorer to go into the hass.agent topic and clear the old data
How to limit notification
I have setup a notification on my doorbell camera with frigate that sends notification whenever there's someone near the front door. The notification is working great with the option to open the camera live feed, but it just keeps on spamming me with notifications until the person is not detected anymore. Any tips or suggestion would be awesome!
Solution:
Yep, just checked:
Make sure automation is set to single
Add a time delay of 5 mins or so in the steps...

How do I send a notification
I cant figure out how to send a notification to my pc
Solution:
OK so I don't know if something changed overnight but its now working.
Mute Status of Input Device
I don't seem to be able to get the muted status of my device from HASS.Agent. I'm on Windows 11 Enterprise 22H2 and running HASS.Agent 2.0.1. There are many entries in "AudioSessions" and there is an entry for Teams that does report changes in PeakVolume, just not muted, nor does the default_input_device_muted show anything. I've tried with both the CTRL+SHIFT+M and WIN+ALT+K to mute the mic. The default audio input device shown in HASS.Agent is the same as is used in MSTeams and is the default...
Solution:
RE: https://discord.com/channels/1173033284519862392/1173033285845266515/1245689413770416210
The problem here is the same as with discord, teams does not tell windows and by extensions hass.agent if it is muted or not...
HASS.Agent closes when switching monitor profiles
I have a 2 monitor profiles configured through Display Fusion, hotkeys configured to choose between them, and HASS.Agent broadcasting them to Home Assistant - When I switch profiles, HASS.Agent seems to close itself, cutting off my profile switching options in Home Assistant. I believe a prompt mentioned something about scaling.
Any thoughts on how to resolve this and keep HASS.Agent running when switching between monitor profiles?
Thanks!...
Solution:
Updating to the beta seems to have resolved this issue
Get discord mute status
Hi, does someone know of a way to get the current mute status of discord. I'd like to colour a light based on mute status but it seems quite hard to get info out of discord locally.
Thanks!...
Solution:
For anyone finding this thread:
Discord does not work nicely with windows mic status. There is at the moment no easy way of getting the mic status unless you use something through discord's own API. As this is nothing to do with Hass.Agent its not possible at the moment....
Logger: homeassistant.util.logging
I am getting this error.
Exception in updated when handling msg on 'hass.agent/devices/MIKES-PC': '{"serial_number":"776872ee-5f6c-4070-8cd1-d79912566601","device":{"identifiers":"hass.agent-MIKES-PC","manufacturer":"LAB02 Research","model":"Microsoft Windows NT 10.0.19045.0","name":"MIKES-PC","sw_version":"2022.14.0"},"apis":{"notifications":true,"media_player":true}}' Traceback (most recent call last): File "/config/custom_components/hass_agent/init.py", line 147, in updated hass.async_create_task(handle_apis_changed(hass, entry, apis)) File "/usr/src/homeassistant/homeassistant/core.py", line 816, in async_create_task self.verify_event_loop_thread("async_create_task") File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread frame.report( File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report _report_integration(what, integration_frame, level, error_if_integration) File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration raise RuntimeError( RuntimeError: Detected that custom integration 'hass_agent' calls async_create_task from a thread at custom_components/hass_agent/init.py, line 147: hass.async_create_task(handle_apis_changed(hass, entry, apis)). Please report it to the author of the 'hass_agent' custom integration....
Solution:
you need to install the forked integration: https://github.com/hass-agent/HASS.Agent-Integration?tab=readme-ov-file#installation
Hass Agent Notify not working
I have tried these steps to rectify the situation.
Reinstall Hass.Agent
Reinstall Hass.Agent and Hass.Agent notifier in HACS
Reinstall Hass.Agent and MQTT plugin in Home Assistant Plugins...
Solution:
that should be the fix then, homeassistant 2024.5 broke the connection so you need to update, we will hopefully have a HACS entry soon, maybe not until the end of this year though

How to use Switching Virtual Desktop with a button in Home assistant
There is no help available or a how to make this work, i have two entity's in Home assistant a Button and a Entity /Sensors that present me de ID's of the Virtual Desktops created, but how can i switch between the ID's or virtual desktops with the button?
Anybody van help me with this?
Thank you....
Solution:
okay so step 1 is to create an
ActiveDesktop
sensor and a SwitchDesktop
Command
2. open the activedesktop entity in homeassistant and switch to the blue iris desktop for about 15s
3. Copy the ID and mqtt publish it to the switchdesktop command topic in the script...i buggered the install
hey I installed the new integration but did it all in one go (installed the new one in hacs, then deleted the old regular integration, then the old hacs integration but it said that I didn't delete the old one even though I did) so now after installing the new one it won't let my pc connect to the mqtt in ha, saying failed. (but the agent does show up as connected)
presumably the old one didn't get completely deleted? how do I do that manually? everything old is now gone in the UI...
Entity rename script instructions
Where can I find the instructions to rename entities from the old HASS Agent naming? I just updated to the fork and still have the old entity names.
Solution:
Amadeo is right, but full instructions are in #entity-names
no auto discovery
after breaking changes, i updated to hass agent 2, and downloaded the client fork. pc not being auto discovered, but sensors and commands show in mqtt.
Solution:
nevermind, i dont know what i did but it just showed up

hass.agent media_player
in my mqtt I see hass.agent and below that media_player and below that my computer and the the duration,currentposition,state, volumn etc...
how can I see this in home assistant?
I don't see that I can add that as a sensor that goes to the home assistant...
Solution:
ok, - thank you - now with 2.1.0-beta1 it works
and I can get the state and other information...
A few questions about HASS.Agent recent changes
I've used HASS.Agent for a few years to send toast notifications to my PC. They recently stopped working and I finally decided to explore why. I've poked around and I have a few questions.
(1) There is a lot of talk about release 2.0.0 and I am confused because I am using version 2022.14.0 which would seem to indicate something has changed. Has HASS.Agent been reborn under new custodians? Sorry if I have been under a rock. I found documentation on how to migrate, but migrate to what?
(2) In the past I have solved issues on the HA side by deleting the HASS.Agent integration and restarting HA and in no time autodiscovery finds the Agent and all becomes well again. That isn't the case anymore. Plus, my HA autodiscovery actually finds two HASS.Agent clients, including one that was on an old PC I haven't turned on in many months. How is HA "finding" this old agent? Strange....
Solution:
Please go to #👋・new-comers
Failure setting up integration
Hi everyone,
Since the last update of the integration to 2.1.0-beta1 I get the following error message in my log in home assistant:
`Traceback (most recent call last):...
new API-key dossent work
ha 24.5.3
agent 2.0.1
deleted the old API-key thinking it was unused sense i have disabled local-API. Relishing i needed it, i made a new long term access token and added it to the agent. clicking "check connection" it said it was ok, but after sawing settings and reboot it failed to connect....

Help with missing entities on new installation
After upgrading to HA v2.0.1 by deleting everything and starting from scratch, the HA integration is not finding the appropriate notify service entity (see screenshot). I'm also missing the media player entity (see second screenshot). I've tried restarting the windows agent and home assistant. Any other suggestions?
Solution:
good to hear 😄
for anyone else that looks at this thread the link is: https://github.com/hass-agent/HASS.Agent-Integration...
