Operations and troubleshooting

Always running

The viewer and background components start automatically at boot, and a watchdog component restarts processes that have died. If a screen looks off or frozen, first check the device’s power, network, and connection to the CMS.

Power state outside operating hours

Operating hours, operating days, and holidays are set on the Settings (설정) screen. What happens to a device outside those hours depends on whether the device supports sleep.

	Outside operating hours	How it comes back on
Devices that can sleep	Go into sleep (standby)	Wake themselves with a built-in timer scheduled on the device
Devices that can’t sleep	Stay on, with only the screen turned black	Resume playback automatically when operating hours begin

No device is fully shut down on a schedule

Outside operating hours, a device is either asleep or on. If it were shut down completely, there would be no good way to turn it back on at an unattended site.

🔵 Because devices wake with their own timer, they come on on time even if the network is down. Even at sites where the internet is blocked, the morning wake-up works independently of the CMS.

⚠️ Leave the PC BIOS setting Power On By RTC (power on at a set time) turned off. It is an alarm for a fixed time written in the BIOS and does not follow operating hours — waking on schedule is done by the wake timer the player sets when it goes to sleep.

🔵 If the screen is off during operating hours, the CMS turns it back on. The device reports its screen state (playing · black screen · panel off) to the CMS, and when it reports the screen is off during operating hours the CMS sends a wake signal — this covers someone pressing the power button or Windows turning the display off.

• The device cannot tell when the monitor itself is switched off at its power button, so it cannot turn it back on — switch it on on site.
• While someone is connected to that PC by Remote Desktop, the screen state is treated as unknown and is not reported as off (from viewer 2026.9.383) — the player is not restarted while you do maintenance.

Each screen group can differ

The values on the Settings (설정) screen are the site-wide default. To give a screen group its own schedule, open that screen group in Scheduling (편성관리) and, under [Operating hours] in its header, pick one of three for Mode:

Choice	What it means
Follow the site operating hours	Follow the default schedule from the Settings screen
This screen group’s own hours	Give this screen group its own on time · off time · days off · holidays
No operating hours (always on)	Use no schedule — the devices stay on all the time

Picking This screen group’s own hours reveals the On at · Off at · Days off · Holidays (specific dates) fields below it. Use it when groups need different hours — for example, floors of a building that open at different times. When you save, “Operating hours saved — sleeping devices will be woken within a minute to get the new schedule.” appears, and the change takes effect right away without saving the schedule again. Removing a holiday removes only this screen group’s holiday.

No operating hours stops app updates from installing

App updates install outside operating hours on their own (the screen goes black for a few seconds, so they avoid business hours). No operating hours (always on) removes the concept of operating hours altogether, so “outside operating hours” never arrives — devices in that group keep deferring and never install.

If a device keeps logging 앱 업데이트 미룸 — 운영시간 중이라 미룹니다 (“update deferred — still within operating hours”), suspect this. To install, switch the group to Follow the site operating hours or This screen group’s own hours, or select the device in the device list and press Commands for selected → Install now.

Power on / power off / restart buttons

You can send these to devices selected in the device list in Devices (기기관리).

Power on only reaches devices on the same network

Power on works by sending a signal to wake a sleeping device, so the device has to be on a network the signal can reach. Depending on the site setup, the CMS sends it directly, or another device at the same site that is already awake sends it instead.

If a device doesn’t come on when you press it, check ① that the device isn’t fully shut down and ② that there is an awake device at the same site.

Common situations

• No content on the screen — 🔴 Check the CMS address first. Right after installation the player holds the development default (127.0.0.1), so if the address isn’t entered, the screen comes up fine in full screen but no content appears. To check, look at the [사이트설정] (site settings) line in that PC’s %APPDATA%\TreeTview\logs\main_<date>.log: if it says 확인 — … 걸리는 것 없음. (check — no problems) it passed; if it says ✗ CMS 주소가 아직 개발 기본값입니다 (the CMS address is still the development default), that’s the cause. Enter the address with F8 on the player screen → Site deployment. 🔵 If nothing shows even though the address is correct, then check registration and schedule assignment.

