Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug - ZHA E2002 Long Press Down not releasing #698

Open
1 task done
kkthxbye-code opened this issue Feb 25, 2025 · 12 comments
Open
1 task done

Bug - ZHA E2002 Long Press Down not releasing #698

kkthxbye-code opened this issue Feb 25, 2025 · 12 comments
Labels
blueprint An issue related to a blueprint bug Something isn't working

Comments

@kkthxbye-code
Copy link

Blueprint name

Controller - IKEA E2001/E2002 STYRBAR Remote control

Home Assistant Core Version

2025.2.5

Home Assistant Installation Type

Home Assistant Container

Description

When using an IKEA E2002 STYRBAR with zha as the integration, the brightness down hold command does not release and keeps turning down the brightness until another button is held.

Automation YAML config

alias: IKEA Remote N2 1 Automation
description: ""
use_blueprint:
  path: EPMatt/ikea_e2001_e2002.yaml
  input:
    integration: ZHA
    controller_device: 3d26ff8eff16feb11377f4450d9d92ef
    helper_last_controller_event: input_text.ikea_remote_n2_1_last_controller_event
    button_up_long_loop: true
    button_right_long_loop: true
    button_left_long_loop: true
    button_down_long_loop: true

To Reproduce

  • Use the ZHA integration option
  • Add E2002 device
  • Add the light hook
  • Hold the brightness down button and release

Expected behavior

Brightness should stop turning down.

Actual Behaviour

Brightness keeps turning down.

Additional Details

  • I'd like to help developing a fix for this issue.

Screenshots

No response

Additional context

I fixed it locally by adding stop_0_0 to button_down_release.

button_down_release: [stop, stop_with_on_off, stop_0_0]

At least my controller sends stop_0_0:

event_type: zha_event
data:
  ...
  endpoint_id: 1
  cluster_id: 8
  command: stop
  args:
    - 0
    - 0
  params:
    options_mask: 0
    options_override: 0
origin: LOCAL
...
@kkthxbye-code kkthxbye-code added blueprint An issue related to a blueprint bug Something isn't working labels Feb 25, 2025
kkthxbye-code added a commit to kkthxbye-code/awesome-ha-blueprints that referenced this issue Feb 27, 2025
@AlTyndall
Copy link

Has anyone noticed their right/left buttons not working? I've recently updated to 2025.2.5 and none of my 5 Styrbar remotes' left/right buttons are firing anything that they used to in the automation. I can run the associated routines manually from within editing the automation itself). I don't know quite how to submit anything (nor see what command the buttons are sending to HA or not), but I wondered if this had been noticed by anyone else who might be able to confirm yea/nay whether it is a common thing?

@yarafie
Copy link
Contributor

yarafie commented Mar 6, 2025

I'm using zigbee2mqtt and all buttons working as expected after upgrage to latest HA 2025.3.0

@AlTyndall
Copy link

Sorry - should have mentioned I'm on ZHA.

@yarafie
Copy link
Contributor

yarafie commented Mar 7, 2025

Sorry - should have mentioned I'm on ZHA.

I don't use ZHA but can help debug if you do the below

In homeassiatant go to Developer Tools -> Events and Listen/Subscribe to the Events for your Styrbar.

Start clicking the buttons on the Styrbar you should see the text of the event something like what is between the brackets [ ] below for each button at least the text part the numbers may not appear joined to the text take note of what you see.

zha:
  button_left_short: [press_257_13_0]      <------ Left Arrow <
  button_left_long: [hold_3329_0]              <------ Left Arrow <
  button_left_release: [release]                   <------ Left Arrow <
  button_right_short: [press_256_13_0]    <------ Right Arrow >
  button_right_long: [hold_3328_0]            <------ Right Arrow >
  button_right_release: [release]                 <------ Right Arrow >
  button_up_short: ['on']                               
  button_up_long: [move_with_on_off_0_83, move_with_on_off_MoveMode.Up_83]
  button_up_release: [stop, stop_with_on_off, stop_0_0]
  button_down_short: ['off']
  button_down_long: [move_1_83, move_MoveMode.Down_83_0_0]
  button_down_release: [stop, stop_with_on_off]

@AlTyndall
Copy link

I've tried firing events and listening for them. The up and down buttons result in zha_events, but nothing registering with the left/right buttons. 🤔

I wonder whether the built-in quirks have changed between 2025.1 and 2025.2.5? Any ideas where I should take this? ZHA help with HA?

Thanks all.

@yarafie
Copy link
Contributor

yarafie commented Mar 8, 2025

What firmware version is your e2001?

@AlTyndall
Copy link

What firmware version is your e2001?

0x00010024

Wouldn't know how to update the firmware if necessary, though. Can't see any options to change it, and the "Configuration" entry for Firmware is "unknown". Hadn't been an issue until I updated to 2025.2.5...

@yarafie
Copy link
Contributor

yarafie commented Mar 8, 2025

Ok. I'm trying to setup ZHA on my system and also happen to have a styrbar at that same version of firmware which is the older firmware latest is 2.4.16 which I also have one of my styrbars at.

May take me a day or two to figure it out then I can test both to see what is going on.

BTW HA is now at 2025.3.1 which is what I'm using.

@AlTyndall
Copy link

Amazing. Thank you.

I tend to avoid the .0 and .1 updates. I've been left without Tuya and Tado control a few too many times by doing the early releases, so I tend to wait until the end of the month for things to settle down!

@yarafie
Copy link
Contributor

yarafie commented Mar 9, 2025

@AlTyndall

Some good news and some bad news.

I was able to run zha and zigbee2mqtt in parrallel tested the strybar with the latest firmware 2.4.16 and all buttons regstered fine. So I know that it works with at least the latest strybar firnware,

Unfortunatly this crashed my system befiore I could test with a strybar with the 10024 firmware. I had to restore without ZHA.

So, If i were to suggest. Remove the current strybar and pair it again and check after that if the left and right buttons work. If not you will need to figure out how to update the firmware.

Sorry but wish I could have helped more.

@AlTyndall
Copy link

I wonder if it has anything to do with this...

zigpy/zha-device-handlers#3135

Perhaps the firmware got upgraded, which broke some bits, which got fixed and applied recently, but broke the old firmware as a result?

I'll try upgrading the firmware using the instructions in the above thread (but not quite yet - not got the time to do proper remedial work if it breaks them altogether - at least I have up/down at the moment!).

Thanks for your time spent. I'll update when I have some sort of answer.

@yarafie
Copy link
Contributor

yarafie commented Mar 10, 2025

I wonder if it has anything to do with this...

zigpy/zha-device-handlers#3135

Perhaps the firmware got upgraded, which broke some bits, which got fixed and applied recently, but broke the old firmware as a result?

I'll try upgrading the firmware using the instructions in the above thread (but not quite yet - not got the time to do proper remedial work if it breaks them altogether - at least I have up/down at the moment!).

Thanks for your time spent. I'll update when I have some sort of answer.

You just jogged my memory on why I had 2 Strybars sitting idle.

A while back i updated the firmware on the two that were being used and they both stopped working. So I went down to our local Ikea and bought 2 more. They worked fine (they both were on firmware10024) the old ones were 2.4.11 and eventually 2.4.16 but I ran into another problem in which I couldn't pair them (I'm using zigbee2mqtt).

Fast forward to today, I managed 2 pair them (I'm using the latest zigbee2mqtt) and they both worked,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blueprint An issue related to a blueprint bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants