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

@miblanchard/homebridge-big-ass-fans

v1.1.13

Published

A Homebridge plugin for Big Ass Fans

Downloads

6

Readme

Homekit

A Homekit implementation for Big Ass Fans. Is heavily dependant on the unofficial Big Ass Fans API.

Installing

First install homebridge - instructions here

An example config.json is as follows:

    "platforms": [
        {
            "platform": "BigAssFans",
            "name": "Big Ass Fan",
            "fan_count": 1
        }
    ]

This config will automatically scan and add all fans that are on your local wifi network. However you should also always add the expected number of fans with the optional config parameter fan_count (by default this assumes 1). Otherwise homebridge will not always discover all the fans.

Install this package with

npm install -g homebridge-bigAssFans

Important note

All of the smarts in your fan will continue to operate - eg. If you set homekit and your fan's local settings set to turn the light on when occupancy is sensed, and then decide to turn it off via homekit the local settings will still turn the light on

Legacy

Legacy mode allows you to specify a single fan to control - and also allows more fine grained control regarding the settings of the single fan.

Legacy mode can not run at the same time as the new Platform mode. In addition this mode does not support running multiple big ass fans.

{
    "accessory": "BigAssFan",
    "name": "Sean's Big Ass Fan",
    "fan_name": "Sean's Room",
    "fan_id": "20:F8:5E:AA:7A:57"
}

In order to get the fan_id, run the example program getFanInfo.js from theBigAssFansAPI.

You must also set the fan_name to the name returned here.

About the legacy config

| Field | Required? | Description | |--------------------|--------------|------------------------------------------| | name | Optional | Overall Name to use for this accessory | | fan_name | Required | Must get this from getFanInfo.js | | fan_id | Required | Must get this from getFanInfo.js | | fan_ip_address | Optional | IP address of fan, defaults to broadcast | | light_exists | Optional | Has light? set to true - default false | | light_on | Optional | What "On" means - default Max | | fan_on | Optional | What "On" means - default 3/7 | | homekit_fan_name | Optional | Name to call the Fan in Homekit | | homekit_light_name | Optional | Name to call the Light in Homekit |

Future features

  • Getting motion sensors to work
  • Allowing all Legacy settings in the Platform mode

Testing

In order to test a local copy you can read here, or as a brief tldr:

/usr/local/bin/homebridge -D -P ./homebridge-bigAssFans/

(Or if homebridge is somewhere else, run which homebridge to find it's location)

Other issues:

  • If you can't add the bridge device try changing the `"username"`` in the config file, sometimes this needs to be changed to fix a caching issue on iOS