Does this actually install homebridge-ui?

[rosshettel]

Current Situation

New user here, a little confused by the documentation and what I'm seeing.

Following these instructions but they seem to be out of date, the HOMEBRIDGE_CONFIG_UI_PORT is apparently no longer being used.

That issue says you can configure the UI port via config.json directly. Ok, so my config.json looks like this:

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },

    "description": "This is an example configuration file. You can use this as a template for creating your own configuration file containing devices you actually own.",

    "accessories": [
    ],

    "platforms": [
    ]
}

Looking at an example of the homebridge-ui config it seems platforms should not be empty?

Regardless I'm not able to access the UI at all on any port, and indeed querying for services listening to the default port reports no results via lsof -i :8581

Docker Config

homebridge:
        image: oznu/homebridge
        container_name: homebridge
        restart: unless-stopped
        network_mode: host
        environment:
            - TZ=${TZ}
        volumes:
            - /srv/homebridge:/homebridge

Logs

No response

Host Operating System

Ubuntu / Debian (or a variant)

Host Architecture

x86_64 / amd64

[rosshettel]

Adding a basic homebridge-ui config results in this error when I start the container:

homebridge        | [11/15/2022, 8:47:13 PM] ---
homebridge        | [11/15/2022, 8:47:13 PM] Loading 1 platforms...
homebridge        | /usr/local/lib/node_modules/homebridge/lib/api.js:122
homebridge        |       throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
homebridge        |       ^
homebridge        | 
homebridge        | Error: The requested platform 'config' was not registered by any plugin.
homebridge        |     at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
homebridge        |     at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:316:45)
homebridge        |     at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:36)
homebridge        |     at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
homebridge        |     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
homebridge        |     at Module._compile (internal/modules/cjs/loader.js:689:30)
homebridge        |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
homebridge        |     at Module.load (internal/modules/cjs/loader.js:599:32)
homebridge        |     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)

[rosshettel]

I was running the latest tag, but after deleting the container and volume and trying the tag 2022-11-10, its now creating a proper config.json and starting up the UI on port 8581 - seems like the latest release has broken something

[Goldsucher]

Yes, same problem here. Tried a fresh install of latest docker and can't reach homebridge ui

[bdsoha]

@rosshettel The port configuration was removed from the docs. Is this still relevant or can it be closed?

[rosshettel]

@bdsoha please read the rest of my comments - the issue is not the port configuration, it's that the latest version of this image does not properly install or configure homebridge-ui. Another user confirmed this behavior, so this issue is still relevant and should not be closed

[whitte-h]

I get the same result, except that for me doesn't even work with 2022-11-10 I'm on an m1 mac running Ventura

[whitte-h]

@rosshettel It looks that's there was an error building the image, if you pull the repo and build and start it locally, it works

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.