Problem/Motivation

In the web interface/Uptime Kuma it shows the push monitor up. However, in Home assistant it says disconnected, sometimes it updates, and sometimes it doesn't. There appears to be some sort of disconnect between Home Assistant and Uptime Kuma, but just for the push monitor, I have other HTTP monitors and they work fine in HA and Uptime Kuma.

Expected behavior

Home Assistant entity to update and show the correct information from Push Monitor from Uptime Kuma.

Actual behavior

Home Assistant entity does not update and seems disconnected from Push Monitor from Uptime Kuma. However, as I said my other HTTP monitors within Uptime Kuma update correctly and work as expected. The only problem is with the Push Monitor.

Steps to reproduce

Set up a push monitor and see if it works in Home Assistant.

Proposed changes

I don't have a fix, there appears to be some sort of disconnect between Uptime Kuma's push monitor and the home assistant entity, I don't know how this addon works, so not much help from me.

Problem/Motivation

Noticed cloudflared is not included in the addon. This is probably one of the easiest ways a user can setup a reverseproxy, especially within homeassistant. While its not required, it would lower the barrier to entry.

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

• Install a fresh copy of the addon
• setup your admin account
• navigate to reverse proxy setting

Proposed changes

Add a working instance of cloudflared

Problem/Motivation

When setting up HTTP(s) - Keyword monitor, some websites (internal and safe devices) return error in Uptime Kuma - Parse Error: Invalid header value char.

Expected behavior

Website would be parsed like before.

Actual behavior

Websites are not parsed.

Steps to reproduce

For reference on this issue you can look at original issue on Uptime Kuma github site:
louislam/uptime-kuma#23

Proposed changes

Add ability to configure:

NODE_OPTIONS=--insecure-http-parser

As a optional configuration element.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Problem/Motivation

Not able to monitor docker host

Expected behavior

Successfully add the docker host

Actual behavior

Error: Connect ENOENT /var/run/docker.sock

Steps to reproduce

In uptime-kuma go to settings--> docker hosts and try to setup a new host

Proposed changes

according to this we need to bind the /var/run/docker.sock as read only

Problem/Motivation

Uptime Kuma fails to setup when updating to HA Core 2023.3.0 on HAOS. Reverted to 2023.2.5 and everything works fine.

Expected behavior

Uptime Kuma should start without error.

Actual behavior

Uptime Kuma reports a setup failure within Home Assistant with the following relevant log information:

Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].

It should be noted that the web dashboard appeared to still load when visiting the web address.

Steps to reproduce

Upgrade HA Core from 2023.2.5 to 2023.3.0

Problem/Motivation

Home Assistant raises a notification that Upotimekuma could not be setup correctly

Expected behavior

I expect no Home Assistant error notification

Actual behavior

Logger: homeassistant.setup
Source: setup.py:205
First occurred: 07:46:38 (1 occurrences)
Last logged: 07:46:38

Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].
)

Steps to reproduce

This notification error occurs each time Uptimekuma addon is restarted

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Hello -

I added the addon, but it won't start. When I hit start, nothing happens?

Here is the log. Any help would be greatly appreciated.

