zwave-js-ui VS graylog-docker

The software I want to compile is open source. On the GitHub page below the author provides a copy of the source code as well as the compiled exe file. https://github.com/zwave-js/zwave-js-ui/releases

It's a bit convoluted. That's the ZWave-JS-UI for HA addon release notes. The note indicates an update to ZWaveJS-UI to v8.8.6. Those release notes say ZWaveJS-Server updates to v1.26. Finally, the ZWaveJS-Server release notes indicate the actual ZWaveJS package is updated to 10.10.0.

If that doesn't work then I would try connecting it to another piece of software like the Z-WaveJSUI software. It's the same thing as the addon that you would find in home assistant but it is standalone self contained windows program that's about 50mb in size. Download the latest version from here then extract the files and run the exe file. Now just type in 127.0.0.1:8091 in your browser to pull up the management webpage. Then you can go to settings and try to connect your USB. I believe you can update the firmware in this software as well but I'm not 100% certain.

Once you have all the hardware you’ll want to setup home assistant. Configure your zwave devices. I used zwavejs2mqtt (but without mqtt) I know very confusing… https://github.com/zwave-js/zwavejs2mqtt

However, looking at the githubs for these packages: * sonarr: https://github.com/Sonarr/Sonarr/ * pihole: https://github.com/pi-hole/pi-hole * zwavejs2mqtt: https://github.com/zwave-js/zwavejs2mqtt

I recently deployed a small fleet of Dell thin clients around my house to run zwavejs2mqtt[1] via docker. I decided to use Alpine because the machines have 2GB of ram and 8GB of eMMC storage and I figured Alpine would minimize resource usage. They're working great so far!

[1]: https://github.com/zwave-js/zwavejs2mqtt

/u/Warm_Command7954 is right. You need to map /usr/src/app/store to a folder outside of the container or you will lose your configs on every update. This might help.

This is an upcoming feature that is in development. https://github.com/zwave-js/zwavejs2mqtt/pull/2205

version: '3' services: # MongoDB: https://hub.docker.com/_/mongo/ mongo: image: mongo:5.0.13 networks: - graylog # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/docker.html elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 environment: - http.host=0.0.0.0 - transport.host=localhost - network.host=0.0.0.0 - "ES_JAVA_OPTS=-Dlog4j2.formatMsgNoLookups=true -Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 deploy: resources: limits: memory: 1g networks: - graylog # Graylog: https://hub.docker.com/r/graylog/graylog/ graylog: image: graylog/graylog:5.0 environment: # CHANGE ME (must be at least 16 characters)! - GRAYLOG_PASSWORD_SECRET=somepasswordpepper # Password: admin - GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918 - GRAYLOG_HTTP_EXTERNAL_URI=http://127.0.0.1:9000/ entrypoint: /usr/bin/tini -- wait-for-it elasticsearch:9200 -- /docker-entrypoint.sh networks: - graylog restart: always depends_on: - mongo - elasticsearch ports: # Graylog web interface and REST API - 9000:9000 # Syslog TCP - 514:514 # Syslog UDP - 514:514/udp # GELF TCP - 12201:12201 # GELF UDP - 12201:12201/udp networks: graylog: driver: bridge

So I surveyed docker images in my personal use:

Postgres (Docker provided - https://hub.docker.com/_/postgres): Debian (with alternates for alpine or other debian versions)

Jellyfin (Developer provided - https://github.com/jellyfin/jellyfin/blob/master/Dockerfile): They use an alpine build step but the final distributed image is debian

Calibre-Web (Linuxserver provided - https://github.com/linuxserver/docker-calibre-web/blob/maste...): Ubuntu

Graylog (Developer provided - https://github.com/Graylog2/graylog-docker/blob/4.2/docker/o...): Debian

Vaultwarden (Developer provided - https://github.com/dani-garcia/vaultwarden/blob/main/docker/...): Debian (with alpine alternate available)

For professional use, our company mandates all images used are built off a common base image, which is Ubuntu based (my previous employer was similar, but used a Red Hat based image).

The ROOT_PASSWORD_SHA2 environment variable is only for the web interface. The underlying container is built on an openjdk Debian Bullseye image, as you can see here: https://github.com/Graylog2/graylog-docker/blob/4.2/docker/enterprise/Dockerfile