Access Starling Hub failed: 400 Client Error: Bad Request

My Starling Bridge has been working fine for months, then the Starling "updated" its firmware last night around 3am... nice.

Now my log under Inidgo is flooded with:

Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: ....

Over and over. It is still working fine. I had to set my logging to critical only.

Ideas?

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.

Hi Brian,

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.

I have 3 Nest thermostats, 1 Nest Protect, 2 Nest Cameras (currently not selected as active in Starling) and 1 Temperature probe.

Here are the messages:

Feb 16, 2024 at 8:37:29 PM
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... X?key=xxxx
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... X?key=xxxx
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... JX?key=xxx
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... JX?key=xxx
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... JX?key=xxx
Starling Bridge Error Access Starling Hub failed: 400 Client Error: Bad Request for url: https://192-168-11-152.local.starling.d ... JX?key=xxx

That helped. I found the device that was complaining and it seemed there was a "ghost" device and a "real" device for my one Garage NEST.

I don't know why - but I edited the device in Indigo and picked the real one - and it's fine now. Thanks!

Same symptoms popped up for me sometime in the last week or so...

Same fix worked for me. Extra detail: I picked the parent device in indigo (in my case, a Nest thermostat) that was showing up in the logs. Edited the device, hit "Edit Device Settings..." and then where there is a pull-down menu for "Nest ID", there were two choices with the exact same name. I selected the other one (the one not currently selected) and the error messages immediately stopped.

Same for me. I found two doorbells in the list with the same exact name. No idea how it got there. But when I picked "the other one", everything started working.

Thanks for the quick-fix, and as always, the community here, for answering almost every question I've had since, well, I don't quite know how long any more.

Steve