#Conflicting integrations

1 messages · Page 1 of 1 (latest)

untold pier
#

Gecko just added their official integration to HACS to control in.touch 3 devices, primarily spas and hot tubs: https://github.com/geckoal/ha-gecko-integration

However there was a preexisting unofficial integration for older in.touch 2 devices: https://github.com/gazoodle/gecko-home-assistant

These two appear to cause a conflict such that Home Assistant thinks they’re the same integration. I previously had an in.touch 2 device already added and working properly using the unofficial integration. After adding the official integration, it’s combined both and shows a migration failure for the unofficial device (understandably).

I actually use both an in.touch 2 and 3 device. Is it possible for me to fix this? Do I need to fork the HACS repo and change some metadata so it shows up as a different integration? Does HA just use the display name to list/group integrations?

turbid dove
# untold pier Gecko just added their official integration to HACS to control in.touch 3 device...

ouch this is a bit painful. forking the unofficial integrations repo and changing its config (i beleive what you need is in manifest.json) would probably be the solution. you would have to set things up again but it most likely should work.

you may get issues down the line if the new integration decides to support the old devices too but that's a problem for down the line.

I would also suggest raising this as an issue on the unofficial repo and suggest changing its config to prevent this being a thing. this would obviously be a breaking change though.