SmartThings Community

ST Hub/devices all work, then drop off one by one

#7

So turning off device health actually made them all appear as “active” again in Classic but doesn’t seem like anything is actually working.

It will toggle but then resets and I am checking on my cameras to see the lights haven’t actually gone on.

Rebooted hub from IDE and rebuilt Zwave (still had errors of route fails or unable to update mesh) and they all appear disconnected in the new app.

Guess I’m SOL like everyone else, apparently?

0 Likes

#8

Nope, something else is going on though. What DTH are those outlets using? Try using the DTH called Z-Wave Switch Generic if it isn’t already.

What other devices are you trying to control that aren’t working?

IT could be something really simple that ST support can help with, but we can at least triage some stuff.

This can be indicative of a bad device, chatty device, or a device not properly configured when it joined, but that’s fixable too.

0 Likes

#9

Support was no help. They recommended I replace the hub (I am going to try this on Saturday).

Here’s everything on the system. Again, pretty basic.

The outlets I believe are GE branded and htis is how they paired. The Termostats are technically CT101’s, not 100’s, regardless they are natively supported (confirmed when it was working including current state of unit, etc.)

Thank you VERY much for your help; this system is at a vacation home and not having a working automation system is distressing to me!

0 Likes

#10

After this occurred with the original install, I performed a factory re-set and repaired each device. Had a minor issue with one lock, repaired that and things were well for ~1 day. Then everything disconnected again.

FWIW there are no new devices (other than a range extender) on this network from when it was run by Iris. Never had a zwave connectivity issue, ever.

0 Likes

#11

No worries!

So looking at your devices, I see just 1 Zigbee device (the SmartSense Sensor). Is that reporting ok, like temperature?

The Ring is a cloud-to-cloud integrated solution, so let’s hold off on that for a bit. You should be able to get a live feed, and/or or motion/ring events if you’ve turned that on.

You may not need the range extender because your other mains powered zwave devices should be doing that for you. Now depending upon the home’s layout and where those other mains powered zwave devices are located, you still may want it.

I’ve got a few questions for you.

Is this a single story home?
Is the ST hub in the same general location to where you had your Iris hub?
What was the purpose of the extender for ST if things were OK with Iris?

I’d almost would like to see the extended removed, and then run several zwave repairs until routes clean up.

0 Likes

#12

Zigbee is reporting correctly and yes, that is the only Zigbee device. I intended to replace all my door sensors with them but the size and my moldings didn’t allow me to install 2. The old Iris ones refuse to pair.

Agree on Ring - not part of this discussion

Is this a single story home?

2 stories.

Is the ST hub in the same general location to where you had your Iris hub?

Exact same location.

What was the purpose of the extender for ST if things were OK with Iris?

I was concerned about the initial pairing with devices devices that are upstairs. One thermostat and one switch is upstairs (though there are more I can attempt to connect to help repeating). Bought it to cover myself, so to speak.

Everything upstairs paired fine and was fully functional for a while.

I am not at the house now but can I remove the extender via the classic app, without excluding, and still be able to properly rebuild the network?

0 Likes

#13

Technically yes via a force delete, but you’ll have a ghost device more than likely; and the extender will still keep trying to send messages to the hub.

In my opinion, I’d properly exclude it so that there’s no unwanted “noise” while trying to figure this out. I know that means getting to the house, which can be a pita when it’s far away.

You could give it a shot like you mentioned, but it could cause you more work in the end.

0 Likes

#14

As much as I’d like to resolve this remotely, I think you are 100% correct. I’ll head down this weekend and fiddle. My Ring PoE adapter is being delivered so I’ll install the stick-up cam to replace my indoor Iris.

1 Like

#15

Keep us posted!

0 Likes

(Joseph Fattizzi) #16

i have had the same issue. Things seem much better with the new app though. But it is annoying. I called customer service and no one has yet to call me back after they said they would escalate.

0 Likes

#17

How did you reconnect your devices? Re-pairing? Did they simply reconnect on their own?

0 Likes

#18

jshapnyc,