2022-11-02T18:54:00.116Z [DB] INFO: Your database version: 0
2022-11-02T18:54:00.116Z [DB] INFO: Latest database version: 10
2022-11-02T18:54:00.116Z [DB] INFO: Database patch is needed
2022-11-02T18:54:00.117Z [DB] INFO: Backing up the database
2022-11-02T18:54:00.118Z [DB] INFO: Patching ./db/patch1.sql
2022-11-02T18:54:00.135Z [DB] INFO: Patched ./db/patch1.sql
2022-11-02T18:54:00.150Z [DB] INFO: Patching ./db/patch2.sql
2022-11-02T18:54:00.155Z [DB] INFO: Patched ./db/patch2.sql
2022-11-02T18:54:00.164Z [DB] INFO: Patching ./db/patch3.sql
2022-11-02T18:54:00.175Z [DB] INFO: Patched ./db/patch3.sql
2022-11-02T18:54:00.181Z [DB] INFO: Patching ./db/patch4.sql
2022-11-02T18:54:00.192Z [DB] INFO: Patched ./db/patch4.sql
2022-11-02T18:54:00.197Z [DB] INFO: Patching ./db/patch5.sql
2022-11-02T18:54:00.208Z [DB] INFO: Patched ./db/patch5.sql
2022-11-02T18:54:00.214Z [DB] INFO: Patching ./db/patch6.sql
2022-11-02T18:54:00.224Z [DB] INFO: Patched ./db/patch6.sql
2022-11-02T18:54:00.229Z [DB] INFO: Patching ./db/patch7.sql
2022-11-02T18:54:00.235Z [DB] INFO: Patched ./db/patch7.sql
2022-11-02T18:54:00.240Z [DB] INFO: Patching ./db/patch8.sql
2022-11-02T18:54:00.245Z [DB] INFO: Patched ./db/patch8.sql
2022-11-02T18:54:00.250Z [DB] INFO: Patching ./db/patch9.sql
2022-11-02T18:54:00.254Z [DB] INFO: Patched ./db/patch9.sql
2022-11-02T18:54:00.260Z [DB] INFO: Patching ./db/patch10.sql
2022-11-02T18:54:00.278Z [DB] INFO: Patched ./db/patch10.sql
2022-11-02T18:54:00.283Z [DB] INFO: Database Patch 2.0 Process
2022-11-02T18:54:00.285Z [DB] INFO: patch-setting-value-type.sql is not patched
2022-11-02T18:54:00.288Z [DB] INFO: patch-setting-value-type.sql is patching
2022-11-02T18:54:00.297Z [DB] INFO: patch-setting-value-type.sql was patched successfully
2022-11-02T18:54:00.297Z [DB] INFO: patch-improve-performance.sql is not patched
2022-11-02T18:54:00.298Z [DB] INFO: patch-improve-performance.sql is patching
2022-11-02T18:54:00.303Z [DB] INFO: patch-improve-performance.sql was patched successfully
2022-11-02T18:54:00.304Z [DB] INFO: patch-2fa.sql is not patched
2022-11-02T18:54:00.304Z [DB] INFO: patch-2fa.sql is patching
2022-11-02T18:54:00.310Z [DB] INFO: patch-2fa.sql was patched successfully
2022-11-02T18:54:00.310Z [DB] INFO: patch-add-retry-interval-monitor.sql is not patched
2022-11-02T18:54:00.310Z [DB] INFO: patch-add-retry-interval-monitor.sql is patching
2022-11-02T18:54:00.315Z [DB] INFO: patch-add-retry-interval-monitor.sql was patched successfully
2022-11-02T18:54:00.316Z [DB] INFO: patch-incident-table.sql is not patched
2022-11-02T18:54:00.316Z [DB] INFO: patch-incident-table.sql is patching
2022-11-02T18:54:00.320Z [DB] INFO: patch-incident-table.sql was patched successfully
2022-11-02T18:54:00.321Z [DB] INFO: patch-group-table.sql is not patched
2022-11-02T18:54:00.321Z [DB] INFO: patch-group-table.sql is patching
2022-11-02T18:54:00.327Z [DB] INFO: patch-group-table.sql was patched successfully
2022-11-02T18:54:00.327Z [DB] INFO: patch-monitor-push_token.sql is not patched
2022-11-02T18:54:00.327Z [DB] INFO: patch-monitor-push_token.sql is patching
2022-11-02T18:54:00.332Z [DB] INFO: patch-monitor-push_token.sql was patched successfully
2022-11-02T18:54:00.333Z [DB] INFO: patch-http-monitor-method-body-and-headers.sql is not patched
2022-11-02T18:54:00.333Z [DB] INFO: patch-http-monitor-method-body-and-headers.sql is patching
2022-11-02T18:54:00.340Z [DB] INFO: patch-http-monitor-method-body-and-headers.sql was patched successfully
2022-11-02T18:54:00.340Z [DB] INFO: patch-2fa-invalidate-used-token.sql is not patched
2022-11-02T18:54:00.342Z [DB] INFO: patch-2fa-invalidate-used-token.sql is patching
2022-11-02T18:54:00.347Z [DB] INFO: patch-2fa-invalidate-used-token.sql was patched successfully
2022-11-02T18:54:00.347Z [DB] INFO: patch-notification_sent_history.sql is not patched
2022-11-02T18:54:00.347Z [DB] INFO: patch-notification_sent_history.sql is patching
2022-11-02T18:54:00.353Z [DB] INFO: patch-notification_sent_history.sql was patched successfully
2022-11-02T18:54:00.353Z [DB] INFO: patch-monitor-basic-auth.sql is not patched
2022-11-02T18:54:00.353Z [DB] INFO: patch-monitor-basic-auth.sql is patching
2022-11-02T18:54:00.360Z [DB] INFO: patch-monitor-basic-auth.sql was patched successfully
2022-11-02T18:54:00.360Z [DB] INFO: patch-add-docker-columns.sql is not patched
2022-11-02T18:54:00.360Z [DB] INFO: patch-add-docker-columns.sql is patching
2022-11-02T18:54:00.367Z [DB] INFO: patch-add-docker-columns.sql was patched successfully
2022-11-02T18:54:00.367Z [DB] INFO: patch-status-page.sql is not patched
2022-11-02T18:54:00.368Z [DB] INFO: patch-status-page.sql is patching
2022-11-02T18:54:00.377Z [DB] INFO: patch-status-page.sql was patched successfully
2022-11-02T18:54:00.377Z [DB] INFO: patch-proxy.sql is not patched
2022-11-02T18:54:00.377Z [DB] INFO: patch-proxy.sql is patching
2022-11-02T18:54:00.385Z [DB] INFO: patch-proxy.sql was patched successfully
2022-11-02T18:54:00.385Z [DB] INFO: patch-monitor-expiry-notification.sql is not patched
2022-11-02T18:54:00.385Z [DB] INFO: patch-monitor-expiry-notification.sql is patching
2022-11-02T18:54:00.391Z [DB] INFO: patch-monitor-expiry-notification.sql was patched successfully
2022-11-02T18:54:00.391Z [DB] INFO: patch-status-page-footer-css.sql is not patched
2022-11-02T18:54:00.391Z [DB] INFO: patch-status-page-footer-css.sql is patching
2022-11-02T18:54:00.519Z [DB] INFO: patch-status-page-footer-css.sql was patched successfully
2022-11-02T18:54:00.519Z [DB] INFO: patch-added-mqtt-monitor.sql is not patched
2022-11-02T18:54:00.520Z [DB] INFO: patch-added-mqtt-monitor.sql is patching
2022-11-02T18:54:00.532Z [DB] INFO: patch-added-mqtt-monitor.sql was patched successfully
2022-11-02T18:54:00.532Z [DB] INFO: patch-add-clickable-status-page-link.sql is not patched
2022-11-02T18:54:00.533Z [DB] INFO: patch-add-clickable-status-page-link.sql is patching
2022-11-02T18:54:00.542Z [DB] INFO: patch-add-clickable-status-page-link.sql was patched successfully
2022-11-02T18:54:00.544Z [DB] INFO: patch-add-sqlserver-monitor.sql is not patched
2022-11-02T18:54:00.544Z [DB] INFO: patch-add-sqlserver-monitor.sql is patching
2022-11-02T18:54:00.556Z [DB] INFO: patch-add-sqlserver-monitor.sql was patched successfully
2022-11-02T18:54:00.556Z [DB] INFO: patch-add-other-auth.sql is not patched
2022-11-02T18:54:00.556Z [DB] INFO: patch-add-other-auth.sql need parents
2022-11-02T18:54:00.557Z [DB] INFO: patch-add-other-auth.sql is patching
2022-11-02T18:54:00.574Z [DB] INFO: patch-add-other-auth.sql was patched successfully
2022-11-02T18:54:00.574Z [DB] INFO: patch-add-radius-monitor.sql is not patched
2022-11-02T18:54:00.574Z [DB] INFO: patch-add-radius-monitor.sql is patching
2022-11-02T18:54:00.591Z [DB] INFO: patch-add-radius-monitor.sql was patched successfully
2022-11-02T18:54:00.592Z [DB] INFO: patch-monitor-add-resend-interval.sql is not patched
2022-11-02T18:54:00.592Z [DB] INFO: patch-monitor-add-resend-interval.sql is patching
2022-11-02T18:54:00.604Z [DB] INFO: patch-monitor-add-resend-interval.sql was patched successfully
2022-11-02T18:54:00.604Z [DB] INFO: Database Patched Successfully
2022-11-02T18:54:00.619Z [SERVER] INFO: JWT secret is not found, generate one.
2022-11-02T18:54:00.868Z [SERVER] INFO: Stored JWT secret into database
2022-11-02T18:54:00.870Z [SERVER] INFO: No user, need setup
2022-11-02T18:54:00.872Z [SERVER] INFO: Adding route
2022-11-02T18:54:00.958Z [SERVER] INFO: Adding socket handler
2022-11-02T18:54:00.958Z [SERVER] INFO: Init the server
2022-11-02T18:54:00.991Z [SERVER] INFO: Listening on 3001

