@apocaliss92/scrypted-advanced-notifier 1.8.1 → 1.8.3
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 +28 -5
- package/dist/plugin.zip +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
@@ -7,13 +7,17 @@ This plugin is feature rich notifier to handle detection notifications.
|
|
7
7
|
## Homeassistant
|
8
8
|
It's possbile to configure an homeassistant connection (or utilize the one configured in the `Homeassistant` plugin) to fetch configured Rooms and Entities which are identified by one of the `Entity regex patterns`, these can be then assigned to a camera or sensor to add metadata used to render the notification. The fetched data will be visible in the `METADATA` group, and edited
|
9
9
|
|
10
|
+
## General
|
11
|
+
- `Scrypted token`: Token stored on the scrypted entity on homeassistant
|
12
|
+
- `NVR url`: Url pointing to the NVR instance, should be accessible from outside
|
13
|
+
- `Images path`: If set, the images used to populate MQTT topic will be also stored on the drive path
|
14
|
+
- `Images name`: The name pattern to use to generate image files. The placeholders ${name} and ${timestamp} will be available. Using only ${name} will ensure the image to be overriden on every detection instead of saving one additional copy
|
15
|
+
|
10
16
|
## MQTT
|
11
17
|
It's possible to use MQTT to report data to homeassistant, can be configured standalone or use the configuration from the main `MQTT` plugin.
|
12
18
|
- `Active entities topic`: topic the plugin will subscribe to activate the rules `OnActive`. Useful to sync the plugin with an alarm system connected to homeassistant (i.e. Alarmo)
|
13
19
|
- `Active devices for MQTT reporting`: devices selected will be periodically reported to MQTT with several information, i.e. last detections happened, images, status and so on
|
14
20
|
- `Use NVR detections`: MQTT topics will be published using the detections coming from NVR detections, instead of the one provided by the plugin
|
15
|
-
- `Images path`: If set, the images used to populate MQTT topic will be also stored on the drive path
|
16
|
-
- `Images name`: The name pattern to use to generate image files. The placeholders ${name} and ${timestamp} will be available. Using only ${name} will ensure the image to be overriden on every detection instead of saving one additional copy
|
17
21
|
|
18
22
|
## Notifier
|
19
23
|
Mainly supported notifiers are from `Homeassistant` and `Pushover` plugins
|
@@ -65,6 +69,27 @@ Similar concept applied to occupancy, a combination of observe zone + detection
|
|
65
69
|
- `Priority`: Priority of the notification, will have effect only for pushover
|
66
70
|
- `Actions`: actions that will be shown on the notification. Rendering will vary depending on the notifier. For HA will be an actionable notification, for pushover will be additional links in the text. Both of them require homeassistant to work, the same event will be triggered with the specified action type
|
67
71
|
|
72
|
+
## Timelapse rules
|
73
|
+
Allow to generate regular timelapses for a specific camera. The output folder will be `Images path`, if not set, the plugin folder will be used instead. For the initial period, no data clear will be done, the frames will be only moved to bkp folders. A cleanup functionality will be implemented
|
74
|
+
### General configurations
|
75
|
+
- `Notificataion message`: Message sent when the timelapse will be notified
|
76
|
+
- `Timelapse framerate`: FPS of the final timelapse. The higher the value, the faster will be the timelapse
|
77
|
+
- `Force snapshot seconds`: A new snapshot will be pushed to the timelapse on regular intervals
|
78
|
+
- Schedule properties for the time period to capture. This functionality is very well implemented with the homeassistant notifications, the video will be shown in the preview of the notifications
|
79
|
+
|
80
|
+
### Rule configurations
|
81
|
+
- `Enabled`: Enable or disable the rule (On homeassistant will be available a switch to enable/disable each rule)
|
82
|
+
- `Detection class`: Detection class to match in the zone
|
83
|
+
- `Observe zone`: Zone of type 'Observe' that will be matched
|
84
|
+
- `Zone type`: Intersect if the match can happen on any intersection, Contain if the detection must happen completely inside the zone
|
85
|
+
- `Score threshold`: minimum score to trigger the occupancy
|
86
|
+
- `Occupancy confirmation`: minimum amount of seconds to wait if the state should be updated. This should avoid some false positives
|
87
|
+
- `Zone occupied text`: Text that will be notified when the zone gets occupied
|
88
|
+
- `Zone not occupied text`: Text that will be notified when the zone becomes free
|
89
|
+
- `Notifiers`: notifiers to notify
|
90
|
+
- `Priority`: Priority of the notification, will have effect only for pushover
|
91
|
+
- `Actions`: actions that will be shown on the notification. Rendering will vary depending on the notifier. For HA will be an actionable notification, for pushover will be additional links in the text. Both of them require homeassistant to work, the same event will be triggered with the specified action type
|
92
|
+
|
68
93
|
## Test
|
69
94
|
A test notification can be send with the specified settings
|
70
95
|
|
@@ -88,6 +113,4 @@ Simple webooks to retrieve information, only the last snapshot is for now availa
|
|
88
113
|
|
89
114
|
## What's next
|
90
115
|
* Add boundary box on detected object (really struggling :D)
|
91
|
-
* Add more test suits to emulate a detection on specific conditions
|
92
|
-
* Setup a timeframe where all the notifications are kept and release as a GIF at the end (I saw a comment from an user on discord and I found it a great idea!)
|
93
|
-
* ...
|
116
|
+
* Add more test suits to emulate a detection on specific conditions
|
package/dist/plugin.zip
CHANGED
Binary file
|
package/package.json
CHANGED