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

pushover-mqtt

v0.4.0

Published

Relay messages from MQTT to Pushover

Downloads

13

Readme

pushover-mqtt

Relay messages from MQTT to Pushover

Breaking change in 0.3. api_token is now just token, and user_key just user to match the Pushover fields and documentation.

Topics

With a configured prefix of pushover, the following topics can be used:

  • pushover/{target}/send/text
  • pushover/{target}/send/message

Where target is the key of a target defined in configuration. Target configuration should contain at least token and user, but can contain any field defined here: https://pushover.net/api

text accepts a string payload which will be passed on as the message body to Pushover.

message accepts an object with any valid API field. These fields merge with the values in the target, so you can essentially define "default" values in the target, and override them in each message. Example fields include:

  1. title (optional) - defaults to target.title if not provided
  2. message (required)
  3. url (optional)

Full list of fields available are: https://pushover.net/api

Examples:

  • Topic: pushover/send/jack/text

  • Payload: Hi Jack!

  • Topic: pushover/send/jack/message

  • Payload: {"title":"Hello","message":"How are you?"}

Running

It is intended to be installed globally, ie npm i -g pushover-mqtt

Create a YAML file somewhere. See config.example.yml

You will need to define at least 1 target in the config.

Run (replace path)

CONFIG_PATH=/path/to/myconfig.yml pushover-mqtt

You can also use Consul for config. See mqtt-usvc for more details.

Example Config

mqtt:
  uri: mqtt://localhost
  prefix: pushover
service:
  targets:
    # Will allow sending on pushover/send/myapp/text and pushover/send/myapp/message
    - key: myapp
      token: "setme"
      user: "setme"
      title: "My App"