Public device page (Guntimes)

The Public Device Page is a single shareable page that shows the signals one of your timing devices (TSOne / TS2 or TS2+) has reported over the last two hours, and keeps showing new ones as they arrive. On screen, this page is called Guntimes.

If you don't know how to generate a signal from a TSOne or a TS2, see Generating a signal from a TSOne or TS2.
If you don't know how to generate a signal from a TS2+, see Generating a signal from a TS2+.

This article describes the public page opened from my.timingsense.com: where to find it, how to share it with someone who has no account, what it shows, how signals arrive live, and the states you may come across.

1. What is the Public Device Page

The Public Device Page is a single shareable page that shows the signals one of your timing devices has reported over the last two hours, and keeps showing new ones as they arrive.

It is the one page in the app that opens with no login. Anyone you send the link to can open it: no account, no password, nothing to install. They see that one device's signals and nothing else: not your inventory, not your company, not the rest of the app.

2. Where to find it, and how to share it

You open the page from inside the app, and then pass its address on:

1. From Devices › My Devices: open a device's ⋮ actions menu and choose Guntimes.
2. From Devices › Dashboard (Devices Dashboard): click a device's card to open its detail drawer, then choose Guntimes.

Either way the page opens in a new tab, so the app stays where it was behind it. Copy the address out of your browser's address bar and send it to whoever needs it: it works for them exactly as it works for you.

The link carries one device's identifier, and the page shows that device.

3. What you see

The page is deliberately plain: no menu, no sidebar, nothing to sign into.

• The Timingsense logo top left, and the light/dark button top right.
• The device's name, with its type as a tag beside it. Some devices have neither recorded (a device reporting through a Bubble, for instance), and then that heading is simply empty: the link is what identifies the device.
• A live badge, a Local time / UTC switch, and an Update button (reload icon).
• The last signal received, in the Last received block above the list, whenever the live connection is up.
• The list of signals, newest first, with two columns:
  • Wave time: when the device generated the signal.
  • Received in cloud: when that signal reached the Timingsense cloud, shown as how long ago it was ("3 minutes ago") and kept up to date every half-minute. Hover over it, or tap it on a phone, to see the exact timestamp.

Comparing the two columns tells you how long a signal took to get from the device to the cloud.

Times are shown down to the millisecond. A dash means that timestamp wasn't reported.

The window is fixed at the last two hours (there is no date picker), and so is the order, newest first, which is why the columns don't sort. If there are more rows than fit on one page, the list pages; changing the clock or receiving an update won't throw you back to page one.

On a phone, signals are shown as cards rather than as a table.

4. Signals arrive live

There is nothing to switch on and no need to keep refreshing. The page opens a live connection when it loads, and new signals appear on their own: in the Last received block above the list, and as a new row in the list itself.

The badge beside the controls tells you where that connection stands:

• Live: connected and listening. It doesn't depend on the device being switched on or connected to the internet.
• Connecting…: still establishing the connection.
• Live feed disconnected: the connection dropped.
• Live feed not available here: this page has no live feed at all, so the two-hour list is the whole story. This one is not an error.

Until the first live signal lands, the block reads "Connected and waiting — no detection has arrived yet."

If the connection drops, the page reconnects on its own and pulls in whatever arrived while it was down, so you can leave it open and come back to it.

5. What you can do

• Switch between your local time and UTC: the Local time / UTC switch changes every time on the page at once: the list, the Last received block, and the exact times behind the tooltips. It starts on your local time.
• Update: fetches the most recent two hours again. The list doesn't blank while it works; the icon spins until it's done. Useful if you think you missed something.
• Read the exact time of a signal: hover over, or tap, the "x minutes ago" value to see the full timestamp in whichever clock you've selected.
• Switch between light and dark: see the next section.

6. Light or dark

The button in the top right corner switches the page between light and dark appearance. The icon shows the mode you are in now: a moon in dark mode, a sun in light mode.

The first time the page is opened it follows whatever the browser or computer is already set to. After that, the choice made here is remembered in that browser, and it stays put even if the computer's own setting changes later.

It is the only appearance control a viewer has on this page: the app's other one lives in the user menu, which only exists once you've logged in.

7. What the page doesn't show

• No tag numbers and no participant details. The list holds two columns, and both are timestamps.
• No way into your account. There is no login, no menu and no link back into the app.
• No other devices. One link, one device, the last two hours.
• Nothing to change. The page is read-only: nothing on it configures, starts or stops the device.

8. States you might see

• Loading guntimes…: the page is fetching the window. On a busy device it counts up as it goes.
• This device has not reported any detection in the last 2 hours.: the device exists and hasn't sent any signal in that time. The live connection stays open, and the first signal to arrive replaces this message with the list.
• Device not found: no device matches the identifier in the link; check it was copied whole. This is deliberately a different answer from the one above: "doesn't exist" is not the same as "exists and sent nothing".
• Guntimes are not available here yet: the service behind the page hasn't been switched on for this address yet. Not a problem with the device.
• Guntimes could not be loaded: something else went wrong, with the server's own message underneath. Press Update to try again.
• Showing the first … guntimes: a warning that the two-hour window holds more signals than the page fetches in one go, so the list is genuinely incomplete rather than merely long.

9. How it connects to the rest

• The device is the same one listed in My Devices: this page is that row's recent signals, opened up so someone without an account can follow them.
• The Devices Dashboard answers the same "what's happening right now" question for all your exporting devices, behind a login. The public page narrows it to one device, drops everything private, and needs no account.
• The device's Telemetry answers a different question: what the device reported about itself (signal coverage, battery, status) over time, rather than what it recorded.
• The device's Exports are where you manage where a device's readings are sent, and where you download them as a file. The public page neither sends nor changes anything.

Following these steps, you can open the public page for any of your timing devices, share it with whoever needs to follow its signals without an account, and know at a glance what each state on the page means.