Problem/Motivation

Currently there is no way to set log-level to any othe (default: INFO)

Expected behavior

Possible to set log-level

Actual behavior

INFO log level is massive if a lot of sensors set

Steps to reproduce

Start addon and add >20 monitos

Proposed changes

Add log_level option to lower the amount of not necessay information

Problem/Motivation

didnt update to 0.9.1

Expected behavior

to update without issues

Actual behavior

Can't install ghcr.io/hassio-addons/uptime-kuma/aarch64:0.9.1: 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/hassio-addons/uptime-kuma/aarch64:0.9.1/json: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument")

Steps to reproduce

just press update

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Works great with 2023.2.5

Log:

2023-02-23T00:00:05+02:00 [RATE-LIMIT] INFO: remaining requests: 20
2023-02-23T00:00:51+02:00 [MONITOR] WARN: Monitor #1 'HomeAssistant': Failing: connect ECONNREFUSED 192.168.1.171:8123 | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Worker for job "clear-old-data" online undefined
2023-02-23T03:14:02+02:00 [DB] INFO: Data Dir: /data/
2023-02-23T03:14:02+02:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-02-23T03:14:02+02:00 [DB] INFO: SQLite Version: 3.39.4
{
name: 'clear-old-data',
message: 'Clearing Data older than 180 days...'
}
{ name: 'clear-old-data', message: 'done' }
2023-02-23T07:04:25+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2055ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T09:32:54+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2062ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T09:33:55+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T09:34:58+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2059ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T11:32:25+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2033ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T12:36:51+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2050ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T13:20:58+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.131 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2057ms
pipe 3
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T14:19:42+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
--- 192.168.1.131 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9212ms
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
2023-02-23T14:33:10+02:00 [MONITOR] WARN: Monitor #7 'AC-Livingroom': Failing: PING 192.168.1.131 (192.168.1.131) 56(84) bytes of data.
--- 192.168.1.131 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9201ms
| Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0

