-
Notifications
You must be signed in to change notification settings - Fork 4
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
Strange log error #24
Comments
Interesting, i'm guessing you don't have 2 inputs on your apex both called apex_Leak? It does create a unique ID based upon the controller IP/DNS and the input/output name. I guess one way to handle potential conflicts is to create the entity name based upon the DID instead of the name as the DID should always be unique. Will have to run some tests. |
indeed:
|
Ok will mean adapting another breaking change but in the next update I'll change the entity ID to use the DID but keep the name as the name. So theoretically automations shouldn't need changing but will need to reload the integration to remove duplicate sensors. New Id will be:
|
I looked at changing this to use the did instead of the name, but instead I went into the Apex and made sure all my devices were uniquely named. It felt like a better interface to have the names show up in the HA entity id than just the did. HA warned adequately of the problem, so I don't think the integration needs to change here. |
When restarting HA:
Platform apex does not generate unique IDs. ID 10.0.5.85-apex_Leak already exists - ignoring sensor.apex_leak
The text was updated successfully, but these errors were encountered: