Matrix Booking Knowledge Base

Signage device time troubleshooting

Problem

  1. How do I change the time on the signage devices?

  2. The time on the tablets is a few minutes out. How do I correct this?

  3. The time is incorrect on my tablet or kiosk. What do I do?

  4. My device is in the wrong time zone. How do I change this?

  5. Why can I check in to a booking on the Signage app, but then get an error message stating that the booking can’t be started at this time?

Solution

To resolve the incorrect time, including time drift, on your devices depends on your hardware options:

Regardless of what the hardware option you picked, you should make sure that your organisation has our servers as approved endpoints where applicable.

With MDM

If your room signage or kiosk devices are showing the incorrect time, this is normally because the devices are blocked from looking for the current time using a firewall.

Matrix Booking can push time zone changes via MDM if you have our Hardware as a Service subscription. For this to work, your organisation needs to make sure that all of Matrix Booking’s endpoints including the NTP server (the time server described above) are approved endpoints. Otherwise, it could affect the time displayed on your devices.

When the devices are sent out to your organisation, they are set up to reach out to one of the international time servers constantly. These Android devices normally use: *.pool.ntp.org. Sometimes they will be set with 2.android.pool.ntp.org or something similar, but it will normally always be a variant of *.pool.ntp.org unless you’ve requested a specific server.

If your devices are locked to a Matrix Booking app using our Hexnode MDM kiosk software, you need to:

  1. Take the device out of kiosk mode.

  2. Go to the Android settings screen.

  3. Change the time zone settings.

  4. To re-enter kiosk mode, open the Hexnode MDM application

  5. Select Activate.

If you’re unable make the time server an approved endpoint or you’re having issues exiting kiosk mode, raise a support ticket and our Hardware Team will help you.

Without MDM

If you’ve opted to not use our MDM software, raise a support ticket and our Hardware Team will help you.

Your own hardware

If you’ve opted to purchase your own hardware, raise a support ticket and our Hardware Team will help you.

Servers you should have as approved endpoints

The table below shows the full list of application endpoints that you need to include in the allowed or trusted list to fully utilise the Matrix Booking applications on a closed network. If any endpoints aren’t in your allowed or trusted list, you may have issues with the service related to the endpoint.

Rule

Server name

Direction

Application

Port and protocol

Notes

Matrix Booking app endpoints

app.matrixbooking.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Matrix Booking data.

cdn.matrixbooking.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Organisation logo.

signage.prd.matrixbooking.com

Outbound

Signage

443/TCP (HTTPS)

Event based communication.

Android NTP

2.android.pool.ntp.org

Outbound

Floor plan
Signage
Welcome

123/UCP (NTP)

Time and date server.

Hexnode MDM

s3.eu-central-1.amazonaws.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Hexnode app updates.

[portal name].hexnodemdm.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Hexnode client portal.

downloads.hexnode.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Hexnode app updates and delivery.

Hexnode remote view

remoteview-eu.hexnodemdm.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Hexnode remote view.

remoteview-eu.hexnode.com

Outbound

Floor plan
Signage
Welcome

443/TCP (HTTPS)

Hexnode client portal.

twilio.com

global.stun.twilio.com

Outbound

Floor plan
Signage
Welcome

3478/TCP
3478/UDP
5349/TCP

Hexnode remote view.

global.turn.twilio.com

Outbound

Floor plan
Signage
Welcome

3478/TCP
3478/UDP
5349/TCP

Hexnode remote view.

Hexnode push notifications

push-eu.hexnode.com

Outbound

Floor plan
Signage
Welcome

1883/TCP
8883/TCP

Hexnode remote view: receive push notifications via MQTT.

push-ldn.hexnode.com

Outbound

Floor plan
Signage
Welcome

1883/TCP
8883/TCP

Hexnode remote view: receive push notifications via MQTT.

Google

mqtt.googleapis.com

Outbound

Floor plan
Signage
Welcome

5228/TCP
5229/TCP
5230/TCP
443 TCP (HTTPS)

Remote view persistent connection.

fcm.googleapis.com

Outbound

Floor plan
Signage
Welcome

5228/TCP
5229/TCP
5230/TCP
443 TCP (HTTPS)

Remote view push notifications.

Time drift

Time drift is where a device’s time is no longer correct. What may happen as a result of time drift is that the Signage app gives you the option to check in to (start) a booking, but the device gives you an error message stating that the booking can’t be checked in to:

Error message stating that the booking couldn't be checked in to.

To fix this, the device will likely need to be taken out of kiosk mode before changing the device’s time.