-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error Log: Platform meshtastic does not generate unique IDs. #17
Comments
Thank for reporting. It is kind of a known issue and can happen in certain circumstances, it can also happen for notify entities. I think in your case the issue is the old entities still lying around. You probably can workaround that issue when you reconfigure the config entry. You don't need to delete and re-add a gateway when the IP address changes. For the entry in question, use the three dots next to configure and select reconfigure. |
Another new instance when this can happen: If the gateway node loses its name, we fallback to default short name, and thus get different entity ids. Will also happen when short name of the gateway node is changed
|
I did notice that the shortname is being used in the entityid, and in my case that shortname is an emoji (which is encouraged in meshtastic). But I don't think we should be using an emoji in entityids inside homeassistant? It feels like the nodeid should be enough, and that generally speaking doesn't change because it's tied to the BT MAC of the device. |
Did notice that as well in your logs and was surprised. But nice that it actually seems to work perfectly fine in home assistant. I think there is nothing that forbids emojis in entity ids (probably the allow all unicode except some reserved characters) Using short name was an attempt to get some more meaningful entity ids. At least the gateway is expected to have rather static short name. Otherwise you end up with It is still unclear to me what the best strategy is for entity ids. |
Im am having the same issue, the log is full of this errors |
I suspect in your case it is caused by adding the same gateway via two different interfaces (TCP and serial) |
Im only using one TCP connection, another node arrives tomorrow for the (hopefully) more stable serial connection. |
I get the same messages in my debug log, and a whole bunch of other issues. |
Can you share some of the log message so that we know what instance of this problem yo have? I don't know exact details when and how home assistant cleans old data. You will for need to remove the configuration in Home assistant and then restart. Removing the integration beforehand might prevent from cleaning up the old data. |
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Checklist
Describe the issue
Error log complaining that Meshtastic platform component does not generate unique IDs
Reproduction steps
...
Debug logs
The text was updated successfully, but these errors were encountered: