Multiple Instances of One Application

It appears from the behavior of the API that an application using PIN authorization can only have one instance running across machines. This seems to be due to the API only allowing one token per application. For example, starting the application on my desktop for the first time prompts for registration via the PIN. If I start a second instance on my laptop, and register using the acquired pin number, this applications continues but the first instance stops working and requires a new PIN request. This cycle repeats indefinitely. Please note that this same situation occurs if I run the application on my desktop and then later run it on my laptop (they do not necessarily have to be running at the same time).

Is there something in this transaction that I am missing that allows multiple instances of the same application or is this a limitation of the API?
1 person has
this problem
+1
Reply
  • MarkK (API Architect) July 30, 2013 14:08
    This is a current limitation of the API. ecobee authorization is designed for one instance per device per user. You generally do not run multiple instances on one machine for the same user. If you wish to do that, have them share the tokens when they make requests.

    I realize that your issue is regarding the same application on multiple machines for the same user. Currently, this is limited because of the restriction of one token set per app/user irrespective of client. This is a limitation which we will probably relax in the future. The original implementation was primarily aimed for mobile devices and 3rd party web sites where only a single instance will run.

    The issue stems from the fact that there must be a unique identifier for each client which the API cannot obtain and we cannot guarantee it will be unique when provided by the client. This and other issues like privacy, etc. (i.e. see the iPhone UID issue in the news).

    Meanwhile, to get around this limitation, you can create a separate app key for each installation. Not the ideal solution, but works as a workaround.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • MarkK (API Architect) August 07, 2013 13:38
    This issue has been fixed. It will be part of the next update to production sometime in late August.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Has this issue been resolved? It appears in my systems that it has, but I am having some other issues as well and am being prompted for a PIN id. I am not receiving this as regularly as described above so I do think it is the issue, but I want to eliminate this as a possible source of error. Thanks
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • MarkK (API Architect) November 12, 2013 14:45
    Sara,

    That particular issue was fixed a while ago. If you are having a specific issue, please provide all relevant details (full request/responses) in a new topic describing your issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated