# "Error: Matter is not available" crashing frequently — requires full restart **URL:** \ **Category:** Homey Self-Hosted Server\ **Tags:** matter\ **Created:** [June 7, 2026, 2:50am UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871 "2026-06-07T02:50:36Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![amsterdam](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/amsterdam/32/166423_2.png) [@amsterdam](https://community.homey.app/u/amsterdam)\ **Post date:** [June 7, 2026, 2:50am UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/1 "2026-06-07T02:50:36Z")
Hi everyone, I’m running into a recurring issue with my Matter devices where the Matter subsystem seems to crash entirely. Whenever I try to toggle a device (turn it on or off), the action fails, and I get the following stack trace in my logs: ```auto Error: Matter is not available. Please try again later. at wrapMatterError (file:///app/node_modules/@athombv/homey-matter/dist/util/Util.js:212:19) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async HomeyMatter.sendCommand (file:///app/node_modules/@athombv/homey-matter/dist/HomeyMatter.js:245:32) at async MatterNode.sendCommand (file:///app/packages/homey-local/lib/matter/MatterNode.mts:996:14) at async Object.setState (file:///app/packages/homey-local/lib/matter/data-model/cluster/library/general/OnOffCluster.mts:14:7) at async file:///app/packages/homey-local/lib/matter/data-model/cluster/library/general/OnOffCluster.mts:129:5 at async MatterClusterInstance.onSetCapabilityValue (file:///app/packages/homey-local/lib/matter/data-model/cluster/ClusterInstance.mts:129:5) at async MatterDevice.onSetCapabilityValue (file:///app/packages/homey-local/lib/matter/MatterDevice.mts:398:5) at async VirtualDriverMatterLocal.wrapMatterError (file:///app/packages/homey-local/lib/VirtualDriverMatterLocal.mts:692:14) at async DeviceLocal.setCapabilityValue (file:///app/packages/homey-core/lib/Device.mjs:1180:5) ``` ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [June 7, 2026, 5:33am UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/2 "2026-06-07T05:33:09Z")
You should contact Athom via [support](https://homey.app/en-us/support/). ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 8, 2026, 12:04pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/3 "2026-06-08T12:04:07Z")
I am having the same issue, no matter devices work in homey but work in Apple home. I have tried putting in a support request, but I keep getting referred back to the forum. I am running the latest release candidate (I had the same issues with the stable version) ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [June 8, 2026, 1:10pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/4 "2026-06-08T13:10:38Z")
> [@JMDPC](#): > > but I keep getting referred back to the forum I guess they’ve given up on providing support 🤷🏼‍♂️ ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 8, 2026, 1:38pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/5 "2026-06-08T13:38:07Z")
Yes apparently so. ![Screenshot 2026-06-08 at 9.37.37 AM](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc1bff0ede85e810a1e3c15b1c1f8d77a9a5cbaf.png) ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [June 8, 2026, 2:00pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/6 "2026-06-08T14:00:12Z")
Choose “Other”, then at the bottom you can fill in a form. ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 8, 2026, 2:08pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/7 "2026-06-08T14:08:34Z")
Thx but it gives me the same message. Maybe it is due to using Self Hosted Server ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [June 8, 2026, 3:18pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/8 "2026-06-08T15:18:14Z")
Then choose “My Homey isn’t listed” ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 8, 2026, 5:59pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/9 "2026-06-08T17:59:29Z")
LOL that worked thank you ---
**Author:** ![Welshsmarthome](https://avatars.discourse-cdn.com/v4/letter/w/df705f/32.png) [@Welshsmarthome](https://community.homey.app/u/Welshsmarthome)\ **Post date:** [June 10, 2026, 7:59pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/10 "2026-06-10T19:59:55Z")
This sadly seems to be a recurring theme. I had lots of matter issues a while ago. After some back and forth, They too referred me to the forum and told me they cant offer any help. Begs the question, whats the point of support if they cant help? This forum is amazing and everyone on it is very helpful but that shouldn’t be the default go to for support Ive since shifted my devices to home assistant and bridge them over. Surely this isnt really what homey wants its customers to do! Hope you get sorted ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 10, 2026, 8:09pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/11 "2026-06-10T20:09:34Z")
One thing that I have noticed seems to help me is periodically rebooting my AppleTV and HomePod. Matter always works on Apple Home, but when it stops working in Homey, that is what I have started doing. If they don’t fix Matter, I may invest in a few Zigbee plugs and use them to report my Apple devices every day. ---
**Author:** ![amsterdam](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/amsterdam/32/166423_2.png) [@amsterdam](https://community.homey.app/u/amsterdam)\ **Post date:** [June 10, 2026, 8:27pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/12 "2026-06-10T20:27:59Z")
Hello folks! I “may” have a “possible fix”. I’m running this fix for about 4 days now and seems stable. I have my homey SelfHosted on proxmox. Disabling IGMP Snooping on the Proxmox host’s virtual bridge seem to have resolved the issue. I added `bridge-mcsnoop no` and `post-up echo 0 > /sys/class/net/vmbr0/bridge/multicast_snooping` to my net file. ```auto > cat /etc/network/interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to move any of # the PVE managed interfaces into external files! auto lo iface lo inet loopback iface nic0 inet manual auto vmbr0 iface vmbr0 inet static address 10.X.X.X/24 gateway 10.X.X.X bridge-ports nic0 bridge-stp off bridge-fd 0 bridge-mcsnoop no post-up echo 0 > /sys/class/net/vmbr0/bridge/multicast_snooping source /etc/network/interfaces.d/* ``` Then > ifreload -a to apply the fix. Hope this helps ---
**Author:** ![AusLuke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ausluke/32/167617_2.png) [@AusLuke](https://community.homey.app/u/AusLuke)\ **Post date:** [June 20, 2026, 11:13am UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/13 "2026-06-20T11:13:13Z")
I’m experiencing the same issue with self-hosted on a Mac OS machine. Didn’t have an issue while evaluating now having buyers remorse for buying a lifetime licence, I hate subscriptions! Great to find such a active community though! ---
**Author:** ![bwa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bwa/32/17852_2.png) [@bwa](https://community.homey.app/u/bwa)\ **Post date:** [June 20, 2026, 6:55pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/14 "2026-06-20T18:55:14Z")
100% of my tickets to Athom about anyting in SHS, is closed with ‘not supported platform’. Maybe they should put the on the SHS infopage. : This product is not supported by Athom The interresting this is that some of the issues was also on my Homey Pro, and these tickets was also closed with without any helpful other than reinstall, dont use it and things like that. So Athom is not what they was a couple of years ago. sad story ---
**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\ **Post date:** [June 20, 2026, 9:40pm UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/15 "2026-06-20T21:40:30Z")
I updated to the latest beta and my SHS has been stable for three days with no dropped matter devices ---
**Author:** ![AusLuke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ausluke/32/167617_2.png) [@AusLuke](https://community.homey.app/u/AusLuke)\ **Post date:** [June 24, 2026, 2:06am UTC](https://community.homey.app/t/error-matter-is-not-available-crashing-frequently-requires-full-restart/155871/16 "2026-06-24T02:06:23Z")
Hi Everyone. I have been provided with an answer. Posting it here in case others have not heard back. \*\* Niels\*\* (Athom) Jun 23, 2026, 14:52 GMT+2 Hi Luke, Thank you for reaching out to our support. The “Matter is not available” issue you’re seeing is a known bug that we’ve fixed in the 13.3.0 beta release. This is because of the OTA (over the air) update features that got implemented. You can resolve this today by switching your Homey Self‑Hosted Server to Experimental updates and then rebooting to install 13.3.0: - Enable Experimental updates via Developer Tools: [https://support.homey.app/hc/en-us/articles/12199889665308](https://support.homey.app/hc/en-us/articles/12199889665308) - Reboot your SHS so the update installs. If you prefer, you can wait for the stable rollout instead. If you choose this option you could choose to make yourself a [power user](https://support.homey.app/hc/en-us/articles/16280294671516-Power-User-Experiment) and make a flow that your Homey reboots every day automatically. After updating, please let me know if Matter stays available. If not, we’ll collect a fresh diagnostic and app log and review refund options.