Skip to content

incrementBrightness on Groups gone now? This used to be a thing... #380

Description

@peterbaker

Describe the bug
After upgrading Hue Magic to v4, none of my dimming switches work on groups anymore. incrementBrightness is no longer recognized, or mentioned in the README. There's no mention of it's removal, what gives? Are we really meant to brighten individual lights? That's a nightmare.

Expected behavior
The same incrementBrightness and decrementBrightness options in Hue Lights used to be and should be available for Hue Groups.

Please complete the following information:

  • Node-RED version: 12.0.2
  • Hue Magic 4.0.2 (with the message.js fix from some other issue)

Activity

  1. peterbaker commented on Jun 21, 2022

    @peterbaker
    Author

    Here's @Foddy mentioning decrementBrightness being available for Groups: #141 (comment)

  2. peterbaker commented on Sep 16, 2022

    @peterbaker
    Author

    Nothing? This is a pretty crippling change for using Hue Magic with dimmer switches. I don't think I'll ever be able to upgrade from v3 without this.

  3. peterbaker commented on Nov 18, 2022

    @peterbaker
    Author

    Asking again here, as this is a gigantic change to how Hue Magic works, and given that it stills in the mentions of functionality (#141 (comment)) , I'm feeling like this is a mistaken removal or bug.

  4. fjulian79 commented on Dec 26, 2022

    @fjulian79
    Contributor

    Same here .. I want to do build a bridge between KNX and hue. In this scope I have already implemented the scene selection .. now I want to be able to dimm a scene or group in a relative way but this does not work!

    My next step is to help myself by checking the old code .. maybe it's possible to see how it is done there and replicate it somehow.

  5. fjulian79 commented on Dec 26, 2022

    @fjulian79
    Contributor

    See my pull request #417 .. works for me!

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

    @Foddy
    Owner

    @peterbaker thanks for reporting this, and sorry that it took me such an absurd amount of time to get back to you :S

    @fjulian79 – this hit you as well.

    HueMagic still resolved groups over the old API and expected every group to carry a legacy identifier. Newer bridge firmwares stopped handing that out for a lot of rooms and zones, so the lookup came back empty – and you got "The group is not yet available" even though the group itself was perfectly fine. Third party devices behind a group made it worse, because a missing service could send the resolution into recursion.

    The whole "Hue Group" node now runs on the CLIP/v2 grouped_light service. Rooms, zones and third party devices are found again, incrementBrightness / decrementBrightness are back, and the group finally reports brightness and colour as well.

    This is fixed as of v5.0.0, now available 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