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.
No description
No description
Solution:
nevermind, i dont know what i did but it just showed up
Jump to solution
11 Replies
DrR0x
DrR0x9mo ago
could you get mqtt-explorer and check the mqtt payloads are being sent
ChaosBreaker
ChaosBreakerOP9mo ago
DrR0x
DrR0x9mo ago
do any of the 3 instances show in home assistant?
ChaosBreaker
ChaosBreakerOP9mo ago
nope
DrR0x
DrR0x9mo ago
you still need help sorting this out?
ChaosBreaker
ChaosBreakerOP9mo ago
Yeah im stuck
Solution
ChaosBreaker
ChaosBreaker9mo ago
nevermind, i dont know what i did but it just showed up
DrR0x
DrR0x9mo ago
is it working okay?
ChaosBreaker
ChaosBreakerOP9mo ago
yup
Uyly
Uyly2mo ago
I'm having the same issue. Mqtt is up and working and sensors work fine. I can get notifications working via the api, but home assistant isn't auto discovering my pc, so no media (the whole reason I got HASS agent🤦‍♂️). With MQTT explorer I can see that (under hass.agent>media_player>[pc_name]) it is broadcasting the mediaplayer state. My current best guess is that I'm sending the requests to the HA server's ip address, not the HTTPS login url. I updated both the HASS agent and the HASS agent integration to the newest forked version to no luck. After restarting my HA Server due to a HA update my computer showed up lmao. Nothing was changed, and this was probably like the 10th restart (including a full restart)
DrR0x
DrR0x3w ago
Yeah unfortunately this 'bug' or group of bugs tends to do that, it is extremely difficult to track down and then solve.

Did you find this page helpful?