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 - Aqara Opple 6 Button don't work (wxcjkg13lm) #591

Open
1 task
Typ1er opened this issue Jan 6, 2024 · 0 comments
Open
1 task

Bug - Aqara Opple 6 Button don't work (wxcjkg13lm) #591

Typ1er opened this issue Jan 6, 2024 · 0 comments
Labels
blueprint An issue related to a blueprint bug Something isn't working

Comments

@Typ1er
Copy link

Typ1er commented Jan 6, 2024

Blueprint name

xiaomi_wxcjkg13lm.yaml

Home Assistant Core Version

2024.1.1

Home Assistant Installation Type

Home Assistant Operating System

Description

I have a problem getting my Opple 6 button to work with the Blueprint.

From another blueprint for the 2 button Opple. I had to remove this line (attribute: action), then the blueprint worked. I also had the same problem with my HueTap (ZGP) switch. Both blueprints contain this line under the trigger:

trigger:
platform: state
entity_id: !input action_sensor

attribute: action

Do I have the wrong setting in Zigbee2mqtt or has something changed in HomeAssistant? Can I change the setting here, if so where?

Here is the blueprint, which works so far.
https://community.home-assistant.io/t/zigbee2mqtt-aqara-opple-switch-2-buttons-wxcjkg11lm/504310

The automation is triggered somehow, the timestamp is reset each time.

Automation YAML config

alias: Controller - Xiaomi WXCJKG13LM Aqara Opple 6 button remote
description: ""
use_blueprint:
  path: EPMatt/xiaomi_wxcjkg13lm.yaml
  input:
    action_button_1_short:
      - service: light.toggle
        metadata: {}
        data: {}
        target:
          device_id: 25ec6d2e8579a2873ead83e0d2bd3f41
    integration: Zigbee2MQTT
    controller_entity: sensor.schlafzimmer_lichtschalter_2_action

To Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Trigger the automation '....'
  4. See error

Expected behavior

no text

Actual Behaviour

no text

Additional Details

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

Screenshots

No response

Additional context

No response

@Typ1er Typ1er added blueprint An issue related to a blueprint bug Something isn't working labels Jan 6, 2024
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

1 participant