Just as the title says: is this possible?
Iβm in the process of ordering another zigbee coordinator (SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P) and since I already use MQTT and want to redo my zigbee setup, I am tempted of going with Z2M.
I use HA Core (LXC/Proxmox) and my system is at it limits (Ram) so I cannot add a VM to be able to use docker anyway and it would be a waste of resources if it were possible, just for this.
Thanks a lot for any help!
Owkay⦠thanks a lot for that link!
I was searching here on the forum and the documentation since I thought Z2M is more of a HA thing.
Do you have any idea if it would be wise/advisable/bad/β¦ to install it in the same LXC as my HA?
If you prefer LXC containers, hereβs a source that provides one-line installation scripts for the most common applications and services, including an LXC for Zigbee2MQTT.
I recommend keeping each service separate so that you can have individual backups for each. This way, in case of any issues, restoring the service becomes straightforward and simple.
Why not put everything in Docker, HA Core, Z2M and MQTT? I have a βQuickStartβ project for this at Github.
Currently this βstackβ uses 650 MB RAM.
The original poster is utilizing Proxmox, which makes use of Linux containers. Although it is possible to run Docker in an LXC for these services, it would bring extra overhead and would not permit separate backups for each individual service.
Understood. So why not drop Proxmox/LXC completely in favour of docker compose and (if management UI is required) Portainer?
Why not continue using Proxmox with virtualization rather than switching to Docker?
Ease of use. But itβs just a proposal, both alternatives are valid.
In my view, utilizing services with Proxmox is as easy as it gets.
You are actually installing the Home Assistant Container, not Home Assistant Core.
You are correct.
tteck, should it be possible, normally, to install/run Z2M in the same container as my HA?
Like I already wrote: my system runs at itβs max (8 LXCβs and 1 VM) and you are right that the preferred way is to keep them separate.
In this case, HA & Z2M is used together/βlinkedβ to each other so the advantage is minimal of separating them, no?
Yes, it is possible, but creating a Zigbee2MQTT LXC would be a recommended option. The additional memory usage of around 20MiB is relatively small and acceptable, especially given the benefit of having a continued Zigbee mesh even if Home Assistant were to go down.
What is the one virtual machine that you are currently running, if you donβt mind me asking? Perhaps you can consider converting it to a LXC to conserve resources.
What is that benefit to keep the Zigbee network up if HA is down?
So you are saying that I can fire up a LXC with only 32Mb of RAM for this?
That VM is a W10.
My server is at the max of itβs RAM capacity and I am considering something else but thatβs for later.
The resources are available for you to investigate and verify for yourself.
Keeping the ZigBee network going means any direct triggering will still work, eg from dimmer to bulb. Also the less you tear it down and build it up the stabler your ZigBee network will be.
Hi Nick, thanks for jumping in!
Direct triggering: I know that itβs possible but I donβt think this works over here (have never tried that)
Stability of Zigbee network: is the mesh rebuilt every time after going down?
Until now I was using Debian for my containers because thatβs what I used most and know best - even though Iβm not very experienced in Linux.
Iβm looking at Alpine Linux now to see it thatβs an option, first for Z2M and later to redo my other containers.