home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.2k stars 31.16k forks source link

Philips Hue Automation - Vimar Friends of Hue switches #63799

Closed giles-sr closed 2 years ago

giles-sr commented 2 years ago

The problem

I’m using Vimar Friends of Hue switches (four button version), connected to a Hue bridge. In HA under automations (in the gui) I had the option to press/output multiple button presses at once i.e. when I push button 1 & 3 it opened an Ikea (Zigbee) blind. Since 2021.12 in automations under the ‘device’ doesn’t show multiple button presses as an option, and my previously created automations are greyed out.

What version of Home Assistant Core has the issue?

2021.12.8

What was the last working version of Home Assistant Core?

2021.11

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Philips Hue

Link to integration documentation on our website

No response

Example YAML snippet

Example of previous yaml text/automation (I’ve taken out ID’s):

- id: ''
  alias: Landing Blind V-Open
  description: ''
  trigger:
  - device_id: 
    domain: hue
    platform: device
    type: remote_double_button_short_press
    subtype: double_buttons_1_3
  condition: []
  action:
  - device_id: 
    domain: cover
    entity_id: cover.landing_blind
    type: set_position
    position: 100
  mode: single
- id: ''

Anything in the logs that might be useful for us?

No response

Additional information

I know the Hue integration has changed under 2021.12 can this be resolved? Happy to be in contact with the developer to help resolve if needed. Many thanks in advance

probot-home-assistant[bot] commented 2 years ago

Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)


hue documentation hue source (message by IssueLinks)

marcelveldt commented 2 years ago

Hi, at this time you're out of luck as Signify removed these events from their API. We're trying to get in touch with them about the few missing parts in the new API. In the meanwhile you could try to complain on their forum. We can't do magic and provide support for something that is removed by the vendor.

q1x commented 2 years ago

Having a somewhat similar issue here on my Busch Jaeger FoH switches and also on my Philips Dimmer Switches. Long presses are no longer registered in the Home Assistant hue events, but they did until recently (I upgraded to 2021.12 this week).

Is this also related to missing API events or is this a different issue that I need to report separately?

Edit: Turns out long presses still work for the philips dimmer switches, but the event looks completely different from before and I need to adjust my automations. FoH switches no longer register long presses at all for some reason.

marcelveldt commented 2 years ago

Edit: Turns out long presses still work for the philips dimmer switches, but the event looks completely different from before and I need to adjust my automations. FoH switches no longer register long presses at all for some reason.

Yes, that was mentioned pretty clearly in the release notes.

marcelveldt commented 2 years ago

@giles-sr we've received a reply from Signify that the multi press events for FoH remotes will not be back on the new V2 api, at least it doesn't have priority.

If you really rely on the multi button press, maybe add these switches to an external zigbee stick ?

q1x commented 2 years ago

Edit: Turns out long presses still work for the philips dimmer switches, but the event looks completely different from before and I need to adjust my automations. FoH switches no longer register long presses at all for some reason.

Yes, that was mentioned pretty clearly in the release notes.

Couldn’t find a notice about breaking changes here: https://www.home-assistant.io/blog/2021/12/11/release-202112/ but maybe I’m looking in the wrong place?

That being said, the new api events looks a lot easier to work with, plus the better integration it allows is definitely a plus. I’ll just need to find another workaround for the FoH switches.

thanks for the great work!