npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@luqman/node-red-security-spy

v0.0.16

Published

Simple Node-Red Subflow focused on SecuritySpy (NVR) event stream.

Downloads

2

Readme

node-red-security-spy

Security Spy Events

Simple Node-Red Subflow focused on SecuritySpy (NVR) event stream.

Note: No easy way to get camera number, use debug node to get camera number.

Subflow Environment Variables

PROTOCOL: http:
HOSTNAME: localhost
PORT: 8000
USERNAME:
PASSWORD:
AUTO_CONNECT: true
RETRY_DURATION: 30
LOG_EVENTS: false

If AUTO_CONNECT is false you have to manually inject to trigger connection.

Output

Output 1: connecting, connected or disconnected

Output 2: Stream of parsed events from https://bensoftware.com/securityspy/web-server-spec.html#miscDiv

All events have;

{"time":"20240928132817","number":"0" ...}

Personally I've not used these values for anything. number resets after re-connection.

Heartbeat

{"camera":"X","event":"NULL","info":""}

If camera is X it means heartbeat/ping/keepalive, I use this to ping uptime checker.

File Written

{"camera":"4","event":"FILE","info":"/Volumes/Storage/Security Spy/CameraX/{date}.mov"}

Motion

{"camera":"4","event":"MOTION","info":{"x":"0","y":"1538","w":"420","h":"594"}}

Classify

{"camera":"4","event":"CLASSIFY","info":{"HUMAN":100,"VEHICLE":0,"ANIMAL":1}}

Motion End

{"camera":"4","event":"MOTION_END","info":""}

Trigger

{"camera":"4","event":"TRIGGER_A","info":"128"}

All events can be found here https://bensoftware.com/securityspy/web-server-spec.html#miscDiv

Personally I use TRIGGER_A in combimation with MOTION_END to create a sensor in Home Assistant.