Problem/Motivation

The addon stopped working

Expected behavior

Addon continue to work after update

Actual behavior

HA Integration page show "(i) not loaded"

Steps to reproduce

update to core 2023.3

Proposed changes

Problem/Motivation

Uptime Kuma Supports SSL Certificates Natively
https://github.com/louislam/uptime-kuma/wiki/Environment-Variables#server-environment-variables

I would like to utilize Let's Encrypt SSL certificates similar to the Nginx Addon, but to load Uptime Kuma utilizing SSL.

I'd be willing to create a PR, but less familiar with how I can modify the addon to request a path for the certificate and key files.

Problem/Motivation

Looks like the main branch has support for JSON MQTT checks?

Expected behavior

Ability to check payload using JSON-query

Actual behavior

Not available

Proposed changes

Would it be possible to add this? louislam/uptime-kuma#3857

Thank you!

Problem/Motivation

Missing options in hassio/addon/abbbbbbb_uptime-kuma/config

Expected behavior

Setting up the addon

Actual behavior

No options other than Network webgui port.

Steps to reproduce

N/A

Proposed changes

Add them for more customization in settings
Add ssl options for https protocol
Thanks ;)

Proposed changes

Add UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN=TRUE to the environment

Proposed change:

Implement a field on the add-on configuration page to add custom CSS code. Uptime Kuma could really benefit from custom theming, and applying custom CSS persistently to docker hass add-ons through restarts running in Supervisor is not very straightforward.