I initially struggled with the same “symptoms” you describe. Unfortunately this was at a second home 2000 miles away. I realized after I got home that I did not understand mesh networks, and smarthings methods to repair/heal these networks.

Anyway, second trip to the home I added more than another half dozen or more “repeaters” - mainly iris 3210-L’s (with both zwave and zigbee repeaters). I also thoroughly replotted the placement of all the repeaters, and performed MANY zwave network repairs until it passed without errors. Similarly I “healed” the zigbee mesh multiple times.

I now have zero drop outs.

I would invest some time and learn how to layout, and implement an stronger mesh network. A quick glance at your devices and it seems you may be lacking repeaters for your size residence.

Wifi can also interfere with the mesh. there is a ton of info around to help troubleshoot your problems. Are you using wifi with your v3 hub? If yes, check the wifi channel in your IDE for your hub and make sure your router channel is not overlapping. Also, check if your neighbors wifi might be an issue.

Start with tguac’s wiki - it is extremely helpful.

0 Likes

#19

Madisonriver, thank you so much for your response.

I am using a hardwired Ethernet connection into my router.

I will look further into stregthening the mesh of the network but will point out I never had any issues whatsoever running the same devices on Iris. Perhaps the Iris hub had a stronger radio?

I added the one Aeotec range extender out of pure caution, it seems hard to believe a fully working Zwave network would then have issues of this magnitude.

Edit to add - I believe that “always on” devices like the hardwired outlet receptacles constantly act as repeaters - if this is the case, I would have the house extremely well covered on both floors, front to back.

1 Like

(Steve Jackson, USA, Shard 1) #20

Yes, the GE outlets will act as repeaters. I don’t believe anything else on your list in your OP will repeat.

0 Likes

#21

Interestingly enough, one of the two thermostats (closet to the hub) has reconnected itself and is giving a proper reading. Haven’t fiddled with anything in several hours.

Thoughts?

0 Likes

#22

Was able to bring everything back online last night.

Turned off Device Update earlier today. Rebuilt Zwave network many times (~15). Two or three times before the thermostat came back online, the rest after. Also used the “refresh” button in the classic app which brought them back one by one.

Only concern is one door is reporting a dead battery when I’ve just changed them, feeding my suspicion that there may be some connectivity issue with that one device that has cascaded.

Plan to go to the house tomorrow night - good chance to monitor things before then.

0 Likes

#23

I would make a list and map of what devices are zwave and which are repeaters as well as which are zigbee and zigbee repeaters. Make note that the repeaters only repeat a single protocol (except for a properly setup Iris 3210-L pocketsocket). And plan the physical location of the various repeaters to maximize the mesh.

Also note that 2.4 gHz wifi can interfere with zigbee, so physical location of the hub in relation to your router AND the 2.4gHz channel and zigbee channel can result in zigbee mesh interference. I am not familiar with all of your devices and their protocols so that is why you need to make an inventory.

I believe most experienced users would support the idea that you can not have too many repeaters, and success of failure depends on a robust mesh networks (zwave AND zigbee ) if you have devices of each protocol.

0 Likes

#24

Madisonriver - I appreciate and understand the “never too many” approach.

However, given that the system worked perfectly under Iris, is there any logical reason to assume that all of a sudden using ST, the system would fail for that reason?

The only change would be the hub and its own protocols.

0 Likes

#25

I can empathize. Bottom line is you now have a different hub, I am unfamiliar with the Iris hub, obviously they aren’t identical in construction and implementation. It should be in bold lettering that this is not "plug and play ".

All I can add is I went through your exact same issues, various sensors and devices would drop off, reappear and eventually drop off for good. I’m 2000 plus miles away so I had months to think about it and research what I had done incorrectly between infrequent visits. I did a lot of reading here, and was able to diagnose what I had previously overlooked, in my case , a weak and improperly deployed mesh networks.

0 Likes

#26

Happy to report that, and at the risk of jinxing myself, have been fully operational since Sunday. No dropouts since replacing some door batteries (that I think were originally drained because of zwave malfunction).

Only significant changes were turning off device health and rebuilding the zwave network many many times.

Fingers crossed we continue operating!

1 Like