Ensure that all Settings and UI files relevant for commissioning a new device are available prior to moving the Token/license to a new device i.e. unless the Settings and UI file(s) have been/were commissioned in TPCloud for the Token, simply registering a new device does not mean that the device will be ready to use with your AMX system. Contact your AMX integrator for more details.
It is the responsibility of the AMX integrator and|or end-user to ensure that they retain a reference of any TPControl Token value that has been purchased.
Touch Panel Control provides online management of all purchased Tokens via TPCloud, but may not be able to positively identify Token ownership in cases where integrators and|or end-users do not know their TPControl Token value.
We will endeavour to assist in identifying device|token matches if and where possible.
Specifically in the case of iOS devices, this is limited to the possibility that Touch Panel Control may have a UDID (Apple Unique Device Identifier) reference stored on the licensing server from an earlier (pre-iOS7) registration of TPControl on the device - but this is not guaranteed.
An illustrated guide that will assist in retrieval of the UDID for the device, that we can then try to reference in our system, is available here iOS - How to get the device UDID.
My device was lost|stolen|replaced|upgraded. How do I transfer the token to the new device?
Firstly, ensure that you know the Token value used to register the original device. If you have the original device, and it is still licensed you can review the Token value within Settings for TPControl. Tokens are paired with an email address (TPC User ID), so if you do not know the email the Token is paired with, turn on the 'Token Registration' option within Settings for TPControl and return to TPControl and you will be presented with a screen noting the TPC User ID and Token value.
Deauthorization is the process used to de-register a registered TPControl Token, releasing it from the paired TPC Device ID relating to the current registered device. Once deauhtorized, the Token can be registered with a replacement device.
NOTE: Deauthorizing a device will remove all content from the device, including TP4 files and Settings. Ensure you have access to the relevant Settings and TP4 files or that they have been stored in TPCloud prior to deauthorization. Contact your AMX integrator for more details.
When you still have the original registered device
· Log in to the TPCloud account that the token is associated with, all tokens are associated with a TPC User ID|Email)
· Navigate to 'TPCloud -> Tokens -> (Token value) -> Deauthorize’ and select the ‘Deauthorize and reassign by PIN’ option
· Take note of the Current PIN value generated
· On the original device, go to Settings for TPControl and enable ‘TPCloud PIN’
· Exit Settings and return to TPControl, and a keypad will appear. Type in the Current PIN value from step 3, and press SEND . Assuming the device has internet access, the device will deauthorize.
· On the new device, go to Settings for TPControl and enable ‘TPCloud PIN’
· Exit Settings and return to TPControl, and a keypad will appear. Type in the Current PIN value and press SEND . Assuming the device has Internet access, the device will be registered to the Token value. If Settings and TP4 files have been configured and enabled in TPCloud, the device will also update with the relevant information stored in TPCloud.
When you no longer have the original registered device
Firstly, try the on-device 'Token Registration' option, which is available within Settings for TPControl. Only if prompted by that process will the token need to be Deauthorized via TPCloud as per the following:
· Log in to the TPCloud account that the token is associated with ie all tokens are associated with a TPC User ID|Email)
· Navigate to 'TPCloud -> Tokens -> (Token value) -> Deauthorize’ and select the ‘Deauthorize by Request' option
· Enter the details and submit your request.
· Wait for an emailed response from firstname.lastname@example.org regarding your request. Upon approval, the token is then available to be registered with the new device.
NOTE: while waiting for a deauthorization to be processed, you can at any time use the TRY links available on our Products pages to get "new" devices up and running immediately.
When the original token has been released, simply re-register the device either via TPTransfer or use the TPCloud 'Create a PIN' method.
For more details on deauthorization methods, registering devices and TPCloud, you can find setup documents within the Downloads section of our website, or refer to 'TPTransfer -> Documentation -> (iOS/Android/Windows 8-RT) Setup guide'.