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

Notifications trigger when turned on #718

Open
freggel2 opened this issue Mar 10, 2024 · 6 comments
Open

Notifications trigger when turned on #718

freggel2 opened this issue Mar 10, 2024 · 6 comments

Comments

@freggel2
Copy link

freggel2 commented Mar 10, 2024

Describe the bug

When the washer or dryer is ready I get a notification. But this notification is also sent when the washer or dryer is turned on. This was not the case before.
binary_sensor.dryer_dry_completed
binary_sensor.washer_wash_completed

Expected behavior

It is expected to be triggered only when the program is finished and not when the machines are turned on.

Screenshots

Environment details:

  • Environment HomeAssistant Raspberry pi4 SSd

  • Home Assistant version installed: Home Assistant

    Core 2024.2.5
    Supervisor 2024.02.1
    Operating System 12.0
    Frontend 20240207.1

  • Component version installed: 0.38.7

  • Last know working version:

  • LG device type and model with issue:

  • LG devices connected (list):

Output of HA logs
none


Additional context
Add any other context about the problem here.

lg

@ollo69
Copy link
Owner

ollo69 commented Mar 10, 2024

Please attach integration diagnostic captured before and after that the sensor change state

@freggel2
Copy link
Author

I want to do that but in the diagnostics there is some sensitive data like user id, ssid, etc.. I'm not comfortable with posting it here. The diagnostics has about 631.284 characters.

@ollo69
Copy link
Owner

ollo69 commented Mar 11, 2024

Just edit the files replacing data that you don't want provide. Normally that data are not really sensitive, data as Mac addr, password, access token etc should be already redacted. Please attach the file and don't paste contents in the thread.

@freggel2
Copy link
Author

Copy link

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Apr 28, 2024
@ollo69
Copy link
Owner

ollo69 commented May 4, 2024

@freggel2 ,

sorry but I was very busy on last months, but I do not forget this issue.
If this is still an issue for you, to analyze this I don't need integration logs but device diagnostic generated before and after the issue occurs. You can generate diagnostic directly from the device page.

Thanks👍

@ollo69 ollo69 removed the Stale label May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants