A few months back, Connected by TCP started to roll out a firmware update to address security concerns. Prior to this update anyone who has access to the local network of a user with a TCP gateway had full control of the users lights.
Now if the user has a secured Wifi network this would not be a huge concern but if their network was unsecure, they were at major risk. Because TCP could not force a user to have a secured Wifi I believe they felt it necessary to take this an extra step and require any local connection to first be initiated after pressing the sync button on the gateway itself.
Once a device is authenticated it saves it’s token and can now communicate freely with the Gateway.
The process involves:
– Securely connecting to gateway using ssl on port 443 setting the rejectUnauthorized to false
– Generate a UUID [myuuid]
– Press the Sync button on the gateway
– Send a log in command to the gateway in the format:
– Receive token from the response from gateway in the form of:
– Save that token [mytoken] for future calls
– Request state of system using:
The return format of the response is still in the same format as outlined in my previous post of the TCP Connected API.
will be updating my Node.js version of the ConnectedbyTCP interface have updated the Node.js Connected By TCP interface and will expand on this post with more details to come.