search

hassio-addons / addon-emqx

EMQX - Home Assistant Community Add-ons
MIT License
63 stars 13 forks source link

Error rendering multiple views: "hotconf not found" #62

Closed jymbob closed 11 months ago

jymbob commented 1 year ago

Problem

I can't see several views inside EMQX, and am instead left on a loading screen. Inspecting the connection reports a failure to load "hotconf"

Expected behavior

I expect to be able to see e.g. management MQTT settings

Actual behavior

I see a loading page which never populates. There is a 404 in developer tools

Steps to reproduce

Proposed changes

I've no idea what this file does, but it looks to me like the path hasn't been properly set, potentially due to an errant / at the start.

In Chrome devTools Network tab, for example, I can see a successful (200) fetch request for
https://<my-homeassistant-ip>/api/hassio_ingress/<plugin-id>/api/v5/stats
...followed by an unsuccessful (404) one to https://<my-homeassistant-ip>/api/v5/schemas/hotconf

note the lack of the hassio_ingress part of the path

I've had a quick look through the files in this repo, but couldn't see anything obvious, although I'm not familiar with how hassio plugins work. It may be that this needs something changing upstream?

DN0000 commented 1 year ago

Having a similar issue: image

-----------------------------------------------------------
 Add-on: EMQX
 The most scalable open-source MQTT broker for IoT. An alternative for the Mosquitto add-on
-----------------------------------------------------------
 Add-on version: 0.2.10
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.9.1
 Home Assistant Supervisor: 2023.08.3
-----------------------------------------------------------

Logs otherwise clean

kloodhu commented 1 year ago

same here. is there any solution? thx!

edit: or is there an option to reach the ui NOT ingress?

github-actions[bot] commented 11 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

seebaer1976 commented 10 months ago

Unfortunately the problem still exists in version 0.2.13