Open dfrazao opened 1 month ago
Hello,
In the current version of HASS.Agent the audio sensor is of "multi" value - multiple separate sensors are created when you add "Audio" sensor. The infinite symbol is expected, could you please check if the sensors are present in Home Assistant / MQTT?
One thing that I've noticed though that there are multiple entries of failed session retrieval for "NVIDIA High Definition Audio" - I might add a logic that will stop printing those out after X iterations.
Hi, I believe that the user is referring to the Peak Volume function which just stopped working after upgrading to 2.1.0. I have a lot of automations and dashboards which update or do things based on whether Peak Volume has been 0 for some time or above 0 for a while, but as of last night all that has simply frozen.
I tried also going through the Satellite Service route, but even the satellite sensor is not updating at all. Additionally, I've reinstalled hass agent once, rebooted both HAOS Server and the machine running HASS Agent but everything is still pretty frozen. The other computers which have not been upgraded yet to agent 2.1.0 are not experiencing this issue.
Hi, with some additional mucking about with the thing, I found that the entire audio sensor stops working after I reinstall the agent.
Unsure if this is related, but mine is giving very wrong values for the default input device volume.
Describe the bug I'm having an issue with the audio sensor, the value is not being updated and in the sensor configuration the last known value is infinite. I've added the logs below, with screenshots of the sensor configuration window and the specific sensor configuration.
Expected behavior The audio sensor being updated
Screenshots
Misc info:
Please check what's applicable (multiple answers possible):
Logs
HASS.Agent Logs:
Satellite Service logs: