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

Stopped reporting #116887

Closed
Doser86 opened this issue May 5, 2024 · 3 comments
Closed

Stopped reporting #116887

Doser86 opened this issue May 5, 2024 · 3 comments

Comments

@Doser86
Copy link

Doser86 commented May 5, 2024

The problem

After the Mai update folder watcher stopped reporting

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

core-2024.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

folder watcher

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

@home-assistant
Copy link

home-assistant bot commented May 5, 2024

@demey
Copy link

demey commented May 19, 2024

Same here.
After update to core-2024.5.4 yaml configuration was imported from configuration.yaml to UI.
Integration works only for local folders and does not work if folder attached using Samba/Windows (CIFS) on HA level.
Previously my configuration works without any problems.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 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

3 participants