Help ZWave down

[keltymd (Matt)]

Im getting tired real tired. Support “Helped” me last night because 4 days ago I opened a ticket saying it was taking forever for functions to happen if they ever did. Now 3/4 of my Zwave do not work at all and the rest if they work will take 30-60 seconds this time to come on and next time are normal then 30-60 seconds to respond. I have rebooted the hub countless times, performed ZWave repair countless times, tried to exclude and reaad devices and cant exclude them because they cant talk long enough to exclude, tried to add new devices and cant, I am out of ideas.

ZWave repairs give me “Failed to update route” or “Failed to update mesh info”

Zigbee appears to be working fine

Any help is appreciated

[SBDOBRESCU (Bobby)]

Did you see the z-wave error of death err 101, by any chance?

Err 101 - ZW module not responding

@bamarayne Just saw your further post. 1 - hub is showing currently active in the ide and the app This was a symtom I had with the 101 error as well I kept disconnecting via the IDE as well and then pinging via the IDE to get the Hub back when I restarted. You’re still screwed though…

[keltymd (Matt)]

no just 103 and 114 when I tried to remove and reaad a device

[krlaframboise (Kevin)]

I doubt this will matter, but since you’re out of ideas, have you tried moving any of the z-wave devices within a few feet of the hub to see if that makes a difference?

[SBDOBRESCU (Bobby)]

@aaron just posted this…on a different thread. Sounds like support is your best bet for now.

Early bedtime for SmartSense Motion?

Weird question… is there something that happens in your home (or the neighbors’) around the same time that could cause interference? I once worked with a customer that couldn’t figure out why many devices went nonresponsive in the evening. After probing, it turned out that the whole family came home, started cranking the wifi and TVs (and what sounded like an industrial audio system) that started causing Zigbee devices to become nonresponsive. However, everything would work again in the morning and on weekends because people weren’t just sitting around with devices. Check in with support@ and they can dig it to the event logs. I am envisioning something like this: [image]

[keltymd (Matt)]

@krlaframboise

I doubt this will matter, but since you’re out of ideas, have you tried moving any of the z-wave devices within a few feet of the hub to see if that makes a difference?

yes all my rooms have Ethernet connections so I have move the hub within a foot of most the devices to see if it would work

[keltymd (Matt)]

odd thing my outside sensors, Aeon multi4 sensors, are reporting as coded once every minute. everything else in the house is hit or miss at best. Some never work others work when they want too

[Aaron (Aaron S)]

Z-Wave networks do not automatically re-map themselves when devices or the Hub are moved/removed. The Hub is still going to look for the devices/repeaters directly connected to the Hub - rather than those one or two hops away - even if they are on the opposite side of the house. If you see some devices working but others not, this is like the issue.

Unless you have a gigantor Z-Wave network, a good rule of thumb is to run a Z-Wave Network Repair every time you remove or re-add a device.

[keltymd (Matt)]

@Aaron

I didnt remove or reaad anything before this issue started. I tried to remove and reaad something today and couldnt. What can be done can you look at my account?

[sidjohn1]

You may also have a malfunctioning zwave device, jamming up the rest of the in range zwave network. You can try killing power to all zwave devices and restoring power one device at a time. Either you’ll find the offending device, or your zwave devices will start to work again.

[keltymd (Matt)]

