These docs are not up to date yet. The app is moving faster than we can describe it. These pages cover Watchpost 0.1.0 alpha (build 444) and may be incomplete or out of date. Details
HTTP cameras
The Apple apps can receive MJPEG video from an HTTP camera. This is a separate connection type from ONVIF and RTSP. The current default uses the D-Link DCS-93x paths; it does not imply compatibility with every camera that has a web interface.
Add and test
Section titled “Add and test”In Add Device, choose the HTTP-camera option in the Protocol menu. Enter the camera’s address, web port, user name and password, then test the connection before adding it. The default port is 80.
The D-Link profile uses /video.cgi for video, /image.jpg for a snapshot and /audio.cgi for audio. A camera with different HTTP endpoints will not work just because it has the same web port. The current form does not provide a general-purpose editor for arbitrary HTTP paths.
Available features
Section titled “Available features”Use the live grid or open the camera separately. You can save a snapshot. Sound requires a supported audio stream from the camera.
HTTP connections have no archive, events, camera control or device-settings forms in Watchpost. To change the camera itself, use its own administration tools. If the same camera also supports ONVIF, that is a separate connection with different capabilities.
Android
Section titled “Android”HTTP-camera playback is not yet offered on Android. Receiving an imported record with HTTP settings does not make that connection supported there.