I only have 5 device but my Deadbolt was doing the same thing, Can’t Detect Device. Last week I put in a ticket and yesterday my Deadbolt decided to start working so when Tech Support got on this morning they couldn’t find anything wrong.
Jim
I have the same issue on VeraPlus with all my Fibaro 2 dimmers. I have got a response from support stating: “Please know that this has been reported to our development team and they are working on a fix patch but for the moment I don?t have a ETA”
Update from my side.
I opened a support case 27 feb:
Since latest firmware I get for all my battery operated devices “Can’t Detect Device”.
I read on the forum that more people have this problem. As well as vera plus users.
What is this problem? Devices work correct but it very annoying to have 9 “non working” devices in the dashboard.
28 feb support asked and I gave them acces to my unit.
Answer from support:
For some reasons the devices have lost connectivity with the unit and my suggestion is that you try to exclude and re-include them. To do this please go to your UI at Devices-Add devices- Generic device-Next-Next-Retry and the steps on the device for adding it and after this please add them again.
And I responded:
That the devices do work but just give this message.
I do thus think it is not related to hardware but UI7 again :-(.
In my case, I currently have 10 devices that say “can’t detect device”. Most of them don’t work, so the error is not just cosmetic, and that number fluctuates daily. For me, sometimes it’s wired devices, sometimes battery devices, sometimes devices that are 200 feet away, and sometimes devices that are 4 feet away. There’s no rhyme or reason whatsoever. I have excluded/included every single one of my 70~ devices when I received my VeraPlus thinking that would solve it. I was wrong… The only common denominator for me is UI7 and the new zwave firmware. Same thing was happening on VeraLite with the latest UI7 and now it’s worse on VeraPlus. UI5 was rock solid.
So far, support has been very unhelpful and unresponsive. I don’t entirely blame them, because to me it looks like they simply don’t have a solution. They want me to move the controller closer to some of these devices and to do stress testing, but again these devices are all over the place and different devices fall on/off the network every day.
same here, all my wave devices giving ‘cant detect device’.
Emailed & rang support but they are hiding under their desks at the moment! 
Seriously not impressed having gone from fully working Edge to a buggered Plus!
Gary
I have the same problem with one of my devices. A GE outlet. It works fine and stress tests fine, but keeps popping up with “Can’t Detect Device”. Going to try and clear the error to see what happens.
It just happened to me on my ZigBee Iris contact sensor. In the logs, no records found. 
My problem is sent to L2 support.
I am sort of glad to read this, I thought it was just me. I currently have 21 devices with that error, I had none before I migrated from Vera 3. Support suggested going to advanced in the device, commands, run a stress test, and the poll the node. That gets rid of the error. This obviously only works on the mains powered zwave devices. Problem is, a few hours later the error is back. The devices in question have 10 out of 10 in the stress test, and all work fine. I have errors on my battery powered Fibaro window sensors as well, but have not managed to clear the errors at all. I managed to get one of my motion sensors to work again with a lot of waking up and fiddling, took about 1 hour to do that. A couple of hours later it had the error again. I have told support and they have access to my Plus, but I dont know if they have done anything yet. But if this a common problem we might have a chance that they fix it soon…
This might also be related. Yesterday all of a sudden about 10 of my devices turned on without me touching anything. I turned them all off again. An hour later same again. This happened throughout the night (very annoying). This morning, when I looked at my system, turns out it was every device with an error. No othe deice did this. It must be related.
In a previous post, I was advised:
Quote from: rbakley on February 29, 2016, 05:21:38 pm
Hi Marc,Thanks for putting this list together. It will be very helpful. Just a minor suggestion, the list would be easier to read if there were three columns, Type, Device, Communication Protocol.
Thanks,
-bob
Hi Bob, a more user friendly version is coming with much more information. It is still under development, once all of the data is populated we will post the link at getvera.com.
mizzstepwhyte, it is important to keep in mind that the ZigBee network is independent from the Z-Wave network, so distance can become an issue. ZigBee is in the 2.4Mhz band which is very crowded. There are a number of apps that allow you to look at the 2.4Mhz spectrum in your home to see if something is operating on the same channel. You can see the channel that the VeraPlus is on in Settings–>ZigBee and you can look and see in your router’s settings what channel is it on, you can change both so they don’t step on each other.
I btw am using two of the GE bulbs in my office with no issues.
Sent from my SM-N920P using Tapatalk
I am having the exact same issue. My network was rock solid for over a year with only the occasional rare issue with a node. Now, my nodes come and go all day. They will be fine one minute and then error out the next. And if I run configuration on them often they will get stuck at “Getting the manufacturer”. But If I keep running it over and over again the node falls back in line again. … That is for a while longer until it (and others) go out again.
I have been running UI7 since it’s original release, so it’s not an issue with UI7 itself per se. My hypothesis is that we are getting these issues because they moved away from Vera routing to Z-wave routing. It is EXTREMELY frustrating.
I have a Vera Plus on order and I was hoping this would help resolve the problem, but from what i’m reading I guess it will not.
I updated from UI5 to UI7 last night. I’m seeing the same “Can’t Detect Device” issue on all my sensors and a wall switch. Reading the various threads, there doesn’t appear to be a solution. Considering how long UI7 has been out, this is very frustrating.
I’m now thinking about going back to UI5…
Out of curiosity is there any commonalities between the devices that are showing the “Can’t Detect Device” message. For me, I only have two devices that are showing it and nothing will get rid of it. Both are newer devices from Aeon Labs (a Smart Switch 6 and Power Strip). I never see it on devices from other manufactures and older Aeon Labs products.
Mine are different devices, though they are all battery operated and all are sensors (door, motion, etc.). At the same time, I have several door locks that are battery operated and they work fine.
To add some more data to this problem with the Vera Plus. Out of about 50 different devices I only have one device that is showing “Can’t Detect Device” but otherwise works fine. The curious thing is that it worked fine on a VeraLite running close to the latest UI7 software (probably 2 versions behind the latest). I excluded it from the Lite and reset it on the Plus It is also a battery model from Aeon Labs and is the newer Gen5 Recessed Door Sensor model ZW089-C. I do have an older Aeon Labs Door Window Sensor model DSB29 that works fine on the Plus.
I would settle for a command to run at startup to ignore the message, similar to the Invisible command to ignore child devices. Any programmers think that might be possible?
-bob
For me, when the sensors cannot be detected, the alerts do not come through (via Vera Alerts). After rebooting the device, they came back to normal. I doubt that this still stick though. I’ve read that the problem reoccurs over night.
I’ve pretty much given up on Vera. I bought myself an Aeon Labs Z-Wave Stick Gen5 and for the past several days have been evaluating HomeSeer. It’s enormously more reliable and exponentially faster than Vera. I’m not sure if it’s because I have it connected to a really fast computer or what, but everything is instant no matter how far a device is from the controller. Including/Excluding devices is also a breeze (way more efficient than Vera). It’s more expensive, but at this point I just can’t take Vera anymore. It would have been great if HomeSeer had some sort of “competitor upgrade program”. For now though at least, both my VeraLite and VeraPlus are just sitting there collecting dust. It’s a shame that with every release Vera takes a step backward. It used to be a good product.
Isn’t HomeSeer expensive? The controller is a couple hundred for the cheapest one and the Plug-ins are $29 to $49 each. I would have to pay $39 for the DSC plug-in and another $39 for the Thermostat Plug-in. That would add up very fast.
Jim
I spoke with MCV technical support today about the “Can’t Detect Device” issue. They are very aware of this issue as it is coming in everyday to them since Vera Plus hit the streets a few weeks ago. They said they are working on a patch that will be in a future release. Until then they have a workaround that clears the error. They said in most cases the device does work but the error message displays anyway. They shared with me the code. As a convenience I turned this into a scene because the error comes back on occasion. It may need to be run several times in order to clear all the errors.
for devNum, devAttr in pairs(luup.devices) do
local commfailure = luup.variable_get("urn:micasaverde-com:serviceId:HaDevice1", "CommFailure", devNum)
if (commfailure == "1") then
luup.log("Device "..devNum.." has CommFailure="..commfailure..". set it to 0")
luup.variable_set("urn:micasaverde-com:serviceId:HaDevice1", "CommFailure", "0", devNum)
luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "Reload", {}, 0)
end
end
Isn’t HomeSeer expensive? The controller is a couple hundred for the cheapest one and the Plug-ins are $29 to $49 each. I would have to pay $39 for the DSC plug-in and another $39 for the Thermostat Plug-in. That would add up very fast.
Jim[/quote]
I guess it could be expensive if you buy the top of the line Pro stuff. It can be as little as $150 if you buy the Raspberry Pi version… Also, I think twice a year they have a 50% off software sales. I heard they have them in May and November (I could be wrong). I’m still evaluating it and am only down $45 for the ZWave stick. So far, it’s leaps and bounds faster and more reliable than VeraPlus. I’m planning to buy a Voyo V2 Computer ($100), and hopping to get the software during their sale (hopefully less than $200 including the plugins I need), plus the ZWave stick that I already bought ($45), so maybe $350 for a great system. I wish I could stay with Vera, but it’s just unbearable. This is supposed to be the brain of my home automation system, but lately it’s been acting pretty psychotic and it’s getting worse and worse with every release.