You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 18, 2026. It is now read-only.
I've been having this issue for a while -- it seemed as though the more recent connection fixes had addressed it (at least they did in beta), but since release, I'm having it again.
The status on my camera nodes gets stuck at "Initialized" - the easiest way I've found to get it out of that state is to change some element (reconnect/heartbeat time, or even just the name) on the unifi-access-controller configuration node, save, then deploy.
I've played with the heartbeat/reconnect times a bit (didn't seem to solve it) before going back to default.
I'm running a UDM-SE with UniFi OS 4.0.20 and Protect 5.0.34.
Please let me know if there's anything I can do to help troubleshoot this further.
I've been having this issue for a while -- it seemed as though the more recent connection fixes had addressed it (at least they did in beta), but since release, I'm having it again.
The status on my camera nodes gets stuck at "Initialized" - the easiest way I've found to get it out of that state is to change some element (reconnect/heartbeat time, or even just the name) on the unifi-access-controller configuration node, save, then deploy.
I've played with the heartbeat/reconnect times a bit (didn't seem to solve it) before going back to default.
I'm running a UDM-SE with UniFi OS 4.0.20 and Protect 5.0.34.
Please let me know if there's anything I can do to help troubleshoot this further.