I am seeing the same behavior on my hub. Repeated Z-Wave power cycle events, such as:
2017-10-28 12:39:42.516 PM MDT HUB zwStatus ready Z-Wave is ready
2017-10-28 12:39:40.955 PM MDT HUB zwStatus power cycle Z-Wave power cycle started
Hub is on FW: 000.019.00014
Z-wave is currently severely crippled in this latest beta. My system is borderline usable and these reboots are almost certainly guaranteed to happen whenever running a routine or a SmartLighting automation. Even my Z-Wave thermostat is now affected, and thatâs run almost flawlessly on both SmartThings and Iris. Iâm losing hope that ST will ever have a stable Z-wave platform.
This is just the last 30 minutes. What kills me is that these âBad Nodesâ all work fine both for manual and automated control. I am guessing theyâre slow to respond so ST is falsely declaring them dead and killing Z-wave to recover.
Date Source Type Name Value User Displayed Text
2017-10-31 8:12:54.749 AM EDT
moments ago HUB index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN index:04, mac:4C72B9F8B735, h... index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-31 8:10:27.405 AM EDT
moments ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9f574236-73ce-477d-8a9f-3e9633ea28e9, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9f574236-73ce-477d-8a9f-3e9633ea28e9, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 8:08:48.880 AM EDT
moments ago HUB ping ping ping
2017-10-31 8:08:05.385 AM EDT
6 minutes ago HUB index:16, ip:7F000001, port:0BB8, requestId:d20da7c9-7398-495d-8df2-75621028d82b, headers:SFRUUC8xLj index:16, ip:7F000001, port:0... index:16, ip:7F000001, port:0BB8, requestId:d20da7c9-7398-495d-8df2-75621028d82b, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:08:05.325 AM EDT
6 minutes ago HUB index:15, ip:7F000001, port:0BB8, requestId:7775b674-a2a1-47df-bca7-35073aa22f13, headers:SFRUUC8xLj index:15, ip:7F000001, port:0... index:15, ip:7F000001, port:0BB8, requestId:7775b674-a2a1-47df-bca7-35073aa22f13, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:08:05.185 AM EDT
6 minutes ago HUB index:16, ip:7F000001, port:0BB8, requestId:08bb3866-86f4-4216-9c68-1bb6ace40ed5, headers:SFRUUC8xLj index:16, ip:7F000001, port:0... index:16, ip:7F000001, port:0BB8, requestId:08bb3866-86f4-4216-9c68-1bb6ace40ed5, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:08:05.081 AM EDT
6 minutes ago HUB index:15, ip:7F000001, port:0BB8, requestId:a81fc612-66f0-4ed5-8b71-512f74eb6644, headers:SFRUUC8xLj index:15, ip:7F000001, port:0... index:15, ip:7F000001, port:0BB8, requestId:a81fc612-66f0-4ed5-8b71-512f74eb6644, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:08:04.997 AM EDT
6 minutes ago HUB index:16, ip:7F000001, port:0BB8, requestId:c7e2c1a7-1039-4b88-8cf8-fe7eeb245075, headers:SFRUUC8xLj index:16, ip:7F000001, port:0... index:16, ip:7F000001, port:0BB8, requestId:c7e2c1a7-1039-4b88-8cf8-fe7eeb245075, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:08:04.890 AM EDT
6 minutes ago HUB index:15, ip:7F000001, port:0BB8, requestId:0cbacef2-b54e-4549-ae91-c14e58302a94, headers:SFRUUC8xLj index:15, ip:7F000001, port:0... index:15, ip:7F000001, port:0BB8, requestId:0cbacef2-b54e-4549-ae91-c14e58302a94, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-31 8:06:01.086 AM EDT
8 minutes ago HUB index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN index:06, mac:4C72B9F8B735, h... index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-31 8:05:54.779 AM EDT
8 minutes ago HUB zw device: 69, command: 3002, payload: 21 74 00 16 61 FC 00 00 00 00 00 00 zw device: 69, command: 3002,... zw device: 69, command: 3002, payload: 21 74 00 16 61 FC 00 00 00 00 00 00
2017-10-31 8:05:53.949 AM EDT
8 minutes ago HUB zw device: EB, command: 3202, payload: 21 74 00 12 61 FC 00 00 00 00 00 00 zw device: EB, command: 3202,... zw device: EB, command: 3202, payload: 21 74 00 12 61 FC 00 00 00 00 00 00
2017-10-31 8:05:53.217 AM EDT
8 minutes ago HUB zw device: 69, command: 3002, payload: 21 74 00 16 61 FC 00 00 00 00 00 00 zw device: 69, command: 3002,... zw device: 69, command: 3002, payload: 21 74 00 16 61 FC 00 00 00 00 00 00
2017-10-31 8:05:27.329 AM EDT
8 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:d77b3e88-58cc-480a-8574-1d053ddc9404, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:d77b3e88-58cc-480a-8574-1d053ddc9404, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 8:05:22.831 AM EDT
8 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:eab7ca33-fb7e-4723-a499-1948e5d3b678, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:eab7ca33-fb7e-4723-a499-1948e5d3b678, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 8:05:20.818 AM EDT
8 minutes ago HUB index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:df5efadb-634c-4920-afee-5c409bcbff98, index:16, mac:000420F3C826, i... index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:df5efadb-634c-4920-afee-5c409bcbff98, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 8:04:56.852 AM EDT
9 minutes ago HUB index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN index:06, mac:4C72B9F8B735, h... index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-31 8:03:46.960 AM EDT
10 minutes ago HUB ping ping ping
2017-10-31 8:01:08.885 AM EDT
13 minutes ago HUB zwStatus ready Z-Wave is ready
2017-10-31 8:01:04.928 AM EDT
13 minutes ago HUB zwBadNode Err 120: Z-Wave send timed out (Rptr: Lamp in Dining Room [09])
2017-10-31 8:01:04.927 AM EDT
13 minutes ago HUB zwStatus power cycle Z-Wave power cycle started
2017-10-31 8:01:03.075 AM EDT
13 minutes ago HUB zw device: 2B, command: 3202, payload: 21 34 00 17 D8 5D 00 00 00 00 00 00 zw device: 2B, command: 3202,... zw device: 2B, command: 3202, payload: 21 34 00 17 D8 5D 00 00 00 00 00 00
2017-10-31 8:01:01.366 AM EDT
13 minutes ago HUB zw device: 2B, command: 3202, payload: 21 34 00 17 D8 5D 00 00 00 00 00 00 zw device: 2B, command: 3202,... zw device: 2B, command: 3202, payload: 21 34 00 17 D8 5D 00 00 00 00 00 00
2017-10-31 8:01:00.904 AM EDT
13 minutes ago HUB zw device: 6F, command: 3202, payload: 21 74 00 17 C8 5D 00 00 00 00 00 00 zw device: 6F, command: 3202,... zw device: 6F, command: 3202, payload: 21 74 00 17 C8 5D 00 00 00 00 00 00
2017-10-31 8:00:28.842 AM EDT
13 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9c304f15-bdbe-46ee-aace-c6e9cd63ab4b, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9c304f15-bdbe-46ee-aace-c6e9cd63ab4b, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 7:59:39.053 AM EDT
14 minutes ago HUB zw device: 7B, command: 600D, payload: 02 00 32 02 A1 7C 00 00 1A 89 00 00 00 00 00 00 zw device: 7B, command: 600D,... zw device: 7B, command: 600D, payload: 02 00 32 02 A1 7C 00 00 1A 89 00 00 00 00 00 00
2017-10-31 7:59:37.329 AM EDT
14 minutes ago HUB zw device: 7B, command: 600D, payload: 02 00 32 02 A1 7C 00 00 1A 89 00 00 00 00 00 00 zw device: 7B, command: 600D,... zw device: 7B, command: 600D, payload: 02 00 32 02 A1 7C 00 00 1A 89 00 00 00 00 00 00
2017-10-31 7:59:19.357 AM EDT
14 minutes ago HUB zwStatus ready Z-Wave is ready
2017-10-31 7:59:16.869 AM EDT
14 minutes ago HUB zwStatus power cycle Z-Wave power cycle started
2017-10-31 7:59:16.865 AM EDT
14 minutes ago HUB zwBadNode Err 120: Z-Wave send timed out (Lights in Garage Interior [B3])
2017-10-31 7:58:44.866 AM EDT
15 minutes ago HUB ping ping ping
2017-10-31 7:58:33.091 AM EDT
15 minutes ago HUB zw device: 2B, command: 3202, payload: 21 74 00 27 D9 2E 00 00 00 00 00 00 zw device: 2B, command: 3202,... zw device: 2B, command: 3202, payload: 21 74 00 27 D9 2E 00 00 00 00 00 00
2017-10-31 7:58:32.991 AM EDT
15 minutes ago HUB zw device: 2B, command: 3202, payload: 21 74 00 27 D9 2E 00 00 00 00 00 00 zw device: 2B, command: 3202,... zw device: 2B, command: 3202, payload: 21 74 00 27 D9 2E 00 00 00 00 00 00
2017-10-31 7:55:49.032 AM EDT
18 minutes ago HUB zw device: 6A, command: 600D, payload: 01 00 32 02 20 74 00 1C 15 E4 00 00 00 00 00 00 zw device: 6A, command: 600D,... zw device: 6A, command: 600D, payload: 01 00 32 02 20 74 00 1C 15 E4 00 00 00 00 00 00
2017-10-31 7:55:30.900 AM EDT
18 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:576aa025-8f32-487f-b168-5a21d12cfab2, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:576aa025-8f32-487f-b168-5a21d12cfab2, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 7:55:06.869 AM EDT
19 minutes ago HUB Lights on Garage Exterior [45... Lights on Garage Exterior [45]: Not responding
2017-10-31 7:54:58.868 AM EDT
19 minutes ago HUB index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN index:01, mac:4C72B9F8B735, h... index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-31 7:53:42.938 AM EDT
20 minutes ago HUB ping ping ping
2017-10-31 7:52:17.374 AM EDT
21 minutes ago HUB zwStatus ready Z-Wave is ready
2017-10-31 7:52:15.216 AM EDT
21 minutes ago HUB zwStatus power cycle Z-Wave power cycle started
2017-10-31 7:52:15.212 AM EDT
21 minutes ago HUB zwBadNode Err 120: Z-Wave send timed out (Lights on Garage Exterior [45])
2017-10-31 7:52:10.824 AM EDT
22 minutes ago HUB zw device: 69, command: 3200, payload: 21 74 00 2E D7 45 00 00 00 00 00 00 zw device: 69, command: 3200,... zw device: 69, command: 3200, payload: 21 74 00 2E D7 45 00 00 00 00 00 00
2017-10-31 7:51:20.878 AM EDT
22 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:34ca6655-186a-445a-8baa-22d30888f3b4, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:34ca6655-186a-445a-8baa-22d30888f3b4, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 7:51:15.377 AM EDT
22 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:901bb3f3-16c3-4bff-8c6d-783e5803a0d6, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:901bb3f3-16c3-4bff-8c6d-783e5803a0d6, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 7:50:30.852 AM EDT
23 minutes ago HUB index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:524fcd47-75c7-460c-8622-fc4f9b5336d5, index:15, mac:000420F3C826, i... index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:524fcd47-75c7-460c-8622-fc4f9b5336d5, headers:SFRUUC8xLjEgMjAwIE...
2017-10-31 7:50:18.919 AM EDT
23 minutes ago HUB zw device: 29, command: 3200, payload: 21 34 00 2F 6A AE 00 04 00 00 00 00 zw device: 29, command: 3200,... zw device: 29, command: 3200, payload: 21 34 00 2F 6A AE 00 04 00 00 00 00
2017-10-31 7:50:18.896 AM EDT
23 minutes ago HUB zw device: 2B, command: 3202, payload: 21 34 00 2F 6A AE 00 00 00 00 00 00 zw device: 2B, command: 3202,... zw device: 2B, command: 3202, payload: 21 34 00 2F 6A AE 00 00 00 00 00 00
2017-10-31 7:50:07.394 AM EDT
24 minutes ago HUB zwStatus ready Z-Wave is ready
2017-10-31 7:50:05.095 AM EDT
24 minutes ago HUB zwStatus power cycle Z-Wave power cycle started
2017-10-31 7:50:05.093 AM EDT
24 minutes ago HUB zwBadNode Err 120: Z-Wave send timed out (Lights on Garage Exterior [45])
2017-10-31 7:49:29.446 AM EDT
24 minutes ago HUB zwStatus ready Z-Wave is ready
2017-10-31 7:49:26.859 AM EDT
24 minutes ago HUB zwStatus power cycle Z-Wave power cycle startedSteve,
Sorry to hear that. We are working on getting the Z-Wave chipset firmware update working in 0.20.x hubCore, this should help with the power cycle/non responsive issue we are having.
Furthermore, As for bad nodes, I can expand on the technical details of it a little more. Basically, when we send a message to a device on the Z-Wave network, we wait to receive an acknowledgment that the message was received. If the acknowledgment does not come back after a decent wait period, then we have to assume the node is bad. The terminology can be changed here to indicate more slow or temporary unavailable.
Also I would like to ask if you are having any functional issues? Basically if you did not have access to the logs, was something not working that you can expand on?
Kianoosh
Thank you for the explanation, and it certainly does make sense. Some of the nodes that are repeatedly failing are distant from the hub and likely going through one or two hops. What doesnât make sense is some of the failures are occurring in devices 10-20 feet away. I wouldnât expect those to repeat.
When the resets occur it throws the entire system into a frenzy. Commands are missed, devices donât receive commands etc. I donât understand why a failure to receive a message from a device would cause the entire Z-Wave chip to power cycle. That seems very extreme, like rebooting your internet router every time a packet is lost.
The effect has been detrimental, just today. For example we attended a halloween event today. When I got there I realized that I forgot to disable to SmartLighting rules to turn off the porch and halloween lights so trick-or-treaters wouldnât come to the door. I had to make several attempts to turn off the exterior lighting as it appeared the commands were not taking the first time around.
Looking at the logs a few minutes later showed a couple power cycle events. I also noticed that none of our z-wave locks automatically locked when we left. They all failed to lock due to numerous z-wave power cycle events. In fact, it took me several tries to lock the door as that action itself caused another power cycle event.
Monday morning, the z-wave thermostat didnât change the set point when the Good Morning routine ran. Looking at the event log I showed another cluster of power cycle events. I would say the impacts are fairly severe right now, especially regarding the failure to lock doors!
Steve,
Thanks for the clear explanation. So if you keep a little faith for us, I can tell you that we are currently working on avoiding the messages being dropped for the next release as well.
As for why we power cycle the chip, basically the chip is non responsive to any of our commands, therefore we have to power cycle to chip to get it out of the funk that it is in. Much like your router example, if the router never responds to you, you would have to disconnect the WiFi connection at some point and restart the connect again.
Sorry again, hopefully we can get the next hub firmware to you as soon as possible.
Kianoosh
Iâm hopeful this can get fixed soon as I just had another incident this morning where two doors did not lock when they should have. Iâm certainly willing to volunteer for any advance pre-beta testing at this point once there a reliable solution ready to test.
Thank you for your help with this!
@Kianoosh_Karami, I am suddenly experiencing the exact same issues as @SteveWhite concerning z-wave devices. They are all extremely sluggish and sometimes do not work at all. Specifically, I am seeing degradation of service on my four Aeon Smart Dimmer 6 devices; I am using the device type âAeon Smart Dimmer 6 - RV v0.1â by @Robert_Vandervoort at https://github.com/robertvandervoort/SmartThings/blob/master/Aeon%20SmartDimmer%206/device_type-aeon-smartdimmer6-v0.1. These devices have worked flawlessly for several years up until 2 weeks ago. I have a ST hub v2, have contacted support concerning multiple mobile app crashes (every single time I use the ST app on iOS) and have received the standard âclear your web cache, uninstall app and reinstallâ which I have done to no avail.
I am convinced that my z-wave devices are causing these issues but see nothing in live logging. The ONLY z-wave device that I am not currently experiencing problems with is my Kwikset 916 z-wave lock!?!? I have uninstalled ALL z-wave devices, restarted ST Hub, and then re-installed each z-wave device; however, this has not solved the issue at all.
Please help!
Let me take a look at your hub and the available logs to see if you are experiencing similar issues as to Steve.
Kianoosh
Itâs a Z-wave chip problem which I hope can be fixed with a firmware update. I have always been leery of the stability of the Z-wave stack in SmartThings. There have always had the power cycle events. The difference is that instead of having 2-3 events per day as in the past, Iâm now seeing them 3-4 times per hour at one point on the .14 release they were occurring 9-11 times an hour.
Aside from random lag, the most serious effect has to been to mess up my locks. Iâve had random user codes on random locks, across 2 manufacturers just stop working. This behavior just began with the start of the beta and has actually caused people to be locked out of the house.
@blong Your hub is currently on 18.22 Firmware release, you are not running the beta firmware (19.x). Hopefully once you get 19.x, you can get back to us about your experience.
Thank you for the quick response! I guess I will need to move back to 100% zigbee devices for now!
Yes, I am seriously considering abandoning my $400 worth of z-wave tech due to the constant issues since moving to ST. It is very annoying that we have invested so much $$ in z-wave devices for the constant headaches that ST seems to not be able to resolve over the past 2 years. The z-wave stack, even when it was working, was unreliable and require me to rebuild devices at least 2 times over the past two years. Thanks for the response!
I am sorry about your frustration, perhaps wait till 19.x and see how that bodes with your Z-Wave setup. I am hopeful by future releases we can provide much better experience that you are having now. 19.x should be out hopefully in the next few weeks.
so I had to redo the device handler when I went v2⌠canât recall what I changed though I guess I could diff the code and tell you⌠either way, give this one a try
Wow! Whatever changes you made to this DTH work; and lightning FAST! Thanks for sharing your code, it is really nice! I am no longer experiencing any issues on my end. The ST Hub v2 is crisp and responsive now!
And, I need to come clean with @Kianoosh_Karami⌠After further research into my own WebCoRE script, I found that I was calling for a device refresh within a DO WHILE Loop with a wait time of 500 ms. This was creating a Z-Wave request overload and caused my devices to become unresponsive. I hope this can help any future âscript kiddiesâ see the err of their ways. I knew better than this! Sorry for the message in hasteâŚ
I am having a incredible frustrating experience, and from what I am reading this is the status quo with ST. I have installed ST for a client, with 69 Z-wave devices, 5 Zigbee contact sensors, 13 Virtual devices.The break down are as follows:
24 X Fibaro Dimmer 2 (Z-wave Plus)
2 X Fibaro Double Switch 2 (Z-wave Plus)
8 X Fibaro Single Switch2 (Z-wave Plus)
2 X FortrezZ MIMOlite (Z-wave)
1x Vision Dual Relay (Z-wave)
3x Monoprice Contact sensors (Z-wave)
2x Ecolink Contact sensors (Z-Wave Plus)
5x Yale smartlock (Z-Wave Plus)
21x Zooz 4in1 Multisensor (Z-Wave Plus)
I have used WebCore and have duplicated the rules in Core, to rule out any issues with WebCore, as it is not official but in beta. (I must also state that I have paused Webcore when running Core)
I have removed everything and started from scratch 5 times, I have replaced the hub with another hub now 3 times. But the issues keeps popping up.
My issues (and questions) are as follows:
But when everyone is up and there is motion it looks like this:
I have to mention that none of the pistons that is running is set to execute during the day as it is set to run only if the LUX levels are below 30 and there is motion. So it looks like it is falling over because of all the motion reports?
Yesterday we were busy adding more devices to the network, and all of a sudden the radio stopped and I could not get it back on again. I then held the reset button in for around 30seconds until the yellow led stayed solid. This reloaded the local OS and brought the radio back on.
At this point the system is responding perfect when there is no motion or no one at home, but the moment the motion starts it will respond well until something random is happening, then it would drop instructions or not get it.
4. Sometimes the app would show a device as "OFF "but indicate the accurate power drawn and the light would actually be âONâ and vice versa. This often happens when the device was turned on via a piston execution.
I have mapped the network out with the Z-Wave toolbox. all the nodes has between 5-20 neighbors, so there can not be a range issue.
Can this be a corruption in the DB, if so how can this be fixed, and why would this happen every time, or is this caused by the ST architecture?
I am pulling my hear out, and the opinion of Smartthings being the best is seriously in question.
When I send a email to support it takes between 1-2 weeks to get a response.
I would appreciate any help.
I just googled err 120 timeout and it seems that the error is in reference to a specific device.
So first remove all devices that generate err 120 and see if this helps.
See if after removing them you can do a zwave repair with no errors.