this is my log
2016-01-27 9:52:17.066 AM CST
moments ago HUB zwStatus ready Z-Wave network repair finished
2016-01-27 9:52:17.011 AM CST
moments ago HUB zwNwkRepair finished Z-Wave network repair finished
2016-01-27 9:51:30.124 AM CST
moments ago HUB zwNwkRepair failure Network repair for Light-Kitchen Main Dimmer [1C]: Failed to update route
2016-01-27 9:51:07.372 AM CST
moments ago HUB zwNwkRepair failure Network repair for Multi-Shed [1B]: Failed to update route
2016-01-27 9:50:34.853 AM CST
moments ago HUB zwNwkRepair failure Network repair for Switch-Ariel Bedroom Main [15]: Failed to update route
2016-01-27 9:50:23.083 AM CST
moments ago HUB zwNwkRepair failure Network repair for Light-Hall [14]: Failed to update route
2016-01-27 9:50:12.192 AM CST
moments ago HUB zwNwkRepair failure Network repair for Switch-Erica Bedroom Main [13]: Failed to update route
2016-01-27 9:50:00.419 AM CST
moments ago HUB zwNwkRepair failure Network repair for Fan-Hall Bath [07]: Failed to update route
2016-01-27 9:49:33.168 AM CST
moments ago HUB zwNwkRepair failure Network repair for Fan-Living Room [03]: Failed to update route
2016-01-27 9:49:11.638 AM CST
moments ago HUB zwNwkRepair failure Network repair for Light-Living Room [02]: Failed to update route
2016-01-27 9:49:08.273 AM CST
moments ago HUB ping ping ping
2016-01-27 9:48:49.634 AM CST
moments ago HUB zwNwkRepair failure Network repair for Thermostat-CT30 [29]: Failed to read protocol info
2016-01-27 9:48:34.622 AM CST
5 minutes ago HUB zwNwkRepair failure Network repair for Outlet-Humidifier [28]: Failed to update mesh info
2016-01-27 9:47:48.077 AM CST
6 minutes ago HUB zwNwkRepair failure Network repair for Light-Kitchen Main Dimmer [1C]: Failed to update mesh info
2016-01-27 9:46:58.765 AM CST
7 minutes ago HUB zwNwkRepair failure Network repair for Multi-Shed [1B]: Failed to read protocol info
2016-01-27 9:46:43.830 AM CST
7 minutes ago HUB zwNwkRepair failure Network repair for Light-Laundry Room [1A]: Failed to update mesh info
2016-01-27 9:46:15.683 AM CST
7 minutes ago HUB zwNwkRepair failure Network repair for Switch-MBR Main [17]: Failed to update mesh info
2016-01-27 9:45:44.229 AM CST
8 minutes ago HUB zwNwkRepair failure Network repair for Light-MBR Closet [16]: Failed to update mesh info
2016-01-27 9:45:15.411 AM CST
8 minutes ago HUB zwNwkRepair failure Network repair for Switch-Ariel Bedroom Main [15]: Failed to update mesh info
2016-01-27 9:44:44.394 AM CST
9 minutes ago HUB zwNwkRepair failure Network repair for Light-Hall [14]: Failed to update mesh info
2016-01-27 9:44:18.645 AM CST
9 minutes ago HUB zwNwkRepair failure Network repair for Switch-Erica Bedroom Main [13]: Failed to update mesh info
2016-01-27 9:44:07.229 AM CST
10 minutes ago HUB ping ping ping
2016-01-27 9:43:47.679 AM CST
10 minutes ago HUB zwNwkRepair failure Network repair for Fan-Hall Bath [07]: Failed to update mesh info
2016-01-27 9:43:19.824 AM CST
10 minutes ago HUB zwNwkRepair failure Network repair for Light-Hall Bath [06]: Failed to update mesh info
2016-01-27 9:42:47.320 AM CST
11 minutes ago HUB zwNwkRepair failure Network repair for Light-Front Porch [05]: Failed to read protocol info
2016-01-27 9:42:32.317 AM CST
11 minutes ago HUB zwNwkRepair failure Network repair for Light-Flood Front [04]: Failed to update mesh info
2016-01-27 9:41:55.723 AM CST
12 minutes ago HUB desc F129 desc: 02 C2DF 000C 00 05 0000 0001 0003 0B05 FC0F 01 0003
2016-01-27 9:41:55.678 AM CST
12 minutes ago HUB desc F129 desc: 01 0104 0402 00 07 0000 0001 0003 0020 0402 0500 0B05 01 0019
2016-01-27 9:41:55.015 AM CST
12 minutes ago HUB desc F129 desc: 02 C2DF 000C 00 05 0000 0001 0003 0B05 FC0F 01 0003
2016-01-27 9:41:54.876 AM CST
12 minutes ago HUB desc F129 desc: 01 0104 0402 00 07 0000 0001 0003 0020 0402 0500 0B05 01 0019
2016-01-27 9:41:54.822 AM CST
12 minutes ago HUB ep_cnt:2, ep:01 02 ep_cnt:2, ep:01 02 ep_cnt:2, ep:01 02
2016-01-27 9:41:53.597 AM CST
12 minutes ago HUB ep_cnt:2, ep:01 02 ep_cnt:2, ep:01 02 ep_cnt:2, ep:01 02
2016-01-27 9:41:53.545 AM CST
12 minutes ago HUB join join join
2016-01-27 9:41:52.665 AM CST
12 minutes ago HUB join join join
2016-01-27 9:41:43.282 AM CST
12 minutes ago HUB zwNwkRepair failure Network repair for Fan-Living Room [03]: Failed to update mesh info
2016-01-27 9:40:56.424 AM CST
13 minutes ago HUB zwNwkRepair failure Network repair for Light-Living Room [02]: Failed to update mesh info
2016-01-27 9:40:28.430 AM CST
13 minutes ago HUB hubInfo hardwareID:000D, version:07, … hardwareID:000D, version:07, mac:D0:52:A8:45:1F:BF, localip:192.168.1.114, localSrvPortTCP:39500, localSrvPortUDP:0, zigbeeFWM…
2016-01-27 9:39:51.800 AM CST
14 minutes ago HUB zwNwkRepair started Z-Wave network repair started
2016-01-27 9:39:51.799 AM CST
14 minutes ago HUB zwStatus network repair Z-Wave network repair started

[keltymd (Matt)]

Im trying that now thank you

[keltymd (Matt)]

when you do a repair it shows failures. will it show success if something works?

[SBDOBRESCU (Bobby)]

You’d want to see no failures between started amd ready…

[keltymd (Matt)]

@sidjohn1 may have earned a gold star. I pulled the air switch on all my GE switches and then tested all battery devices that I couldnt easily get to the battery on (in door sensors) and contact sensors work and I am moving thru my GE switches now. I got two of them online now woo hoo. 40 more to go

[keltymd (Matt)]

gentlemen thank you for your assistance

[SBDOBRESCU (Bobby)]

Phew, so you’ve got you system back?! That was a great idea @sidjohn1. Sounds like you’ve been in his shoes before I’ve been hitting the breaker occasionally, pulling the air switch is much better!

[keltymd (Matt)]

90% back so far. I have a few more devices to test but wanted to get my HVAC working again. Gotta love @Mike_Maxwell vent app and well Im spoiled by it

[SBDOBRESCU (Bobby)]

Now the million dollar question! What has caused this and how to avoid it?!?!

[keltymd (Matt)]

good question now the issue its all failing again. Nothing changed in the last 15 minutes