Vera Edge mysteriously added several sensors

I have a Vera Edge that I bought in July along with 1 camera, 2 plugs, and 5 light switches. I had a Schlage door lock already, and 1 foscam camera. I have everything up and running and was becoming pretty familiar with the basics.

I go on vacation and come back and found that some how on my dashboard there are several motion sensors, 1 smoke alarm, and 1 door and window sensor.

I did not add these, nor do I own any of these sensors. I try to delete them, but they wont delete. I get a message saying the command was sent, but the sensors never leave the device list. I am also starting to get emails and text messages from one kf the motion sensors.

Any help on what is going on, and gow to fix it would be greatly appreciated.

UI7 Seems to have issues with randomly adding extra controllers. From installing a Qubino flush wall thermostat, it started adding motion sensor controllers (I now show 9!!) and from a Fibaro 2x Relay, it added a random “scene controller.” It doesn’t impact actually system function but it makes the UI a mess and hiding them is just a temporary hack. Hopefully they will fix.

That also happened to me a couple of times but unlike most people I was actually able to delete the devices after a few attempts. So you may want to try a few times to ride them from the UI, it may actually work.

Yeah - they just come back. I notified Vera support which seemed surprised to learn of this issue even though as far as I can tell it’s been around for a few months on the forums.

Yesterday night I had the same problem.
Three sensors have been added. Two motion sensors and one smoke sensor.
This happened while I was trying to add to the network a new Aeon minimote (but I did not succeed).
I couldn’t remove them. So I restored an old backup.

I had the same problem after including a smart energy switch by Aeon Labs. I had a smoke detector, (2) motion sensors, and a glass breakage sensor show up unexpectedly. I am running on the UI7. I went into devices, clicked on the arrow to the right of the ghost device. Then went to the Advanced tab. Scroll down to the id_parent field and entered 1, (it will probably have the device number of another device that was added when these ghost devices showed up) this makes the ghost device controllable by the Vera. Then click outside of the field to save the changes. I was then able to delete the device by again clicking the arrow to the right of the ghost device and going to the bottom of the page and selecting Delete Device and follow the prompts. It will ask you to try excluding the device instead of deleting it but you can’t since it is a ghost device. Just go ahead and delete it. It worked for me, I hope this helps

Thanks this really works and allows you to delete the “ghost” devices.

I had a Smoke Sensor and 2x Motion sensors just appear in my UI for seemingly no reason.

Their id_parent field had number 75 in it. Device #75 is a Fibaro Roller Shutter module.

Hope they don’t come back anyway’s.

For the record I am on a Vera Edge UI7 version 1.7.1598 which as of writing is the latest firmware.

This way doesnt seem to work for me. As soon as I delete one ghost device, its just creates a new one with the next number in line. I probably have 20, at least, ghost devices. And the Vera is acting slow and annoying more often then I am willing to accept.

Have the same problem, :frowning:

Sent from my iPhone 6 using Tapatalk

Just thinking out of the box…
As a workaround I created a room 999_Invisible.
Map all devices that I dont want to it, and hide the room in VeraMate.

PS I do agree it should be fixed by Vera. ;D

January 3rd, 2017
I have a Vera Plus with the same issue reported here. Extra motion sensors created with a id_parent of 71.

I’m not sure what firmware they were created in, but I updated the firmware to the latest - 1.7.2414 - and I was able to delete the sensors.
I’ll update the reply if they come back.

Hi there,

This was an issue present in one of the older firmware. As paulstephenson003 mentioned, the latest official firmware, will not only stop these devices being created, but it will also let you delete them right from the UI.

Suddenly I see that most probably in the last week (I look into Vera often) I have 3 extra motion sensors as childs fro my EZMotion+ device. Can’t delete them.

Seems this problem has not been addressed correctly in the last firmware update then?

Sender best way to clear it up is restore a back up before they appeared. (You should not need to restore the z-wave mesh). Haven’t seen many complaints of this in a while so maybe it is “mostly fixed” :grin:

Thanks for the tip. But practically not possible since I dont know exactly when they appeared. And I did a lot of changes last week…

For me Ghost devices appeared again! latest firmware on my Veralite. These are motion sensors from Aeotec 4 in 1. asked support to help me to resolve this, they deleted all my 4 in 1 sensors… I tried to set parent_id to 1 and was able to delete it but re-appeared just 10 seconds after…
i’ve seen in wiki that there is an NoChildren parameter, where can I activate this? http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions

[quote=“Sender, post:13, topic:188521”]Suddenly I see that most probably in the last week (I look into Vera often) I have 3 extra motion sensors as childs fro my EZMotion+ device. Can’t delete them.

Seems this problem has not been addressed correctly in the last firmware update then?[/quote]

Hi, issue is still present with latest firmware on Veralite UI7.

[quote=“Sorin, post:12, topic:188521”]Hi there,

This was an issue present in one of the older firmware. As paulstephenson003 mentioned, the latest official firmware, will not only stop these devices being created, but it will also let you delete them right from the UI.[/quote]

Wrong.

The LATEST firmware still creates “ghost” devices with no category or sub-category so they are hidden from the UI. However they are created and created at RANDOM.

Example Device Issue:
I have several devices that are “supported” per the web site, but not completely when you look into it. Example the NYCE Motion sensors all have temp/humidity capabilities. Vera does NOT support those so devices are not created. However every now and again at random after a luup reload a ghost device is created as a child of the NYCE sensor but with no name or category/sub-category and it’s pulling data and can be seen through the http api.

I’m speculating that if you have devices that Vera doesn’t know how to deal with then it’s not gracefully creating devices, or it’s doing like it does for my sensors and creating the device and HIDING it by not assigning a name or category/sub-category to the device.