Autodiscovery Issues with Integration
Thread to keep track of instances where the integration fails to autodiscover hass.agent instances.
16 Replies
Help us Help Others!
To help others find answers, you can mark your question as solved via
Right click solution message -> Apps -> ✅ Mark Solution
Help us Help You!
Please don't delete messages or posts because it makes it impossible to understand what happened. If you don't want your messages to be seen then don't post here.
Please provide us with your integration version number.
You can find it in HACS -> HASS.Agent -> Top left for installed version number.
Make sure to provide detailed reports of bugs.
Please include error log uploads and info about the bug.
@DrR0x
@Shredder5262
okay so looks like you are having an autodiscovery issue with the main integration. Could you try removing both. And then reinstalling just the hass.agent one after a full HA restart?
Hi there,
I've got one PC that I migrated from the OG HASS Agent working normally.
I just tried to add a second PC. I've got it recognized under the HA MQTT integration, but it won't show up under the HASS Agent integration (v2022.11.9) after multiple restarts of HA and HASS Agent.
Quick follow up, after reading this issue on the OG HASS Agent GitHub
https://github.com/LAB02-Research/HASS.Agent-Integration/issues/37
... I went ahead and deleted my original device from the HASS.Agent integration, then deleted the integration itself from HACS and restarted.
After the restart I reinstalled the integration, and restart it again.
Now all three agents showed up as auto discovered. I haven't tested everything in them, but my assumption is they will work. It seems there may be something related to auto discovery that was inherited from the original project.
GitHub
Autodiscovery doesn't work on newly added devices · Issue #37 · LAB...
Hi. I installed HASS.Agent on new device (win10 notebook with name 'notebook'). Only MQTT used. I checked mqtt topics via MQTT explorer and I can see hass.agent\devices\notebook topic (and ...
Yeah we do not yet have our own integration unfortunately
We do not have any way of controlling the original one. So we are looking at making our own called hass.agent 2 or something
Copy that, no worries, just wanted to follow up with a workaround and perhaps the origin of the original bug report.
Just saw this, I can try a bit later on one of my offending machines.
I may recommend HASS.Agent Fork so it doesn't confuse people with the new version moniker
Yeah, honestly the best option is to rename.
But that's out of the question because we are still hoping to remerge with Sam.
So fork could be the best option afaik it's the only one
.
From @Shredder5262
I'm still struggling to get one instance autodiscovered... It seems there is only a small window where autodiscovery works and never again and it's only when the media player integration is added and then reboot...after that it doesn't autodiscover anymore...This is definitely interesting. I am going to setup a VM or 2 on my server and try to replicate this stuff and get it sorted Once this but is fixed we will be full go ahead on the fork integration
Well it seems that worked this time. I guess that it's because i have all machines on the new agent now. Fully uninstalling the old agent on the client machines and installing the new one may have helped....? fwiw, I kinda wish there was a different name for this new agent, it's difficult to make the distinction between the old and the new....even though it's the same thing with continued development.
I'm kinda dumb, so there's that also....
It's still a mystery to me on why this didn't work before. I did install the hass.agent first, and that didn't work until i installed the media player piece. Perhaps the (full) reboot?...idk
I just noticed that none of these discovered entities have media players...
noticed in MQTT explorer that there is a discrepency of media players listed...
#Media Player unavailable