Always improving

What's new

We keep refining SkyView — here's a timeline of the features and improvements each release brings you.

  1. v0.9.52Latest

    Reset a forgotten admin password yourself · AI recognition silently falling back to the CPU on some NAS systems is fixed · Fall detection no longer alerts twice for the same person

    • The only administrator can now reset a forgotten password. SkyView runs on your own machine, so there is no password-reset email to send; until now, if the sole administrator forgot their password, the only way back in was to have support edit the database directly. You can now reset it with a single command on the device (docker exec -it yunkan skyview-reset-password --user admin) and type the new password twice when prompted; a disabled account can be re-enabled at the same time. The password is only ever typed into the terminal — it is not passed on the command line, so it never ends up in your shell history. This also fixes a problem that could swallow the first few characters of a password as you typed it, leaving the new password wrong no matter what you entered, with no error message anywhere.
    • RK3588: fixed AI recognition silently falling back to the CPU on some NAS systems while the accelerator sat idle. On NAS systems running a newer kernel (fnOS among them), face, pose, licence-plate and gesture recognition quietly reverted to running on the CPU. Everything still worked and nothing was logged — the only clue was the odd combination of "the NPU shows load, yet the CPU is pegged", which made it very hard to spot. On the same device, system load dropped from 14.4 to 7.2 after the fix, and utilisation across the accelerator's three cores rose from just over 10% to 33–50%. The related problem where the entire NPU card vanished from the Performance page on those same systems is fixed as well.
    • A dedicated setup file for fnOS NAS devices with ARM processors. On these boards the accelerator and graphics chip carry the opposite device numbers to a standard board, so the generic configuration fails to find the hardware; a dedicated setup file is now provided.
    • Fall detection: no more repeat alerts for the same person. A customer received a second fall alert for the same person a few minutes after a genuine one. The cause: while sitting at a low table, part of the body was hidden behind furniture, and the sudden drop in apparent height was read as another transition from sitting to lying down — restarting the timer and firing again. For a stretch that has already been reported, the system now checks where the lower edge of the body is: someone genuinely going down from sitting only ever moves that edge toward the floor, never upward, which is enough to tell "partly hidden" apart from "actually fallen". Situations that have not been reported are judged as before, and genuine falls are unaffected.
    • Traditional Chinese: notification wording now uses 推播. In Taiwan, Hong Kong and Macau, phone notifications are called 推播; 推送 reads closer to "recommend" or "promote" there. The Traditional Chinese interface in the mobile apps and on the web has been revised term by term, changing only the notification-related wording.
  2. v0.9.51

    Event descriptions are no longer blank in bot notifications · Desktop event banners no longer cover window buttons · Fall detection no longer misreads prolonged sitting

    • The event description in DingTalk / WeCom / Feishu and similar notifications is no longer blank. Those messages cannot be edited once sent, while the scene description only becomes available after the AI has looked at the footage (usually a few seconds) — so any bot message whose text referenced the event description always arrived with that line empty. Now, whenever an action's text uses that variable, the system waits for the description before sending: up to about 15 seconds with on-device recognition, or about 60 seconds with cloud recognition (adjustable). If it still is not ready, the message goes out as before, just without the description. Actions that do not use the variable, phone notifications and voice announcements still fire immediately. The rule editor now tells you that the message will wait, and for how long. Cloud recognition also runs in parallel now, so busy periods no longer queue up for minutes.
    • Desktop: event banners no longer cover a window's minimize / maximize / close buttons. With a window maximized or snapped to the top of the screen, the banner in the top-right corner landed exactly on those three title-bar buttons, leaving you to wait for it to disappear before you could click them — a long wait when events come in quickly. The banner now shifts down out of the way and slides back once the window is restored.
    • Fall detection: no more false alarms from prolonged sitting. The previous release added a supplementary check based on how long a body stays spread out horizontally, so that someone lying curled on their side (legs hidden behind their own body) would not be missed. In practice, a child sitting still in a high chair could accumulate enough brief leaning-forward moments to trip that check, producing a fall alert that never happened. The check now requires the horizontal posture to be the dominant one for that stretch of time, rather than a few scattered moments adding up over a minute or two. Prolonged sitting and desk work no longer trigger false alarms, while the side-lying case fixed in the previous release still works and genuine falls are unaffected.
  3. v0.9.50

    Notification channels configured once · fall detection catches lying curled on one side · RK3588 runs face/plate on nine main streams · clearer upgrade guidance for managed platforms

    • Notification channels, configured once and picked per rule: DingTalk, WeCom, Feishu (both bot and app flavours), Bark, ServerChan, Telegram, Discord, Slack, Synology Chat, VoceChat and more are now set up once under Settings → Notifications (credentials entered a single time, test-before-save with a sample snapshot and the last result kept on record). Automations gain a "Notification channel" action: pick the channel, write the message, optionally attach the snapshot or @everyone. Previously every rule carried its own bot URL and rotating a key meant editing rules one by one — now one change applies everywhere, and a channel referenced by rules can't be deleted by accident (the dialog lists the rules using it). Telegram can look up the chat_id in one click; the DingTalk app can find groups and add them one at a time. Existing DingTalk / WeCom / Feishu / Bark actions migrate into channels automatically — nothing to reconfigure.
    • Fall detection: lying curled up on one side is no longer missed: when someone lies on their side curled up, the legs are often hidden behind the body, and that posture could go unreported before. Detection now also considers how long the body stays spread out horizontally — about 3 seconds on the floor triggers the alert — while one-or-two-second motions such as bending down to pick something up still don't.
    • RK3588 edition: face and plate recognition on every camera's main stream no longer restarts on memory pressure: memory used by detection and by the display cache is sharply reduced, so nine main streams run steadily and the video wall keeps its native frame rate.
    • Clearer upgrade guidance for managed platforms: on deployments where the platform manages the container — Synology Container Manager, the Home Assistant add-on, TrueNAS — the upgrade page now points straight to that platform's own update flow instead of offering an upgrade path that could not complete.
    • Mobile app (Android / iOS) update: the automation editor gains the "Notification channel" action — pick a channel, write the message, attach the snapshot, @everyone — matching the web; rule cards wrap channel tags onto multiple lines when several are attached.
  4. v0.9.49Highlight

    Automation notifications can carry the live snapshot · fall mute now covers webhooks / bots · drag-and-drop camera ordering · new "Starting" service state

    • Webhook and bot notifications from automations can now embed the actual snapshot: messages could previously only carry a snapshot link, which recipients (especially off-site or on third-party platforms) often couldn't open because it points into your home network. A new "Snapshot image data" variable embeds the annotated snapshot straight into the webhook body or MQTT payload. The WeCom bot gains an "Attach event snapshot" switch that sends the picture right after the text message (off by default; a failed attachment never blocks the text, and the run log shows what happened). DingTalk, Feishu and other bot messages can now also include the snapshot link, viewable from inside your network.
    • The fall "don't notify when on a bed/sofa" switch now applies to automations too: it used to cover phone and desktop alerts only, while webhooks and DingTalk / WeCom / Feishu / Bark bots configured in automations still fired. Actions for falls the double-check judges to be on a bed or sofa are now skipped as well; every other verdict, plus timeouts and errors, still fires. Also, when a fall action references the event summary, it now waits for the double-check description (up to about 10 seconds) instead of sending an empty summary.
    • Drag-and-drop ordering on the camera management page: the list order was fixed to the order cameras were added, so there was no way to put "Front door" first. Click "Reorder" to open a card grid, drag cards (long-press on touch screens) or nudge them with the arrows, then save. This only affects the management page itself; the live wall and the phone home screen keep their own layouts.
    • New "Starting" service state: while AI detection loads its models (seconds to a few minutes), the service page used to show it as "Stopped", which was especially confusing right after toggling it off and on. That period now shows as "Starting (loading recognition models)" and flips back to "Running" automatically.
    • Two "nothing happened when I clicked" fixes: ① when the disk is full, feature toggles couldn't be written down, so a feature you had just enabled (AI detection, face recognition, etc.) stayed idle until a restart — it now falls back to reading settings directly and starts as expected; ② "Resume all" on the AI detection page did nothing for cameras still in automatic back-off (up to an hour of waiting); it now retries immediately, just like toggling a single camera.
    • Text in the desktop-style web UI can finally be selected and copied: event summaries, RTSP addresses, log lines and device info were unselectable anywhere on the desktop. Window content can now be selected normally, while dragging windows and widgets still doesn't select text by accident.
    • Mobile app (Android / iOS) update: the automation editor gains the "Snapshot image data" variable and the WeCom "Attach event snapshot" switch, and bot messages can include the snapshot link — matching the web.
  5. v0.9.48

    Fall mute switch now applies to desktop alerts too · no more lingering high CPU after a stutter · RK3588 frame-drop and reboot fixes

    • The fall "don't notify when on a bed/sofa" switch now applies to desktop alerts too: with the switch on, phones correctly stayed quiet, but the desktop alert on the web and browser notifications still fired. Both now honour the switch: alerts the double-check judges to be on a bed or sofa no longer interrupt you, while every other verdict — plus timeouts and errors — still alerts as usual. We would always rather over-alert than miss a fall.
    • Fall event summaries no longer mention a "red box" that isn't in the picture: the double-check marks the person in question so the AI locks onto the right subject, but that marker was leaking into the summary text (e.g. "the child in the red box is sitting on the bed") while you could see no such box in the frame. Summaries now describe only the person and the scene.
    • A single stutter no longer leaves a camera burning CPU: previously, a few consecutive stream failures on one camera (typically a network hiccup or a camera reboot) permanently dropped that camera to the far more CPU-hungry decoding path until a restart. With several cameras degraded, load stayed pegged and streams got even less stable — a vicious circle. Hardware acceleration is now retried automatically at gradually increasing intervals, so a passing hiccup recovers on its own, while a stream that genuinely can't be accelerated settles down instead of flapping.
    • RK3588 build fixes: multiple streams dropping to a few frames per second, or freezing outright, while AI detection was also running is fixed (several decoding components on the same device were running mismatched versions and interfering with each other). On devices with more than 4GB of memory, the last known path to a full device reboot under memory pressure is now closed.
  6. v0.9.47Highlight

    One-click upgrade "can't pull image" fix · fall double-check verdict in the event summary · one-tap AI connectivity test · RK3588 crash fixes

    • One-click upgrade fix: on deployments using the manual compose templates (image name without a registry address) or the older image naming, tapping "Upgrade" pulled from the wrong registry and only failed after a long timeout. The correct image address is now derived automatically. ⚠️ Since the fix ships in the new version, affected users need one more manual upgrade (docker compose pull && docker compose up -d); one-click upgrades work normally from then on. Installs done with the one-line install script are not affected.
    • Fall double-check verdict now goes into the event summary: the cloud double-check conclusion (on a bed / on a sofa / down on the floor) used to be buried in the event details; it now shows as the event summary in the app, on web event cards and in Home Assistant, and is searchable. The check also tells "squatting" and "standing, bent over" apart more reliably, and in multi-person scenes it locks onto the person who triggered the alert.
    • A toddler bending down to grab something no longer counts as a fall: without a visible drop, the alert now requires the child to stay lying flat for a while (about 10 seconds); a momentary bend or crouch won't trigger it. A real fall followed by lying still is still reported promptly.
    • "Test connection" on the AI analysis settings page: after configuring cloud or local AI, verify it in one tap — you see the response time, the model in use and a sample reply, instead of finding out the endpoint was misconfigured only when a real event arrives.
    • Desktop control panel catches up on settings: the two fall double-check switches and the WebRTC IPv6 switch were only on the classic settings page; the desktop version now has them too, and both views are aligned.
    • RK3588 build fixes: detection crashing every minute or two after switching to the sub-stream or auto stream is fixed; face, pose and plate recognition occasionally receiving invalid frames is fixed (when hardware cropping fails it now falls back to the regular frame instead of using garbage data).
    • Mobile app (Android) update: fall event frames now draw the person's pose skeleton instead of just a box, so you can see at a glance whether they were lying, sitting or bending over; the app will prompt you to update.
    • Mobile app (iOS) update: the iPhone / iPad app moves to 0.9.47 (available once App Store review completes) and rolls up every mobile improvement since 0.9.38: fall events get their own filter, show the evidence behind the verdict and draw the person's pose skeleton; camera IR light auto / on / off; download progress for exported clips; DingTalk / WeCom / Feishu / Bark presets in automation actions; the free tier's settings page clearly marks what's free and what needs an upgrade; the pet sample picker uses cropped thumbnails; event thumbnail proportions fixed.
  7. v0.9.46

    Smart double-check for fall alerts · a batch of setup wizard install failures fixed

    • Fall alerts now get a cloud smart double-check: after an alert fires, cloud AI takes a second look at the frame to judge whether the person is on a bed or sofa versus actually down on the floor, and writes the conclusion into the event details. You can optionally mute push notifications when the double-check concludes bed/sofa (off by default; the event is still recorded and shown on the web as usual). If the check is uncertain, slow, or cloud AI isn't enabled, the alert goes out as usual — we would always rather over-alert than miss a fall.
    • "I drew an ignore zone but it still alerts" is now self-explanable: every fall event records how many fall ignore zones were loaded on that camera, where the judged position was, and whether it hit — so you can tell at a glance whether the zone didn't take effect or simply didn't cover the spot.
    • Setup wizard: a batch of "can't install" failures fixed: fresh installs choosing MySQL used to fail every time — fixed. When the database is temporarily unreachable, the system no longer restarts in a loop — a status page explains why and it recovers automatically once the database is back. "Test connection" now tells you upfront if the database version or charset is unsupported. The endless-redirect loop when opening from a NAS management panel, and the wizard silently spinning because of a leftover login session from a previous install, are both fixed.
    • Offline import of AI summary models via the web now works: real-size model packages previously always failed to upload. Packages that don't match your machine are now clearly rejected with a note on what's needed, instead of overwriting a working installation.
    • RK3588 build fixes: pose and fall detection was completely non-functional — fixed. Two issues that could occasionally freeze or reboot devices with more than 4GB of memory are fixed.
  8. v0.9.45

    Fall alerts: several classes of missed falls fixed, false alarms tightened

    • Several falls that previously went unreported now alert: the camera briefly losing sight of someone who has gone down, falling again shortly after getting up, falling behind a table or other furniture, and someone already on the floor when the system starts or when they enter the frame (lying across the view, or head towards the camera). Lying head-away with no reference at all still can't be judged — a limit of the viewpoint itself.
    • False alarms tightened alongside: sitting down at a table or bending over no longer triggers; toddlers crawling and squatting still don't alert — only lying visibly flat and still for a while does.
    • Fuller logs for this area: if an alert fired wrongly or failed to fire, exporting the logs lets us pinpoint the exact reason.