Replacing Faulty Z Wave Device - Is there an easier way?

[johnwill1]

I have a C7. I need to replace a faulty device today and this is always a bit of a pain.

First I'll exclude the old device and include the new device which is easy enough but afterwards...

I need to go into each rule that the device is in and delete the "broken action" line and add them back in referencing the new device. Then I'll need to authorise the new device to SharpTools and edit up to 6 dashboards to replace the old device with the new.

In this instance the new device is not the same model. I'm replacing a Fibaro FGS-223 with a Fibaro FGS-224. Both are added as a single device but use 2 child devices.

Is there an easier less time consuming way to replace it with less work? Thanks

[Inge_Jones]

Often requested.

[aaiyar]

If the device has failed, then make use of the zwave replace function as described:

Reconnect known device

The C-7 has the ability to replace ZWave devices. Zigbee have factory set hard coded Node Numbers. They never change and thus once its paired to a hub, its identity is known. This allows it to be a "device previously known." to the hub, and get dropped right back into that known spot. However, Zigbee doesn't have a replace... if the device actually dies and you buy a replacement, the device will pair as a never-before-seen. On the ZWave Details page devices is a stack of buttons for each devic…

[johnwill1]

It hasn't actually failed from a z wave perspective. One of the 2 relay outputs has welded on. So it is currently online. I'll take look at the linked post - I can power down the device so that it appears to have failed...

[johnwill1]

So looking at that article @aaiyar my procedure should be:

1 - Power up and exclude the new device to ensure it is defaulted
2 - Power down the existing device, then on the Z wave details page click the replace option once available
3 - Triple click the b button on the new device and it should include in place of the old one

Does that sound right?

[aaiyar]

@johnwill1

Does that sound right?

Yup.

[johnwill1]

Perfect. I should get the replacement device today and will try that method - thanks for your help.

[johnwill1]

Ok - device replaced. It sort of worked, but I've ended up with just as much work....

Using the replace option, the FGS-224 was included in place of the defective FGS-223. It correctly included without security (I wasn't sure how it would handle that) and it correctly selected the appropriate (different) drivers for both the parent and child devices.

Unfortunately even after a configure, the child devices would not operate so they had to be deleted and created again in the parent device preference panel - not so bad I thought..

...however that has caused the rules to be broken and deleted the items from all SharpTools dashboards. When I authorised the two "new" child devices in the Hubitat SharpTools app it deleted EVERY device from every dashboard! I couldn't get this working again using the app and had to re authorise the hub via the SharpTools web page to get the devices to display again.

Panic over but blood pressure increased substantially. I'll now spend another hour or so trying to get things back how they were.

[cgmckeever]

@aaiyar I thought this is what the device network id is for all the devices? It would be nice if all rules/etc were just based off that Hub controlled id. I must have it mixed up