operating-system VS node-zwave-js

https://github.com/home-assistant/operating-system/pull/3248

BTW found exact same issue with homeassistant browsing the internet; Add support for Intel GMAC Ethernet controller (#2589) (#2593) · home-assistant/operating-system@9ca836f (github.com)

HAOS (https://github.com/home-assistant/operating-system) is not "vanilla" linux, and I have somewhat little experience of linux, although using raspberry-based systems (Domoticz, Pihole, etc) and basic usage of unix mainframes since early 90s. But the question I could not find answer for by googling is, could I use HAOS to farm chia as well, or is it too much optimized towards HA usage to reasonably serve as a chia farming computer too?

The main issue with the 3A+ is the 512MB of RAM. Combined with only having one USB port and no Ethernet, I would not advise using a pi3A+ as a sustainable foundation for HA.

Home assistant was the last thing I had running as a VM, but recently switched over to running it in a LXC container with their ContainerOS (i think that's what they call it). I would say don't do it (at least not yet), and go with their full OS in a VM (dl link to correct KVM/qcow2 version). I say don't start with HomeAssistantContainer b/c you lose Supervisor and the add-on store, and it's a bit less straighforward to get installed.

One thing to notice, I have been able to successfully boot Home Assistant OS Generic x86-64 https://github.com/home-assistant/operating-system which is using kernel 5.15+ and I don't know why I am able to boot HAOS (maybe they are using uncompressed kernel?), but not other general or special Linux distributions.

Raspberry Pi 4 64-bit

hass.io builds the whole gamut of images. There's a list at the bottom of the github page https://github.com/home-assistant/operating-system/releases/tag/8.0.rc2

There's also the Z-Wave JS command-line flash utility (same code used by ZUI). Still requires node.js, but easier than installing ZUI, if the latter is not in your plans. https://github.com/zwave-js/node-zwave-js/tree/master/packages/flash

First, it's not in the ZWaveJS database yet, so I can't reconfigure anything for it (via Home Assistant). The dimmer/on/off all work, but I'm unable to change the device settings (like dim time, scene triggers, etc). I've opened a request about it, but have no idea what that time frame looks like. I've pinged the company about this and they're going to look into it.

I found the solution, the problem was with z-wave-js and the device, here is the resolved issue in GitHub for future reference https://github.com/zwave-js/node-zwave-js/issues/5599

Responding to a merch message related to Z-Wave problems. If they are using a 700 series stick then that is your network problem. You'll need to update the firmware to fix it https://github.com/zwave-js/node-zwave-js/issues/3906

Be careful using RGBGenie z-wave stuff. I have one of their touch panels, and it doesn't work in Home Assistant with zwave-js. Likely never will unless RGB Genie releases a firmware update for it. It works fine in Hubitat though, where a custom driver was written.

The Z-Wave JS author is on Reddit sometimes, so maybe he'll see this, but you'd get a better answer on GitHub. https://github.com/zwave-js/node-zwave-js/discussions

I checked the zwavejs device database, and it looks like the device doesn't have anything configured.

I just checked this thread - not sure if Aeotec has a different firmware then the 700 series zooz, but looks like the new firmware is markedly better but still has some issues as of 10 days ago: https://github.com/zwave-js/node-zwave-js/issues/3906

I second this - I've been doing it for the last 4 years in a library with over 10k active users. Node.js might not be as fast as C for some tasks, but when the hardware you're talking to is the limiting factor, it just doesn't matter that the driver could be 4x as fast.