Verification Request: @linanw/homebridge-mijia-remote-camera
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- devtools
Research direction
Read the verification requirements and related-plugin disclosures in the issue, then review the linked plugin repository and its 0.4.1 release. Assess the stated Linux x64 and locally supplied component requirements alongside the disclosed overlap with existing plugins. Done means the verification request receives a decision based on those limitations and the submitted evidence.
Written by the indexing model from the issue text.
Description
Plugin Name
@linanw/homebridge-mijia-remote-camera
Link To GitHub Repo
https://github.com/linanw/homebridge-mijia-remote-camera
Plugin Icon (Optional)
No response
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟢 Yes
The plugin successfully installs and does not start unless it is configured.
🟢 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
🟢 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
🟢 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
🟢 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
🟢 Yes
More Information
Review target: 0.4.1, published publicly on npm, with matching source and release. The repository is public with Issues enabled. No Homebridge Verified badge or approval is claimed.
Purpose and distinct functionality
This dynamic-platform plugin connects one selected supported Xiaomi/Mi Home camera through the account's remote camera transport and publishes an external native HomeKit camera. Camera and Homebridge may be on different networks. Its Homebridge settings page handles Xiaomi login, owned/shared-home discovery, camera selection and component import without requiring a TTY, special Homebridge startup flags or another relay container.
The single real device validated is a Xiaomi Smart Camera 3 Pro PTZ / C500 Pro using CS2/vendor 4 transport. Other models are not promised. Features include snapshots, live video, actual PCMA/Opus camera audio, talkback transport, night-vision control and finite direction steps on supported models. Optional independently registered Matter Camera and vendor metadata interfaces are experimental, use development attestation, and are not Matter-certified. There is no HSV, recording, motion-event or absolute PTZ position implementation. Physical camera-speaker talkback audibility and long-duration reliability remain limitations documented in the README.
Related verified projects, checked against the official list:
- Camera FFmpeg accepts a user-supplied FFmpeg source. This plugin obtains the supported Xiaomi remote source through account/home selection, without requiring a pre-existing RTSP URL.
- camera.ui targets RTSP sources and provides broader HSV/recording/motion management. This plugin instead addresses the Xiaomi remote transport, without claiming those broader features.
- homebridge-miot supports broad Xiaomi MIOT controls and camera devices. Its current CameraAccessory exposes a power switch, and CameraDevice monitors MIOT power/indicator/storage properties. Those camera classes do not implement a HomeKit streaming delegate; this request concerns remote video/audio/talkback and scoped cloud metadata.
We also disclose substantial overlap with homebridge-xiaomi-go2rtc, whose README documents local Xiaomi streaming/controls, go2rtc provisioning and broader architectures. It was absent from the official verified list checked for this request. Our remote backend and optional Matter/metadata integration address a different use case; we welcome the team's assessment of overlap.
The official form also identified homebridge-xiaomi-camera-native and its pending verification request #1289. It was not in the verified list at submission. Its README describes direct LAN MISS/CS2 video, snapshots and pan/tilt without a native camera SDK; it requires LAN access and excludes audio/two-way talk. Our remote-camera transport, audio/talkback and explicit Mi Home/Matter metadata are the relevant differences. Its existing functionality and pending request are disclosed for the team to assess.
Material installation and licensing limitation
Linux x64 only. Declared engines are Node ^22.13.1 || ^24.0.0 and Homebridge ^1.11.4 || ^2.0.0; the development dependency is Homebridge 2.4.0. ARM, macOS and Windows are unsupported by the pinned local runtime.
The public package contains MIT plugin source, our own Java adapter/source, configuration, provenance hashes and notices. It excludes micam, vendor/native components, JRE and FFmpeg. The known micam source has no license and the known FFmpeg build enables nonfree; no redistribution rights are asserted. See third-party notices.
The settings GUI asynchronously imports matching component files the user already holds inside Homebridge storage. It checks fixed hashes, preserves legal notices, rejects descendant symlinks/path escapes, and refuses to replace an active runtime. The trusted Homebridge storage root may itself be a directory alias, fixed in 0.4.1. There is no automatic component download. A new user without these local files cannot obtain working video from npm alone. Please assess this remaining component-availability/setup restriction explicitly. GUI import does not remove it.
Metadata scope and safety
The selected camera's Mi Home name/home/room is read every 60 seconds, with manual refresh and a persisted pause control. The settings page and supporting Matter vendor clients can rename the device or move it to an existing room of the same home. Writes require ownership of that home, a fresh matching editor baseline, one mutation without retry/session renewal, and an independent confirming read. Shared homes are read-only. There is no room creation/rename, cross-home move or home-root move.
Cloud-side edits update the same HomeKit accessory's name information without changing pairing or restarting video. Apple Home may retain its own alias; Apple Home's name/room edits are not written back to Mi Home. Matter metadata requires explicit vendor-client support and uses a 160-byte UTF-8 bound. This is not universal HomeKit/Matter room synchronization. Locally valid Unicode can still be normalized/rejected by Xiaomi; confirmation requires exact authoritative readback.
Validation for this release
- The public CI run passed all six combinations of Node 22.13.1 / current 22.x / 24.x and Homebridge 1.11.4 / 2.4.0 for commit
b0fcb441872d5fd38e6035b18a3967c9e7c49421. It uses fresh public dependencies and runs the unfiltered suite without proprietary assets; component-dependent tests explicitly skip. - Full local suites with already-held components and independent Matter controller integration: Node 22.22.1 and Node 24.19.0 / Homebridge 2.4.0 each ran 328 tests, 327 passed, 1 root-only ownership test skipped, 0 failures. These full-runtime results are separate from public CI.
- Anonymous registry verification on 2026-10-24 returned HTTP 200 for package index, version 0.4.1 and tarball; latest is 0.4.1. Tarball SHA-256:
548e53170d67547281373b1c43ac311f0732724c3729caaaa1f132dc138d069f. - A fresh nonroot installation of 0.4.1 from the public registry passed with lifecycle scripts disabled. The plugin has no install hook. Homebridge loads the unconfigured plugin and starts normally without creating its runtime, account session or camera. The package contains no vendor runtime assets. Its production
npm auditreported 0 vulnerabilities. - Synology DS1618+ Docker host-network deployment preserved credentials, selected camera and existing HomeKit pairing. The human user confirmed the settings GUI displays the new name/room controls. The actual Synology storage alias was accepted while a user-selected descendant symlink was rejected; no runtime components were replaced.
- Real owned-account metadata validation changed a temporary Chinese device name, independently read it back, then restored the original; moved between two existing rooms in the same home, independently read back, then restored the original room. Original name/room and credentials were preserved. An emoji name normalized by the cloud correctly returned
metadata_not_applied, rather than confirmed, and was restored. No automatic rollback is promised. - Real RPC readback also confirmed idempotent name/room operations advance the observation timestamp and preserve the active video source. Actual remote video decoded to a JPEG snapshot in memory without saving camera imagery. Earlier real-device testing confirmed Apple Home preview/live video, real Opus decode, HomeKit audio/talkback transport and a night-vision read/write/restore round trip.
- MatterDesk's native Qt editor was exercised through an isolated OHF Matter controller and real encrypted Matter sessions against synthetic metadata fixtures, including Chinese rename, room changes, stale baselines and incomplete state. The existing live controller retained all five nodes and its fabric when reloaded with the vendor interface. This is protocol/client validation, not a claim of extra cloud writes or universal controller support.
The plugin has no analytics or author-operated tracking service. Xiaomi account/cloud/remote-camera services remain necessary dependencies. Private credentials, selection, imported runtime, metadata settings and Matter identity are confined to Homebridge storage; raw camera-source listeners are loopback-only, and camera media are not recorded. HomeKit and Matter expose the intended local-network accessory endpoints. Failure paths are bounded and handled, including account cancellation, network failures, component setup and shutdown. Homebridge/HAP are obtained from the host; Homebridge is a development dependency only.
Please review the disclosed Linux x64/component-acquisition restriction and related-plugin overlap. The README and release describe the limitations openly, and no verification badge will be added unless the Homebridge team approves.
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 26
- Avg merge
- 1h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from homebridge/plugins
-
awaiting-final-review request-icon
Difficulty 1/5 Under an hour Newbie friendliness 70/100
homebridge/plugins#1376 · 1 comment ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
homebridge/plugins#1331 · 2 comments ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
homebridge/plugins#1288 · 1 comment ·
-
awaiting-changes request-icon
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
homebridge/plugins#1222 · 8 comments ·
-
awaiting-final-review request-verification
Difficulty 4/5 3-5 days Newbie friendliness 35/100
homebridge/plugins#1374 · 2 comments ·
All issues in homebridge/plugins
Similar issues
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: testing bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
snapotter-hq/SnapOtter#5099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day