Closed KipK closed 1 week ago
To properly comply with Home Assistant concepts, the addon version will always match the version of the app inside. Additionally Home Assistant does not allow switching between Addon versions.
I get it. I've wanted to test back alpha 18, checking if min max thermostat properties were working ok. I feel it was, but not sure.
I've tried running a docker instance of it on one of my servers, but it always exit :
[ 2024-11-15T14:34:43.953Z ] [ INFO ] [ Storage ]: Storage location: /data
home-assistant-matter-hub start
start the application
Options:
--help Show help [boolean]
--log-level
[string] [choices: "silly", "debug", "info", "warn", "error"] [default: "info"
]
--disable-log-colors [boolean] [default: false]
--storage-location Path to a directory where the application shoul
d store its data. Defaults to $HOME/.home-assis
tant-matter-hub [string]
--web-port Port used by the web application
[number] [default: 8482]
--mdns-network-interface Limit MDNS to this network interface [string]
--home-assistant-url The HTTP-URL of your Home Assistant URL
[string] [required]
--home-assistant-access-token A long-lived access token for your Home Assista
nt Instance [string] [required]
1
Docker is started with all the environment variables needed, I haven't found what I've missed here
Can you provide the command you use to execute it?
The 1
at the end indicates that something went wrong when initializing matter.
Did you use "host" network?
yes here is it :
docker run \
--hostname=dd15b05e3f88 \
--env=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
--env=NODE_VERSION=20.18.0 \
--env=YARN_VERSION=1.22.22 \
--env=HAMH_LOG_LEVEL=info \
--env=HAMH_DISABLE_LOG_COLORS=false \
--env=HAMH_STORAGE_LOCATION=/data \
--env=HAMH_WEB_PORT=8482 \
--env=HAMH_HOME_ASSISTANT_URL=http://192.168.1.205:8482 \
--env=HAMH_HOME_ASSISTANT_ACCESS_TOKEN=xxxx \
--volume=/data \
--network=host \
--restart=no \
--runtime=runc \
-d \
ghcr.io/t0bst4r/home-assistant-matter-hub:3.0.0-alpha.18
docker run \
--hostname=dd15b05e3f88 \
# all of these should not be neccessary:
--env=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
--env=NODE_VERSION=20.18.0 \
--env=YARN_VERSION=1.22.22 \
--runtime=runc \
# this looks good:
--env=HAMH_LOG_LEVEL=info \
--env=HAMH_DISABLE_LOG_COLORS=false \
--env=HAMH_STORAGE_LOCATION=/data \
--env=HAMH_WEB_PORT=8482 \
--env=HAMH_HOME_ASSISTANT_URL=http://192.168.1.205:8482 \
--env=HAMH_HOME_ASSISTANT_ACCESS_TOKEN=xxxx \
--volume=/data \
--network=host \
--restart=no \
-d \
ghcr.io/t0bst4r/home-assistant-matter-hub:3.0.0-alpha.18
is any of the ports blocked needed for matter? 5353, 554x ?
--env=HAMH_WEB_PORT=8482 \ --env=HAMH_HOME_ASSISTANT_URL=http://192.168.1.205:8482
i think you got the Home assistant port wrong 😀
damn, I've put the bridge port instead.... It's ok it starts, thanks :)
Could be nice for easy debugging that we could select the release version from addon configuration page.
This way we can easily rollback if needed for testing purpose, or when something is broken.