Built for integrators. Access control, video, networking, cable, alarm and fire on one quote. Pre-config on cameras and NVRs so gear shows up ready to install.
Security notice: it was disclosed today that some signing keys at certificate authority eMudhra were weak enough to recover. Fake sites and fake "signed" software can look real on out-of-date systems.
Update browsers, OS and phones. Patch NVR, camera and router firmware. Never click past a certificate warning.
Camera dropped off the NVR? Don't swap the camera first.
Check for an IP conflict. Ping the address with the camera unplugged. If something still answers, a second device has that IP and a new camera will drop the same way.
@ZephrFish@Ubiquiti Ubiquiti's Bulletin 070 covers it. AI Key 2.2.6 and earlier is affected and 2.2.8 or later fixes all six CVEs. If you've installed AI Keys for customers, check the firmware on each one.
@michaelbeal1@Ubiquiti Check the gateway first. The release notes list WiFi Uplink on four gateways that have a built-in WiFi radio, running UniFi OS 6.0.10 or newer. A console without WiFi still needs a separate backup link.
@michaelbeal1@Ubiquiti Matter in Network 11 is monitoring for now. UniFi shows the devices but doesn't manage them. For Thread devices, turn on mDNS and enable IPv6 on the VLAN where the border router lives. Session behavior on failover isn't documented yet, so test it.
@spanishmuscle@Ubiquiti Same boat for most gateways. Network 11 needs UniFi OS 6.0, and WiFi Uplink and Matter want 6.0.10 on the gateway itself. While you wait, check that mDNS is on and IPv6 is enabled on the VLAN your Thread border router sits on.
@RemyAlidarso@Ubiquiti Network 11 needs UniFi OS 6.0 on the console. Gateway releases on the public channel were still on 5.x at launch, so most consoles won't offer it yet. Back up before you take it. It moves every site to the zone-based firewall.
UniFi Protect AI Key owners: Ubiquiti's Security Advisory Bulletin 070 covers six CVEs in AI Key 2.2.6 and earlier. The fix is 2.2.8, which needs Protect 7.2 or newer. Update, then confirm your cameras come back in Protect.
https://t.co/jmTOvjs1dx
Network 11 is out. It won't size PoE for your cameras or plan your door access, so that still takes a site plan. WiFi WAN backup only runs on certain gateways, so check your model before you promise hotspot failover.
Introducing UniFi Network 11—our most impactful release yet.
🔹 30% greater device capacity
🔹 Real-time traffic visibility
🔹 SLA-based SD-WAN routing
🔹 WiFi WAN backup
And for the first time, UniFi is Matter-aware.
https://t.co/WK7nZF7Xi7
If the mount is loose, someone can pull it and get at the wiring behind it. Use the right anchors for the substrate, back it with a mud ring or box, and wire the tamper switch back to the panel so a pulled reader shows up as an alarm.
Fix the mount once and the callback stops.
Got a parts list for a job? Send it through our new Request a Quote page. One item per row, by SKU or a plain description like "4MP turret, 2.8 mm." We'll come back with a quote.
https://t.co/iGRW6brlvM
@zoecyber001 Practical or not, the fix exists. OSDP readers and controllers with Secure Channel on encrypt the reader link, and a tamper switch wired to the panel flags a pulled reader.
Wiegand sends badge data in the clear, in one direction, and the panel has no way to tell who else is on the wire.
The fix is already a standard. OSDP readers and controllers with Secure Channel turned on encrypt the reader link with AES-128 and supervise it. Wire the reader tamper switch back to the panel too, so a pulled reader raises an alarm.
If your doors still run Wiegand, put the swap on this year's plan.
Behind almost every RFID badge reader on an office wall is a four-wire cable: Ground, 12V, Data0, and Data1.
That cable runs the Wiegand protocol, which has zero encryption and zero authentication.c Even when an enterprise buys expensive smart badges with encrypted RFID chips, the reader decodes the signal and spits the raw card number down those wall wires in plaintext pulses.
If you pull the reader off the exterior wall, you can tap a tiny microcontroller like an ESP32 into Data0 and Data1. It can log every employee badge to memory and replay the exact pulse sequence back to the door controller to pop the lock on command.
NVR retention arguments lose at the counter because they only talk about days.
"30 days" is a storage number. The insurer or the lawyer asks something else. Can you export the clip and prove it wasn't altered? Can you show who handled it?
Badge readers rarely fail at the reader.
What the counter sees first:
A weak power supply or battery.
A loose termination at the controller.
A REX or strike out of adjustment.
A network drop.
Test the whole chain before you swap the head.
Quote the plant before the camera count.
Watts per head, plus headroom.
UPS runtime for the full PoE load.
IDF space and power.
Tested Cat6 inside 100 m.
Skip it and the camera line item becomes a change order. Bring the list to the counter and we'll run it with you.