overlays.uno SetMatchTime requires seconds, but ScoreSight outputs Time.

[miranbehluli]

Hi Roy!

I am trying to use ScoreSight with an overlays.uno Soccer Overlay, but it needs a value in Seconds for the SetMatchTime, and I can't figure out how to convert the Time into seconds in ScoreSight. Is this possible with a "Custom" Format for the Time Field?

Thanks!
Miran

[royshil]

Hi Miran, thanks for the screenshot, it makes the problem clear.

You're right: the UNO Soccer API's SetMatchTime takes a number of seconds ("600" for 10:00), but ScoreSight sends the clock as it reads it ("45:47"). The Format setting can't fix that, Custom or not. It only decides which readings are accepted; it never changes the text that is sent. ScoreSight has no option today to send the time as seconds. (Our UNO docs even say the overlays expect mm:ss, which is wrong for this API.)

I'll add this: when a field is mapped to SetMatchTime (and the other match-time commands that take seconds), ScoreSight will convert mm:ss to seconds before it sends it.

Two things to know before relying on it, both from the API description in your screenshot:

1. SetMatchTime pauses the overlay's clock ("Use PlayMatchTime to resume"). With ScoreSight sending it at every new reading, the overlay shows ScoreSight's reading, updated once a second, instead of running its own clock.
2. Call limits: a clock that changes every second uses about 3,600 UNO calls an hour, and the Free plan allows about 10,000 a day. A full match plus warm-up fits, but not several matches a day.

So until the conversion is in a release, a practical setup is to clear the command next to Time in ScoreSight's UNO mapping table. ScoreSight then keeps sending scores and period, and you start the overlay's own clock with PlayMatchTime (or its control app) at kick-off.

One question that would help me get the conversion right: the API says "match time of the current period". In the 2nd half, if you send 2747 manually (45:47 in seconds), does the overlay show 45:47, or does it add the first half and show 90:47?

Also see #163 for the reason the Time field stops at 59:59 with the mm:ss format.

[miranbehluli]

Hi Roy.

I spoke to a developer from Singular.LIVE and he said that converting the value specifically just for SetMatchTime is a workaround and that it shouldn't have to be done. This is a complication due to the way the overlay was built in Singular's Composer.
So, please don't implement this change for now:
when a field is mapped to SetMatchTime (and the other match-time commands that take seconds), ScoreSight will convert mm:ss to seconds before it sends it.

A new feature is in the works for overlays.uno called "Data Gateway" which will allow users to set up real-time data much more easily via the UI directly in the App.
It uses webhooks and will allow for much faster data transfers, especially useful for clocks.

To answer your question about Periods:
When 2nd half is chosen, it starts at 45 minutes (Depending on "Period Duration" option in "Setup" panel)

and the Clock values are added on top of that, which further complicates things, so the user would always have to keep the Period set to 1st Half.

We will discuss this internally with the Singular team and keep you updated.

Would you be interested in looking at Data Gateway when an early release is available?
We can coordinate, so that newly released overlays can work with Data Gateway + ScoreSight properly.

I will put the Tutorial Video for overlays.uno + ScoreSight on hold for now and will resume at a later time.

Thank you.
Miran

[royshil]

Thanks Miran, that's very helpful. Understood: I won't add the seconds conversion for SetMatchTime.

Your screenshots also show why it would have been the wrong fix. In the 2nd half the overlay adds the period's start to the clock (25:25 shows as 70:25). A scoreboard clock already shows the whole match time (70:25), so ScoreSight sending its reading plus SetPeriod would have counted the first half twice. To use it, people would have had to leave the period on 1st Half, as you say.

Yes, I'm interested in Data Gateway. I'd be happy to try an early release and coordinate so that the new overlays work with ScoreSight. What matters most on our side:

• The clock as the scoreboard shows it. ScoreSight reads the clock as text (70:25, 45:00, 9.8 for tenths). It would be ideal if the overlay could take that text as is, or the total match time in seconds, without adding the period's offset.
• Sending every second. The clock changes every second. Today that's about 3,600 calls an hour against UNO's call limits, so the way the Data Gateway counts and limits calls matters for clocks.
• How the data gets in. ScoreSight can already push to a URL (the outbound API output, which can send JSON with all fields in one request) and serves /json, /xml and /csv on its built-in HTTP server for a gateway that pulls. If the Data Gateway accepts one of those, it may work without any ScoreSight change.

Send me the docs or the webhook format whenever you have them. And thanks for putting the tutorial on hold until this is sorted out.

[royshil]

For completeness: ScoreSight 0.4.3 fixes the Overlays.uno page. It no longer says that overlays take the match time as mm:ss. It now says what ScoreSight sends (the clock as the board shows it) and what to do when a command such as SetMatchTime expects something else. The same release also has the soccer clock fix from #163. I'm still glad to try the Data Gateway whenever it's ready.

[miranbehluli]

Thank you!

I wil let you know when we are ready to share Data Gateway with you for testing.