npm node-red-contrib-ccu 4.10.3
v4.10.3

38 minutes ago

Fixed

  • ccu-homeassistant: a closed cover could show "open" at position 0 in
    Home Assistant (and one opened from 0 "closed").
    The cover's state came
    from the DIRECTION/ACTIVITY_STATE message, which says "stopped" before the
    final LEVEL arrives; Home Assistant then fixed open/closed from the stale
    position and ignored the later one. The state now comes from the LEVEL
    message itself, which carries working, direction and the position
    together. With ccu-mqtt's mqsh-basic or plain payloads the cover gets no
    state topic and Home Assistant derives open/closed from the position. Home
    Assistant picks up the changed discovery on the next deploy
    (hobbyquaker/hm2mqtt.js#35, @sgybas).

Commits since v4.10.2

  • 4.10.3 - ccu-homeassistant: a cover's open/closed state follows its final position (af68233)
  • docs(changelog): 4.10.3 (904d1f5)
  • fix(homeassistant): a cover's state comes from its LEVEL message (18b8317)

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

NewReleases is sending notifications on new releases.