MedClock Setup & Troubleshooting Guide

To set up your MedClock you will need the device, the power cable, your reminder schedule, and for SMS users you will need the designated phone number, your token, and your Wi-Fi name and password.

Yes, you can use the alert feature without Wi-Fi, however you may experience time drift over long periods of time. The SMS feature cannot be used without Wi-Fi.

Yes, but SMS features will remain disabled until a valid token is entered.

One device with a browser is enough.

Usually 5–15 minutes.

Only if your plan or features require SMS.

Your token is emailed to you when you purchase a subscription.

Yes. Anyone with the setup details can configure it for you.

You should see a setup-ready screen and the MedClock setup Wi-Fi network should become available.

It means the device is waiting for portal configuration.

During the portal the button does not do anything other than move to time mode when configured correctly.

Brief beeps can be normal. Repeated alert beeps usually mean the device is in an active reminder state.

Check power, cable connection, and try rebooting the device.

If settings have not been saved to the device, all the settings will be reset.

The device restarts and uses the last saved settings.

The MedClock setup Wi-Fi should be visible and the setup screen should be active.

Join the MedClock Wi-Fi network, then open the captive portal prompt or your browser.

The access point may be off, the device may already be in time mode, or you may be too far away from it. Reboot the MedClock and make sure you are in the settings page to be able to connect.

That is normal. The setup Wi-Fi is a local device network used only for configuration.

Yes. Stay connected until your settings are submitted.

Captive portal detection can fail on some phones or browsers. If it does not open automatically, open any browser and search 192.168.4.1.

Open 192.168.4.1 manually in your browser.

Yes.

Refreshing the page can cause issues. If you need to reconfigure the device, reboot the MedClock and connect again.

MedClock uses 2.4 GHz Wi-Fi.

Hidden networks are not recommended and may not be supported during setup.

Standard WPA or WPA2 personal passwords are supported.

Common causes include weak signal, 5 GHz-only networks, router incompatibility, band steering, or router limits.

The firmware waits through retries and timeouts before showing a failure message.

It means the device could not connect to or reach the selected network within the allowed attempts. Make sure your Wi-Fi is connectable and the device is within a reasonable range to the Wi-Fi and it will auto reconnect.

Yes. The device will retry every 20 seconds.

Local reminders continue, but online features such as SMS alerts pause until Wi-Fi reconnects.

Yes. You can update Wi-Fi settings through the setup portal. Reboot the device to show the settings page and connect via your browser.

Treat it as a new Wi-Fi network and update the device settings.

Yes, as long as the network uses 2.4 GHz and allows normal outbound internet access.

No. Networks that require login pages, enterprise authentication, or captive portal sign-in are not supported.

The token is required to enable SMS features.

SMS setup failed due to a network, server, token, or account issue.

The token entered is incorrect, expired, or not recognised.

This usually means the token is already linked to another device and cannot be reused. If you believe this is a mistake, please contact us.

The token format may be valid, but the linked subscription is not currently active.

Rate limits or a cooldown period have been triggered after repeated failed attempts.

Yes. Enter a valid token later and update the settings to enable SMS features.

Yes. SMS setup requires internet access. Normal local reminders do not.

No. It is one token per device.

Local reminders continue working, but SMS features remain unavailable.

Yes.

Use the country code plus a valid local number in international format.

The most common reason is an incorrect length or invalid format for the selected country.

Yes, if supported by your plan and available routing.

The reminder occurred, but SMS delivery was not attempted or did not complete successfully.

Common causes include no Wi-Fi connection, token issues, SMS quota limits, rate limits, or a temporary server error.

Limits depend on your plan and provider settings. Standard paid setup supports up to 2 SMS alerts per day to one number.

No. SMS sending requires network connectivity.

Yes. Update the contact number in settings and submit the changes.

Turn off SMS in the settings and submit the changes once.

Select the timezone where the device is physically located.

Automatic time is best when internet access is stable. Manual time can be used when needed.

It is a fixed manual time mode that does not automatically adjust for daylight saving.

Common causes include wrong timezone selection, incorrect manual time entry, or no successful time sync.

Yes, in normal timezone mode. No, in Manual/No DST mode.

The device continues using its current clock until time can be synced again or updated manually.

