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

IKEA Dirigera lights not triggered first time #125622

Closed
durd opened this issue Sep 9, 2024 · 6 comments
Closed

IKEA Dirigera lights not triggered first time #125622

durd opened this issue Sep 9, 2024 · 6 comments

Comments

@durd
Copy link

durd commented Sep 9, 2024

The problem

Hi,

I'm using IKEA Dirigera through the Matter add-on. Works pretty good when it does work, it's noticeably faster.

But, after a few hours pass without a light being triggered. It seems that something is reset and the light needs to be triggered twice for it to turn on. I'm not sure how much time needs to pass, sometimes it seems like an hour, and sometimes several hours. The logbook shows the scene is being activated, but Overview shows that it's not turned on.
Once the light has been triggered to turn on, it works perfectly.
This happens with another light that also is only triggered by automations. Other lights I trigger manually with an IKEA smart switch and then is controlled by automations, these work fine.

I have an automation that depending on what time it is, activates different scenes which should turn on the light at a certain brightness and warmth. After presence turns negative, the lights are turned off.

Looking at the Matter addon logs it seems like it sends the same data both times. I've increased log levels in the addon, but logs rotate too quick. I've tcpdumped to check that HA sends packets which it does (via IPv6 link-local).

Any help or ideas are appreciated.

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter Server

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

home-assistant_matter_2024-09-09T17-54-44.662Z.log

There are three triggers in above log, the first fails to turn on the light, the second "turns off" the lights, and the last successfully turns the lights on.

Example YAML snippet

alias: Bathroom light on
description: ""
trigger:
  - type: occupied
    platform: device
    device_id: b6f0e85d3c081ec000ee117647d62692
    entity_id: 03d6d6dd66a32dbbdf00062f6dfc8669
    domain: binary_sensor
condition: []
action:
  - choose:
      - conditions:
          - condition: time
            after: "07:00:00"
            before: "08:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_07_08
      - conditions:
          - condition: time
            after: "08:00:00"
            before: "09:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_08_09
      - conditions:
          - condition: time
            after: "09:00:00"
            before: "20:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_09_21
      - conditions:
          - condition: time
            after: "20:00:00"
            before: "21:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_20_21
      - conditions:
          - condition: time
            after: "21:00:00"
            before: "22:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_21_22
      - conditions:
          - condition: time
            after: "22:00:00"
            before: "23:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_22_23
      - conditions:
          - condition: time
            after: "23:00:00"
            before: "07:00:00"
        sequence:
          - action: scene.turn_on
            metadata: {}
            target:
              entity_id: scene.bathroom_23_07
  - wait_for_trigger:
      - type: not_occupied
        platform: device
        device_id: b6f0e85d3c081ec000ee117647d62692
        entity_id: 03d6d6dd66a32dbbdf00062f6dfc8669
        domain: binary_sensor
  - metadata: {}
    data: {}
    action: light.turn_off
    target:
      device_id:
        - 4121016d171425142c947783f3dc86c7
        - 247a431d5ffdfccbee823850a8b45b7d
mode: single

Anything in the logs that might be useful for us?

Can't find any log errors that would give a clue.

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Sep 9, 2024

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign matter Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


matter documentation
matter source
(message by IssueLinks)

@durd
Copy link
Author

durd commented Sep 9, 2024

Can't figure out how to find the YAML for scenes. LMK how if you could use them too.

@durd
Copy link
Author

durd commented Sep 9, 2024

I found some information in the automations traces that I haven't seen before.

Screenshot 2024-09-09 at 23 08 36 Screenshot 2024-09-09 at 23 08 44

@marcelveldt
Copy link
Member

Can you please tell me how this is a HA/Matter issue if we send the command but the light doesn't respond ?

@durd
Copy link
Author

durd commented Sep 17, 2024

Because if I use the regular Homekit integration with Dirigera, the lights respond as expected with the same automation and scene.
I've duplicated the Choose-action so that I now have two after each other and that works when using the HA/Matter-integration.

I guess the issue could lie with automation or scenes. But as I mentioned, lights that I manually turn on with IKEA Rodret switches work with other automations using HA/Matter.
Edit: I could create an HA automation to handle this event instead of through the IKEA app/Dirigera. Would that help pinpoint the issue?

I'd be happy to provide better logs if you let me know how, I expected more than the little I got from following the official article on how.
Is there a way I can increase the amount of logs saved so I can see more instead of only the last 100 rows?

@durd
Copy link
Author

durd commented Oct 14, 2024

Good news! Somewhere between the Matter Server 6.6.0 update and IKEAs 2.660.2 the issue resolved itself.
I forgot to test after Matter Server upgraded.
Thanks for the help. I'll close the issue.

@durd durd closed this as completed Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants