If you have a configured switch in the HUE app there is a “reset” below the line stating “Configure in Apple Home”. When I press this “reset” it show a new setup page. In the buttom of this page there is a “configure in another app”. Then you have a “not configured” switch in the HUE app
Just tested it:-) Hope the wife/kids will not enter the kitchen during the next 5 min:-)
…BINGO … so now i just have to instal the right blueprint and re config the 5 X4 clicks… Hope the family dont come home for another 3 hours or so … WAHA
Hmm i can se the buttons sends signal to HA but the action from the blueprint dont show. aka nothing happens. Tried with “room” and also with “entitet”
short release and press … still no light? What do i miss
Which version of the blueprint? I know the version in post 1 works, as I use it
Tried the advanced one from post 32
will test the one from post 1 today… 
Post 32 and post 1 is currently the same. You mentioned 4 taps, so I thourght you might be using the blueprint from post 69, which i do not know.
Try and describe the error, we should be able to get this to work with the post 32 blueprint.
ah well i have them both and none off them are working .
The error - simple noting happends .
The assigned light(s) stay off (or on- tried to toggle and Off) i can se the switch being pressed in the tracking, but some how it doesn’t affect the bulb …
also tried to hit “run” in the blueprint- and the light respond perfect. But pressing the button no respond…
“Trace” in the automation, does that show anything when triggered. Is the blueprint triggerede at all?
If triggerede, please take a snapshot and paste here. Something like this.
Your automation, what is the yaml code?
im having the yaml in front -as shown i can mode the picture/trace behind but not se it all at once …
I can see your screeeshot is from the blueprint in post 69. Please use post1/32 for this to work. When we have that one working, then you can try the one in 69.
I can have it all in one screenshot.
Your YAML for the automation, copy it from the automation in YAML mode and paste using the preformated text mode, so it looks like this
alias: Køkken kontakt
description: ""
use_blueprint:
path: Hue-Friends-of-Hue-All-Functions.yaml
input:
hue-switch-button1:
- event.kokken_kontakt_button_1
hue-switch-button2:
- event.kokken_kontakt_button_2
hue-switch-button3:
- event.kokken_kontakt_button_3
hue-switch-button4:
- event.kokken_kontakt_button_4
button_1_short_release:
- service: input_boolean.toggle
metadata: {}
data: {}
target:
entity_id: input_boolean.aa_test_boolean
Well made a little test. Ilet the entry for the 4 bottons stay i HUE - and replicated them i in HA with a little extra bullb to se if the blueprint was on the job. Now it works.
After that, deleted the switch in HUE app - and it still works… SUCCES. Thanks for staying om the problem @khvej8 … Still have to se how i make a screen shot of the trace in a whole pic.
Not sure I understand “after that, deleted the switch in HUE app”, as the switch should be in the HUE app, with no actions.
Well, if it works, then we are all happy 
If i start with the switch with no actions in the HUE app / aka start with it in “controlled in another app” then the bluprint dont work.
If i have action i the hue app - then make action in AND THEN discard the actions in the HUE app/ turn it to be “controlled in another app” then it works.
So… make actions in the HUE app for al 4 buttons- then make same or different action i HA / Blueprint and the discard the actions in the HUE app…
Just tested again - it will not trigger the action if there are no actions in HUE …
Hey,
I am trying to make the blueprint work for me. However, I am running into a problem
In the traces I always get this error message
Any idea what causes this?
Try the blueprint in post 1, the first post in this thread. The one you use needs a lot of additional setup
I have been using the blueprint for a few months now, but since today, dimming and brightening the lights no longer works. This problem occurs on all 4 buttons (2 switches). Anyone have an idea what’s going wrong?
Turning on or off works.
alias: Schakelaar berging kantoordeur
description: ""
use_blueprint:
path: mertodinlo/foh4bbp.yaml
input:
hue-switch-button1:
- event.friends_of_hue_switch_1_button_1_2
hue-switch-button2:
- event.friends_of_hue_switch_1_button_2_2
hue-switch-button3:
- event.friends_of_hue_switch_1_button_3_2
hue-switch-button4:
- event.friends_of_hue_switch_1_button_4_2
button_1_short_release:
- service: light.turn_on
metadata: {}
data: {}
target:
entity_id: light.berging
button_2_short_release:
- service: light.turn_off
metadata: {}
data: {}
target:
entity_id: light.berging
button_3_short_release:
- service: light.turn_on
metadata: {}
data:
kelvin: 2470
brightness_pct: 12
target:
entity_id: light.hue_aurelle_panel_1
button_4_short_release:
- service: light.turn_off
metadata: {}
data: {}
target:
entity_id: light.hue_aurelle_panel_1
button_1_long_release: []
button_2_long_release: []
button_1_repeat:
- service: light.turn_on
metadata: {}
data:
brightness_step_pct: 10
target:
entity_id: light.berging
button_2_repeat:
- service: light.turn_on
metadata: {}
data:
brightness_step_pct: -10
target:
entity_id: light.berging
button_3_repeat:
- service: light.turn_on
metadata: {}
data:
brightness_step_pct: 10
target:
entity_id: light.hue_aurelle_panel_1
button_4_repeat:
- service: light.turn_on
metadata: {}
data:
brightness_step_pct: -10
target:
entity_id: light.hue_aurelle_panel_1
button_3_long_release: []
Have you upgraded to 2024.07?
I do not use the blueprint anymore, as I have moved the switches to Zigbee2MQTT, however moved one back to test.
The Hue_event still shows a “repeat”, however the automation using the variable will get a initial_press value with the same timestamp. These should be the same and was earlier.
Have you tired to move to 2024.06.xx. If it works, then it is a Hue integration problem. Needs to be reported to the Hue integration developers.
Or, anybody else on 2024.06 and can test?
EDIT:
Found this issue,
Hue FoH switches not longer fire long press · Issue #119807 · home-assistant/core (github.com)
Pretty sure this is same issue. However a change from 2024.05 to 2024.06.
thnx for the link, i can’t get Zigbee2MQTT to work but maybe i can add the switches to ZHA.
I believe they will solve the problem. Maybe comment on the GitHub case, so they know others hve the issue
There is currently an error, probably started by 2024.07 or 2024.06. As the repeat and long_release is not triggerede correctly in the integration, the blueprint is not working
The initial_press and short_release are working. Be aware that if you make a long press it will result in several “initial_press” commands.
The error is handled in this Github issue
Hue FoH switches not longer fire long press · Issue #119807 · home-assistant/core (github.com)
I will report back when solved.