Uptime-kuma to home-assistant

Third party integrations
144

Have there been any updates on this bug? I still fail to connect to my UpTime Kuma instance.

145

You need to add “http://” or “https://” to the URL. It’s not intuitive because “host” implies hostname, which does not have “http://”.

146

Looks like you can disable auth and It will work, Unexpected error, first installation ¡ Issue #55 ¡ meichthys/uptime_kuma ¡ GitHub

147

how to set up database monitoring MariaDB?
mysql://username:password@host:port/database

mysql://user:******@10.0.1.111:3307/homeassistant

does not work

148

Thanks for the tip! Had me stumped for a bit, then I realized can’t use it with 2FA, so I then found you can use api keys and then use your username and the api key to add it to HA.

149

Would you care to share your yaml for that?

Cheers, Richard

150

I use the Uptime Kuma HACS integration to get the Uptime Kuma sensors into HA - they appear as regular sensors with an up, paused or down status that you can react to.

To monitor the Z2M network for devices, you add an MQTT monitor to Uptime Kuma. You put in your MQTT hostname, port, username and password and then for the topic I use zigbee2mqtt/DEVICENAME/availability (where DEVICENAME is the Z2M device name), and put “online” in the MQTT Success Message.

Uptime Kuma will then report the monitor as down if the Z2M device changes to anything other than online.

From there, you can do what you want in HA using the sensor, which will be called sensor.uptimekuma_MONITORNAME.

1 Like
151

Thanks. In my case, I also needed in Z2M to turn on Settings > Availability.

153

Should we be able to see this ability in the HA addon? (JSON MQTT payload check)

1 Like
154

I had the custom Uptime Kuma integration from HACS running and from one day to another it stopped. I reinstalled it and when I enter my uptime Kuma credentials (ip, port, user etc.) it says „Failed to connect“ I set correctly to ignore SSL and added http:// in front of the IP (as before). Uptime Kuma is running and I can access it via the IP

Any Idea what is wrong or on which door I should knock?

155

2024.5 broke uptime kuma, frigate and adguard integrations using ssl. It also broke tuya local. 2024.5.1 didnt fixed the issue.

156

it already broke before I updated to 2024.5