[Bug] Interface not updating correctly

[seriousm4x]

For me it woke up two scheduled times now with lazy ping enabled.

Not related but what I noticed now in this version (at least, can't remember this happening before):
I did notice that when trying to wake up a machine manually that the red power icon didn't change to the yellow timer. Only when refreshing the page it did.
Then I noticed the timer counting down all the way until 0 and it returned to the yellow timer at 2 mins. It stayed there while the machine I woke up is responding to pings. Another refresh of the page and the icon changed to green.

Originally posted by @levelsw in #669 (comment)

[seriousm4x]

I had encountered this issue before when opening the page for the first time (or after clearing all caches and cookies), logging in, and immediately pressing the wake button, the yellow timer wouldn't appear. Fortunately, that issue is now resolved.

Then I noticed the timer counting down all the way until 0 and it returned to the yellow timer at 2 mins. It stayed there while the machine I woke up is responding to pings. Another refresh of the page and the icon changed to green.

I hadn't noticed this behavior before. Could you provide more details on how I can reproduce this issue?

[levelsw]

I tried it again and everything just worked fine. Restarted the container and it also just worked fine. Will test it out again at a later moment

[rockerbacon]

I'm running into the same problem. In my case the updates just seem intermittent, not working most of the time.

I'm seeing a request to /api/realtime that never finishes and I can't see any network activity in the browser inspection tab that would suggest the interface is trying to get any updates - no polling requests and no WebSocket connections.

[seriousm4x]

I'm seeing a request to /api/realtime that never finishes and I can't see any network activity in the browser inspection tab that would suggest the interface is trying to get any updates - no polling requests and no WebSocket connections.

This is expected. UpSnap doesn't use websockets, it uses SSE (server sent events). The /api/realtime endpoint will never finish because this is the connection which receives the changes.

[seriousm4x]

Anyone still having this issue with version 4.3.2 or later? If so, please tell me how I can reproduce it.