npm node-red-contrib-ccu 4.11.1
v4.11.1

latest release: 4.12.0
one hour ago

Fixed

  • openccu-lite: the interfaces stayed disconnected after the system was
    unreachable for more than about 40 seconds, until Node-RED was restarted
    or the flow deployed again.
    During a firmware update, a longer reboot or
    a network outage the connection took three unanswered probes as "this
    system is no longer openccu-lite" and closed lite-rpc; when the system
    answered again, the names came back but the interfaces did not. A system
    that does not answer is now waited for: lite-rpc and the names keep
    reconnecting and pick up where they were once the system is back (the log
    says the system does not answer … - waiting for it once). lite-rpc is
    closed only when the system answers as something other than openccu-lite,
    and if it is detected as openccu-lite again later, lite-rpc starts again
    with the same interfaces, without a deploy. (#190, @reini12345)

Commits since v4.11.0

  • 4.11.1 - openccu-lite: the interfaces come back after the system was unreachable (f9cca0f)
  • docs(changelog): 4.11.1 (27d4a5f)
  • fix(connection): keep lite-rpc while the system does not answer, start it again when openccu-lite is back (#190) (bce2756)
  • README: openccu-lite links to the openccu-lite organisation (4723d4e)
  • README: drop the Internet Explorer and Node-RED 1.0 notes (dabbbc5)

Don't miss a new node-red-contrib-ccu release

NewReleases is sending notifications on new releases.