Anything from the custom CSS field could be tacked on to assets\index-fc5855ea.css and then also gzipped to assets\index-fc5855ea.css.gz at container run time through options and run.sh. -- or any other method which might be less cumbersome like a linked reference in-line.

Problem/Motivation

It would be nice to have a sidebar link that displays the web interface rather than requiring you to go into the addon to get to the web interface.

Expected behavior

A link in the sidebar that opens the web UI

Problem/Motivation

recently updime Kuma don't work very weel

(Why the issue was filed)
i see in the log this " SQLITE_CORRUPT: database disk image is malformed] "

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Resolution of hostnames not possible correctly.
Noticed when trying to create a ping monitor with a (local) hostname and no IP address, it could not be resolved correctly.

Expected behavior

The DNS servers that HomeAssistant also uses should be queried. After that, the correct IP address should also be resolvable.
(Tried by manually entering the same name server directly into resolv.conf. After the entry the resolution was successful).

Actual behavior

The resolc.conf contains:
search local.hass.io
nameserver 127.0.0.11
options ndots:0

Therefore the nameserver (in my case 192.168.178.3) is not queried, which is also stored in the HomeAssistant configuration.

The name resolution can therefore not take place.

Steps to reproduce

New installation in HomeAssistant
Create a PING monitor with hostname, instead of IP address

Proposed changes

One solution would be to use the Docker host's name resolution.

It would also be desirable, for the more expert administrator, if the nameservers to be queried could be entered in the addon configuration in HomeAssistant, which would then be transferred to resolv.conf.

First of all: thanks for the fantastic work!

Problem/Motivation

I forgot my admin password and I'm not able to reset it.

Expected behavior

Following the guide on https://github.com/louislam/uptime-kuma/wiki/Reset-Password-via-CLI should help.

Actual behavior

docker exec -it addon_a0d7b954_uptime-kuma /bin/bash
cd /opt/uptime-kuma
npm run reset-password

gives me

> [email protected] reset-password
> node extra/reset-password.js

== Uptime Kuma Reset Password Tool ==
Connecting the database
2023-01-29T11:16:57+01:00 [DB] INFO: Data Dir: ./data/
Error: select * from `user` limit 1 - SQLITE_ERROR: no such table: user
2023-01-29T11:16:57+01:00 [DB] INFO: Closing the database
2023-01-29T11:16:59+01:00 [DB] INFO: SQLite closed
Finished.

There seems to be a non-standard configuration for the database which is not linked to the reset-password tool.

Steps to reproduce

See section above.

Proposed changes

It would be fine if there is a possibility to reset the admin password. This possibility should be described in https://github.com/hassio-addons/addon-uptime-kuma/blob/main/README.md - If such a possibility is pointed out to me, I would be happy to complete the README.md.

Thanks in advance,
Gregor

Problem/Motivation

After HA 2023.3 core update, uptime kuma loading fails with error message "Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']."

Expected behavior

Integration / Add-on to load

Actual behavior

Does not load with above error

Steps to reproduce

Update HA to core 2023.3 and attempt to load uptime kuma add-on / plugin

Proposed changes

Change or update dependency

Problem/Motivation

By default, Uptime Kume doesn't allow being embedded in an iframe. Because of that, it cannot be added to the Home Assistant sidebar.

Expected behavior

Being able to access it from the sidebar

Actual behavior

Doesn't work

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

A UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN environment variable can be set to allow embedding in an iframe.

Problem/Motivation

Add-on only responds to http

Expected behavior

The ability to add SSL certificate and access via HTTPS

Actual behavior

Give err: Connection is not secure. ERR_SSL_PROTOCOL_ERROR

Steps to reproduce

Load with site using https instead of http

