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.08k stars 31.09k forks source link

Only every second lamp switching off is registered by the system #125273

Open imago54 opened 2 months ago

imago54 commented 2 months ago

The problem

Issue started to appear in one of the latest releases. Consistent for two MJTD01SYL Desktop Lamps by Yeelight Technology istalled in HA as HomeKit Devices.

Steering from the HA works perfectly, but when the device is turn off by its hardware switch only every second turn off is registered while each turn on is registered correctly.

What version of Home Assistant Core has the issue?

core-2024.9.0

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

HomeKit Device

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

### Tasks
home-assistant[bot] commented 2 months ago

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

Code owner commands Code owners of `homekit` 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 homekit` 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)


homekit documentation homekit source (message by IssueLinks)

home-assistant[bot] commented 2 months ago

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

Code owner commands Code owners of `homekit_controller` 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 homekit_controller` 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)


homekit_controller documentation homekit_controller source (message by IssueLinks)

bdraco commented 2 months ago

Please follow the troubleshooting steps and provide Debug logs AND diagnostics

https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

imago54 commented 2 months ago

Are there any ways to anonymize the logs before sharing?

On Wed, Sep 4, 2024 at 11:38 PM J. Nick Koston @.***> wrote:

Please follow the troubleshooting steps and provide Debug logs AND diagnostics

https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/125273#issuecomment-2330190149, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJUDM47ZOW7AM3R7HOPS2TZU54T7AVCNFSM6AAAAABNVFGR42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGE4TAMJUHE . You are receiving this because you authored the thread.Message ID: @.***>

imago54 commented 2 months ago

Or can they be shared privately?

bdraco commented 2 months ago

You can send them to my dropbox nick@koston.org or gdrive bdraco@gmail.com

But that also means nobody else can help and you'll have to wait for me to have time to look.

imago54 commented 2 months ago

Sent to gdrive. Pl let me know if anything else is needed. Thanks.

bdraco commented 2 months ago

Firmware version 2.1.20

bdraco commented 2 months ago

I see nothing wrong in the logs so it might be a firmware issue in the device that was previously only working because we were polling the device every 30s, but we stopped doing that as it lead to crashing devices.

imago54 commented 2 months ago

Well, the actual version is 2.1.7_0020 and manufacturer app claims that this is the latest version. I haven't updated it recently and the issue is very consistent. Every second manual turn on of the light is registered by the HA.

imago54 commented 2 months ago

Screenshot_20240905-184551_Mi Home_r

imago54 commented 2 months ago

Previously each manual turn on of the light was registered by HA immediately not with a delay of few or up to 20s.

imago54 commented 2 months ago

Is there a way to trigger the status check (pooling) manually? So I could create an automation to w/o that problem?