Replacing a motion sensor

#1

Want to replace a Bosch motion sensor with monoprice sensor for cosmetic reasons. After replacing, do I have to open every piston which has Bosch motion sensor and update it with monoprice motion sensor OR is there a better way?

#2

Yes you will have to do this for each piston.

You could use device variables instead. But this would still require you go through everything and change all areas where the devices are to be updated with a variable. Then you would only need to sit a variable instead of each spot in the code.

#3

if you swap names, that is first rename bosch to new name then rename monoprice to bosch’s old name you may not need to change any of the pistons.

if you try it, let me know if it worked. :slight_smile:

#4

This would actually be a great feature, @ady624 when they put Florida back together, is there any chance to build in a replace option? Say in settings, create a replace all feature, user opens the future, select the old device, select the new device, and webcore simply overrides the old device with the new device in all pistons. It would be great for situations exactly like this.

An exception could be written in that if the old device does not have a matching condition to what is being replaced, it could either be set to fail on replacing in that piston, or replace it anyway but deselect the attribute. Any piston where replace all is used where all conditions do not match, the piston could be paused and something like it exclamation flag put next to it saying requires user attention

I moved this thread to the feature suggestion category

#5

That won’t work… change a name in ST and webCoRE keeps in sync.

If they were Zigbee devices you could probably use the replace function baked into ST.

With Zwave you’re stuck with trawling through every line of every piston I’m afraid :sob:

#6

While that is possible, to swap a like-for-like device, pistons ar eindicidually keeping track of devices they use so changing a device implies waking up all pistons to go through their devices and do the swap. Which is prone to 20s timeout depending on how many pistons you have. Unless I use a sendLocationEvent… hmmm…

#7

not sure, but I seem to remember doing something like this before. the steps may have been:

  1. delete old device from ST
  2. add new device to ST with same name as deleted old device.

the devices had the same capabilities, might have been ZigBee devices. thought the pistons were all fine afterwards without any change.

got to try it again sometime.

#8

do the pistons individually track the device hardware id or those are resolved on reference?

#9

How about a search option? Maybe you can search for a sensor and all the pistons which are using that sensor will show up as search results.

#10

What I have done in the past with zigbee devices is this.
Connect up the new zigbee device.
Look in the device and note the zigbee Id.
With the old zigbee, amend it to the new devices zigbee Id.
Delete the newly connected device.
The old device is now effectively the new device.

BTW. This assumes you are changing like for like devices.

Global Replace Feature