zwave-js-ui VS musl-cross-make

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

I've done the same alpine trick for static binaries but may I introduce you to musl-cross-make?

https://github.com/richfelker/musl-cross-make

Just burned out static toolchains that make me static binaries for all architectures gcc supports. Much like musl.cc but they suggest building your own and I do.

I use these toolchains on debian (/ anywhere a non-ancient linux kernel runs) to make static binaries, you can too!

Python obviously isn't 14kb because its code is divided into hundreds of shared object files. So the way I like to measure things is using static executable size, using tools like https://github.com/jart/cosmopolitan or https://github.com/richfelker/musl-cross-make of which you'll find a static build in the cosmo repo. For example, here's the technique I used to build TinyLISP was something like this:

I have a different issue with ring. This is on a custom Cortex A9 board at work. For most depedencies I can get compilation working fine with armv7-unknown-linux-musleabihf. I was able to build the cross compiler using https://github.com/richfelker/musl-cross-make , adding

A bit off topic, I hope someday GCC's build system gets overhauled. A huge advantage of LLVM is that it is quite easier to rebuild the runtime libraries without rebuilding the compiler. With GCC that's a pain, unless one takes the time to re-package GCC very carefully like https://github.com/richfelker/musl-cross-make and https://exherbo.org/.

Maybe getting some new GCC devs in there with projects like this would help with that?