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

@mangar2/remotecontrol

v1.1.0

Published

runs remote commands on pc

Downloads

6

Readme

Abstract

Service to run operating system commands remotely and continuously send keep alive messages . It is used to include computers in the yaha home automation system . It can for example be used to shutdown a computer . Then switch of the power remotely once keep alive messages are no longer received . For security , it will only support remote commands configured in a configuration file , it will not directly process message content ( send as string ) on a remote computer .

Installation

Install the package globally with node package manager

npm i @mangar2/remotecontrol -g

Behaviour

If you add then "remotecontrol" to your autoexec bat, the pc is integrated in the yaha home automation. The Broker will receive messages with the value 'alive' as long as the system is up and running.

  • Sending YOURTOPIC/set with value = 'hibernate' will hibernate the computer with a delay of 60 seconds.
  • Sending YOURTIOIC/set with value = 'stop' will stop hibernation

Add then an automation rule to the yaha automation service to automate anything base on the state of the pc. Remove the pc safely from power, if you have for example a remote controllable switch to remove the power from your pc. Switch power back on to start your computer automatically. Do not forget to enable "bool on power on" in the BIOS or your computer

Add more commands to integrate more features. For example add a backup command and then steer backups form your home automation. As an example, wake up the computer and the backup-system at 2:00 a.m., start the backup, and hibernate both systems once the backup is finished.

Configuration

Many options are "preconfigured", but you need to add some configuration options manually. Add a "yahaconfig.json" file to the direcotry and add the following configuration"

{
    "production": {
        "remoteControl": {
            "subscribeTopic":  "add/your/topic/string/here",
            "clientId": "ThisIsAUniqueClientId"
        }
    }
}

subscribeTopic

Add the topic string to scbscribe to your yaha broker. The remotecontrol will subscribe with the topic + '/set' and thus receive all commands changing the status of your pc. The remotecontrol service will then reply with a message having this topic without the /set appendix to inform about the new status.

clientId

Unique identifier of your client. You can give it a user-friendly name here.

Default Configuration

Add any of the following configuration options to your yahaconfig.json file to change the default settings:

{
    "version": "1.0",
    "clean": true,
    "broker": {
        "port": 8183,
        "host": "127.0.0.1"
    },
    "listener": 8205,
    "keepAliveInSeconds": 600,
    "log": [
        {
            "module": "send",
            "topic": "#",
            "level": 1
        },
        {
            "module": "all",
            "topic": "$SYS/#",
            "level": 0
        }
    ],
    "subscribeQoS": 1,
    "statusIntervalInSeconds": 60,
    "commands": [
        {
            "name": "hibernate",
            "command": "shutdown /h",
            "delayInSeconds": 60,
            "value": "hibernate"
        }
    ]
}