New button in the Mobile App?


(Tim Slagle) #1

Look what I found in the smartapp! A replace function??


(Brian Smith) #2

I saw that the other day and couldn’t remember if it was there before. I’m glad to see it may have finally made it’s way into the app!


(Tim Slagle) #3

I was trying to find that thread and couldn’t! Lol…

Way to show me up @brianlees :stuck_out_tongue_winking_eye:

@april can you provide some insight to whether this is ready for prime time?


(Beckwith) #4

I saw it in the Windows Phone release notes. What device do you have?


(Tim Slagle) #5

iPhone. It was in the recent iOS uograde release notes too, but just showed up recently. Must of been a backend change recently.

Tried messing with it but not sure it’s fully functional yet.


(Christopher Masiello) #6

This is great. I have a z-wave wall socket that is acting flaky lately. I didn’t want to rip apart all of the smart apps that use it. Just what I need.


#7

@duncan can probably provide the best explanation but this feature allows you to swap out a Z-Wave device with another of the same type.


(Gary D) #8

Doesn’t appear in the android version… poor neglected android. :frowning:


#9

The iOS team got it in before the mobile teams paused bi-weekly releases for the big app rewrites. Our Android team is the largest mobile development team we have and I’m pretty sure we have more Android users working for SmartThings at this point than iOS.

If you haven’t seen it, this is the difference between the current build on the Play Store and the one we’re almost finished with:


(Duncan) #10

This is a special Z-Wave feature designed to be infrequently used in the situation where a device disappears, dies, or in any way becomes completely and permanently unresponsive. It allows you to replace the device with another of the same kind of device without going through the entire setup again.

When you attempt to replace a device, the hub will first try to contact the device to determine if it is actually unresponsive. This can take from a couple seconds to tens of seconds depending on several factors that the Z-Wave protocol uses to determine how long is reasonable to wait for a response. When the hub is satisfied that the device is unresponsive, it will initiate the replacement search process. Push the button on the new device or follow whatever the device’s usual procedure is to add it to the network.

Some further info:

The replacement search is like a developmentally stunted version of inclusion. It uses the same mechanism but the API has less feedback and control. From the new device’s point of view, it is just getting included – it doesn’t know that it’s getting a preowned network ID – so it must be in an excluded state and put in learn mode as if it were being included. The device network ID is the only info that links a device in the SmartThings cloud to the actual device on the network, so once the new device is included and given the failed device’s ID, all communication is effectively redirected to it without anything having to change in the cloud.

There are a couple ways this can make a mess. The protocol has no way of preventing you from replacing the device with a totally different kind of device. If you replace a switch with a motion sensor it will just confuse everything. Also, if you trick the hub into thinking the device was unresponsive – say, by unplugging it – and replace it without resetting it somehow, there will be two devices with the same ID that will both act as the same device from the hub’s and cloud’s point of view, which can have weird side effects. Sleepy devices are by default in an unresponsive state, so they can be “falsely replaced” in this way easily. If this happens, exclude both devices – the first will remove the device from the system so the second must be excluded via general device exclusion.


(Duncan) #11

Also, to be clear, this is not yet the general purpose “replace” function that @brianlees suggested that can replace any SmartThings device with another that can fill the same role. It is a specific protocol-level thing that was required for Z-Wave+ certification. We’re considering expanding it to be more general though – basically to join a new device or rejoin the same one but keep all the configuration on the cloud to avoid needing to tear down all the SmartApp connections and rebuild them.


(Tim Slagle) #12

This…

+10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000


(Beckwith) #13

I could have just used this. I had five devices that I had to re-add after becoming unresponsive. I have two to go. I’ll try to hold off till Android app gets this feature.


(Michael Langkilde) #14

It does not seem to work at all with the Aeon MultiSensor. I have tried it on two of mine and it checks and never completes it’s process. It basically deletes the multisensor. So you’ll have to delete the smartapp if there was any associated with the device and then exclude it. Then finally include the multisensor and then add the smartapp back.

I have tried it on other devices it works fine and does what it is designed to do but so far the Aeon MultiSensor does not work.


(Tim Slagle) #15

So it checks and then asks you to select a new device?


(Michael Langkilde) #16

No. It just checks and just keeps spinning the wheel. You have to close the app down then open the app back up.


(Tim Slagle) #17

Please tell me what your experience was. :smile:


(Michael Langkilde) #18

Well, I had an issue with the Jasco light switch. I pressed the button and did the check and it recognized the device and after I verified the smartapps that I have assigned to the switch still function which they do.


(Tim Slagle) #19

Ahhh ok. So its not a “replace” it button but more of a fix the association button?


(Michael Langkilde) #20

Yeah, that is what it seemed to me. I fixed the background stuff while keeping in tacked the smartapps and other settings in place.