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:
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)
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)
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!
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.
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.
> 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/*
