# Z-Wave unreachable issues **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave, homey-pro\ **Created:** [August 13, 2024, 10:09pm UTC](https://community.homey.app/t/z-wave-unreachable-issues/114365 "2024-08-13T22:09:46Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [February 12, 2025, 11:22pm UTC](https://community.homey.app/t/z-wave-unreachable-issues/114365/9 "2025-02-12T23:22:31Z")
> [@loy80y](#): > > aeotec It probably is not even solely a Homey issue, but a combination of z-wave devices flooding the mesh network, and Homey lacking tools or systems to control that behaviour. The Aeotec app should be updated, to have the default check and poll interval settings less nervous. > [@Homey Pro Zwave Stability Issues](https://community.homey.app/t/homey-pro-zwave-stability-issues/107463/3): > > I’ve read several posts about these things ruining your mesh, because they’re way too ‘chatty’ > Try to increase the intervals, avoid "every 1 second’ check-intervals and such; > Here’s an excellent explanation and howto: > [@Homey Pro 2023 Zwave issues](https://community.homey.app/t/homey-pro-2023-zwave-issues/79656/38): > > I found the same situation with my Aeotec switches. They were sending a large number (hundreds per minute) of messages all related to metering which flooded the z-wave network and made it unresponsive for other control signals. 2023-05-18T21:31:15.278Z Node[33]: [COMMAND\_CLASS\_METER] {“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[161]},“Properties1”:{“Meter Type”:1,“Rate Type”:1,“Scale bit 2”:true},“Properties2 (Raw)”:{“type”:“Buffer”,“data”:[108]},“Properties2”:{“Size”:4,“Scale bits 10”:1,“Pre… --- _[View the full topic](https://community.homey.app/t/z-wave-unreachable-issues/114365)._