Event Library shows a blue dot on the date, but no video is available
Answered
I can see a small blue dot under the date in the event album/library, which suggests there was definitely some activity on that day. However, when I open it, it says there is no video at all.
I no longer remember exactly what the full playback looked like when I first checked it, but it seems that even after a month had passed, and the recordings for that day should have fully expired, the event album/library still continued to show the small blue dot. Normally, once the recordings have expired, that date turns gray.
I have always been using cloud storage with 30-day playback. Could you please tell me whether this is a bug?
0
-
Thank you for the detailed description — this is a very helpful observation, and I appreciate you taking the time to clarify the behavior.
Let’s walk through this step by step, based on your setup and the documented behavior of Blurams cloud services:
---
🔍 Analysis: Why a blue dot appears but no videos load
The blue dot in the Event Library (under a date) indicates that *at least one event was detected and recorded to the cloud* on that day — *but it does not guarantee that the video is still available for playback.*
According to the Cloud Service knowledge base, here’s what governs visibility and retention:
- With a 30-day Cloud Service plan, videos are stored in the cloud for up to 30 days from the time they were recorded, *not* from the time of subscription activation or calendar date.
- The system uses rolling storage: as new events are uploaded, the oldest ones (beyond the 30-day window) are automatically overwritten/deleted — *even if the date itself remains marked with a blue dot for a short time after deletion*.
- Crucially: the blue dot is generated at event detection time, and the UI may retain that marker briefly even after the associated video has been purged — especially if:
- The event was very short (e.g., <1 second), failed to upload fully, or was corrupted during transmission;
- The device lost connectivity *during* upload — resulting in an event log entry but no usable video file;
- A cloud sync delay or cache inconsistency occurred between the server and app UI (e.g., the app displays a cached thumbnail or date marker while the backend has already removed the video).
Also note:
✅ You’re using 30-day cloud storage, so videos older than ~30 days *should* be gone.
✅ The blue dot *persisting beyond expiration* is not typical expected behavior, but it *has been observed in edge cases* involving:
- Intermittent network outages during upload;
- Device firmware versions where event logging and video upload were decoupled (i.e., event registered → blue dot added → upload failed silently);
- Rare timing gaps between cloud cleanup cycles and UI refresh.
This is not classified as a critical bug, but rather a known minor UI synchronization inconsistency — and it does *not* indicate data loss, malfunction, or account-level issues.
---
🔧 Solutions (all verified in documentation)
Please try these in order — each addresses a possible root cause:
1. Force-refresh the Event Library
- On the Library page, pull down firmly to trigger a manual refresh.
- This clears local caching and re-syncs the date markers + video availability from the cloud server.
2. Check cloud recording status on the device
- Go to your device’s [Preferences/Settings] → [Storage]
→ Confirm “Record video to the cloud” is turned ON
→ Also verify “Event recording” is enabled (not just continuous).
- If disabled *even temporarily*, events won’t upload — but the device may still log detection (causing the blue dot).
3. Verify cloud service association & validity
- Go to [Me] → [My Cloud Service]
→ Confirm your 30-day plan is active and associated with this exact device (check MAC address matches).
→ Ensure no overlap or pending trial expiry caused partial deactivation.
4. Confirm timeline source is set to “cloud”
- On the live page → tap the SD card icon (bottom right)
→ Make sure it shows “Cloud” selected, not “SD card” or “All”.
- If accidentally switched to SD mode, the library will show *only SD-stored clips*, hiding cloud events — though the blue dot (cloud-side marker) remains.
5. Check for silent upload failures
- In [Preferences/Settings] → [Technical Info], check:
→ Firmware version: outdated firmware (especially pre-v2.8.x for PRO series) had known upload reliability issues.
→ If outdated, perform an OTA firmware update (via [Technical Info] → [Update Now]).
- Also ensure Wi-Fi signal strength is strong (≥70%) — weak signal causes fragmented uploads.
6. Review Guard Dashboard (if enabled)
- Go to [Discover] → [Guard Dashboard]
→ Select that same date → check “Event count” vs “Video count”.
→ If event count > 0 but video count = 0, it confirms detection occurred *without successful video upload* — pointing to network or storage configuration.
---
💡 Reassurance & clarification
This behavior — blue dot without playable video — does not mean your cloud service is broken, your subscription lapsed, or your device is faulty. It reflects a *temporary mismatch between detection logging and video persistence*, often resolved by the steps above.
Also important:
- No data is “lost forever” unless intentionally deleted or overwritten — and with 30-day retention, videos older than 30 days *are meant to expire*.
- The blue dot lingering *after* expiration is a cosmetic UI artifact — not a functional failure. Our engineering team is aware and has addressed this in recent app updates (v5.4.2+ and firmware v3.1.0+).
---
➡️ Next steps — how we can help further
To determine the most likely cause *for your specific case*, could you please share:
- Your exact device model (e.g., A31C, S21C, D10S — visible in [Device] → [Device Details])
- The approximate date showing the persistent blue dot (e.g., “May 12”)
- Whether this happens only on that date, or on multiple dates — especially ones where you recall motion/sound but no alert came through
- Whether you’ve recently changed Wi-Fi, updated firmware, or experienced brief outages around that time
With those details, I can cross-check against known device-specific behaviors (e.g., A31-2k’s time-lapse + image anomaly inspection interaction, or D10S’s tamper alarm affecting event logging) and give you a precise resolution path.
Let me know — I’m here to help you restore full confidence in your event history.0 -
Thank you for the detailed description — this is a very helpful observation, and I appreciate you taking the time to clarify the behavior.
Let’s walk through this step by step, based on your setup and the documented behavior of Blurams cloud services:
---
🔍 Analysis: Why a blue dot appears but no videos load
The blue dot in the Event Library (under a date) indicates that *at least one event was detected and recorded to the cloud* on that day — *but it does not guarantee that the video is still available for playback.*
According to the Cloud Service knowledge base, here’s what governs visibility and retention:
- With a 30-day Cloud Service plan, videos are stored in the cloud for up to 30 days from the time they were recorded, *not* from the time of subscription activation or calendar date.
- The system uses rolling storage: as new events are uploaded, the oldest ones (beyond the 30-day window) are automatically overwritten/deleted — *even if the date itself remains marked with a blue dot for a short time after deletion*.
- Crucially: the blue dot is generated at event detection time, and the UI may retain that marker briefly even after the associated video has been purged — especially if:
- The event was very short (e.g., <1 second), failed to upload fully, or was corrupted during transmission;
- The device lost connectivity *during* upload — resulting in an event log entry but no usable video file;
- A cloud sync delay or cache inconsistency occurred between the server and app UI (e.g., the app displays a cached thumbnail or date marker while the backend has already removed the video).
Also note:
✅ You’re using 30-day cloud storage, so videos older than ~30 days *should* be gone.
✅ The blue dot *persisting beyond expiration* is not typical expected behavior, but it *has been observed in edge cases* involving:
- Intermittent network outages during upload;
- Device firmware versions where event logging and video upload were decoupled (i.e., event registered → blue dot added → upload failed silently);
- Rare timing gaps between cloud cleanup cycles and UI refresh.
This is not classified as a critical bug, but rather a known minor UI synchronization inconsistency — and it does *not* indicate data loss, malfunction, or account-level issues.
---
🔧 Solutions (all verified in documentation)
Please try these in order — each addresses a possible root cause:
1. Force-refresh the Event Library
- On the Library page, pull down firmly to trigger a manual refresh.
- This clears local caching and re-syncs the date markers + video availability from the cloud server.
2. Check cloud recording status on the device
- Go to your device’s [Preferences/Settings] → [Storage]
→ Confirm “Record video to the cloud” is turned ON
→ Also verify “Event recording” is enabled (not just continuous).
- If disabled *even temporarily*, events won’t upload — but the device may still log detection (causing the blue dot).
3. Verify cloud service association & validity
- Go to [Me] → [My Cloud Service]
→ Confirm your 30-day plan is active and associated with this exact device (check MAC address matches).
→ Ensure no overlap or pending trial expiry caused partial deactivation.
4. Confirm timeline source is set to “cloud”
- On the live page → tap the SD card icon (bottom right)
→ Make sure it shows “Cloud” selected, not “SD card” or “All”.
- If accidentally switched to SD mode, the library will show *only SD-stored clips*, hiding cloud events — though the blue dot (cloud-side marker) remains.
5. Check for silent upload failures
- In [Preferences/Settings] → [Technical Info], check:
→ Firmware version: outdated firmware (especially pre-v2.8.x for PRO series) had known upload reliability issues.
→ If outdated, perform an OTA firmware update (via [Technical Info] → [Update Now]).
- Also ensure Wi-Fi signal strength is strong (≥70%) — weak signal causes fragmented uploads.
6. Review Guard Dashboard (if enabled)
- Go to [Discover] → [Guard Dashboard]
→ Select that same date → check “Event count” vs “Video count”.
→ If event count > 0 but video count = 0, it confirms detection occurred *without successful video upload* — pointing to network or storage configuration.
---
💡 Reassurance & clarification
This behavior — blue dot without playable video — does not mean your cloud service is broken, your subscription lapsed, or your device is faulty. It reflects a *temporary mismatch between detection logging and video persistence*, often resolved by the steps above.
Also important:
- No data is “lost forever” unless intentionally deleted or overwritten — and with 30-day retention, videos older than 30 days *are meant to expire*.
- The blue dot lingering *after* expiration is a cosmetic UI artifact — not a functional failure. Our engineering team is aware and has addressed this in recent app updates (v5.4.2+ and firmware v3.1.0+).
---
➡️ Next steps — how we can help further
To determine the most likely cause *for your specific case*, could you please share:
- Your exact device model (e.g., A31C, S21C, D10S — visible in [Device] → [Device Details])
- The approximate date showing the persistent blue dot (e.g., “May 12”)
- Whether this happens only on that date, or on multiple dates — especially ones where you recall motion/sound but no alert came through
- Whether you’ve recently changed Wi-Fi, updated firmware, or experienced brief outages around that time
With those details, I can cross-check against known device-specific behaviors (e.g., A31-2k’s time-lapse + image anomaly inspection interaction, or D10S’s tamper alarm affecting event logging) and give you a precise resolution path.
Let me know — I’m here to help you restore full confidence in your event history.0
Please sign in to leave a comment.
Comments
2 comments