The app
The app is an ordinary viewer for OpenIPC cameras: at home it works with them directly, with no cloud involved at all. The cloud is added by one setting and changes exactly one thing – the cameras stay available when you are not at home.
The app build, like the agent, comes from the owner of the instance: ask in the beta chat.
Connect the cloud
Settings → "Cloud (Streq)":
- Server URL – the address of the cloud,
https://cloud-api.openipc.ru, without the/v1at the end: the app appends that itself. - Access token – a token for the app. Issue one to yourself in the panel: "Sign-in" → "Sessions" → "Issue a token", having named the client (say, "viewer"). A token per application is not a formality: signing out of the panel then leaves the app running, and a lost phone is revoked by one line in the session list.
- "Check and save" – the app calls the cloud and shows you who you are signed in as.
The token is kept in your system's secret store, not in a settings file next to the cameras. "Disconnect" erases it; the cameras' bindings stay.
Bind a camera to its cloud node
Each camera has its cloud node set in the same section (Cloud node id → "Bind"). The node's id is in the panel, under "Devices and network". Until a camera is bound, the app knows only what it knew before – that is, it works with the camera at home only.
What happens after that
The app picks the route itself, and there is no "I am away" switch in it:
- At home – straight to the camera. The cloud is not involved: it would add nothing but latency.
- Away – over a connection to the camera itself that the cloud brokers. What plays is the camera's own bytes, under its own password, and the cloud never sees that password.
- When that is not possible – the camera advertises no RTSP, or your access does not cover it – through the cloud's relay.
Away from home you get: viewing, pan-tilt and presets, the camera's settings, and SSH. That last one belongs to the device owner only: no grant ever carries it, and that is the cloud's rule rather than the app's (see Control away from home).
If something is wrong
| Symptom | Usually | What to do |
|---|---|---|
| "Invalid token" when saving | the token expired, or belongs to another instance | ask the owner for a new one |
| An error about the server address | /v1 was left in the address | remove it: the app appends it itself |
| A camera plays at home and is silent away | it is not bound to a cloud node | put in the node id and press "Bind" |
| No controls or settings away from home | no control / configure verb | check what access you have to the device |
| SSH is unavailable while everything else works | you are not the device owner | that is by design: no grant carries shell |