dr1rrb / ha-twinkly Goto Github PK

There is an existing unofficial XLED library that could be used as a base for this component
https://github.com/scrool/xled

2020-08-28 14:39:42 WARNING (MainThread) [homeassistant.components.light] Light is deprecated, modify TwinklyLight to extend LightEntity

I guess it's a easy fix!

First, thanks for this integration and Happy New Year!
I've just noticed that when Twinkly is off, the brightness sider is still active in standard Lovelace light element. Not sure whether it is intentional, however, sliders for all my other lights set at 0 when they are off.

it seems it is not possible to edit the entitity so it can be set to an area.
(I have multiple Twinkly devices in the configuration).

Would be nice to be able to set it to an area.

I read on the net that there are rest-api that cnsentoo the total implementation of the device for third-party use. did you take a look?
(https://xled-docs.readthedocs.io/en/latest/rest_api.html)

It seems when this implmentation is active, it scans the twinklys every x secs. which interferes when trying to mapp the lights via the app or direct control the light effects.

I am using this integration successfully for a while.

My Twinkly Fesstoons can be witched on/off and control brightness via light card in HA.

The Entity I call is light.twinkly, this works perfectly!!!

Now as my wife always forgets to switch Twinkly off in the morning I want to Add an Automation for this to switch it off at sunrise.

All Hue lights I have the automation of this is at no issue but Twinkly is not listed at all under devices.

Is there any suggestion how an automation for twinkly off at sunrise can be created, am I overlooking something, or is there a bug that could be fixed.

Thx in advance!

Currently effects are pushed by the app to the device in raw octets stream and are customized per device / configuration (especially for grouped devices). This means that:

1. Adding supports for effects is not just requesting to the device to use a well known effect indexed by name or id, but instead it would require that HA stores and send the full effect data each time.
2. We cannot just hard-code a bunch of pre-configured effects, but we have to get them from the Twinkly application or the physical device.

There is 3 approach to get the effects:

Get it from the device

The idea would be to add a "service" in HA which would get the current effect from the device and store it for later on a file on disk.

The issue is that currently there is no "get_movie" endpoint documented (https://xled-docs.readthedocs.io/en/latest/rest_api.html#upload-full-movie). Maybe it has not been discovered yet?

Act as proxy

The more complex approach would be to act as a proxy in order to save the effects when they are sent to the device.

The main issue is: how to we support multiple devices? Are we able to "multiplex" devices from a single IP by tweaking the discovery payload?

Simulate a device

Probably even more complex: fake a device just to save the effect.

The issue are that

• How do we let the app know the type of device (and number of LED)?
• How to not break app feature like mapping / live frames when designing effect etc. ?

For the two last solution, we could also imagine to create a dedicated external app that would dump an "effects" file that can be pushed to HA.