HoverCam Hub
Instala el hub
El hub es el pequeño programa que conecta tus cámaras y tu grabador con la app HoverCam. Instálalo una sola vez en una computadora de tu casa que quede encendida, en la misma red que tus cámaras. Sin abrir puertos y sin pagar por grabación en la nube.
●Última versión: 1.0.17· 19 nov 2026
Windows
Windows 10 u 11 de 64 bits
- Abre Inicio, escribe PowerShell, haz clic derecho y elige Ejecutar como administrador.
- Pega este comando y presiona Enter:
irm https://hovercam-api.hoverlayer.com/install/hub.ps1 | iexMac
macOS 12 o más reciente, con Homebrew (brew.sh)
- Abre Terminal (Aplicaciones › Utilidades).
- Pega este comando y presiona Enter:
curl -fsSL https://hovercam-api.hoverlayer.com/install/hub.sh | bashLinux y Raspberry Pi
64 bits: Ubuntu 22.04+, Debian 12+, Raspberry Pi OS (Bookworm) en una Pi 4 o 5
- Abre una terminal.
- Pega este comando y presiona Enter:
curl -fsSL https://hovercam-api.hoverlayer.com/install/hub.sh | sudo bashDespués, vincúlalo
- 1Al terminar, el instalador muestra un código de vinculación de 8 caracteres (también está en http://localhost:8099 en esa computadora).
- 2En la app HoverCam toca Add hub (Agregar hub) e ingresa el código.
- 3Agrega tus cámaras o tu grabador desde la app. Listo.
Las actualizaciones son automáticas
- Tu hub busca versiones nuevas y las instala solo en un momento tranquilo, nunca mientras alguien ve una grabación.
- Cada actualización está firmada por HoverLayer; el hub rechaza cualquier otra.
- Si una versión nueva no arranca, el hub vuelve solo a la anterior.
- La app muestra la versión de cada hub en Menú › Hubs & updates.
Qué necesitas
- Una computadora que quede encendida: PC con Windows, Mac, mini PC o Raspberry Pi 4/5.
- 8 GB de RAM para ver grabaciones en el teléfono (4 GB alcanzan para en vivo y alertas).
- La misma red de tu casa que tus cámaras o NVR (cable o Wi-Fi).
- Una cuenta de HoverCam: gratis 30 días, después $5.99/mes o $59/año para toda la casa.
Historial de versiones
- 1.0.1719 nov 2026
Panic: same video as the live view for viewers that play H.265; H.264 fallback Re-encoding every camera at once overloaded the Pi and dropped the feeds. iPhone browsers play the cameras' H.265, so for them go2rtc relays each camera from its own local RTSP into a private per-viewer stream: no ffmpeg, full quality, every camera at once. Removing that stream still ends the video. Browsers without H.265, or a direct feed that fails, get the re-encoded H.264 feed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1619 nov 2026
Panic video: cheaper H.265 decode (skip loop filter) for all cameras at once Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1518 nov 2026
Panic: keep "H.264" in the no-answer error (a test checks it) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1418 nov 2026
Panic video: pass H.265 through for viewers that play it; lighter H.264 otherwise Re-encoding every H.265 camera at once overloaded the Raspberry Pi, so emergency views connected but showed "No picture". Viewers whose offer includes H.265 (Safari, the iPhone app) now get the camera video unchanged, at no CPU cost; others get a lighter 360p/12 fps H.264 feed. One feed per camera and kind, shared by viewers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1318 nov 2026
Release: builds upload to a draft release instead of Actions artifacts The account-wide Actions storage quota filled up and blocked releases (it only recounts every 6-12 hours). Builds now upload straight into a draft release (invisible to hubs), and publish signs the manifest and makes it a pre-release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1214 nov 2026
Panic video: use -timeout for RTSP (ffmpeg quit on -rw_timeout, so no video) -rw_timeout is not an RTSP input option; ffmpeg exits with "Option rw_timeout not found" before sending a frame, which is why every emergency camera answered 503. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1110 nov 2026
Hub reports why an update failed; a door sound error can't stop the hub - update.status: running/pending/skipped versions, the launcher's last failed start and the last traceback from console.log, with camera URLs and passwords removed. - Errors in door sound handling are logged instead of crashing the hub (a crash three times in a row made the launcher give up on a new version). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.1010 nov 2026
Alarm: motion in Away, entry delay with countdown chimes, exit delay - Selected motion sensors sound the alarm in Away (never at Home or in Night). - Entry delay (default 30 s, 0–180): an armed door or motion sensor starts a countdown that chimes every 10 s; disarming in time cancels it, otherwise the full alarm sounds. Later triggers join the running countdown. Sensors marked instant skip it. - Exit delay (default 60 s, 0–300): right after Night/Away is applied here, triggers are ignored so people can leave. A restart doesn't restart it. - Status reports motion sensors, entry_delay_supported and entry_remaining_s. - Settings an older app doesn't send are kept, not reset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.99 nov 2026
Release: ready-made cryptography only, and a crypto self-test in the smoke test On the Intel Mac runner pip compiled cryptography against Homebrew's OpenSSL, and the bundled app loaded Python's older libssl instead ("Symbol not found: _SSL_get0_group_name"), so the packaged hub crashed at start once backups imported it. Signed-update verification had the same latent problem (imported lazily). Builds now take only the official wheels (OpenSSL built in), and the smoke test runs `hovercam-hub --self-test` (backup seal/unseal plus an Ed25519 check). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.89 nov 2026
Panic: private, revocable live relay for emergency camera sharing Panic viewers never get a normal camera peer. The hub relays the camera through its own ffmpeg feed into a private go2rtc stream it can cut off: video stops when the viewer stops renewing (30-second lease), at the 30-minute limit, when the incident is revoked, or as soon as the hub loses its cloud connection. Video only, receive-only offers, loopback-only feed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.78 nov 2026
Night and Away door arming with Home disarm
- 1.0.68 nov 2026
Temperature warning chimes and measurement freshness
- 1.0.57 nov 2026
Fix paired-siren discovery and missing sound details
- 1.0.47 nov 2026
Home door chime and Away alarm
- 1.0.36 nov 2026
Release: build the Apple silicon hub on macos-15 GitHub retired the macos-14 runners ("The configuration 'macos-14-arm64-us-xl' is not supported"), which cancelled the v1.0.3 release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.21 nov 2026
Z-Wave: temperature and humidity readings (e.g. Zooz ZSE44) Multilevel Sensor readings are kept per device in °F (converted from °C when the device reports Celsius) and sent with the device list; the cloud compares them with the owner's limits. Temperature-only devices show as "climate". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUsNe46pFfrhK4Pq6SnaQP
- 1.0.127 oct 2026
Update now from the app
- 1.0.027 oct 2026
First release
Desinstalar el hub
Windows: en PowerShell como administrador ejecuta $env:HOVERCAM_UNINSTALL='1' y luego el comando de instalación otra vez. Mac/Linux: agrega -s uninstall después de bash (por ejemplo … | sudo bash -s uninstall).
¿Preguntas? Escríbenos a support@hoverlayer.com