Subathon widget fails to add time after some time

[alvarogzp]

Hello!

I'm using the subathon element for my long-running subathon stream. I customized the widget using the StreamElements UI, then saved, published the widget and added it as a Browser Source into OBS, and finally started the timer.

It works great: when a new event happens, it displays a notification on top of the timer with the user and the time to be added, and when the notification fades out, the time is increased accordingly.

But after a few days with the widget running, when a new event happens, it still displays the notification with the user and time to be added, but after the notification fades out, time doesn't increase anymore.

When I go to the Browser Source of the subathon widget and select "Reload cache of the current page", then the time is increased according to the last event received (ex. if it was a follow, the time for a single follow is added), but the time of all previous events after it started not increasing the timer, is lost.

I'm trying to understand how the widget works and am willing to help debug this issue, but I would appreciate some help from someone more familiar with the SDK and the widget itself to tell me where to look.

Thanks.

[alvarogzp]

More details after some testing:

It only happens on the OBS Browser Source. I have kept a background tab on my Firefox browser with the same widget URL as the OBS Browser Source for the Subathon Widget, and after a few days, the Firefox timer is still updated when new events are received. However, the OBS Browser source doesn't and is behind the Firefox counter (it is still counting to zero, but not updating the counter when an event happens).

After forcing reloading of the OBS Browser Source (by switching scenes), the Subathon widget appears on OBS with the same time as the Firefox time, and it is working again (ie., updating when events are received), for some time until it stops updating again.

So, it seems this could be an OBS-specific issue, or maybe Chromium.

[alvarogzp]

New update, now it has also happened on Firefox. The time didn't went up after sending some !subaddtime commands, neither on Firefox nor in the OBS Browser source.

I've tried to debug this in Firefox opening the Console, and it seems that the widget no longer receives the chat commands. Usually, it prints a lot of messages to the console after receiving a !subaddtime command, but in this case nothing was printed, as if the command wasn't issued.

Then, I tried reloading the OBS Browser source for it to start updating the timer again, to see what happened to the Firefox tab. At first, nothing happened, but after sending a !subaddtime command and the OBS Browser source increasing its timer, on the Firefox Console I could see a single message. The message said usePersistentDataEvents: onPersistentStorageVariableValueChanged: enabledRef.current: false. So it seems that these events are still received on the bugged timer. However, the time still didn't increase until I realoaded the Firefox tab.

[alvarogzp]

Sorry for the multiple posts, but I have noticed the subathon timer starts failing after my internet connection is lost.

Sometimes I have small cuts on my Internet connection (Windows sets the adapter as offline, and after a few seconds, it switches back online). When this happens, all internet sockets are shut down (the stream too), and they have to reconnect when the adapter is back online.

So I think that the websocket the subathon uses for receiving events is disconnected when this happens, and it never reconnects again after this.

Then, maybe the problem is in the SDK and not on the widget. It should have a retry reconnect logic for the websocket so it can connect again after the system is back online.