Anto79-ops Posts - Answer Overflow

Anto79-ops

•Created by Anto79-ops on 6/21/2024 in #💬・get-help

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

37 replies

HHASS.Agent

•Created by Anto79-ops on 2/29/2024 in #💬・get-help

mqtt discovery on every update bug

Hey! I'm currently in HA core beta, and was looking for other bugs but ended up noticing that hass.agent does something that's not very efficient on the home assistant side, it sends the discovery payload on every update for every sensor which cost CPU time on HA. For example

4-02-28 15:45:46.785 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ANTO_HP a2c6a82f-f7a9-4e48-aa6e-2e47c3df05ce_total_disk_count, sending update

4-02-28 15:45:46.785 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ANTO_HP a2c6a82f-f7a9-4e48-aa6e-2e47c3df05ce_total_disk_count, sending update

I reported the exact same thing for another integration and you may want to read this here: https://github.com/bachya/ecowitt2mqtt/issues/704 This will definitely lower the burden on HA when it does mqtt processing. I'm running 2.0.1. Sorry if this was already fixed in beta or even reported already

50 replies

HHASS.Agent

•Created by Anto79-ops on 1/25/2024 in #💬・get-help

Sensors become unavailable after a while but all green status in HASS.agent

6 replies

HHASS.Agent

•Created by Anto79-ops on 12/29/2023 in #💬・get-help

how to get started - migration?

hello! I've read the docs but not sure about a couple of things. At the moment, I have the old HASS.agent service and satellite running with Win10 computer and HA(HAOS). Do I have to uninstall the Windows program and use the new beta? do I have to remove the HA integration also and replace that, also? thanks

178 replies

Gaming

Programming