# Just got 13.2.0 and matter died **URL:** \ **Category:** Questions & Help\ **Created:** [May 21, 2026, 12:30pm UTC](https://community.homey.app/t/just-got-13-2-0-and-matter-died/155166 "2026-05-21T12:30:20Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![Thyg0d](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thyg0d/32/80627_2.png) [@Thyg0d](https://community.homey.app/u/Thyg0d)\ **Post date:** [May 22, 2026, 6:14am UTC](https://community.homey.app/t/just-got-13-2-0-and-matter-died/155166/13 "2026-05-22T06:14:33Z")
The official updatelog is where I got the info from. It’s probably just missing the text -r.2 But it is what it says. ![AISelect_20260522_080937_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/73c3fe0e71038883b9660382b41414f0828dc8a7.jpeg) Question remains though. Why doesn’t homey wait longer for replies from the GH? Devices on the same vlan, mdns active and working shouldn’t have a problem. Why can’t I force it to try to connect? And I’m apparently not alone reading posts here and other topics. An example. > [@Matter devices are unavailable](https://community.homey.app/t/matter-devices-are-unavailable/148583/57): > > He Guys… aim realy frustrated! 14 Thread Devices, 11 of them are Smart Plugs from Eve which working as Thread Router in a Family House with 165m2 with 3 Floors…after some changes on Homey Pro 26 (power supplier-cable-place of homey-router network changes..) it works 3 weeks without failure till i add a new thread device and the problems starts again…sporadically the thread network break down, devices lost the IPV6 address and Ping Test to the affected devices reports.. Well, i am fed… --- _[View the full topic](https://community.homey.app/t/just-got-13-2-0-and-matter-died/155166)._