Chris Mullins

I dodge the problem in the UI by making the browser do the work (browsers obviously have to be able to scale images, and they do it really well).

Yeah, it's a hard problem to solve well generally. Agreed -- let's discuss elsewhere if we want to continue. Automatic size detection definitely worth it. This is a good change....

Sure, sounds good. I'm playing around with a wacky idea right now (adding a Lua scripting engine), so might be a bit before I get to it. Nah, I expect...

I'm not familiar with the display board. If you know what the pins are _supposed_ to map to, I'm happy to help out or take a loot.

Was this after formatting and re-flashing the ESP? Can you share how you formatted the flash? Some additional output that might help: 1. /api/v1/settings (sensor passwords!) 2. /api/v1/templates 3. /api/v1/system

What do the `json` and `Format, add timestamp` blocks for the `tempetura esterna` look like? In summary, these should: 1. Extract the value of the temperature 2. Publish a new...

It looks like you just need to change the code in `Format, add timestamp` to: ``` ... payload: msg.payload ... ```

This is probably not something I'll have the chance to look into for a while. Here's the relevant code, for anyone brave enough to go spelunking :) https://github.com/sidoh/esp8266_milight_hub/blob/master/lib/MiLight/RgbCctPacketFormatter.cpp#L110

Appreciate you taking a stab at it, @camcs1! If it helps, there's some very light documentation on the protocol here: https://blog.christophermullins.com/2017/03/18/reverse-engineering-the-new-milightlimitlessled-2-4-ghz-protocol/ Let me know if there's anything I can help...

Hello, Your hypothesis makes sense to me, although your guess is as good as mine as to why that happened. Bulbs de-pair when they get an "on" packet from their...