Proposed changes

Allow the add-on to upload certificate(s) and key files to the necessary location. Add the option to turn on and/or require SSL connection.

Problem/Motivation

To embed this addon in the dashboard (without reverse proxy) it would be nice to have the option to set UptimeKuma´s "disable-frame-sameorigin" argument

Expected behavior

Set "disable-frame-sameorigin" to allow embedding in home assistant dashboard

Actual behavior

setting "disable-frame-sameorigin" not possible

Steps to reproduce

-

Proposed changes

Add disable-frame-sameorigin as a config option.
Here is the Config in UptimeKuma "https://github.com/louislam/uptime-kuma/blob/c1efe0f26d7e28f4c656cd05178a0af8424a5a63/server/server.js#L116" (found by checing this issue "louislam/uptime-kuma#1146")

Problem/Motivation

Uptime Kuma not possible to display in iframe

Expected behavior

Web app shown correctly in iframe

Actual behavior

https://url refused to connect

Steps to reproduce

Add uptimekuma as an iframe in Home Assistant, fails to load because 'X-Frame-Options' is set to 'sameorigin':
Google Chrome: Refused to display '<URL>' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

Proposed changes

Fix in original docker image: Set env variable "UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN=true"

Will the Uptime Kuma Integration work with Home Assistant via the Nabu Casa URL i.e. https://[nabuacasaurl]:[uptimekumaport]

I get a server 500 error when I try.

if not how do I configure the Integration to work with another reverse proxy url?

Hello, i got this error, someone any idee what to do, and how.
(Hassio install.)

Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 01:07:56 (3 occurrences)
Last logged: 01:08:01

Unable to install package pyuptimekuma==0.0.6: ERROR: Cannot install pyuptimekuma==0.0.6 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip is available: 23.0 -> 23.0.1 [notice] To update, run: pip install --upgrade pip

Where exactly is this storing its data?

It suggests backing up .data, but it doesnt seem to be exposing it to the host.
"Deprecated: Since a lot of features were added and this backup feature is a bit unmaintained, it cannot generate or restore a complete backup.

Please backup the volume or the data folder (./data/) directly instead."

Problem/Motivation

Service call:

service: hassio.backup_partial
data:
  addons:
    - a0d7b954_uptime-kuma

Result: Failed to call service hassio.backup_partial. invalid slug a0d7b954_uptime-kuma (try a0d7b954_uptime_kuma) @ data['addons'][0]. Got None

With a0d7b954_uptime_kuma slug - HA doesn't create any backup (as with any another formally allowed slug - "qwerty", for example)

Expected behavior

Creating partial backup with Uptime Kuma addon

Or, please, tell me any another way to backup this addon by service call.

Previously I had to turn off authentication for the plugin to work (had been working for several months). Now after upgrading the OS to 11.4 authentication is broken completely which also makes any existing / associated entities disappear.

I am running on a VM so luckily made a snapshot before the upgrade and after rolling back everything is back to working - for now....

Problem/Motivation

To reach kuma we have to click into settings > Addons > kuma > open user ui

Expected behavior

Have a sidebar panel for uptime kuma, optimal would be with sso

Actual behavior

no option to add it to the sidebar

Steps to reproduce

install the addon

Proposed changes

Add the option to add it to the sidebar like for code addon or file addon.

Problem/Motivation

uptime kuma integration will not load and I can not delete it

Expected behavior

That uptime kuma integration loads and works

Actual behavior

Uptime Kuma does not load after 2023.3. No matter if if restart hass or my pi.
I can not delete it either. I can just disable it. When restarting i get the following error:

Home Assistant Core

Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].
09:36:32 – (ERROR) setup.py

I am running HASS os on a pi4

Steps to reproduce

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I want to take a backup, according to the instructions in the addon you just need to backup /data/ directory. Where is directory located/exposed?

Expected behavior

We need a way to backup the info from this addon, otherwise is a bit risky.

Actual behavior

Backup procedure is not documented

Proposed changes

Document how to backup this/ inform that it doesn't have backups available.

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

No MQTT available.

Expected behavior

