DISREGARD - Entities fail to load - Unavailable

[sdholden28]

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)

[sdholden28]

Uptime Kuma logs report no issues.

Uptime Kuma
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.1
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / generic-x86-64)
Home Assistant Core: 2023.3.1
Home Assistant Supervisor: 2023.03.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
[16:14:40] INFO: Starting Uptime Kuma...
Welcome to Uptime Kuma
s6-rc: info: service legacy-services successfully started
Your Node.js version: 18
2023-03-08T16:14:40-06:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-03-08T16:14:40-06:00 [SERVER] INFO: Node Env: production
2023-03-08T16:14:40-06:00 [SERVER] INFO: Importing Node libraries
2023-03-08T16:14:40-06:00 [SERVER] INFO: Importing 3rd-party libraries
2023-03-08T16:14:41-06:00 [SERVER] INFO: Creating express and socket.io instance
2023-03-08T16:14:41-06:00 [SERVER] INFO: Server Type: HTTP
2023-03-08T16:14:41-06:00 [SERVER] INFO: Importing this project modules
2023-03-08T16:14:41-06:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-03-08T16:14:41-06:00 [SERVER] INFO: Version: 1.20.1
2023-03-08T16:14:41-06:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-03-08T16:14:41-06:00 [DB] INFO: Data Dir: /data/
2023-03-08T16:14:41-06:00 [SERVER] INFO: Connecting to the Database
2023-03-08T16:14:41-06:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-03-08T16:14:41-06:00 [DB] INFO: SQLite Version: 3.39.4
2023-03-08T16:14:41-06:00 [SERVER] INFO: Connected
2023-03-08T16:14:41-06:00 [DB] INFO: Your database version: 10
2023-03-08T16:14:41-06:00 [DB] INFO: Latest database version: 10
2023-03-08T16:14:41-06:00 [DB] INFO: Database patch not needed
2023-03-08T16:14:41-06:00 [DB] INFO: Database Patch 2.0 Process
2023-03-08T16:14:41-06:00 [SERVER] INFO: Load JWT secret from database.
2023-03-08T16:14:41-06:00 [PLUGIN] WARN: Skip scanning plugin directory
2023-03-08T16:14:41-06:00 [SERVER] INFO: Adding route
2023-03-08T16:14:41-06:00 [SERVER] INFO: Adding socket handler
2023-03-08T16:14:41-06:00 [SERVER] INFO: Init the server
2023-03-08T16:14:41-06:00 [SERVER] INFO: Listening on 3001

[sinclairpaul]

Please check previously logged issues before creating a new one, your issue is with the custom integration you have installed rather than the addon.

• Error Setup failed for custom integration uptime_kuma #57
• PIP problem  #56
• Fail to load with HomeAssistant 2023.3 #53
• Can’t start Uptime Kuma integration since 2023.3 #52
• Not working with 2023.3 core  #51
• DISREGARD: (Another Custom Integration) Fails to Start on Home Assistant 2023.3.0 #49

[sdholden28]

My apologies