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

Conflict with Xfinity Gateway Integration #4

Open
RGSSoftware opened this issue Jan 7, 2020 · 2 comments
Open

Conflict with Xfinity Gateway Integration #4

RGSSoftware opened this issue Jan 7, 2020 · 2 comments

Comments

@RGSSoftware
Copy link

RGSSoftware commented Jan 7, 2020

I'm on Home Assistant v0.99.3 and using the Xfinity Gateway integration, but I'm getting a configuration error when I add xfinity-usage to my configuration. When I remove Xfinity Gateway from my configuration.yaml the below error goes await.

Installed with: HACS

Home Assistant

@robert-alfaro
Copy link
Owner

Thanks for reporting this issue..I've been expecting someone to notice this.

It boils down to the two components having the same name/domain. A hack is to modify the folder name in custom_components and to change the domain in this components manifest. This isn't friendly along with HACS..sorry.

The ultimate goal is getting the necessary portion of this component into a PyPI package and then getting this component merged with the gateway integration. That would work nicely since they are different platforms; one is a sensor, the other a device tracker.

@RGSSoftware
Copy link
Author

Ok, sounds great.

If anyone else is looking for a HACS workaround until this component is merged with the gateway integration, you can use this.

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