gotDeviceAction resp401 errors with Bond integration

[user3539]

I'm not even sure where to begin....I've reverted all the way back to 2.4.1.151, but this behavior still occurs.

If I turn On, Off or change speed of a Bond ceiling fan using the Bond App on my iPhone, the Hubitat Dashboard device updates and so does the Home App device status using Hubitat's built-in Homekit Integration. The log in Hubitat also shows each command without error that I performed on the Bond iOS App. But if I initiate a command from Hubitat (dashboard or device) or the Home App, for that same device, the log shows
"gotDeviceAction - resp: 401 - [deviceId:xxxxxxxx, actionName:TurnOn]"
gotDeviceAction - resp: 401 - [deviceId:xxxxxxxxx, actionName:TurnOff]
but the device does not respond.

This all started today as of 2:10 pm ET which doesn't coincide with any firmware update of the C7Hub. I reverted back 3 versions to be certain, but not resolved so I upgraded back to 2.4.1.154.

The only thing I did today was shutdown everything: Hubitat Hub, Home Hubs and WiFi router and now this without having changed a single setting on my Wifi. Ideas?

[jtp10181]

Did the bond hub possible change IP's when you shut everything down?

Open the Bond hub device, on device Info tab the IP is saved.

Not sure what will force it to update but you could try Configure and Refresh so see if that will work.

[user3539]

The IPs did not change. I turned off everything again this morning including all iOS devices just in case it was HomeKit. I also now reverted the Bond Hub to prior firmware, but that didn’t do anything either. It is so odd the commands flow out from the Bond Hub as to each device status, but commands originating in Homekit or Hubitat aren’t executed and generate this error.

[jtp10181]

401 is unauthorized response.

In the bond app settings> Advanced
Check the Local Token

Should match the "Token" state variable on the bond hub device page within Hubitat.

If not matching there is command there to set it.

You could also turn on debug logging and try a refresh from the bond hub device page, just to see if that gets similar errors.

[user3539]

That was it. I noticed after last post that all my other fans with their own Wifi(and IP) worked just fine. Their tokens still matched. Thanks for guidance.