node-red-node-pi-gpiod : reconnect missing

Which node are you reporting an issue on?

node-red-node-pi-gpio

What are the steps to reproduce?

use "pi-gpiod in" node (local RPi4) to connect to a remote input pin (remote RPi3+)
reboot remote RPi3+
change input pin at remote RPi3+

What happens?

after rebooting remote RPi3+ no inbound messages are triggered by "pi-gpiod in" node (local RPi4)

What do you expect to happen?

inbound messages to be triggered again, reconnecting to remote RPi3+

Please tell us about your environment:

Docker container nodered/node-red:latest-12 running at RPi4

• Node-RED version:
  bash-5.0$ npm version
  {
  'node-red-docker': '1.2.9',
  npm: '6.14.10',
  ares: '1.16.1',
  brotli: '1.0.9',
  cldr: '37.0',
  http_parser: '2.9.4',
  icu: '67.1',
  llhttp: '2.1.3',
  modules: '72',
  napi: '7',
  nghttp2: '1.41.0',
  node: '12.20.1',
  openssl: '1.1.1i',
  tz: '2019c',
  unicode: '13.0',
  uv: '1.40.0',
  v8: '7.8.279.23-node.45',
  zlib: '1.2.11'
  }
• node.js version:
• npm version: 6.14.10
• Platform/OS: "Raspbian GNU/Linux 10 (buster)"
• Browser: Firefox 87.0 (64-Bit)

Start with the implementation of the "pi-gpiod in" node and reproduce the remote RPi3+ reboot sequence described in the issue. Trace how the connection behaves after the remote input pin changes; done means inbound messages resume automatically after the remote device reconnects.