Will Miles

> Actually, there is perhaps a simpler option - given you have proved that you can build the usermods when both A _and_ B dependencies are included, given the new...

To expand: FX ids are at somewhat of a premium these days. I also think it'd be better to add an "invert" checkbox to TwinkleCat vs giving it a new...

Sorry I'm just catching up. The queuing logic is all merged, but it looks like something has gone wrong with that process - we shouldn't be generating a 503 and...

Arg, I'm just misinterpreting the image of a diff above -- I'm used to a line-oriented diff display. The 0.16 code is fine. So to summarize: a 503 HTTP response...

> so with 0.16 there is no need for HA to adjust something in this matter? "Need" is a strong word .. ;) Yes, 0.16 attempts to accommodate clients that...

0.16.0 alpha includes the request queuing logic described above. It will still return 503s if overloaded, though.

Yup, looks like it's a channel allocation issue. I don't think this is a UI problem so much as a "how to process a config" concern. It's basically the same...

> just realised: if the source segment is inverted, the targed does not invert (which is ok) but if the source is mirrored, only half of the pixels are copied...

> that does not seem to work as intended. We are being foiled by `getPixelColor()`'s internal processing, I think, it's still doing some logical to physical pixel conversion. Possibly we'll...

> I tested just copying the source settings by doing SEGMENT.mirror = strip._segments[sourceid].mirror; for example. that works, even UI gets updated (though not consistently) This feels wrong to me -...