hugopeters / dreamstream Goto Github PK

Make a simple StaticString wrapper to allow for safer string operations.

First of all, awesome work on this! I've done a few small testruns and it works great!

However... I already have a few leds setup slightly differently which works quite nice as well but doesn't have DreamScreen integration.

For this I'm using esphomelib. esphomelib is a really nice library which allows for easy integration with Home Assistant and simple OTA updates.

It would be great if it would also function as a sidekick straight away. Personally I think the easiest method would be to add a "sidekick" effect to the list of possible effects (https://github.com/OttoWinter/esphomelib/blob/dev/src/esphomelib/light/addressable_light_effect.cpp) which activates the code from this library.

I realize this might be a tall order, but it would be really useful for me if I could somehow combine the two so I'm wondering how feasible it would be. I've looked through the code a bit and I'm a tad overwhelmed honestly, there's a lot of code in this project and I'm not entirely sure if the codebases would be compatible.

If it would work, it would immediately take care of MQTT support and (if you add home assistant to the mix) would support Philips Hue too.

As all setter functions will behave differently on an emulated device, is there a real point in keeping them in them as-is in the base class?
Let's look at a better way of dealing with this (perhaps multi-inheritance?) so that the logic can be sort of separated without ugly overrides everywhere.
Also, gotta think of a better naming convention for emulated and incoming devices.

For smaller devices, let's not unnecessarily eat up memory with debug strings.