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
Transfer devices
Import and export transfer saved connections between Watchpost installations. They do not copy the recordings inside a camera or recorder. These tools may require a license that includes work tools in your build.
Export to a file
Section titled “Export to a file”On Mac, choose Devices → Export Devices…. You can export the whole registry or selected devices. Mobile apps offer export from Devices.
Review the options before creating the file:
- Choose which devices to include, grouped by site.
- Decide whether to include saved passwords. An owner check may be required.
- For your own file, choose whether to include configuration snapshots and which history to include.
- Decide whether to include places and the camera layout.
- Set and repeat the file password.
Save the .watchpost file and retain its password separately. The password is not stored in the file and cannot be recovered from it. Without included device passwords, the receiving app will need credentials before it can connect.
Your copy or another person’s access
Section titled “Your copy or another person’s access”The Apple export form distinguishes a copy for yourself from a file for another person. Your own copy can include router private keys when passwords are included. An export for another person excludes router private keys and the hub administrator token, and can request that person’s own access tokens from the sites’ hubs.
Do not use a full copy for yourself as a substitute for granting access to someone else. Review the recipient and the included secrets before transferring the file.
Import and review
Section titled “Import and review”On Mac, choose Devices → Import Devices…. On mobile, use import from Devices or open a supported file in Watchpost.
- Select the file and enter its password.
- Review new devices, existing matches and entries that differ from saved ones.
- Choose the action for differing entries; do not assume every device needs another copy.
- Review sites, account references, places, password handling and whether imported devices should appear in Live or Cameras.
- Confirm the import, then check a connection before relying on the new list.
A site route or cloud-account reference may still require working access on the receiving installation. Importing a device entry does not create permissions on the device itself.
Transfer with a QR code
Section titled “Transfer with a QR code”The Apple export form also offers a QR destination. The code carries device cards, sites and any included passwords. Configuration snapshots, the camera layout and site plans transfer only in a file. Set a code password and share it separately.
For a larger payload, the app can show a changing series of QR frames. Keep the code visible until the receiving scanner has collected enough frames. If the data is too large, reduce the selection or use a file.
Use Watchpost’s QR import or scanner on the receiving device. Mac also offers Import from QR Image…. Opening a Watchpost import link leads to the same review; it does not silently replace the registry. Android includes file transfer and QR scanning, but its export options are not identical to the Apple form.
See Share access to devices to choose between a personal file, Hik-Connect sharing and a Watchpost hub invitation, and to understand their separate revocation controls.