Ignore state changes when new state is unknown

[travisp]

This updates "async_check_cover_state_change" to also ignore when the New state is unknown, not just when the Old state is unknown.

Motivation and Context

I recently wrapped my shades/covers in a template to adjust the functionality of how they respond to commands (some of my shades get unfortunately "stuck" if they havent moved in a while). This worked well, and didn't cause issues with adaptive cover most of the time. However, when Home Assistant restarts or the templates are reloaded, they shades are briefly put in an unavailable state.

Adaptive Cover would read this as a state change and, in addition, report this as a manual action because the "None" position didn't equal the previous position. All of my shades would end up under manual control as a result.

• fixes:

In addition to looking at the old state, also look at the new state, when deciding whether or not to process the state change.

I do not know if there are any unintended consequences of this. Maybe some people would want the shades to enter manual control if the shade is considered unavailable?

How has this been tested?

Mostly just tested locally.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Enhancement (non-breaking which updates existing code)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.