Create the administrator
This is BombeCam's own sign-in. Phones, tablets and other computers on your network always need it to open BombeCam. It has nothing to do with your Osaio logins.
BombeCam's saved information can't be opened (its key is missing or the file is damaged). Delete it to start again.
Sign in to BombeCam
Use BombeCam's administrator sign-in (not an Osaio login).
Forgot the password?
Try these first:
- Your hint:
- Your browser or password manager may have it saved: click the password box, or search it for "BombeCam" or this page's address.
- Check the name too (it is
adminunless you changed it) and that Caps Lock is off. - Lost your phone with the authenticator app? Enter one of your recovery codes where the code is asked for.
- Signed in on another device or browser? Change the password there under Settings → Sign-in settings.
BombeCam has no password reset: the password only changes under Settings → Sign-in settings. Without it, the way back in is to start BombeCam over: this deletes all of its saved data on this PC (the administrator, Osaio logins, cameras and settings), first removing its rules and key from your router if one is connected, and shuts BombeCam down. Start it again to create a new administrator.
BombeCam has no password reset. Only the PC running BombeCam can start it over; it can't be done from this device.
Finish setting up on the PC
BombeCam has no administrator yet. Open BombeCam on the PC it runs on and create one; then you can sign in here.
Add your cameras
BombeCam makes your Osaio cameras (the ones you set up in the Osaio app, sold by Yoton, GNCC, Wolfang, Surfola and others) available on your own network (Home Assistant, NVRs, VLC). Your Osaio login is stored encrypted on this computer and used only to find and reach your cameras.
- In the Osaio app, create a second login (for example
yourname+cams@example.com). - From your usual login, share the cameras you want BombeCam to use with it (open the camera → Settings → Share).
- Enter the second login below, and keep using your usual login in the Osaio app.
A camera streams live video to only one viewer per Osaio login at a time. If BombeCam and the Osaio app use the same login, opening live view in the app stops BombeCam's video until the app's view closes. With separate logins both work at once. Your main password also stays on your phone, and un-sharing a camera cuts BombeCam off.
Osaio's cloud only answers requests signed with this key, and BombeCam has none it can use (see below). Paste a working key; it is saved on this computer. If you saved cameras before, BombeCam reconnects to them once the key is saved.
Osaio's cloud only answers requests that carry this app ID, and BombeCam has none it can use (see below). Paste a working app ID; it is saved on this computer. If you saved cameras before, BombeCam reconnects to them once the app ID is saved.
Connecting to Osaio...
Authenticating credentials and setting up local profile...
Discovered Cameras
Select the cameras you wish to stream and control locally through BombeCam:
Cameras
Cameras added to BombeCam on this computer. Their names come from the Osaio app.
Stream name is the readable part of the camera's address (rtsp://<this PC>:8554/name). Changing it means updating Frigate or Home Assistant; the camera-ID address keeps working. Remove stops the camera's local stream and forgets it; if your router limits it, BombeCam removes it from the router too.
Osaio logins
BombeCam keeps these Osaio logins, encrypted on this computer, and uses them only to find and connect to your cameras. Add another login to bring in the cameras it can see.
Which login should BombeCam use?
- Use a login only BombeCam uses: in the Osaio app, create a second login (for example
yourname+cams@example.com) and share your cameras with it from your usual login (open the camera → Settings → Share). - A camera streams live video to one viewer per Osaio login at a time. If BombeCam and the Osaio app use the same login, opening live view in the app stops BombeCam's video until the app's view closes.
- If you change a login's password in the Osaio app, press Update password here. The new password is checked with Osaio before it is saved, and nothing else changes.
- Remove forgets the login and the cameras added through it. Other logins and their cameras are not affected. Un-sharing a camera in the Osaio app also cuts BombeCam off from it.
Stream addresses
Paste these into VLC, an NVR, Frigate or Home Assistant on your network.
Addresses use this PC's network address, so other devices can open them.
Ports on this PC
What other devices connect to. Ports can be changed on the Frigate / Home Assistant page.
Frigate & Home Assistant
Each camera's stream, ready to paste. The full guide covers controls in Home Assistant, snapshots, a stream password and ports.
config.yml)# Loading Frigate configuration...Loading Home Assistant steps...Block cloud video
Camera internet access is limited by destination and rate; encrypted traffic may still carry image data.
Needs: a GL.iNet or OpenWrt router that your cameras connect to, set to Router mode. Most internet-provider routers can't do this. Other ways to block camera traffic
- Loading...
On: the Osaio app can still control the camera (light, pan/tilt, night vision), under destination and rate limits. Encrypted allowed traffic may still contain image data. Off: the camera works normally. Turn a camera off for a while to update its firmware, then turn it back on.
Same network: a phone or tablet on the same network as a blocked camera may still show its live view in the Osaio app. The video then travels directly over your own network, not the internet, so the camera is still blocked from sending video out.
Router output
How it works
How the blocking works
- The rules live on the router your cameras connect to (not on this PC) and recognise each camera by its network (MAC) address. Each camera has its own switch.
- A blocked camera can still reach only:
- Osaio's control server (
mqtts02-us.osaio.net, port 8883, encrypted), so the Osaio app can still switch the light, pan/tilt and change night vision; - Osaio's stream-setup server (
wss-us.osaio.net) for the few kilobytes of connection details BombeCam needs to start a local stream; - DNS and time sync.
- Osaio's control server (
- All allowed internet traffic normally shares a cap of 4 KB/s per camera, with an 8 KB burst. Some fw3 routers use a 4-packet/s limit with an 8-packet burst instead; router status reports the cap mode. These limits reduce typical streaming, but cannot rule out images, fragments or low-rate video in allowed traffic.
- Other internet destinations are dropped, including the known Backblaze upload and Osaio relay destinations, and all IPv6. Content sent to an allowed destination remains subject to the rate limit.
- Traffic to devices on your own network, like this PC, is left alone, so local streaming keeps working. That includes the Osaio app on a phone connected to the same network: it may keep showing the live view, because that video goes directly over your network. Away from your network, the app's live view has to come through Osaio's relay servers, which a blocked camera can't reach. The router only allows, drops and bandwidth-limits traffic. Nothing is redirected or changed, and the camera itself isn't modified.
- When blocking turns on, the router clears that camera's open connections, so a connection it opened before the block can't carry on past the rules. The camera reconnects through the firewall by itself. If a connection outside the allowed list comes back straight away, the router reports that the block isn't working instead of showing Blocked.
- What Osaio can still see: that the camera is online, your internet (IP) address, and which commands are sent to it. The control channel is encrypted between the camera and Osaio, so the router can't read it; the router cannot determine whether its payload contains image data.
- Connecting the router: you enter the router's admin password once. BombeCam uses it for that one connection and never saves it. It installs its own key on the router, which can only turn camera blocking on and off (it can't open a login on the router). That is what lets the switches, and removing a camera, take effect right away.
What it requires
- A router that runs OpenWrt: a GL.iNet router on firmware 4.x, or OpenWrt 21.02 or newer. Older (fw3) and newer (fw4) OpenWrt firewalls both work; BombeCam detects which one the router uses.
- The router in Router mode, with the cameras on its Wi-Fi or LAN ports. In access point, extender or WDS mode it passes traffic through without routing it, and the rules can't see it.
- SSH turned on (it is by default on GL.iNet) and the router's admin password for connecting once.
- This PC on the same router, and each camera streamed to BombeCam at least once, so BombeCam knows its MAC address.
- Vendor hardware or network acceleration turned off on the router (GL.iNet calls it "Network Acceleration"). BombeCam handles OpenWrt's own offloading setting by itself and warns you if another accelerator is active, because accelerated connections can skip the bandwidth cap.
- Most internet-provider routers (for example Xfinity) can't run this. A small GL.iNet travel router plugged into your main router, with the cameras on its Wi-Fi, can. Other ways to block camera traffic compares the options.
Setup
- Connect the cameras and this PC to the OpenWrt or GL.iNet router.
- Open each camera's live view here once.
- Press Connect router and enter the router's address (GL.iNet routers use
192.168.8.1unless you changed it) and its admin password. - Turn on Block all cameras, or the switch for each camera you want blocked.
- Check it: in the Osaio app, switch the camera's status light. It should still respond. New cloud clips should stop appearing.
Disconnect removes everything BombeCam added to the router, including its key. Removing a camera from BombeCam also removes it from the router, and so does deleting all stored information.
Prefer to do it by hand? Download the router script, copy it to the router's /tmp folder, and run it over SSH:
sh /tmp/bombecam-router.sh apply yes --camera "Name=AA:BB:CC:DD:EE:FF"