Timothy Brown

I should also add that, because of the way I've structured my rewrite, when @Aircoookie finishes support for segments, I'll be able to add segment support into the MQTT code...

@Aircoookie @brentbrooks70 I’ll respond to the other parts of both your posts later tonight when I get more time. I just wanted to respond to the MQTT group stuff right...

### @brentbrooks70 > @timothybrown This would ease my implementation of segment control from the backend platform([QIOT Suite](https://www.qnap.com/solution/qiot-suite-platform/en/)) I am using greatly going forward. I think it would actually make the...

> I argree its not too hard for me to change. I new around here and use openhab mqtt for control. > > Looking at the HA docs for mqtt...

> i think the using the json schema would give greater flexibility going forward. Yes, I tend to agree, however... > I like the idea of the speed and intensity...

What do you guys think about adding some general status topics to the list? These would be published under the root *device topic* only and not duplicated for each segment....

@aidbish Yup! I was just reading through some HA documents and came across another way that might be viable as well. Instead of having all those individual status topics, we...

Okay, here’s my revised list. Did I forget anything? Offhand I can’t think of a scenario that this wouldn’t cover. ### Segment Topics - Power *Device Topic*/*Segment*/switch => *on*|*off* *Device...

Okay, cool! So that’s what I’m going with then. I should have a test branch available sometime this week. This has taken a bit more time than I initially anticipated,...

@Aircoookie > @timothybrown > Awesome! While looking at the topic list, I forgot something though. Although by far not used by all effects, there is a secondary (background) and even...