Yes.

On connection events and during periodic sync cycles.

Up to 10 entries.

Yes.

Yes.

It keeps reminding until acknowledged. It is best suited for important reminders.

It remains unresolved and continues according to the selected reminder mode.

Yes, you can acknowledge up to 3 hours before the next due medication.

Alerts are queued and handled in order.

Check timezone, manual time settings, saved reminder times, and whether a previous reminder was still unresolved.

Changes are saved when you submit them.

It confirms the submitted configuration was accepted and stored.

Usually no.

All settings that have been saved to the device. Exact time only if it is connected to Wi-Fi.

Power cycle your device to bring up the settings page.

Connect to MedClock and delete all the medications.

Keep valid token and contact details entered, submit the update once, and wait for the completion message.

The device may be applying settings, scanning Wi-Fi, or waiting for network actions to complete.

Access point handover, time-mode transitions, or phone roaming can interrupt the session.

Refreshing may land on an action endpoint instead of the main page. Reboot the MedClock and reconnect to the device.

These usually indicate a temporary lock, retry delay, or reduced operation mode.

Check the token, subscription status, internet connection, and device time settings first.

Check that your network is 2.4 GHz, the password is correct, the signal is strong enough, and the router is compatible.

Wi-Fi test failures usually point to network or router issues. SMS setup failures with working Wi-Fi usually point to token, account, or server issues.

Record the exact display message, the time it happened, and what action you were performing.

Please send the exact wording shown on the device, such as Invalid Token, No WiFi, or Too many attempts.

Retry short-lived errors. Wait when the device shows a rate-limit or cooldown message.

Reboot the router for broader internet or Wi-Fi issues. Reboot MedClock for stuck local behaviour or display issues.

Current standard setup is typically one contact per device unless your plan supports more.

Yes, with separate device setups and tokens where required.

Acknowledgement happens on the device, so whoever is present can acknowledge it.

You can use an international number if supported by your plan and destination routing.

Update the account, token, and contact details.

MedClock stores configuration details such as contact information, token state, Wi-Fi settings, timezone or time mode, and reminder settings.

Your details are stored on the device for operation and only transmitted when required for enabled features such as SMS alerts. Physical access to the device should be treated as sensitive.

The token is stored on the device so the enabled features can operate. Keep access to the device controlled.

No, no personal details are sent when acknowledging medication.

Yes. Connect to the device and enter random values.

Yes. Local reminder timing continues even if internet access is unavailable.

The alert continues locally. Online actions resume when connectivity returns.

It resumes normal schedule handling after boot.

It resumes from current schedule and state. Stable power and uptime are best for consistent operation.

Place it in an open indoor space away from thick walls, large metal objects, and major appliances.

Yes, if it provides stable power at the required voltage and current.

Placement can help. Put MedClock in a large open area, ideally where you spend most of your time.

Risk is reduced with dimming and screen management. The device will typically avoid burn-in for a number of years.

Use MedClock in normal indoor, non-condensing conditions.

The latest versions of Chrome, Safari, Edge, or Firefox are recommended.

Auto-fill can overwrite fields unexpectedly. Clear the fields and re-enter them before submitting.

Close it and manually open 192.168.4.1.

Yes, but it will only work while connected to the MedClock setup Wi-Fi network.

The device may prioritise active alert behaviour over configuration changes. If the issue does not fix itself, repower the device and set it up again.

If no dedicated pause option exists in your version, temporarily edit or clear reminder times and then restore them later. Alternatively, unplug the device while you are away to avoid the alerts from going off. Please note that non-Wi-Fi users may need to re-enter the time.

No. All alerts must be acknowledged regardless of whether the medication was taken or not.

Basic scheduling is daily-time based unless your version includes advanced recurrence options.

This usually needs to be entered manually.

Use clear instructions and confirm the device state on screen after button presses.

Your name, when you purchased the device, the exact error wording, the date and time, and the steps that caused the issue. We aim to respond within 1 business day.

Use the exact wording or code shown on the screen.

Most errors fall into token, account, Wi-Fi, server, or limit-related categories. The exact message helps identify which one.

Change only the fields you need, submit once, and avoid resetting settings unless absolutely necessary.