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

homebridge-blynk-plugin

v0.3.0

Published

Based on Peter J Wojciechowski but updated to use the new API

Downloads

45

Readme

homebridge-blynk-platform

Plugin for Homebridge to allow Blynk applications to be controlled throug Apple HomeKit.

Installation

Once you have a working homebridge

sudo npm install -g homebridge-blynk-platform

Configuration

To expose your Blynk powered devices you have to configure the Homebridge to the location of your Blynk server.

    "platforms": {
        "platform": "BlynkPlatform",
        "serverurl": "http://your.blynkserver.com:8080",
        "pollerseconds": "20",
        "devices": [
            {
                "manufacturer": "PeterWoj",
                "name": "HabitController",
                "token": "1e6aa4f587664ed74c8195842d2f1a8d",
                "deviceId": "31225",
                "discover": true
            },
            {
                "manufacturer": "PeterWoj",
                "name": "OutdoorController",
                "token": "1e6aa4f587664ed74c8195842d2f1a8d",
                "deviceId": "112233",
                "discover": false,
                "accessories": [
                    {
                        "model": "extension-cord",
                        "name": "Pergola Lights",
                        "pintype": "VIRTUAL",
                        "pinnumber": 2,
                        "type": "BUTTON"
                    },
                    {
                        "model": "extension-dimmer",
                        "name": "Dimmed Lights",
                        "pintype": "VIRTUAL",
                        "pinnumber": 2,
                        "type": "SLIDER",
                        "min": 0,
                        "max": 100
                    },
                    {
                        "model": "my-thermometer",
                        "name": "Dimmed Lights",
                        "pintype": "VIRTUAL",
                        "pinnumber": 2,
                        "type": "SLIDER",
                        "typeOf": "THERMOMETER_SENSOR",
                        "min": 0,
                        "max": 100
                    }
                ]
            }
        ]
    },

Once your configuration is in place startup Homebridge and to get your devices connected to Apple HomeKit.

Changelog

0.2.6

Default HomeKit type for auto discovery is now an OUTLET.

  • Bug fixes
  • #12 Missing 'D' from the digital pin requests
  • #15 High CPU caused from failed config defaults for pollerseconds.
  • #14 Additional accessory types, SLIDER is now available
    • Adding HomeKit Sensors as well to relate to defined switches/sliders
      • HUMIDITY_SENSOR, LIGHTBULB, OUTLET, TEMPERATURE_SENSOR
  • Multiple devices would trigger a refresh on restart of Homebridge.

0.2.5

Bug fixes to account for discovery on a device which has multiple accessories associated with it.

  • Bugs
    • Accessory discovery would fail to add found accessory due to duplicate UUID

0.2.4 ...

The 0.2.3 release...

0.2.3 Lint This

The fine folks created a linter, so it is good to use one.

0.2.2 The Burned Version

CI killed the version number, really I think it would be my fault.

0.2.1 Project Discovery

Enable fetching from the Blynk application to configure accessories. For a device the parameter discover was added to let the Platform know if it should discover available devices are read the configuration file. If { "discover": true } is found then the accessories are ignored if defined. If there is a change in settings from discover being set to false from true, the accessoriesCache will need to be manually updated to avoid item duplication.

Addition of config.schema.json to allow for easier configuration through homebridge-config-ui-x.

0.2.0 Breakin' Configs

Inlude a way to update the HomeKit if the switch state is changed with the Blynk application.

Format the configuration to allow an application to have multiple attached devices. Each attached device can be configured with multiple functions, provided each function is a switch.

0.1.0 Get it runnin'

Initial release with limited device support, only for switches. Supports only a single device attached to the Blynk application but can have multiple functions on the single device.