Skip to content

problem as here #382

Description

@madmax5900

Hi!

Unfortunately I have the same problem as here.

#315

Is there already a solution? I otherwise use the module super and no other. Or is there an update?

Thanks in advance.

Activity

  1. andesse commented on Jun 28, 2022

    @andesse

    @madmax5900
    Have a look on my repository, it's not hard to setup. I have a lot of tools included. They make it very easy. (Of course it's not that convenient as HueMagic, but it will work!) Please read carefully the readme.

    https://github.com/andesse/hue-clip-api.node-red-flows

  2. added 2 commits that reference this issue on Aug 16, 2026
  3. Foddy commented on Aug 16, 2026

    @Foddy
    Owner

    @madmax5900 sorry for the really long silence on this one – it stayed open way longer than it should have :S

    @andesse – this hit you as well.

    HueMagic was being too clever with its own cache. Before sending a command it compared your payload against the state it had stored, and if that cache believed the light was already in the desired state, the command never left for the bridge. As soon as the cache was out of sync – someone used the app, a switch, another flow – commands silently did nothing. The node status could get stuck on "executing command…" for the same reason, because a command that changed nothing never produced an answer.

    The state is now always sent to the bridge, the node status is scheduled instead of hanging, and the alert effect is handled by the bridge itself so it isn't capped at 15 seconds and restores the previous state on its own.

    Fixed in v5.0.0 – the release is on npm 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions