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

iobroker.pushsafer

v1.1.0

Published

This adapter allows to send pushsafer notifications from ioBroker

Downloads

54

Readme

Logo

ioBroker pushsafer Adapter

Number of Installations Number of Installations NPM version Downloads

NPM

Send pushsafer notifications from ioBroker. Pushsafer.com supports iOS, Android, Windows 10 (Phone & Desktop) devices and Webpush (Chrome & Firefox)

Configuration

First of all it is required an account on pushsafer with a private key, instead of the private key, you also can use a alias key with predefined parameters. Pushsafer configuration

Usage

To send notification from ScriptEngine just write:

// send notification to all instances of pushsafer adapter
sendTo("pushsafer", "message body");

// send notification to specific instance of pushsafer adapter
sendTo("pushsafer.1", "message body");

// To specify subject or other options
sendTo("pushsafer", {
   message:   'Test text',             // mandatory - your text message
   title:     'SweetHome',             // optional  - your message's title, otherwise your app's name is used
   device:    '12',                    // optional  - a device id or device group id (empty or a = all devices)
   sound:     '2',                     // optional  - a number betwenn 0-60 (see pushsafers API description)
   icon:      '2',                     // optional  - a number betwenn 1-177 (see pushsafers API description)
   vibration: '0',                     // optional  - a number betwenn 0-3 (see pushsafers API description)
   priority:  '2',                     // optional  - 2, 1, 0, -1, -2 (see pushsafers API description)
   retry:     '600',                   // optional  - Integer 60-10800 (60s steps): Time in seconds, after a message shuld resend (see pushsafers API description)
   expire:    '1200',                  // optional  - Integer 60-10800: Time in seconds, after the retry/resend should stop. (see pushsafers API description)
   answer:    '1',                     // optional  - 1 = Answer is possible, 0 = Answer is not possible. (see pushsafers API description)
   picture:   'absolutePathToPicture', // optional  - absolute path to picture or base64 coded image URL
   picture2:  'absolutePathToPicture2',// optional  - absolute path to picture or base64 coded image URL
   picture3:  'absolutePathToPicture3',// optional  - absolute path to picture or base64 coded image URL   
   url:       'http://blabla',         // optional  - URL or URL scheme, https://www.pushsafer.com/en/url_schemes
   urlTitle:  'Link to BLA',           // optional  - title of URL
   time2live: '60',                    // optional  - Integer number 0-43200: Time in minutes, after which message automatically gets purged.
});

You can find API description here

You can use blockly too.

Changelog

1.1.0 (2024-04-21)

  • IMPORTANT: This adapter now requires Node.js 18.x+
  • (ChrMaass) Fix Blockly priority and answer

1.0.3 (2021-01-13)

  • (Apollon77) update dependencies

1.0.2 (2020-04-24)

  • (bluefox) Added color icon option
  • (bluefox) Refactoring

0.1.9 (2019-09-19)

  • (appzer) add new sounds & icons, add new parameter (priority, retry, expire, answer)

0.1.8 (2017-09-12)

  • (bluefox) use new pushsafer package

0.1.7 (2016-10-19)

  • (appzer) implement time2live parameter

0.1.6 (2016-10-17)

  • (bluefox) implement picture send
  • (bluefox) add blockly

0.1.3 (2016-09-21)

  • (bluefox) fix config dialog

0.1.2 (2016-09-21)

  • fixed error with private key

0.1.0 (2016-08-28)

  • filter out double messages

License

The MIT License (MIT)

Copyright (c) 2014-2024 bluefox [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.