-
-
Notifications
You must be signed in to change notification settings - Fork 260
HomeKit Troubleshooting
#Secure Video Not Recording
If recordings dont work, it's generally because of a few reasons, follow the steps to determine where it is failing before asking for help:
-
The motion wasn't triggered. You can view if there are motion events in the camera "Events" section.
-
After a motion trigger, the home hub will start recording. Verify that HomeKit is requesting recording by looking in the Camera's Console: you will see logs such as
[HomeKit]: Camera recording session starting
. Sometimes the home hubs bug out and stop responding to motion. Try rebooting the home hub(s) when this happens. iPads and HomePods, which are wireless, are not reliable home hubs. -
The recordings are in a bad format that can't be used by HomeKit. See below for optimal HomeKit Codec Settings. Enabling Transcode Recordings may fix this for testing purposes, but long term usage is not recommended as it reduces quality and increases CPU load.
-
HomeKit decided the motion wasn't worth recording. Set your HomeKit recording options to all motion when testing.
-
If your camera is on a separate VLAN, try disabling that to see if that is the issue.
If HomeKit is not discoverable, make sure LAN/WLAN multicast is enabled on your router. If HomeKit fails while pairing during a Docker install, ensure host networking is being used.
This is a networking issue with multiple interfaces. This is the problem 100% of the time. Use the HomeKit Address Override setting, and set it to the IP Address of your ethernet manually. If your camera is on a separate VLAN, try disabling that to see if that is the issue.
Scrypted Docs have moved. Please visit https://docs.scrypted.app.