In short
- 7.2.101 is a point release on the 7.2 branch. Two bug fixes, one notice, nothing else new.
- Both faults touch only the new evidence tools, Case Manager and Evidence Trust. If you don't use them, you won't notice the update at all.
- The point people confuse: 7.2.101 is not the 7.2 feature update. Recording settings have lived centrally in the Recording Manager since 7.2.
What 7.2.101 actually contains
The change list is short. Two faults were fixed, plus a notice that recalls an earlier change. That is all.
The first fault: case exports from the Case Manager could remain stuck at "Preparing" and never finish. If you assembled an incident into a case file and tried to export it, you got no file — just a status that never moved.
The second fault: large downloads could fail when Evidence Trust was enabled — the cryptographic safeguard that signs every clip. Ubiquiti does not say from what file size this started.
Both bugs stem from the same two functions: Case Manager and Evidence Trust. Both arrived only with Protect 7.2. If you don't use them, you were never affected, and you won't notice the update at all.
Why it stays invisible on most sites
This is the decisive point for judging the release. 7.2.101 brings no new camera function, no better image quality, no new recording mode. It clears two obstacles from tools aimed at securing evidence.
A typical villa with eight cameras that simply record and send a motion alert usually doesn't touch Case Manager or Evidence Trust at all. For a site like that, 7.2.101 is a maintenance update with no visible effect. Install it, let it run on — that is enough.
It gets interesting where someone genuinely prepares footage as evidence: incidents on a company site, repeated break-ins at a holiday complex, anywhere recordings are meant to become a solid file. Those exact workflows were the ones affected by the two faults.
Don't confuse the layers: 7.2 versus 7.2.101
Here is where the most common error creeps in. The version number 7.2.101 looks like "7.2 plus something." It isn't. It is the third decimal on a branch whose real changes already arrived with 7.2 in late July.
What 7.2 delivered is the context in which 7.2.101 makes any sense at all:
- Recording Manager: recording and encoding settings have been managed centrally since 7.2, including for ONVIF third-party cameras — no longer per camera. That is exactly what the notice in 7.2.101 points to.
- Evidence Trust: every clip is given a SHA-256 fingerprint on recording and digitally signed. Authenticity can be checked externally at evidence.ui.com; altered clips are flagged.
- Case Manager: formal case files with assigned footage, an access and download log, and a chain-of-custody trail.
- Plus time synchronisation of third-party cameras via the UniFi time server, and I/O trigger workflows.
Install 7.2.101 and then go looking for the big functions, and you are looking on the wrong layer. They have been there since 7.2. 7.2.101 only patches two of them.
Where we advise caution
Evidence Trust and Case Manager address a real need: footage that holds up against an insurer or in court. The SHA-256 fingerprint is a solid technical foundation for that.
Here we deliberately state what we do not know. Whether a SHA-256-signed UniFi export is accepted as evidence before a Spanish court or by a Spanish insurer is unresolved. We found no proof either way. So don't be quick to call the material "court-proof" — have the question clarified by a lawyer first.
The same goes for data protection. Video surveillance on a property in Spain falls under LOPDGD and GDPR: signage obligations, purpose limitation, limited retention periods. That is not a topic of the update, but it belongs in every plan. Whoever builds a system should factor in the legal side from the start, not afterwards. That is part of what separates a properly planned project from a hastily assembled row of cameras.
What to check after every Protect update
Regardless of 7.2.101, one rule gets overlooked far too often: after an update, recordings do not automatically carry on unchanged. Updates can reset recording profiles or motion detection. Individual cameras sometimes jump to continuous recording without being asked. Gaps appear in the timeline that only surface when you need the footage.
So: after the update, check on two or three cameras that recording is actually happening and the mode is correct. That is the short check that prevents a silent failure. Skip this step, and you often notice the fault only when it is too late.
For a larger site with many cameras, that is precisely why maintenance shouldn't be left to chance. Applying an update takes minutes; confirming everything still runs as before is the real work. What that kind of ongoing care looks like is shown in our references.
What to check after updating to 7.2.101
- Is recording verifiably still running on two or three cameras?
- Is the recording mode still correct, or has a camera jumped to continuous recording?
- Do you use Case Manager or Evidence Trust? Only then does the update concern you at all.
- Look for recording settings in the Recording Manager, no longer per camera.
- Before relying on any clip as evidence: have its legal standing in Spain clarified by a lawyer; assume nothing is "court-proof."
If you are planning a camera system on the island, or want an existing one looked after — from the first cable run to maintenance years later — get in touch. For a slow laptop or a single camera at the front door we are the wrong people; for a well-thought-out system that still does its job in ten years, we are the right ones.
Related reading
German-speaking IT service for fincas, villas and businesses on Mallorca. Networks, Wi-Fi, security technology and smart home — planned, installed and maintained.