You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were recently on vacation and after a few days the accessories exposed by homebridge-volvo showed "on" statuses, unexpectedly. According into the API docs "When the car has not been used for more than 3-5 days, the invocation command request may not be able to perform because is set in standby mode", and includes a table of the possible error status values here: https://developer.volvocars.com/apis/connected-vehicle/details/#vehicle-sleep-and-error-modes
I'm still super new to homebridge plugin development, but I believe we could throw this error in accessories' onGet (and onSet?) methods to immediately cause HomeKit to show accessories as "No Response", which I think would be the best and most accurate status since the vehicle's communication equipment is temporarily disabled.
throw new HapStatusError(HAPStatus.SERVICE_COMMUNICATION_FAILURE);
The text was updated successfully, but these errors were encountered:
We were recently on vacation and after a few days the accessories exposed by homebridge-volvo showed "on" statuses, unexpectedly. According into the API docs "When the car has not been used for more than 3-5 days, the invocation command request may not be able to perform because is set in standby mode", and includes a table of the possible error status values here: https://developer.volvocars.com/apis/connected-vehicle/details/#vehicle-sleep-and-error-modes
I'm still super new to homebridge plugin development, but I believe we could throw this error in accessories' onGet (and onSet?) methods to immediately cause HomeKit to show accessories as "No Response", which I think would be the best and most accurate status since the vehicle's communication equipment is temporarily disabled.
The text was updated successfully, but these errors were encountered: