Error Setup failed for custom integration uptime_kuma #1971

Closed
opened 2026-02-28 02:38:49 -05:00 by deekerman · 2 comments
Owner

Originally created by @Ofir-P on GitHub (Mar 6, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

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

👟 Reproduction steps

By turning on my HA OS.

👀 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

💻 Operating System and Arch

Ubuntu 20.4

🌐 Browser

Google Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

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
Originally created by @Ofir-P on GitHub (Mar 6, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description In Logs i'm getting this error Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']. ### 👟 Reproduction steps By turning on my HA OS. ### 👀 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 ### 💻 Operating System and Arch Ubuntu 20.4 ### 🌐 Browser Google Chrome ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell 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 ```
deekerman 2026-02-28 02:38:49 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@rezzorix commented on GitHub (Mar 6, 2023):

This here is the original repository of uptime kuma.

The problem you have is with a modified version of uptime kuma for home assistant (HA plugin).
It might be a misconfiguration or a bug, but near 100% nothing related to the original.

Therefore best is if you head over to the repository for the plugin and ask there for help:
https://github.com/hassio-addons/addon-uptime-kuma

@rezzorix commented on GitHub (Mar 6, 2023): This here is the original repository of uptime kuma. The problem you have is with a modified version of uptime kuma for home assistant (HA plugin). It might be a misconfiguration or a bug, but near 100% nothing related to the original. Therefore best is if you head over to the repository for the plugin and ask there for help: https://github.com/hassio-addons/addon-uptime-kuma
Author
Owner

@Ofir-P commented on GitHub (Mar 6, 2023):

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

Sorry, thanks!

@Ofir-P commented on GitHub (Mar 6, 2023): > ```shell > 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 > ``` Sorry, thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1971
No description provided.