MQTT included in docker image.

Actual behavior

When trying to set up Apprise notification via MQTT, the following error appears:

ERROR - mqtt:// is disabled on this system.

Steps to reproduce

See above.

Proposed changes

Change Uptime Kuma docker image to one, that includes MQTT.

any way to enable https on custom port HAOS uptime kuma addon?

Problem/Motivation

In Logs i'm getting this error
Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].

Expected behavior

That I will not get any errors.

Actual behavior

Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].

Uptime-Kuma Version
0.6.0

Log:
`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Uptime Kuma
It is a self-hosted monitoring tool like "Uptime Robot"

Add-on version: 0.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / qemux86-64)
Home Assistant Core: 2023.3.1
Home Assistant Supervisor: 2023.01.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service uptime-kuma: starting
s6-rc: info: service uptime-kuma successfully started
s6-rc: info: service legacy-services: starting
[12:20:04] INFO: Starting Uptime Kuma...
s6-rc: info: service legacy-services successfully started
Welcome to Uptime Kuma
Your Node.js version: 18
2023-03-06T12:20:04+02:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-03-06T12:20:04+02:00 [SERVER] INFO: Node Env: production
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing Node libraries
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing 3rd-party libraries
2023-03-06T12:20:06+02:00 [SERVER] INFO: Creating express and socket.io instance
2023-03-06T12:20:06+02:00 [SERVER] INFO: Server Type: HTTP
2023-03-06T12:20:06+02:00 [SERVER] INFO: Importing this project modules
2023-03-06T12:20:06+02:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-03-06T12:20:06+02:00 [SERVER] INFO: Version: 1.20.1
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-03-06T12:20:06+02:00 [DB] INFO: Data Dir: /data/
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connecting to the Database
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite Version: 3.39.4
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connected
2023-03-06T12:20:06+02:00 [DB] INFO: Your database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Latest database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Database patch not needed
2023-03-06T12:20:06+02:00 [DB] INFO: Database Patch 2.0 Process
2023-03-06T12:20:06+02:00 [SERVER] INFO: Load JWT secret from database.
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Skip scanning plugin directory
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding route
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding socket handler
2023-03-06T12:20:06+02:00 [SERVER] INFO: Init the server
2023-03-06T12:20:07+02:00 [SERVER] INFO: Listening on 3001`

Problem/Motivation

using uptime kuma to monitor network. HA is also connected to tailscale via hassio-addon tailscale.
but uptime kuma is not able to check (ping) other tailscale-devices (like mobile phones)

Expected behavior

kuma should bei able to check on all networks

Actual behavior

not using tailscale-network provided by other hassio-addon

Steps to reproduce

using a monitor to ping a tailscale-ip

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

New to Home Assistant. There is no SHOW ON SIDEBAR button.

Can you help with the config to make it work or post update?

Thanks!!

Uptime Kuma 1.20.1 has been released, and this image should be updated.

There's an update available.

https://github.com/louislam/uptime-kuma/releases
1.23.11

The add-on currently provides V1.23.8

It's also noted that in the HASS Add-on's that this repo is unmaintained (stale).

installes this HA addon on the last hass OS update,
added some hosts in uptime kuma, OK

1/ impossible to add integration to display my monitored hosts inside HA ?
this tuto : https://www.youtube.com/watch?v=9xBGO2Fpnkc&t=4s&ab_channel=BeardedTinker
sends to this read only repo to add to HACS : https://github.com/meichthys/uptime_kuma
but the repo si impossible to add in HACS, and sends to an other repo :
https://github.com/jayakornk/pyuptimekuma
but this repo is impossible to add to HACS : jayakornk/pyuptimekuma#1
😭😩

2/ impossible to login
when installed addon i used ipad with his fu * * * g auto-completion i fight all the time,
and in the install process when created user for uptime kuma there is a fu * * * g space character at the end of the user name
uptime kuma created user with the space character,
the ipad recorded credentials, so no problemo to login with this user name on ipad,
but on hte PC, i typed the username without space so uptime kuma displayed the message : wrong user or password
after hours of trial and error, finally copy-pasted infos from ipad and noticed the fu * * * g space character !
and now i can login from PC :)

