You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Love this integration, I monitor around 30 things with it. I know the integration creates a binary_sensor and a regular sensor for each monitor. I don't need a normal sensor, so I disable them, but they all come back after a day or so. I think it's tied to Uptime Kuma itself reloading and not an integration reload.
Thank you for looking into this
The text was updated successfully, but these errors were encountered:
I'll have to take a closer look, but I think this is expected since the entities are re-created each time HA polls UptimeKuma. It was designed this way so you wouldn't have to manually add sensors to Homeassistant after updating UptimeKuma with a new monitor.
I meant to say that the sensors and binary_sensors are re-created each time, but yes, I could see some people preferring just the binary_sensors. You can file that as a separate issue.
This current issue about sensors not staying hidden may be able to be worked around by first checking if a hidden entity exists with the same id, if so, don't re-create it, but i'm just speculating here. I'd have to take a closer look at it (or maybe someone else would be willing to?).
Love this integration, I monitor around 30 things with it. I know the integration creates a binary_sensor and a regular sensor for each monitor. I don't need a normal sensor, so I disable them, but they all come back after a day or so. I think it's tied to Uptime Kuma itself reloading and not an integration reload.
Thank you for looking into this
The text was updated successfully, but these errors were encountered: