Stable MopicHub 1.1.6

페이지 정보

profile_image
작성자 MOPIC
작성일2026.10.01

본문

1.1.6 settles how the hub picks a license when more than one is available, moves live connection verdicts to HubDoctor so the Connection screen and support reports always agree, and adds a watchdog that restarts a tracking module stuck in initialization failure.

License

  • Fixed license priority. The license looked up by monitor serial is used by default. A manual key is used only when it was entered on purpose (the hub asks for confirmation when a MOPIC monitor is already connected), and a key inherited from older software comes after that. When candidates are equal the previous choice is kept. The tracking module runs with the same key the hub selected.
  • Camera check on manual key entry. If the camera bound to a manual key differs from the connected camera, the hub asks before saving, and a mismatched key is blocked rather than silently selected.
  • The license decision for each monitor, the reason it was chosen, and the context of a manual entry are written to the status file and included in support reports.

Diagnostics

  • Live verdicts come from HubDoctor. Whenever the module state, camera holder, USB devices, or loopback status changes, HubDoctor evaluates the situation and the Connection check list and cards show its verdict with area, evidence, and Fix actions. The hub's own camera, USB 3, and loopback checks are replaced by this. An older HubDoctor engine falls back to the previous hub verdicts.
  • Watchdog for a tracking module stuck in initialization failure. A module that stays in init_failed for 30 seconds is restarted, with the wait doubling on each retry up to 10 minutes. Restarts are deferred while the camera is in use or a check is running, and the backoff resets once tracking is idle or active.
  • The first busy check on a camera with no identifiable holder is treated as undetermined. An error card appears only when the second check confirms it.
  • The startup report is sent after the module has come up and the recheck has settled, so it reflects the real resting state.
우리 서비스에 어떻게 적용할 수 있을까요?