...so do I have to DEFINE the actions for each device? (I had up to this point not paid much attention to actions, as I thought they were mainly just for things not normally included in a device, and the basic stuff was 'included' in the device definitions. i.e. I thought if I define a device as a 'relay' it would include a way to click 'on' and 'off' in Indigo and I would just define some pre-named method that takes that click and tells the plugin what to do with it).

I'll check out the actions side of things tonight. That's probably my missing piece. (Yes, I will ready python and xml stuff on my Friday nights).

Relay and Dimmer, as subclass definitions, aren't yet implemented but they will be before we ship 5.0 GM. So you may want to wait for that - you are correct that you won't need to define states, trigger definition UI, or action configuration UI for those devices - they'll inherit what they get from the standard definition of those devices in Indigo (include ad-hoc control UIs). For all intents and purposes they'll behave in the UI just like any other lamp or relay (appliance) device.

At least that's the current plan...

Ahhhh, awesome. I had loaded up my plugin (with no real functioning code yet), added a fake device, and was wondering why there was no way to turn it on or off. I figured I just didn't know what I was doing yet.

So... as is tradition on this site, I will ask, "How long to GM?"

And, as is tradition, "When it's ready"...