108 Replies
@DrR0x
hmm
does Local API need to be enabled on Hass.agent?
oh no i dont think it does
and was never enabled before
The device is not there at all in HA
Yeah delete it
And then restart, Autodiscovery issues are unfortunately common
We can't easily fix it tho, it's almost impossible to get debug info
Delete the whole integration?
or just the device?
Device
First, but a foolproof fix is to delete integration
It seems to always work
So i deleted teh device
restarted HA
it re-found the device automatically
but still no service
Wait, that's weird
Are sensors and stuff going?
i dont use anything else...
just the notifications stuff
just restarting HA again
Just throw a test one on
Or better
Media player test
Start a YouTube video and try adjusting volumd
can you tell me how?
Open the media player entity while a YouTube video is playing
youtube playing on my computer?
sorry i dont mean to sound stupid, but what media player entitiy?
Yep
Click on the device, and then in there you should see media controls
No in the device is nothing!
let me fully delete the hacs intergration and re-install
Oh okay yeah it's messed up then ๐ค
Ok deleted the device and the integration
rebooting
going to re-install
this one right?
there is only one hass.agent
so i assume it must be
2022.11.9
ok installed, rebooting again
ok it auto found my device, but when i go into it there are no entities
rebooting again
yep same again
after rebooting there is the entitiy
but nothing in it
whats annoying is this is mission critical for me ๐ฆ
Hmm, are the mqtt settings correct?
Can you add a sensor?
Anything
CPU usage
i added a sensor
And see if it comes up in home assistant mqtt integration
This
this is the MQTT integration
prime-HWZJCW2 is my PC name
Hmm, mqtt seems to be working
@Amadeo , any idea?
could it be an issue because my PC name has the - in it?
i can't rename my PC
somewhere i go a message in Hass.agent about the name, but i cannot remember where
Sensors are 100% working, if i add a new one i see it straight away under MQTT
OK Renamed the PC within the HASS.Agent settings. Rebooted HA, those updated settings show instantly under MQTT.
Deleted the device and reboted, waited for the device to find its self again with the new name but oddly it finds it under the old name
UGH. So frustrating! Removed it all and starting again!
@Amadeo would really LOVE you if you can help me fix this!
Weird. still finds it as the old name in the integration
so odd it finds the device as teh actual machine name, and not based on the setting i set in Hass.Agent
but MQTT has updated to show the name i put in Hass.agent
uninstalling, removing all my config and trying again!
annoying as ill have to figure out how i did my notification stuff but can worry about that later
Lemme catch up to speed with all the messages ๐
let's start with this, which Home Assistant version are you running?
2024.5.2
now the fun starts
Im starting 100% Fresh FYI
are there any errors related to HASS.Agent in the logs?
fully removed the software from my machine
there should be (โ๏พใฎ๏พ)โ
fully removed the integration in HA
manually removed files/folders
and rebooted
now going through the install process!
GitHub
Bug: Latest HA Core update 2024.5.0 breaks notification entities. ยท...
Please make sure that the issue you're planning to report is not already registered :) Describe the bug The latest HA Core update (2024.5.0) stops hass.agent from creating any notify entities. ...
UGH
lol
and to be specific this: https://github.com/hass-agent/HASS.Agent/issues/75#issuecomment-2090094046
GitHub
Bug: Latest HA Core update 2024.5.0 breaks notification entities. ยท...
Please make sure that the issue you're planning to report is not already registered :) Describe the bug The latest HA Core update (2024.5.0) stops hass.agent from creating any notify entities. ...
wish i had known this 10 minutes ago ๐
ok well let me get it all back installed
its not just the notification service
i was missing the media entitiy
sorry for that, we need to fix that in the integration itself and get it setup as a custom HACS repo - until then the manual fix should be good
ya
if you'll have any issues modyfying the file lemme know, I can send you the whole file to copy/replace
one second
let me get there
but would this same issue cause the missing media entitiy?
ya
can you remind me whilst you are here, where i get the HA API Token from?
setting it all up fresh
since this version (the one that you're running), HA will basically nope any integration that is trying to do async operation on sync thread
the adjustments are needed to make it compatible with HA's requirements
got the API dont worry
bear with
ok re-installed and made the changes
rebooting
100% some progress!
Just restarting it one more time
ok so....
the service is there....
but not working!
100% progress!
nothing happens on my computer
service is there....
what am i missing here?
test notification from within hass.agent works fine
not sure if this is related?
When i am playing a youtube video, im still not seeing anything under the device? Should i?
@Amadeo are you still here? sorry to ping, im just desperate to get this sorted
ya, switching between work and personal pc ๐
sorry! Not meaning to be a pain
no worries, lemme try something
ok, almost the same works for me (aka sanity check)
not getting anything in the logs when i try the above
with my PC name obviously
could you show me this page
So i just renamed the device in that page to test
maybe i should give my machine a quick reboot
as it hasnt been rebooted since re-installing
this is my actual PC name. I had previously tried changing it here to BensPC
incase the - was causing an issue
but the service was always called notify.prime_hwzjcw2 no matter what
ok, let's do this slow, do the following (in order ofc)
1. close HASS.Agent (if you want to rename the device you can do it now, after change HASS.Agent will restart, close it)
2. in Home Assistant remove all devices in HASS.Agent integration (not to be confused with MQTT entities)
3. in mqtt explorer remove entries in hass.agent\devices and hass.agent\media_player
4. start HASS.Agent
5. reboot Home Assisant
6. add the discovered device in Home Assistant
this will give us baseline to play with as I don't know what is the state of things on your end
OK well i just rebooted and tested again
still failed
so now going to follow your steps slowly.
before i close hass.agent
these things being stopped are ok right?
if you have no sensors/commands/quickactions configured then yes
OK Hass.Agent Application Fully Closed
clicking delete here
(not touching MQTT Side of things)
yup
opening MQTT Explorer
Connecting to HA
Removing these
yup
starting hass.agent
rebooting Home Assistant
waiting for reboot, and the auto discover of device......
clicking configure
reboot HA again?
god damnnit wtf
that happens
until i reboot again
then stuff comes up
at least thats whats been happening this morning
this is the first time the PC name looks correct though
so feels like some progress
let me reboot again
if that won't work we can have a voice chat + share if you're willing to, something doesn't add up here
yes that would be amazing
usually those steps solve all the issues
progress
oh, ok
lets try a notification
now the notifications
YAY
๐
ok almost there
can you help me reconfigure this (backup i took) in the gui
eli5 ๐
i deleted everything but took a backup first. This is the only thing i actually use
i think i MIGHT be able to do it... hold on ๐
hmmm
what do i want the new name to be
prime_hwzjcw2_launchurl
hmmm
ok it doesnt fully work
DAM
let me show you what it was for...
but now, clicking the preview button doesnt do anything
it should use Google Chrome (My default browser) to open the payload URL
can you remind me where the new config files are stored?
YES
Got it fixewd!
Thank you!!!!!
โค๏ธ
could not have done that without you!
and thank you too @DrR0x
Can i just confirm, you will fix this in the next update, and when i update, it will automatically overwrite my files with the new (fixed by you) version right?
Honestly, thank you both again SOO much
yup, to be specific the integration will need to be replaced (we have no access to the original one) but we'll write instructions on that ๐
nice that it's working
Honestly, thank you again!
That was stressing me out!
working like a charm now