Repository navigation
0.7.7 — Fix high-CPU/no-reconnect after a camera drop (wraps neolink 0.7.5)
Stable release wrapping neolink 0.7.5.
- High CPU / no-reconnect after a camera drops, fixed. The add-on could peg the CPU and go silent right after
Connection Lost … Attempt reconnect, with the camera not coming back until a restart. The per-camera MQTT handler was restarting in a tight no-backoff loop, flooding the broker and spinning the MQTT client until the runtime starved. It now backs off before restarting, drops and reconnects a spinning connection, and has a poll-rate-cap failsafe. - Snappier, more robust live view. Once a stream's codec has been seen, reopening it builds and serves the pipeline immediately while the camera connects in the background; a brief camera drop resumes into the same session without the card reconnecting. RTSP client setup is time-bounded and self-cleaning, so a slow/offline camera can't stall the server or leave stale mounts.
- Hardened against malformed camera data — bounded protocol resync, stricter audio-frame parsing, and recovery of dropped packets at stream start.
- Docs: added a Home Assistant integration guide (go2rtc / WebRTC / MSE / HLS, H264/H265 + AAC, and the camera-side GOP and CBR/VBR trade-offs).
No add-on configuration changes are required.