remote_rpi_gpio broken in 0.107.0+

[KptnKMan]

The problem

Hi all, not sure what's happening but I'm investigating.

Seems like my remote_rpi_gpio component stopped working when I upgraded to v107.
I got this component working here and here.

This is bad, as its knocked out my heating. ☹️

Anyway, I've checked my pigpiod system and everything seems to be working.
In my logs, I'm getting this error whenever I try to use a remote_gpio pin, indicating it is something to do with the websocket_api component.

Any help would be appreciated.

Environment

Running latest HA 107.7.
Have tested with all releases from 107.0 upto 107.7, same issue persists.

• Home Assistant release with the issue: 0.107.0+
• Last working Home Assistant release (if known): 106.4
• Operating environment (Hass.io/Docker/Windows/etc.): Hass.IO
• Integration causing this issue: remote_rpi_gpio
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/remote_rpi_gpio

Problem-relevant configuration.yaml

switch:
- platform: remote_rpi_gpio
  host: 192.168.1.111
  ports:
    17: Pi Switch 1 (17)
    18: Pi Switch 2 (18)
    22: Pi Switch 3 (22)
    23: Pi Switch 4 (23)

Traceback/Error logs

Logger: homeassistant.components.websocket_api.http.connection.140369233781456
Source: components/remote_rpi_gpio/__init__.py:56
Integration: websocket_api (documentation, issues)
First occurred: 10:02:02 AM (3 occurrences)
Last logged: 10:05:31 AM

cannot set state of pin GPIO23
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 134, in handle_call_service
    connection.context(msg),
  File "/usr/src/homeassistant/homeassistant/core.py", line 1234, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1257, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in handle_service
    self._platforms.values(), func, call, required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 402, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 599, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 433, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 624, in async_turn_on
    await self.hass.async_add_job(ft.partial(self.turn_on, **kwargs))
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/remote_rpi_gpio/switch.py", line 78, in turn_on
    remote_rpi_gpio.write_output(self._switch, 0 if self._invert_logic else 1)
  File "/usr/src/homeassistant/homeassistant/components/remote_rpi_gpio/__init__.py", line 56, in write_output
    switch.on()
  File "/usr/local/lib/python3.7/site-packages/gpiozero/output_devices.py", line 229, in on
    self._write(True)
  File "/usr/local/lib/python3.7/site-packages/gpiozero/output_devices.py", line 106, in _write
    self.pin.state = self._value_to_state(value)
  File "/usr/local/lib/python3.7/site-packages/gpiozero/pins/__init__.py", line 305, in <lambda>
    lambda self, value: self._set_state(value),
  File "/usr/local/lib/python3.7/site-packages/gpiozero/pins/pigpio.py", line 268, in _set_state
    raise PinSetInput('cannot set state of pin %r' % self)
gpiozero.exc.PinSetInput: cannot set state of pin GPIO23

Additional information

I reported this issue in the forums originally, making an issue while I try to fix.

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[scsi050]

It is still broken form me running 0.111.4, issue tracked here - #27724

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[scsi050]

It is still broken in 0.115.6

[KptnKMan]

It's definitely still an issue, and has not been resolved.

I have been slowly working on a fix for some time, but unfortunately I've been busy with other things also.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[scsi050]

Still broken in 2021.1.5

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.