"New" Plugin pimatic-woox

---

I have added a new plugin to my github.com site for Woox RBGW Lights: https://github.com/SenTzu01/pimatic-woox.

Kudos where they are do: I borrowed heavily from @mwittig, @bertreb, and @kosta (pimatic-milight-reloaded, pimatic-dummies and pimatic-tradfri)

Before I NPM package it and release it to the general public please test it (git clone) and add to your config.json.

The Woox devices are basically Tuya, however, my plugin bypasses the Tuya Cloud service (Convenient if you want to switch on lights with no internet connection). It seems that every Tuya reseller can add their own key/value pairs, hence I cannot guarantee this will work for other Tuya resellers. Woox is sold in The Netherlands.

Follow these instructions first to get your deviceID and deviceKey.

Furthermore: I need a front-end dev help me to set the color on the color picker when updated outside pimatic or through the rules engine. (This is a bug I imported from pimatic-tradfri).

Godspeed and hope to hear you feedback.

Dan

Hi @Dan, good to see on the forum
I can’t test your plugin because of the missing wooxes.
But i did a quick scan. It looks like a nice blend of the 2 plugins you mention.
There’s one thing I found. The action setColorFix is missing in /devices/woox-rgbwlight.coffee.

Can you explain a bit more what the problem is on setting the color via the api?

@bertreb
The setColorFix action is not relevant as I have not implemented the WarmWhite function (Not available in Woox Devices).
This would require code-clean up in the front-end files.

Re setting the color ( @kosta might want to look at this too as the logic is also missing in pimatic-tradfri):
Two things:

1. Logic in the front-end is needed to set the color based on a “get” question to the rest API.
2. The Back-end logic to answer such rest API needs to be built. (Which I can do once I know what the question is, e.g. getRGB ). The getter would likely return JSON with {r: int, g: int, b: int} to the front-end, which would then set the color of the color picker.

Then the front-end would get updates if the color is changed through rules, or outside pimatic (e.g. Woox phone app).

somewhere in this front-end code I would think some additions are needed:

afterRender: (elements) ->
      @csliderEle = $(elements).find('#' + @csliderId)
      @csliderEle.slider()
      super(elements)
      $('#index').on("slidestop", " #item-lists #"+@csliderId, (event) ->
          cddev = ko.dataFor(this)
          cddev.onSliderStop2()
          return
      )
      $(elements).on("dragstop.spectrum","#"+@pickId, (color) =>
          @_changeColor(color)
      )
      @colorPicker = $(elements).find('.light-color')
      @colorPicker.spectrum
        preferredFormat: 'rgb'
        showButtons: false
        allowEmpty: true
      $('.sp-container').addClass('ui-corner-all ui-shadow')

    _changeColor: (color) ->
      r = @colorPicker.spectrum('get').toRgb()['r']
      g = @colorPicker.spectrum('get').toRgb()['g']
      b = @colorPicker.spectrum('get').toRgb()['b']
      return @device.rest.setRGB(
          {r: r, g: g, b: b}, global: no
        ).then(ajaxShowToast, ajaxAlertFail)

With the current code you can pick a color and that color is sent via setRGB.
If I understand it right, you want to set the color also via the api and you want to set the color picker also to that value.
You can set the spectrum color picker to a color value and you can ‘subscribe’ to changes of the color attribute(s). That mechanism should solve updating the color of the color picker when the color external is updated via the api.
I use that way to sync the color picker (see pimatic-dummies/ui/dummies.coffee)

@Dan: Good to see you here on the board!

@bertreb I have updated the code to re-use your version of the color-picker, works like a charm.
So consider yourself added to the kudos / contributers

@michbeck100 meanwhile added my integration to pimatic-hap so by the time I am ready to release; a new version of pimatic-hap is also available.

Don’t we just love pimatic and the people supporting it!

Just released it to NPM. Should be picked up by the plugin page soon.
Thanks for your help guys!

Dan