Enable alarmdecoder to see open/close state of bypassed RF zones when armed

[jkeljo]

Description:

The alarmdecoder component already reported RF state bits as attributes. If the user knows which loop is set up for the zone in the alarm panel, they can use that information to tell whether the zone is open or closed even when the system is armed by monitoring the appropriate attribute. That’s awkward, so this commit enables the user to simply configure which loop is used and the component will update the state itself.

Related issue (if applicable): N/A

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#7513

Example entry for configuration.yaml (if applicable):

alarmdecoder:
  # ... other alarmdecoder stuff here ...
  zones:
    01:
      name: 'Smoke Detector'
      type: 'smoke'
      rfid: '0123456'
      loop: 1

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

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

• Documentation added/updated in home-assistant.io

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

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[MartinHjelmare]

Don't change the import path.

[jkeljo]

Ah, sorry that snuck in there. I test these things by installing them as custom components in my home HA system, and absolute imports don't work in that context (if the thing being imported is also a custom component, anyway). I'll change it back.

[MartinHjelmare]

Nice!