npm node-red-contrib-ccu 4.10.0
v4.10.0

47 minutes ago

Changed

  • openccu-lite: the names come from occulite-client's live copy. The
    connection's own HTTP client for the metadata API (snapshot, change
    stream, re-reads) is gone; names, rooms and functions now come from
    occulite-client, in the ReGa shape as before. Where the connection node
    has its own token (as pairing makes it), one client serves the names and
    the interfaces - one connection to the system instead of two. Where the
    names and the interfaces have different credentials (RedMatic on the
    system: the system's read-only token for the names, RedMatic's own token
    for lite-rpc) or the interfaces go the CCU way, a names-only client follows
    the names and opens no lite-rpc stream of its own.

Fixed

  • openccu-lite: a system that did not answer the first connect of the
    lite-rpc client is connected later.
    The client was given up after a
    failed first connect while the log said it kept trying; now a new client
    is opened after 5 s, growing to a minute. A refused credential, or a system
    that is not openccu-lite, still ends it with a message.

Commits since v4.9.0

  • 4.10.0 - names from occulite-client's live copy, one client with lite-rpc (2d3c9e5)
  • docs(changelog): 4.10.0 (0aefe88)
  • docs(changelog): names from occulite-client, one client, the lite-rpc reconnect (bd38293)
  • feat(connection): names from occulite-client's live copy, one client with lite-rpc (ddf9edd)
  • test: ports from the OS for the fake processes and the callback servers (dbc07da)
  • test(lite): the FLOAT check counts only the writes, not the connection's own calls after the start (aae261f)

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

NewReleases is sending notifications on new releases.