This integration merges with and breaks another integration.

[ThatBeardGuy]

This integration has the same name as this one and "merges" with it: https://github.com/Andre0512/hon

It makes all sensors unavailable and breaks it when this integration is removed (probably removes both when you remove one).

[gvigroux]

I'm using this name since the first implementations 2/3 years ago :(. I don't know the impact of changing the main directory name.

[ThatBeardGuy]

I did not know that, it showed up as a new integration on HACS a few days ago. I assumed it was new because of that. Does not change the fact that currently both integrations cannot work side by side, they might both have an issue if something official would come out with the same name.

[gvigroux]

I tries to do some tests but there is a lot of complications...

1. all users will lose their configuration

• they will have to delete the previous invalid config
• reconfigure the integration

2. I cannot do the change because I have no integration images attached to the new domain name. So before I will have to post new images.

Why you need both integrations ?

[ThatBeardGuy]

The integration I have been using has a few quirks that makes it difficult to actually automate my washing machine. So for now I was just curious if I can get that to work using your integration, though part of the testing would be to check a few sensors I already have setup using the other integration.

So if yours can fill the functions I am currently missing or overlooking in the other integration, it might prove useful to run them both. for now I did try to just rename the folder where the other integration was in, but that doesn't work and makes the sensors unavailable

[gvigroux]

I totally understand the struggle and this problem have to be fixed in my extension. But did you try it this one alone ? You will be able to automatize everything with services :)

[JeanMertz]

I have a related question; I too use the "other" plugin. It has a ton of entities, and I expose some of those to our mobile devices via HomeKit. The biggest issue the other plugin has, is that I cannot force it to always disable the device "beep", or to disable the on-device display (I can disable the screen, but any subsequent action resets the screen state).

This plugin would solve that (since I can define multiple attributes in a single action), but from the screenshots, it does not appear that this device exposes any actual device-specific entities by default. Is that correct?

Can I get those entities to appear by manually adding them somehow?

[gvigroux]

Some sensors are reported in this extension. For my climate, on top of standard temperature (I can check them with Google), i've added

• Child Lock
• Health Mode
• Light
• Status

I can add more if needed. Which one do you need ?

[Kfrard]

Are there any plans for this situation? I think it would be worth changing the name, despite the need to reconfigure it for everyone, so that it does not cause conflicts in future custom_integrations (or forks of current custom_integrations). https://github.com/hacs/integration/issues/3883

[tjorim]

so that it does not cause conflicts in future add-ons (or forks of current add-ons).

This is an integration, not an add-on. Add-ons use an automatically generated slug based on the repository author and name (and will not have the issue).

[Kfrard]

so that it does not cause conflicts in future add-ons (or forks of current add-ons).

This is an integration, not an add-on. Add-ons use an automatically generated slug based on the repository author and name (and will not have the issue).

Of course you are right, I meant custom_integrations, not add-ons.

[tjorim]

I know of one other custom integration that recently went through the struggle of renaming theirs, not sure how they did it but might be useful for someone: https://github.com/sca075/mqtt_vacuum_camera