Zac West
Zac West
If the machine is sleeping or changing networks between functioning and not, this is probably the WebSocket in the web frontend getting stuck. Apple introduced a new implementation in the...
You'd need to run a debug build of the app to connect the web inspector to see what's going on. However you may be able to replicate it in Safari...
This issue would best be filed in the frontend repo since the app does not present this UI: https://github.com/home-assistant/frontend
Yeah not stale. Path forward is probably my writing a native sidebar for the app, though. It's next up on my queue when I get time for it.
I think the notable error is actually: > 2022-05-20 17:56:01.808 [Info] [hakit-work-queue] [Environment.swift:71] init() > WebSocket: Received: result failure HARequestIdentifier(rawValue: 2138): external(HAKit.HAError.ExternalError(code: "not_found", message: "Push notification channel not found")) via...
Mac doesn't have this yet. Haven't had time to make the Mac server experience as easy as it could be.
This worked before. Each window/server is persisted and restored by the system as a scene with a user activity in it.
It's possible the Local Push extension went haywire, generally this happens when there's low overall battery use and it percolates up to the top.
Disable Local Push if you do not want the app to do this. https://companion.home-assistant.io/docs/notifications/notification-local
What do you have the Periodic Update value set to in app settings under Sensors? Local Push will also update sensors while it is connected. The system keeps the Local...