Hi Brian,
Brian Gaiser wrote:I also tried creating a new API Key and putting that in the main HUB device. The key works fine, but still getting those messages.
I have just updated my starling software to 14.3.1 which it is showing as the current firmware version.
I got a single
Access Starling Hub failed: 400 Client Error: Bad Request for url: ... message in the Indigo Event log andthen it reconnected and all has been OK since.
It doesn't look like the Starling API has changed since November last year.
Can you PM me some samples of the
400 type messages you are getting and I will take a look.
Also, what Nest device types are you using?
There should be nest device id(s) in the messages which should tie up with the address field on one (or more) of your Indigo devices, which might give a clue.