• Screens are out of step — check the multi-screen sync settings and the network status.

• Remote control (play/stop/volume) doesn’t work — check that the viewer is connected to the CMS and the relay components.

• After replacing the motherboard or network hardware, the device shows up as a “new device” — this is normal. See below.

• “I started an update but it didn’t install” — what to do depends on which line appears in that device’s history in the admin console.

  Line you see	Meaning	What to do
  앱 업데이트 미룸 — 운영시간 중이라 미룹니다	✅ This is normal (“app update postponed — during operating hours”). Installing during operating hours would black out the screen for a few seconds, so it is postponed on purpose	Wait; it installs by itself outside operating hours
  앱 설치 신호 무시 — 앞 설치가 아직 진행 중입니다 repeated	🔴 The previous installation has stalled (“install signal ignored — the previous installation is still in progress”)	Restart the player once on that device and it clears
  앱 설치 실패 — …	It stopped at the download or verification stage (“app installation failed”)	Pass that message on to us exactly as shown
  No line at all	The device can’t talk to the CMS	First see “No content on the screen” above

  It’s normal for installation to take a while

  The player installs by itself outside operating hours, and the other programs (sync, watchdog, broker) check once every few hours. So a new version not installing right after it is uploaded is not a failure.

• You changed the schedule but the screen stays the same, and the device history shows 다운로드 오류! 60초 동안 한 바이트도 안 와 끊습니다 — 다음 확인에 다시 받습니다. (“download error — not a single byte arrived for 60 seconds, so it disconnected; it will download again at the next check”) — the device was downloading content, received nothing for one minute and cut the connection itself. At the next check it resumes from where it stopped, so usually you can leave it. If the same line keeps repeating, check that device’s network and whether a very large file (for example a 6K video over 1 GB) is in the schedule.

After replacing parts, you may need to register the device again

Devices fall into two groups depending on how they prove which PC they are. You can tell which by the tag under the device name in the Devices (기기관리) list in the admin console.

That PC	How it proves its identity	Tag
Has a security chip (TPM) — most recent PCs	A key created inside the chip. It does not look at network addresses	(none)
Has no security chip	System serial number + the motherboard’s network device	약한 신원 (Weak identity)

When you need to register again

What you changed	PC with a security chip	PC without a security chip
Replaced the motherboard (including repairs)	🔴 Register again	🔴 Register again
Replaced, added, or removed the motherboard’s LAN/wireless device	🔵 No effect	🔴 Register again
Plugged in/unplugged a USB LAN adapter or docking station	🔵 No effect	🔵 No effect
Unplugged the LAN cable · switched between wired and wireless	🔵 No effect	🔵 No effect
Windows random hardware addresses (Wi-Fi)	🔵 No effect	🔵 No effect — this value changes on its own, so it isn’t used
Replaced the hard disk, SSD, or memory	🔵 No effect	🔵 No effect

🔵 If a PC has a security chip but shows “약한 신원” (Weak identity), TPM may be turned off in the BIOS.

Logs

Each program keeps logs. Capturing the problem and sending it to TreeT staff helps us find the cause.

🔵 You can see player errors without going to the site. Unhandled errors are recorded in the admin console under Devices → Device history (기기관리 → 기기 이력) — you can look up which error happened on which device, and when (see admin console).

Note

Detailed logs still stay only on the device. What Device history records is errors and major events, not a detailed record of every single playback.

Actions taken by people — the audit log

Separately from the logs devices keep, actions people take in the admin console are recorded on the Audit log (감사기록) screen (logins, changes to devices, content items, schedules, and users, data exports, and attempts refused for lack of permission). The audit log is Master-only, so if you need something checked, ask your TreeT contact (“Audit log (감사기록)” in the admin console guide).

	Retention period
Device logs (Device history)	14 days by default
Audit log	180 days by default

The two values are set separately — device logs are large and only needed for a short time, whereas the audit log is for tracing back “who changed it back then”, so it is kept longer. Anything past its retention period is cleaned up automatically.

Caution

Changing settings during operation (host address, schedules, etc.) can immediately affect the service on site, so check with the person in charge before making changes.