Make SimpliSafe integration more resilient to SimpliSafe cloud issues

[bachya]

Proposed change

This is a follow-up to #30456.

At times, SimpliSafe will do something in their cloud (producing a 500 or 502) and the integration can't recover without a HASS restart. Today, I noticed another such incident in my HASS logs:

2020-01-23 11:54:50 ERROR (MainThread) [simplipy.system] Error while getting latest settings values: Error requesting data from ss3/subscriptions/SID/settings/normal: 502, message='Bad Gateway', url='https://api.simplisafe.com/v1/ss3/subscriptions/SID/settings/normal?forceUpdate=false
2020-01-23 11:54:50 ERROR (MainThread) [custom_components.simplisafe] SimpliSafe error while updating "MY ADDRESS": Repeated 401s despite refreshing access token
2020-01-23 11:55:21 ERROR (MainThread) [simplipy.system] Error while getting latest system values: Repeated 401s despite refreshing access token
2020-01-23 11:55:21 ERROR (MainThread) [simplipy.system] Error while getting latest settings values: Repeated 401s despite refreshing access token

My supposition: at times, a 500 or 502 will seemingly harm simplisafe-python's existing access token and refresh token, thus preventing the integration from recovering. However, the refresh token stored in the config entry escapes unscathed (again, apparently); so, if we detect that we're in such a situation, we should try one last effort using that stored refresh token. This PR implements that.

By all accounts and because this is sporadic, this isn't an issue of how we're using the SimpliSafe's unpublished API.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
simplisafe:
  accounts:
    username: !secret simplisafe_username
    password: !secret simplisafe_password

Additional information

• This PR fixes or closes issue: fixes Simplisafe integration starts getting 401 errors #23669
• This PR is related to issue: N/A
• Link to documentation pull request: N/A

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[MartinHjelmare]

Looks good!

[nguyer]

Thanks for this! I hope this helps the refresh token issues I’ve been having. I’d really like to trust that my system will arm/disarm with my automations...

Do you know which HA release this will be included in? Thanks again!