Troubleshooting

Troubleshooting

An event never runs

Check	Why
Is the event enabled (checkbox)?	Disabled events aren't scheduled
Did you click Ok in the Events window?	The running schedule is rebuilt when you apply it
Is the cron expression six fields with seconds first?	Five-field expressions such as */15 * * * * are rejected and only logged. Use 0 */15 * * * *
Is the event Delayed while the player is stopped?	Delayed events are discarded when the player is stopped. Use Immediate
Has the event expired?	Check the Expires setting

Time or temperature announcement is silent

• Check Time/Temp File Path points at the folder containing Time and Temperature.
• Confirm the exact file exists, e.g. HRS14_O.mp3, HRS14.mp3 + MIN35.mp3, TMP065.mp3, or TMPN005.mp3 for negative temperatures. See Time and Temperature Files.
• The hour and minute clips must have the same sample rate and channel count.
• Temperature needs working Weather settings.

MQTT events don't fire

• Check the broker address and port in Preferences. A warning appears at startup if the schedule has MQTT events but the broker can't be reached.
• Topic and message must match exactly (case-sensitive). Wildcard topics aren't supported.
• The broker must allow anonymous, non-TLS connections.
• A retained trigger message re-fires every time the schedule loads.
• Remember to click Ok in the Events window after changing MQTT events.

No sound or "device in use"

Playback uses WASAPI exclusive mode. Close other applications using the same output device, and check Primary Output Device in Preferences.

Current song file isn't updated

The folder part of Current Song Path must already exist, and the file must not be locked by another program.

Known limitations

• Pause, Humidity Announcement events do nothing yet.
• The event Start Date and Time isn't used to delay scheduling.
• MQTT: no wildcards, authentication or TLS.
• Invalid cron expressions are logged but not reported in the UI.

If you hit something else, please open an issue.