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

Xsense invalid config #141587

Open
meeuwsenha opened this issue Mar 27, 2025 · 2 comments
Open

Xsense invalid config #141587

meeuwsenha opened this issue Mar 27, 2025 · 2 comments

Comments

@meeuwsenha
Copy link

The problem

The integration needed to be installed with HACS in the past. But now you can get the integration in HA. Since a few weeks the integration says 'invalid config'. I did try to delete and install again but now the integration can't see any devices when I'm logged in.

The 'invalid config' logs are also disappeared in HA.

I also couldn't find the integration on the HA website so the known information is from GitHub.

What version of Home Assistant Core has the issue?

core-2025.3.4

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

Xsense

Link to integration documentation on our website

https://github.com/Jarnsen/ha-xsense-component_test/blob/main/readme/README_en.md

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@thecode
Copy link
Member

thecode commented Mar 27, 2025

I don't find any Ha core integration named Xsense or anything with sense that was recently added.
Can you link to the integration you are using from HA:
https://www.home-assistant.io/integrations/
Search in the link above and post the integration, if it is not there you need to create an issue for the custom component

@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.

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