node-red-contrib-ccu 4.4.5

v4.4.5

on Node.js NPM

Fixed

• A Node-RED started before rfd went through the CCU's proxy for good.
  The connection decides at start whether it runs on the CCU itself, and
  looked only for a listener on rfd's direct port. On openccu-lite, where
  RedMatic starts at boot before the interface processes (the early start),
  that port is not open yet, so every interface went through lighttpd's
  proxy ports (XML-RPC instead of BIN-RPC for BidCos) until the next restart.
  A loopback host on a system that has the CCU's interface list
  (/etc/config/InterfacesList.xml) is now taken as local as well.
• Waiting for an interface process that is still starting is no warning
  (task 12). Before the interface was ever connected, a refused connection
  is one info line ("HmIP-RF not listening yet (connect ECONNREFUSED),
  waiting for it - retrying in 1 s"); another transport error, or a refused
  connection after the interface had been connected, is still a warning, and
  a fault answer an error.

Changed

• A failed init is retried after 1 s, 2 s, 4 s and 8 s, then every 15 s
  (task 12; was 2, 4, 8, 16 s, then every 30 s), the schedule of hm2mqtt.js and
  the Homematic Manager.

Commits since v4.4.4

• 4.4.5 - a start before rfd stays local and waits quietly, init retry from 1 s (93af846)
• Start before rfd: local mode from the CCU's interface list, quiet waiting, retry from 1 s (task 12) (1619342)
• README: a short openccu-lite section again (0896b11)