node-red-contrib-ccu 4.4.4

v4.4.4

on Node.js NPM

Fixed

• An interface stayed without events for minutes, or for good, when its
  process did not answer the first init (task 11). A failed init at
  start (connection refused, timeout) was only retried by the ping
  supervision, which does nothing without cached devices and waits the ping
  timeout otherwise: 60 s, and 600 s for HmIP-RF. A Node-RED that starts
  before the interface processes (a box still booting, a daemon restart) now
  retries the init on its own after 2 s, 4 s, 8 s, 16 s and then every 30 s,
  for every interface, until it succeeds or the node is closed or redeployed.
  While it waits, the log has one warning ("HmIP-RF not reachable yet
  (connect ECONNREFUSED), retrying") instead of an error line, the success
  after retries is logged ("HmIP-RF connected after 3 attempts"), and the
  nodes show waiting (yellow ring) instead of disconnected. A fault answer
  of a running process stays an error. After a successful init the ping and
  re-init supervision works as before.

Commits since v4.4.3

• 4.4.4 - a failed init is retried with backoff, the interface shows waiting (d84da4d)
• A failed init is retried with backoff, and the interface shows waiting (task 11) (d716499)