I’ve read the few lines of documentation under:
And I have the following question:
Can I create some child devices that can manage their authentication tokens themselves?
As per the ecobee connect (smartapp) example, I can see that the smartapp (service manager) handles all the authentication tokens (and more) for its children (device type).
For a given device type (such as my ecobee custom device type, see https://github.com/yracine/device-type.myecobee), I’d rather leave that to the child device so that it becomes a fully independent & autonomous device handler. As such, the device handler’s code would be self-contained. This may
allow also the child devices to be spawn under different accounts, which, in my case,
would be ideal as each ecobee user is granted a limited number of transactions (queries/updates) per
In brief, the service manager would spawn the child devices to the world and be done with it!!
In my book, the tight integration between the smartapp (service manager) and
the device type is not always a good software engineering approach, and a source of potential errors/issues.
Your input is appreciated.