I’m sorry to have to ask this but I just can’t spend every evening searching and experimenting to get my new MX3 M.2 working.
I’m using Frigate with:
Home Assistant OS Core: 2026.7.2 Supervisor: 2026.06.2 Operating System: 18.1 Frontend: 20260624.5 and the MemryX MX3 M.2 and it is installed in my SSD M.2 slot on my PC. I added the info to the config file:
detectors:
memx0:
type: memryx
device: PCIe:0
This caused the note on the bottom to change from CPU to GPU and things got slow and unstable. All the instructions out there does not address (Or I can’t figure it out) my particular setup. Does anyone have a step-by-step instruction to load whatever software and or drivers and config files I need? I need help. Thank you
Hi @Sheldon_Goldwing, thanks for this question!
As you read through the available Frigate documentation regarding the use of dedicated AI processors as detectors, you might notice a common theme: the detector device’s drivers will typically need to be installed on the host OS, while Frigate handles runtime installation for the detector inside the Docker environment. The same principle applies here, where you need to have the MemryX drivers installed on your Home Assistant OS image before configuring Docker to use the MemryX detector. Did you attempt to install the drivers in your setup?
Because HAOS is a Buildroot-based OS without the availability of package managers of any kind, you would have to custom-build the MemryX drivers into the OS image from source (MemryX is not included in any of the pre-built HAOS images). This is a somewhat lengthy task, but depending on your prior experience with embedded systems/Buildroot, you may be able to piece something together using our publicly-available MemryX Yocto layers.
When time permits, we can look into how to integrate MemryX into the HAOS image. Sorry for the inconvenience!
Yes, I am aware of how HAOS loads that is why I don’t know how to load the drivers. I also have no issues with reloading HAOS from scratch and feeding in drivers as I go. I just need to know the step by step process.
I guess I could return the MX3 but I really would like to use it. Is there a better deployment option?
Thank you,
Sheldon
Given that Frigate does not generally advise using HAOS with hardware accelerators, this is our first request to support it. That being said, I did manage to integrate the MemryX drivers and daemon into the HAOS image in a custom build, and Frigate is live with the MemryX detector!
I am still working on capturing the step-by-step process as I want it to be detailed and easy to follow. In the coming days, be on the lookout for a new post with HAOS build/config instructions on our Frigate category page.
If you prefer to try out a different/easier method, we support most popular deployment options for Frigate. You can install on a plain Linux distribution as supported by the Frigate docs (this is, of course, the easiest method), use a Proxmox VM, or even a Proxmox LXC. We have also supported Frigate users in setting up the MemryX detector on Unraid. Whetever you choose, I’m happy to support you through the process!
The MemryX detector truly is a great addition to any Frigate setup, and I hope you will find a deployment method that meets your requirements!
Well thank you so much. I swapped (so I could keep the old HAOS configuration) the SSD and reloaded Ubuntu Server and did my best to load the MX3 drivers. I do get the /dev/memx0 when using the la /dev/memx* command. I also get the temperature report BUT when I added the memryx to the frigate configuration I get the same results as before. The video feeds take a while to load and everything is really sluggish. It does not show up on the bottom of the screen like last time. Did I miss something ?
Hm, there could be a couple things going wrong here. First, I would recommend that you follow the manual Frigate setup guide provided on our DevBlog. A very important note: the latest Frigate release supports MemryX SDK 2.1, so when you navigate to our Developer Hub to install the drivers and runtime packages, please ensure the version is 2.1, not our most recent release (v2.2). The SDK version can be selected using the drop-down menu at the upper left-hand corner of the page. The installation instructions on the Developer Hub provide commands to verify your driver installation version, so please complete those steps, and don’t forget to reboot the system when prompted!
Aside from that, the rest of the steps for configuring Frigate should be fairly straightforward if you follow the manual setup guide. Pay close attention to the sections detailing the configuration files, and you should have a working setup! If you hit any issues along the way, just reach out here. It might be helpful to share your config files and Frigate logs for troubleshooting if you’re willing. Please also provide the output of apt policy memx-drivers and apt policy mxa-manager from the Ubuntu Server host to confirm a successful installation.
Thanks!
Hi @Sheldon_Goldwing,
If you prefer to try again with Home Assistant OS, I’ve just published a guide to building the custom HAOS image with MemryX support. The linked repository, memx_haos, will give you a step-by-step process to follow from building the image to configuring Frigate on Home Assistant. Feel free to check it out, and let me know if you have any questions.
Thanks for your patience, and have a great weekend!
WOW! I looked it over and it looks good. I had to stop working on the project (Anniversary week) I will walk though it next week. The one question I have is when would a person restore their HA backed up settings and will that cause any issues with the MemryX install? Thanks again. 
Great question! A Home Assistant backup restores your Home Assistant configuration and add-on data, but it doesn’t replace the underlying Home Assistant OS image. Since the MemryX driver and runtime are built into the custom HAOS image itself, restoring a backup shouldn’t affect the MemryX installation.
My recommendation would be:
- Flash the custom MemryX-enabled HAOS image.
- Complete the initial HAOS setup.
- Restore your Home Assistant backup.
- Reinstall/configure the modified Frigate (Full Access) add-on if it wasn’t included in the backup or if you’re moving to the MemryX-enabled version.
I haven’t specifically tested the backup/restore workflow yet, but based on what I’ve read about how HAOS backups work, I wouldn’t expect any issues with the MemryX integration. Just make sure you uninstall/remove the older Frigate add-on repository (if it’s included in your backup) before installing the MemryX-configured version from our fork.
Congratulations on your anniversary! 
Loaded Ubuntu server 24.04.4 LTS on an i7-10700 2.9Ghz 16gb 512 SSD Gig Ethernet and I SSH into it. No issues for 45 minutes before it timed out.
Might try again tomorrow night.
The retry worked! It took an hour and a half exactly and I then flashed that to a USB Drive as per #5 instructions. Probably some assumed steps here but I booted off the new USB Drive and HAOS booted. I will work on #6 and the rest tonight. Hopefully it will share how to get that onto my SSD as I’m pretty sure I’m working off the USB Flash drive right now. - Thanks again
I’m so sorry and please forgive me but could you please offer more details on steps 5 & 6? I wrote the image to the USB flash drive and restarted. I can’t seem to figure out how to follow the next instruction steps.
Hi @Sheldon_Goldwing,
I’m happy to hear your image built successfully!
As per the README, I would recommend following the Home Assistant Docs to install the image according to your preference. The guide we provide will show you how to build the image, boot it, and verify MemryX + Frigate. For verification purposes, using the bootable USB drive is sufficient. If you prefer to install the image to your SSD, please do reference the official HAOS documentation.
Since you were able to boot HAOS from your USB drive, your system should render the Home Assistant shell, where you can type login to enter the main console. Assuming the host system you used to boot HAOS is the system you intend to use with Frigate, the MemryX M.2 module should be installed. If you intend to use a different host system, move the USB drive to that system and use it to boot the HAOS image there.
Remember that upon booting the image, you need to have an ethernet connection to the host system.
Once you’ve booted and logged in to the console, the commands in step 6 can be run to verify the enumeration of the MemryX device (i.e., confirm your host system recognizes it), the installation of runtime and drivers, and the successful bind-mount of the MemryX daemon, mxa_manager.
If you have any questions about the output of the commands in Step 6, feel free to share them here, and I’ll let you know if it looks correct.
I hope this helps!
