When a device is used in a rule and then breaks due to the device being removed from HE it shows Broken.
What would be really helpful is if it showed Broken(Old Device Name) this would really help when re setting rules up.
Any way, just an idea.....
1 Like
Could be useful, but I'm guessing the name isn't available at that point - probably just a device ID that you and the rule couldn't make correspond to anything (which is why the rule is broken).
1 Like
I think it’s best to change the automations to the new device before removing the old device. To eliminate the issue, remove or re-task automations before deleting the device.
1 Like
With webCoRE, when a device is removed while still resident in a piston, webCoRE seems to allocate a random number for the device. So in affect the piston is broken as the device does not exist, but all you need to do is open the piston and allocate a new device in place of the random number.
Not sure if this could be something that RM could do/be implemented.
OR
If you are manually deleting a device, heed the warning that is given. 
Not always possible on the rare occasion a device goes AWOL or removed by mistake by me.
That’s correct for when things are working however when things go wrong and you need to delete and re add them there’s no choice
No, you can actually change the device ID if it’s broken, add the device back, and remove the bad device after moving the automations.
1 Like
Ironically, the reason it's broken is because the device was taken away, so it doesn't know its name. RM doesn't have the device id either -- it's all gone, and done so behind RM's back. It doesn't even know it's gone until it tries to render the list of actions and finds a hole where there should be a device. This would be true of any app, unless apps kept redundant names of devices around just to deal with this situation (not something I'd see us wanting to do).
The only circumstance where this can't be handled prior to device removal is accidental device removal, especially one caused by Z-Wave Exclusion. However, the most common actual cause of this is simply ignoring the warning given that the device is in use. Heed the warning, follow the link, fix the app, and then, when all in use apps have been fixed, and only then, remove the device.
3 Likes
Sadly fixing the app for me required removing it and reinstating it. You are correct that if your way is followed it works but there are situations when this isn't possible and things are broken with no reference point. I'm now deleting rules as I cant follow them for which devices they used/times/delays etc which is fairly annoying.
Anyway just an idea
Could you describe such a situation?
Whenever I have removed a device, I’ve been prompted to remove it from all the apps that use it, so I’m curious to learn when that doesn’t happen.
1 Like
For some reason the hue app stopped being able to control the lights properly, not matter what i tried they wouldn't work there was probably a better way of resolving it however i didnt know it. removing the app then reinstalling it again did the trick but that's where i then saw the dreaded broken rules
1 Like
