Skip to content

v4.10.2

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 12:16

Fixed

  • openccu-lite: with the ReGaHSS unticked in the connection node, the
    connection did not notice it was talking to openccu-lite.
    The check for
    openccu-lite's metadata API only ran while the ReGaHSS was ticked. Without
    it the interfaces were connected directly with callbacks instead of through
    lite-rpc, and no names were loaded. The check now runs regardless of the
    checkbox; only the ReGaHSS itself (names, rooms and polling on a CCU) stays
    behind it. On openccu-lite the checkbox has no effect: names come from the
    system's metadata API and the interfaces go through lite-rpc either way.
  • ccu-homeassistant: the node could wait the full five minutes ("waiting
    for CCU") for a device description that never comes.
    It waited for the
    values description of every channel of the selected devices, including
    channels that have none, descriptions the interface refused, and devices
    missing from the device table. Those now count as settled; only a fetch
    that is still pending holds the node.

Commits since v4.10.1

  • 4.10.2 - openccu-lite detected with the ReGaHSS unticked; ccu-homeassistant stops waiting for descriptions that never come (fea9eb0)
  • docs(changelog): 4.10.2 (956962a)
  • fix(homeassistant): do not wait for descriptions that never come (B-46) (0cc33a1)
  • fix(connection): detect openccu-lite with the ReGaHSS unticked (B-46) (4b29f5e)
  • test(pairing): the wrong pin differs from the certificate's own in every run (808b05c)