I put this on the Developer’s Call for Wed Feb 25th.
Agenda Item: Can any service be a Thing?
Eg. This one, and also Capability External Logger.
The static parameters are in the SmartDevice Type for each service + Preference at instance creation for individual id, key, password, etc.
This seems to be a reasonable way to abstract and modularize various types of useful services, read, write, or both.
Capability Weather Report, for example could be another “Service Thing”… But let’s see if “Send Message” can be hashed out as a Proof of Concept first.
The Command(s) take the message + any optional arguments like address (if not the instance default), notification sound, priority,… Not much else needed?
It works like any other Cloud-to-Cloud device (like Nest, I think is a comparable example).
This seems like a reasonable and promising way to abstract and modularize useful common service types for use in many SmartApps instead of duplicating code and without requiring new global libraries / methods.
Capability Weather Report might be another, but let’s hash out Send Message first as a Proof of Concept.