Device Type Submission Guidelines

(Jim Anderson) #1

Hey all,

As many of you know, we have had submission guidelines for SmartApps for some time. We’ve realized that the same type of information has been lacking for Device Types, so we have added documentation that addresses this.

Hat tip to @mager for writing this up!

(Andrew Mager) #2

If you have any feedback, please let us know and we’ll update it.

( co-founder Terry @ActionTiles; GitHub: @cosmicpuppy) #3

Great work and thanks for inviting feedback:

Nothing urgent… but over time, and perhaps just as links to a repo of some sort, it would be great to see example(s), both positive (i.e., good example) and negative (bad example) for each Bullet of the Guidelines (well, except for trivial ones).


  • Use capabilities, not device wildcards when gathering device inputs from the user.
    :arrow_right: Show some actual preferences{ input() } statements as good and bad examples.


  • Do not aggressively loop or schedule.
    :arrow_right: Show a meaningful method that does reasonable, meaningful, acceptable loop versus some very nasty loops and schedules that you can suggest good alternatives for …

As you get more and more code to review, you’ll be able to build up a library of good and bad examples. The good examples will start to imply an actual set of boilerplates that developers can use to get off on the right foot. :footprints: :smile: