Skip to main content

How to setup Legacy clock device for Browsers

Audience

This guide is for people managers and supervisors who use Roubler and need to set up or re-register a Legacy clock device for browsers (for example, a shared tablet or PC clocking via a browser).

You will need Admin-level permissions in Roubler, or you’ll need to work with someone who has them.

Description

The Legacy clock device for browsers lets employees clock in/out and record breaks using a web browser instead of the newer Clock App. It is mainly used when:

  • A site still relies on the legacy/web clock, or

  • You need a simple browser-based clock on a PC/tablet, especially in environments with unstable internet where the legacy clock may behave more predictably.

To work correctly, each browser clock must be:

  1. Opened from Clock Applications to generate a Device ID, and

  2. Registered to a location via Location devices.

Steps – How to set up a Legacy clock device for browsers

Step 1 – Prepare the device

On the device that will be used as the clock (PC, Mac, tablet with browser):

  1. Connect the device to a stable internet connection.

  2. Open a supported browser (Chrome is recommended).

Tip: This device should be a shared kiosk/clock, not a personal admin machine.

Step 2 – Open the Legacy clock and get the Device ID

Still on the clock device:

  1. Go to https://app.roubler.com/clock/  

  2. The page will load and show the Device ID:

Write down or copy this Device ID carefully – you’ll need it in the next step.

Leave this browser tab open on the clock device; staff will use this page to clock once it’s registered.

Step 3 – Register the Device ID to a location

On an admin computer (this can be the same device or another one):

  1. Log in to Roubler.

  2. Go to Settings → Location devices 
     

     

  3. Click the + button to add a new device. 
     

     

  4. In the form:
    • Select the Location where this clock will be used (for example, store/site name).

    • Paste or type the Device ID you noted earlier.
       

  5. Click Add / Save.

  6. Go back to the clock device, within 3 minutes the screen will now show the clocking pad:

The browser clock is now registered and linked to that location.

Step 4 – Test the clock

Back on the clock device:

  1. Refresh the Legacy clock page if needed.
  2. Ask a test employee (or yourself) to:
    • Enter their clock PIN, and
    • Perform a Clock in and Clock out.

  3. Check that the test clocks appear in Attendance/Timesheets for the correct location and date.

Recommendation: Bookmark the Legacy clock URL in the browser and avoid re-loading it from other links. If the URL (and embedded token) changes, the device may show as unregistered and you’ll need to repeat the registration under Location devices.

Troubleshooting

1. “Unregistered device” or clock page not recognised

If the browser shows an “unregistered device” type message or clocks don’t record:

  • Confirm you have followed both parts:
    • Opened Legacy clock device for browsers and captured the Device ID.

    • Added that Device ID under Management → Settings → Location devices for the correct location.

  • If you refreshed the Legacy clock URL and the Device ID changed, repeat the registration steps with the new ID.

2. Staff say clocks worked, but nothing appears in Attendance/Timesheets

Possible causes:

  • The device was never properly registered, so clocks weren’t linked to a location.
  • There are network issues and the browser couldn’t send data.

Checks:

  1. Confirm the device appears in Location devices and is linked to the correct location.

  2. On the clock device, open a normal website to confirm the internet is working.

  3. If clocks still don’t appear, try:
    • Logging out of Roubler in that browser and logging back in as Admin,
    • Re-opening Legacy clock device for browsers from Clock Applications, and
    • Re-registering the Device ID under Location devices.

3. Clock page is blank / white / stuck

This is usually a browser or connectivity issue.

On the clock device:

  1. Test another website to confirm internet access.

  2. Clear cache and cookies for the browser, then reload the Legacy clock page.

  3. Close and reopen the browser; if needed, restart the device.

If issues persist, consider whether the site should switch to the New Clock App or Web Clock as a longer-term solution (via your internal Roubler admin).

4. Moving a legacy clock to a different location or new device

If you replace a device or move it to another site:

  1. On the new device, repeat Steps 2–3 to generate a new Device ID and register it to the new location.

  2. (Optional) In Location devices, remove any devices that are no longer used to keep the list tidy.

Who to contact for help

If you still have issues after following this guide:

HR / Payroll / Operations

Contact your HR, Payroll or Operations team for:

  • Decisions on which clocking method (legacy vs new Clock App/Web Clock vs mobile) each site should use.

  • Questions about how to handle missed clocks or manual timesheets and which locations devices should be registered against.

Internal Roubler / System Administrator

Contact your internal Roubler administrator or system owner for:

  • Access to Management → Settings, Clock Applications and Location devices.
  • Migrating sites from legacy clocks to the New Clock App where appropriate.

  • Investigating repeated issues with device registrations or legacy clock stability.

When escalating, provide:

  • The Device ID,
  • The location the device should belong to,
  • The device type (e.g. Windows PC, iPad using Safari, Android tablet with browser), and

  • Screenshots of the clock screen and any error messages.

Authorised internal admins can then decide whether to continue using the Legacy clock or move the site to the New Clock App / Web Clock and, if necessary, escalate to Roubler/MYOB Support