@apocaliss92/scrypted-reolink-native 0.5.19 → 0.5.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +37 -2
- package/dist/main.nodejs.js +1 -1
- package/dist/main.nodejs.js.LICENSE.txt +4 -0
- package/dist/plugin.zip +0 -0
- package/package.json +3 -3
- package/src/baichuan-base.ts +47 -1
- package/src/camera.ts +205 -5
- package/src/email-push-server-device.ts +583 -0
- package/src/main.ts +228 -188
package/README.md
CHANGED
|
@@ -2,10 +2,45 @@
|
|
|
2
2
|
|
|
3
3
|
This plugin aims to use reolink cameras with the only native API to allow a wider range of unsupported cameras + battery ones without hub.
|
|
4
4
|
|
|
5
|
-
##The plugin is still under testing due to the huge amount of possible devices available. If you have any issues with NVR report to me personally first or in the discord's Reolink channel to check if it's an issue with this plugin
|
|
6
|
-
|
|
7
5
|
**Documentation:** [https://advanced-notifier-docs.zentik.app/docs/reolink-native](https://advanced-notifier-docs.zentik.app/docs/reolink-native)
|
|
8
6
|
|
|
7
|
+
## Email Push (battery cameras)
|
|
8
|
+
|
|
9
|
+
Battery cameras (Argus, Go, …) can't keep a TCP push subscription alive while sleeping, so motion alerts get dropped. To work around this the plugin ships an **embedded SMTP intake** — the camera sends e-mail on motion and the plugin turns each delivery into the same `motionDetected` event you'd get from a wired camera.
|
|
10
|
+
|
|
11
|
+
### One-time server setup
|
|
12
|
+
|
|
13
|
+
1. Open the **Reolink E-mail Push Server** device that appears under the plugin provider. It's a singleton, created automatically the first time you open the plugin.
|
|
14
|
+
2. Random `nodelink-<hex>` username + base64url password are generated on first construction — they're shown in the **Auth** group of the Settings panel. Use **Regenerate random credentials** if you ever want to rotate them (re-run Auto-configure on every camera afterwards).
|
|
15
|
+
3. Defaults (`port=2525`, `bindHost=0.0.0.0`, `domain=nodelink.local`, `requireAuth=true`, `tls=false`) work out of the box on most LANs. Flip **Enabled** if you want the server to stay off.
|
|
16
|
+
4. The **Recommended camera-facing host** field shows the LAN IP the cameras should reach. If your Scrypted host has multiple interfaces and the wrong one is picked, set **Bind host** manually.
|
|
17
|
+
|
|
18
|
+
### Per-camera setup
|
|
19
|
+
|
|
20
|
+
You have two equivalent entry points — pick the one closer to where you already are:
|
|
21
|
+
|
|
22
|
+
- **From the server device** — open the *Auto-configure a camera* select in the **Actions** group, pick a camera, click Save. The select resets after each apply so it never silently re-runs. NVR-attached cameras are hidden (they share the NVR's mail path).
|
|
23
|
+
- **From the camera page** — open the camera's Settings, scroll to the **E-mail Push** group, and click **Auto-configure from Email Push Server**. Same effect, plus you can tweak **Trigger events** (`MD`/`people`/`vehicle`, default all three) and **Attachment** (`picture`/`video`/`none`, default `picture`) before applying.
|
|
24
|
+
|
|
25
|
+
What Auto-configure writes to the camera:
|
|
26
|
+
|
|
27
|
+
- SMTP server / port / `AUTH PLAIN` username + password from the server device
|
|
28
|
+
- Recipient `cam-<nativeId>@<domain>` (the plugin's per-camera intake address)
|
|
29
|
+
- Sender nickname = camera name
|
|
30
|
+
- 24/7 trigger schedule for the selected event types (existing schedule slots for other types are left untouched)
|
|
31
|
+
|
|
32
|
+
### Verifying delivery
|
|
33
|
+
|
|
34
|
+
- **Send test e-mail** (camera Settings → E-mail Push) makes the camera perform a real SMTP send against its saved target. Result is logged in the device console and reflected in the **Camera-side SMTP target** status row.
|
|
35
|
+
- **Refresh status** reads back the camera's own config (cmd 42) and renders it as `Target: host:port · Recipient: cam-<id>@<domain> · refreshed <ts>`. Reading wakes battery cameras so it's never automatic.
|
|
36
|
+
- **Last received** (server device → *Recent e-mails*) shows the last 20 deliveries with timestamp + inferred type + subject. In-memory ring, cleared on restart.
|
|
37
|
+
|
|
38
|
+
### Notes
|
|
39
|
+
|
|
40
|
+
- NVR-attached cameras don't get the E-mail Push settings group — the NVR handles mail centrally. Same for multifocal lens children.
|
|
41
|
+
- Recipients `cam-<unknown>@<domain>` are rejected with SMTP 550 — useful if you regenerate credentials or move a camera between Scrypted hosts.
|
|
42
|
+
- The intake is plain TCP; enable **STARTTLS** in the TLS group if you have `cert.pem`/`key.pem` in the configured TLS directory.
|
|
43
|
+
|
|
9
44
|
[For requests and bugs](https://github.com/apocaliss92/scrypted-reolink-native)
|
|
10
45
|
|
|
11
46
|
☕️ If this extension works well for you, consider buying me a coffee. Thanks!
|