jvmahon

> Does this only happen with these remote endpoints then ? Or is a single ESP32 with some GPIO assignments as relays also fine ? Just curious - does the...

> Matter is moving away from that, because that's not very interoperable. So in general, anything that's not allowed by the device type should be flagged (though perhaps not prevented...

Is this still being worked on? I'm particularly interested in the struct entry as it applies to the FixedLabel attribute. It would be very helpful if there was a way...

> If we want to have a fully strict interface it should probably be redesigned since in that case why would the user need to enable or disable anything at...

> we have added some restrictions and are working on adding a "spec check" feature which tells the user what is required for the device type they have chosen I...

> For example, if a user disables an attribute that is required by the device type then the device type does not have the features that it requires and is...

Now look at cluster / attribute level. Say you were doing an Extended Color Light (0x010D), that device has a "Color Control" cluster (0x0300). Looking now just at the Color...

> -play around and make mistakes (good way to learn and become an experienced user) My point is to remove the ability to make mistakes in "strict" mode. A developer...

> My understanding is the device type abstracts all these ideas and whatever is defined in the device type is actually mandatory for that device type. Except some device types...

Thanks. Ideally, I'd like to see Hubitat add a dedicated "FanLevel" Capability and a "FanDirection" attribute, but I'm waiting until 2.2.4 is done to propose that.