Schedule ‘on’ for 403 responses

[jeff-winn]

Describe The Bug:

It has been observed that when 403s are occurring the schedule switch is somehow flipping to an ‘ON’ state even though it should be ‘OFF’

To Reproduce:

• Given a plug-in instance with the client credentials flow
• When the application has no registered APIs and is returning 403 errors when logging in
• Then the schedule switch should be transitioned to an ‘ON’ state

Expected behavior:

The schedule switch should remain in an ‘OFF’ state.

Logs:

[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Arriving Sensor' for 'Front': CLOSED
[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Leaving Sensor' for 'Front': CLOSED
[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Motion Sensor' for 'Front': NO_FAULT
[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Motion Sensor' for 'Front': NOT_TAMPERED
[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Motion Sensor' for 'Front': NO_MOTION
[11/1/2022, 8:45:26 PM] [Homebridge Automower Platform] Changed 'Schedule' for 'Front': ON

Refer to #166 for logs and related configuration screenshots.

[jeff-winn]

Did some investigation, the bug was unable to be reproduced.

[jeff-winn]

The reason it wasn't produced is because even though a 403 error was occurring, the web services from Husqvarna still respond even if the API isn't connected.

Had the mower been running, it likely would have flipped to ON as the plugin would have seen the status. The event streams just would not have worked.