Use 0/1 for raspberry pi cover GPIO writes rather than true/false

[fezfox]

Description:

Raspberry pi GPIO pins don't appear to respond to true/false writes and I have found that for this reason the raspberry pi GPIO cover doesn't appear to work. Other HA code that writes to the RPi GPIO pins is written differently, for example, in \components\switch\rpio_gpio.py the following code is used:

    def turn_on(self, **kwargs):
        """Turn the device on."""
        rpi_gpio.write_output(self._port, 0 if self._invert_logic else 1)
        self._state = True
        self.schedule_update_ha_state()

This code works. Hence this PR uses 0/1 in the raspberry pi GPIO cover, instead of true/false.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

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

• Documentation added/updated in home-assistant.github.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 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.

[homeassistant]

Hi @fezfox,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[balloob]

Thanks! Nice catch. 🐬