Zigbee2MQTT - Phillips Hue Dimmer 324131137411

I could not find a blueprint for these older hue dimmer so adjusted a current one to work with it

Can be imported via URL

or below code

blueprint:
  name: Phillips Dimmer - 324131137411 Legacy FALSE Hue Dimmer
  description: 'Use the individual buttons of the Hue Dimmer Switch to control an action by either a click or a long press.
  '
  domain: automation
  input:
    dimmer:
      name: Hue Dimmer switch
      description: Hue Dimmer switch to use (Zigbee2mqtt Action Sensor)
      selector:
        entity:
          domain: sensor
    button_1:
      name: On Button - single click
      description: Action to run on click of On button
      default: []
      selector:
        action: {}
    button_2:
      name: Dim Up Button - single click
      description: Action to run on click of Dim Up button
      default: []
      selector:
        action: {}
    button_3:
      name: Dim Down Button - single click
      description: Action to run on click of Dim Down button
      default: []
      selector:
        action: {}
    button_4:
      name: Off Button - single click
      description: Action to run on click of Off button
      default: []
      selector:
        action: {}
    button_5:
      name: On Button - long press
      description: Action to run on long press of On button
      default: []
      selector:
        action: {}
    button_6:
      name: Dim Up Button - long press
      description: Action to run on long press of Dim Up button
      default: []
      selector:
        action: {}
    button_7:
      name: Dim Down Button - long press
      description: Action to run on long press of Dim Down button
      default: []
      selector:
        action: {}
    button_8:
      name: Off Button - long press
      description: Action to run on long press of Off button
      default: []
      selector:
        action: {}
mode: restart
max_exceeded: silent
trigger:
- platform: state
  entity_id: !input 'dimmer'
  attribute: action
action:
- variables:
    command: '{{ trigger.to_state.state }}'
- choose:
  - conditions:
    - '{{ command == ''on_press_release'' }}'
    sequence: !input button_1
  - conditions:
    - '{{ command == ''up_press_release'' }}'
    sequence: !input button_2
  - conditions:
    - '{{ command == ''down_press_release'' }}'
    sequence: !input button_3
  - conditions:
    - '{{ command == ''off_press_release'' }}'
    sequence: !input button_4
  - conditions:
    - '{{ command == ''on_hold_release'' }}'
    sequence: !input button_5
  - conditions:
    - '{{ command == ''up_hold_release'' }}'
    sequence: !input button_6
  - conditions:
    - '{{ command == ''down_hold_release'' }}'
    sequence: !input button_7
  - conditions:
    - '{{ command == ''off_hold_release'' }}'
    sequence: !input button_8

Hi.
I’ve tried this one, with a zigbee2mqtt added hue dimmer of the same Model as the title for this one.
But nothing happens when using it.
I am able to make the dimmer work with one automation for each action.

1 Like

Hi,
after fighting with the same issue I found out that in Ziggbee2MQTT you can navigate to “settings (specific)”. Then set the toggle legacy to “true”. Thus the mapping will be changed and the newer scripts are also working with this older one.

1 Like

Hello @DanjO1o1, just to clarify, because I didn’t understand.
Which blueprint do you use for the older Philips Hue Dimmer 324131137411 when enabling the z2m legacy api?
This adapted blueprint above or the one for the newer Philips Hue Dimmer 324131092621 (and then it will work also for the older Philips Hue Dimmer 324131137411?).
Thanks.

Ok, so I tried it myself now and found, that the older Philips Hue Dimmer 324131137411 can be used with the "Controller - Philips 324131092621 Hue Dimmer switch“ blueprint (awesome-ha-blueprints/philips_324131092621.yaml at 9ee5920a3633c87bd8ee8713b83bbbf4705cc31d · EPMatt/awesome-ha-blueprints · GitHub) after going to the dimmer switch settings (specific) in Z2M and enabling the ‚legacy‘ setting there (I confused this with the general Z2M legacy API setting).
So this makes the blueprint above unnecessary.

From what I can gather → The “new” version of Zigbee2MQTT only exposes “Automation” end points - where as the old one (Legacy) exposes both a brightness and an action endpoint - so you can work with those.

Generally I’m thinking of putting my remote back into Hue because Z2M kinda sucks for it.

The remotes work well on ZHA if you have a spare dongle before firing up a Hue Bridge again, unless you already use the Hue Bridge for other things. Also, you don’t get the functionality in this blue print on the Hue Bridge. You only get light and dimmer function.
I know this sucks on Z2M with the latest versions, but on ZHA it works well, except for double press events. They are broken.