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

pimatic-woox

v0.0.4

Published

Pimatic plugin for Woox (Tuya) devices, without using the Tuya cloud

Downloads

2

Readme

pimatic-woox

A pimatic plugin to control WiFi based Woox LED bulbs and potentially others based on the Tuya protocol The plugin works outside the Tuya Cloud, and talks to the lightbulbs directly, removing the need for a working internet connection.

Status of Implementation

Since the first release the following features have been implemented:

  • Added rule action syntax for "Fade" and Blink" effects
  • Support for the Woox R5085 RGBW lightbulb
  • Lightbulbs will automatically be found on the local (non-routed) LAN through UDP broadcast, after adding deviceID and -key
  • GUI element is similar to the ones provided by Pimatic-Tradfri and Pimatic-Dummies
  • Warm White color temperatures are emulated as the device does not support out of the box (User configurable Color temperatures through device config)
  • Rules action syntax to set color (HEX-format or colorname) of the lightbulb.
  • Integrates with Pimatic-HAP with full color support

Roadmap:

  • Building out the class into parent classes to provide an easier way to support other Woox devices

Contributions

Contributions were made by:

  • betreb The GUI element is built on the one used by pimatic-dummies and his debugging skills were very helpful!
  • mwittig The rule actions are built on the ones created for pimatic-milight-reloaded
  • michbeck100 For integrating my accessory template into pimatic-hap
  • treban Inspiration from pimatic-tradfri Contributions to the project are welcome. You can simply fork the project and create a pull request with your contribution to start with. the project on github

Configuration

  • Follow these instructions to get the id and key for your Woox lights.
  • Add the plugin to your config.json, ro via the GUI (Do not forget to activate)
  • Create a device config

Plugin Configuration

{
  "plugin": "woox",
  "debug": false,
  "active": true 
}

The plugin has the following configuration properties:

| Property | Default | Type | Description | |:------------------|:---------|:--------|:--------------------------------------------| | debug | false | Boolean | Debug mode. Writes debug messages to the pimatic log, if set to true |

Device Configuration

Default settings should work fine, only the deviceID and deviceKey MUST be provided

WooxRGBWLight

{
  "class": "WooxRGBWLight",
  "id": "woox-light-1",
  "name": "Woox RGBW Light 1",
  "deviceID": "<device id>",
  "deviceKey": "<device key>"
	
}

The device has the following configuration properties:

| Property | Default | Type | Description | |:--------------------|:---------|:--------|:-------------------------------------------------| | ip | '' | String | Automatically populated | | port | 6668 | Number | The port of the Lightbulb. Default usually works | | minTemp | 2400 | Number | Minimum temperature (Kelvin) for WW emulation | | maxTemp | 9600 | Number | Maximum temperature (Kelvin) for WW emulation |

Predicates and Actions

The following predicates are supported:

  • {device} is turned on|off

The following actions are supported:

  • switch {device} on|off
  • toggle {device}
  • dim {device} to {value}, where {value} is the percentage of brightness (0-100)
  • set color {device} to {value}, where {value} is one of the following
    • a six digit hexadecimal RGB color code optionally preceded by #. e.g. #FF0000 or 00FF00
    • a CSS color name, e.g., red
    • a variable which resolves to either of the above
  • set effect of {device} to {value}
    • a known effect name, e.g., Fade or Blink
    • a variable which resolves to either of the above

License

Copyright (c) 2021, Danny Wigmans and contributors. All rights reserved.

GPL-3.0