Sense API Changes

Cindev has recently been notified that Sense will be deploying several important changes to their App API. As a part of this Sense will be making some privacy changes that will affect existing OAuth integrations which includes the Control4 integration brought to you by Cindev.

Due to these changes existing OAuth tokens will be revoked. As Cindev's Sense driver uses the token in order to authenticate with Sense servers, a new token will need to be obtained in order to regain the functionality of the driver.

Most OAuth implementations have a concept of a "refresh" token that makes this possible without the need to re-enter user credentials. Unfortunately Sense has not implemented this concept which will force our customers to manually reinput that information in order to gain a new token. 

The Sense driver for Control4 does its best to simplify the process of getting a new token. This process will require access to Control4's ComposerPro as well as the Sense owner's username and password.

To begin the reauthentication, log into ComposerPro, find your Sense driver and under Driver Actions select Reset Account Connection. You will see a short message in the Driver Status asking you to select the field again (to prevent accidental resets). Once selected again the driver will reset its OAuth information stored in the driver and it will display a field to reenter the email address to begin authentication anew.

From there you can follow the same steps as were followed during the initial installation:

• Enter email address

  • This does not need to be the email address of the account. This email address will receive an authentication email which in turn will send you to the page where the actual Sense account information will be inputted.

• Customer will need to click activation link provided in email

• Once account has been validated, driver is set up and ready to use!

• Refresh Navigators

That is all! 

All of us here at Cindev and our partner's at Sense apologize for any inconvenience this may cause. We do not foresee this becoming a common reoccurrence, and to avoid future inconveniences we are in talks with Sense about the implementation of a "refresh" token that would circumvent these occurrences.

For any questions reach out to us atinfo@cindev.com and if you require any help with reauthentication visithelp.drivercentral.iofor support.