HASS.Agent•4mo ago

Platform mqtt does not generate unique IDs upon updating to beta2

Hey, thanks for the awesome update! Just updated to beta2 from beta1. I simply ran the installer and followed the prompts and chose migratation. If came back fine, except 2 of my sensors command config sensors came back to HA with the does not generate unique IDs.

Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:766
integration: Switch (documentation, issues)
First occurred: 9:45:58 AM (1 occurrences)
Last logged: 9:45:58 AM

Platform mqtt does not generate unique IDs. ID a61b46e5-132a-48a2-a191-27246f47ba3a is already used by switch.anto_hp_monitorsleep - ignoring switch.anto_hp_monitorsleep_2

Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:766
integration: Switch (documentation, issues)
First occurred: 9:45:58 AM (1 occurrences)
Last logged: 9:45:58 AM

Platform mqtt does not generate unique IDs. ID a61b46e5-132a-48a2-a191-27246f47ba3a is already used by switch.anto_hp_monitorsleep - ignoring switch.anto_hp_monitorsleep_2

and

Logger: homeassistant.components.button
Source: helpers/entity_platform.py:766
integration: Button (documentation, issues)
First occurred: 9:45:58 AM (1 occurrences)
Last logged: 9:45:58 AM

Platform mqtt does not generate unique IDs. ID 5de271fa-4485-4bd6-bd03-e74dfae8e55e is already used by button.anto_hp_monitorwake - ignoring button.anto_hp_monitorwake_2

Logger: homeassistant.components.button
Source: helpers/entity_platform.py:766
integration: Button (documentation, issues)
First occurred: 9:45:58 AM (1 occurrences)
Last logged: 9:45:58 AM

Platform mqtt does not generate unique IDs. ID 5de271fa-4485-4bd6-bd03-e74dfae8e55e is already used by button.anto_hp_monitorwake - ignoring button.anto_hp_monitorwake_2

its only 2 sensors, so not a bid deal. How can solve this? Should I just delete them and re-make the sensors or does HA simply need to be restarted? thanks

Solution:

here's what I did. I ended up deleting it in Hass.Agent configuration, then in MQTT explorer on HA side. Remade the sensors and they are now working without errors. Maybe justa glitch somewhere.

Jump to solution

17 Replies

Amadeo•4mo ago

I need to make it clear in the installer that migration is only when going from original to fork. Between fork versions it's not required May I please see your sensors file from config folder?

Anto79-ops•4mo ago

sure sorry bud, where can I get this file?

Amadeo•4mo ago

Within the HASS.Agent UI go to settings, then logging and click on "open logs folder" It will open a new window with logs, go back/up one folder and then to "config" C:\Users\username\appdata\local\HASS.Agent\client\config (Path from memory :D) You should find json files there with general config, sensors and commands

Anto79-ops•4mo ago

you got a good memory! but for the record, its only the command buttons giving that error

Anto79-ops•4mo ago

commands.json

Amadeo•4mo ago

That's strange In the config there are only 2 entries Is it possible that you have two instances of HASS.Agent running?

Anto79-ops•4mo ago

thats possible. I mean, maybe it didn't shutdown properly

Amadeo•4mo ago

This is the only logical explanation I can think of, there should be no way to have two forked instances Old one maybe? Unless we have a bug

Anto79-ops•4mo ago

yeah, im not sure. Maybe I'll reboot the Windows computer and reboot HA. I mean if there was another instance running, would it also give that error for all the sensors?

Amadeo•4mo ago

Good point Unless the config differs between them If you reboot and it still happens the best way to find it out is to either look at task manager if there are two "HASS.Agent.exe" processes or to remove those two buttons and then seing in HA if they are still "available"

Anto79-ops•4mo ago

ok, great. rebooting the Windows machine, and im only seeing these running:

Anto79-ops•4mo ago

I'll reboot HA in about 1 hr, I think they getting read to release 2024.6.4 shortly BTW, when you say remove those buttons, you mean in HA just delete the entity and it should come back? actually nvm, i cannot delete the entity

Amadeo•4mo ago

Delete them in the forked HASS.Agent and then checking if entity is not unavailable in HA (that would mean there are other instances) If it will still be an issue then we might look at orphaned entities in HA

Solution

Anto79-ops•4mo ago

here's what I did. I ended up deleting it in Hass.Agent configuration, then in MQTT explorer on HA side. Remade the sensors and they are now working without errors. Maybe justa glitch somewhere.

Amadeo•4mo ago

Now I'm curious as hell what caused it, might play in vm with "double migration" to see if it happens

Anto79-ops•4mo ago

Yeah sorry I can't be of more help. Unless it had anything to do with me checking the migration option

Amadeo•4mo ago

all good I'm glad it works 😄

Gaming

Programming

Platform mqtt does not generate unique IDs upon updating to beta2