Monitors added after Integrating with Home Assistant do not appear as entities

[WolfBrandon]

After installing Uptime Kuma, adding monitors, and adding the integration, the initial pull of metrics was successful and all monitors appear as entities. However, after adding any new monitor, and even clicking "reload" on the integration, they will not appear as entities unless I remove and re-add the integration.

Logs do not show any errors -- I see the /metrics endpoint being accessed, but the returned monitor_response does not include the newly added monitor. Accessing the /metrics endpoint directly does show the newly added monitor.

Not sure if this is expected behavior, but it defeats the purpose of the "reload" function.

[meichthys]

I'm not sure what the issue is since it works for me :/ I was able to setup a monitor, and reload HA and see the entity immediately.

[meichthys]

[WolfBrandon]

Strange...I just added the exact same monitor and no dice. Fully appreciate this could be something unique to my setup, but I'm not really doing anything radical (synopsis below) -- any advice on where to look besides logs? Here's a quick overview of my setup:

Running HAOS on baremetal

• Home Assistant 2023.8.4
• Supervisor 2023.08.1
• Operating System 10.5
• Frontend 20230802.1 - latest

Running Uptime Kuma on a separate server, in a Docker Container

• v1.23.0 (I will update shortly)
• 40 monitors (38 appear in HA)
• Mix of HTTP and Ping, nothing more

[meichthys]

I'm still at a loss for ideas, but i can confirm that i'm on the same HA version as you and I also run HaOS. I also run uptimekuma in a docker container, however i do have my UK behind a nginx reverse proxy like nginxproxymanager. I would recommend looking into using a reverse proxy so you can use an SSL cert which may help here. It also allows you to use a domain name for your internal services - so you can have uptimekuma.yourdomain.com, homeassistant.youredomain.com, etc.

[WolfBrandon]

Just out of curiosity, I disabled the integration, restarted HA then re-enabled the integration and it seems to be working as expected (new monitors show up/change near-instantly). Logs don't show anything unusual, but it worked.

Thanks for the second pair of eyes/sanity check.

[meichthys]

Thanks for following up 👍

[LTTS1991]

This shh keeps breaking without even showing its broken. It just shows unavailable. I'm setting up this app for the 3rd time now. it's REALLY starting to annoy me

[meichthys]

@LTTS1991 Feel free to not use the integration. Historically issues that you're seeing have proven to be not related to the integration, but rather related to the user's network environment.

[LTTS1991]

If your integration can't even tell the user somethings wrong properly maybe we all should feel free. I have no clue as to how long the integration hasn't worked other than looking at the entity giving me the finger and saying: "unknown". That's your integration not telling me it can't do it's job.

[meichthys]

Well it works for me and i only created this integration for myself, so if no-one else wants to use it, that's their prerogative. Pull requests are always welcome, and if someone wanted to pay me to fix bugs they are seeing, then I'd be glad to invest the time. It's hard to fix bugs that I can't reproduce 🤷‍♂️

Some links that may help: https://www.youtube.com/watch?v=9xBGO2Fpnkc Ditch my integration and use MQTT instead: https://community.home-assistant.io/t/uptime-kuma-to-home-assistant/339894/15