There was another post about a similar problem somewhere else, where the poster couldn’t delete the phantom devices. I had a similar problem where I had 10 _Motion Sensors appear in my garage and for the life of me I couldn’t get them to go away.
The trick, if you can’t delete them, is to change the parent id value for the undeletable sensor from the controlling device to 1 so the Vera can do something with it. It’s only been about 24 hours and they haven’t come back. Hopefully, they don’t, but I wanted to post this information here so that others might see it if they had the same problem.
[quote=“ceefin, post:21, topic:190099”]There was another post about a similar problem somewhere else, where the poster couldn’t delete the phantom devices. I had a similar problem where I had 10 _Motion Sensors appear in my garage and for the life of me I couldn’t get them to go away.
The trick, if you can’t delete them, is to change the parent id value for the undeletable sensor from the controlling device to 1 so the Vera can do something with it. It’s only been about 24 hours and they haven’t come back. Hopefully, they don’t, but I wanted to post this information here so that others might see it if they had the same problem.[/quote]
I have had this issue for a long time on my Edge, after some reboots more devices get added. All have parent ID of the Aeon Labs HEM, I used to delete them but now they will not even delete. Support got rid of them but they also managed to make the HEM inoperable so I had to remove and add to the system. Now I am getting them again, so they are treating the symptoms but not the cause. I fear that if I ask for help again it will be the same outcome.
I am using vera lite UI7. I have a very simple system, 4-Aeon plugs, 2-Aeon minimotes and 1’ GE light switches. About once a week I get phantom entries. I use a back up of my conf to get rid of them, otherwise some won’t delete.
Recommendation to Vera, there is a button on the devise page to add devices, why not have a button that locks the controller from accepting any new additions. It seems like this would already be an automatic function that a device can’t be added unless the “add device” button is selected.
[quote=“mhawley, post:20, topic:190099”]I have the phantom motion sensors (and smoke sensors) problem, too. They show up as child devices of two Aeon Smart Switches (DSC06106).
This has been happening for months. The counts of the phantom devices keeps growing over time (had 13 motion sensors and 2 smoke sensors just now).
I tried the “configure node” trick of a previous poster (clicking on Devices, picking the smart switch device, then Advanced, then Commands, then “Configure node right now”. Doing this caused all the phantom devices to disappear. Thank you for that tip!
– Mike[/quote]
Following up on Mike’s fix, I had 5 motion sensors and 1 smoke sensor appear with parent IDs split between to two 4-in-1 Aeon sensors. Deleted the spare devices first time around and it wiped the temp/lux/humdity for each of the parent sensors which was annoying as I’d saved a few months worth of data against them. Tried the configure node now trick for the parent device and that cleared all the spare devices for that node as well as the temp/lux/humidty nodes, so didn’t win either way really.