Greetings Jon,
Thanks for the expanded error information. I typed the key in rather than cut and paste, am getting the same error.
Here is the log entry of the expanded error infomation returned:
"Starling Bridge Error Access Starling Hub failed: 401 Client Error: Unauthorized for url:
https://192-168-10-60.local.starling.di ... ort%203080)%0Acheck_circle%0A%0AEnable%20HTTPS%20access%20(port%203443)%0AMY%20API%20KEYS%20help%0AAPI%20Key%0AName%0Aa6659d9RGv87"
I can copy this part directly out of the error message "https://192-168-10-60.local.starling.direct:3443/api/connect/v1/status?key=xxxmykeyherexxx" and paste as url in a web browser and the bridge API responds with:
{"apiVersion":2.4,"apiReady":true,"connectedToNest":true,"appName":"Indigo Starling Plugin","permissions":{"read":true,"write":true,"camera":true}}
This leads me to believe that the starling bridge configuration and key are working and recognized by the Starling bridge. Seems that when the parameters are passed from the plugin the server returns unauthorized but authorizes fine when the same parameters are passed via a web browser from the same machine.
Does the expanded error information provide you with any additional insights on what may be occurring in this area?