BUT :
how do i change the user name in uptime kuma to correct my space error ???
there is only logout and change password options in this HA extension ?

help please xD

Problem/Motivation

UptimeKuma sensor entities dissapeared in HA, showing "Error in describing condition: can't access property "entity_id" of undefined"; manual check for entity availability shows no custom UptimeKuma monitors are populated into HA.

Expected behavior

Custom UptimeKuma monitors should be auto-populated after addon-start

Actual behavior

UptimeKuma sensor entities dissapeared in HA, only the below are available, none of the custom monitors are available

• Uptime Kuma Running
• uptimekuma ha local

Steps to reproduce

Let UptimeKuma run for over 90 days with 28 monitor entities, wait for the database to grow over 2GB (2397.6 GB) While settings are configured to keep only 1 day history.

Proposed changes

Vacuum function clearly not working: "Trigger database VACUUM for SQLite. If your database is created after 1.10.0, AUTO_VACUUM is already enabled and this action is not needed."
This is a re-occurring issue once the database grows above 2GB, having a setting to keep history for 1 days does not do anything.

Current workaround (reinstall UptimeKuma addon)

1. Export all settings manually (since the backup feature does not work and you cannot access the data folder for UptimeKuma on HAOS)
2. Completely uninstall UptimeKuma addon
3. Reboot HAOS
4. Reinstall Uptime Kuma Addon (HA integration can stay as it was), reboot HAOS
5. Reconfigure everything from scratch using the same monitor names and settings
6. Configure database to keep only 1 days of history, observe the second day that th setting is not respected
7. Wait for some time to the database to grow above 2GB then rinse and repeat all the steps

System details:

HomeAssistant Addon version: 0.12.0
HAOS OVA (VMware) - The issue is independent from HAOS and HA versions.
Core 2024.2.2
Supervisor 2024.01.1
Operating System 11.5
Frontend 20240207.1
CPU: 2 vCPU (Intel Core i7-8700T @ 2.40GHz)
RAM: 4GB (DDR4)

Problem/Motivation

The addon doesn't open web interface with ingress

(Why the issue was filed)

Expected behavior

The addon opens its own web interface with ingress

(What you expected to happen)

Actual behavior

The addon doesn't open web interface with ingress

(What actually happened)

Steps to reproduce

Click on the "open web ui" button

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Problem is that kuma is really slow and I cannot edit entry's anymore. Also new entry's creating is also not possible.

Hardware:

Raspberry PI 4

Software:

Core
2023.11.2
Supervisor
2023.11.3
Operating System
Frontend
20231030.2

Uptime Kuma
Current version: 0.9.1

Hi,
The current version of kuma HACS integration (v2.0.2) print an error into the home-assistant console.

WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for uptime_kuma using this method at custom_components/uptime_kuma/init.py, line 52: hass.config_entries.async_setup_platforms(entry, PLATFORMS)

It's still working well, but to avoid a futur issue, a change will be necessary.

Azlux

Problem/Motivation

All uptime kuma entities fail to load. State is Unavailable

Expected behavior

Uptime Kuma entities expected to load and reflect proper state of associated uptime kuma entry

Actual behavior

All uptime entities failed to load after updating to Home Assistant 2023.3.1. Updating to 2023.3.2 did not resolve the issue.

Steps to reproduce

On startup, Uptime Kuma entities fail to load. However, uptime kuma is accessible via web UI and entities/data appear normal there. Logs show:

2023-03-08 16:21:37.616 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package pyuptimekuma==0.0.6: ERROR: Cannot install pyuptimekuma==0.0.6 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

When trying to use the Uptime Kume Integration its not possibel to switch the Addon to ssl and use the homeassistant certificates ?

Expected behavior

Like in some other addons it would be nice to use the onboard certs and provide ssl for https

Actual behavior

Uptime Addon is coming up on default port 3001 but with http

Steps to reproduce

Install and start "normal" addon

Maybe this would be a nice feature or it was forgotten at building the Image :-)

Greetings,

from Austria

Kilowatt