Bug: Sensors go "unavailable" at random time until I do a HASS.agent restart.

[ZackGibby13]

Please make sure that the issue you're planning to report is not already registered :)

---

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Misc info (please complete the following information):

• Windows build (ideally screenshot/info of winver.exe output):
• Windows' UI language:
• HASS.Agent version:

Please check what's applicable (multiple answers possible):

• Installed via installer
• Installed manually
• Problem occurs in HASS.Agent
• Problem occurs in Satellite Service

Additional context
Add any other context about the problem here.

Logs
If possible, please provide the logs of HASS.Agent and - if applicable - the Satellite Service. You can find HASS.Agent's logs by going to the main window, then Configuration -> Logging -> open logs folder. The Satellite Service's logs are in the same window, but the Satellite Service tab -> open service logs folder.

[Sythsaz]

are you able to enable extended logging in configuration -> logging and post that after you experience this issue again so we can see what is going on?

[ZackGibby13]

Okay, I have enable extended logging. When I get the issue again I will pull the logs and post those. Thank you *note: I think it might be due to the "Sleep" setting on my PC, I have turned that off and seems to be working now. Thank you for the reply!

…

On Tue, Nov 19, 2024 at 11:15 AM Ashton ***@***.***> wrote: are you able to enable extended logging in configuration -> logging and post that after you experience this issue again so we can see what is going on? — Reply to this email directly, view it on GitHub <#194 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIIPJYZ52PHRD6CO5DJYPHT2BNPYVAVCNFSM6AAAAABR5IPD3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGE2TGNZWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

--

[1812z]

Same here
I add activewindow in sensors,and when i switch the window to Cloudmusic the MQTT crashed.

2024-12-20 17:24:22.827 +08:00 [INF] [MQTT] Connected
2024-12-20 17:24:22.872 +08:00 [INF] [HASS_API] Home Assistant version: 2024.12.4
2024-12-20 17:24:23.056 +08:00 [INF] [LOCALAPI] listening on port 5115
2024-12-20 17:24:24.744 +08:00 [INF] [MQTT] Initial registration completed
2024-12-20 17:24:36.368 +08:00 [FTL] [PROGRAM] FirstChanceException: A task was canceled.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at MQTTnet.Client.MqttClient.TrySendKeepAliveMessages(CancellationToken cancellationToken)
2024-12-20 17:24:37.056 +08:00 [INF] [MQTT] Connected
2024-12-20 17:24:37.087 +08:00 [FTL] [PROGRAM] FirstChanceException: The operation was canceled.
System.OperationCanceledException: The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at MQTTnet.Internal.BlockingQueue`1.PeekAndWait(CancellationToken cancellationToken)
at MQTTnet.Extensions.ManagedClient.ManagedMqttClient.PublishQueuedMessagesAsync(CancellationToken cancellationToken)