[RESOLVED] VeraPlus "Can't Detect Device"

Ever since the UI7 upgrade, constantly some of my devices fall off the network with Vera saying, “Can’t Detect Device”. I have about 70 or 80 devices and at any point about 15 to 20 of them say, “Can’t Detect Device”. This was happening with VeraLite, so I thought maybe it was due to lack of resources, but now the same exact thing is happening with VeraPlus. For the life of me, I can’t figure out why. One hour the device is fine, and then a few hours later, it won’t detect. This was most positively NOT an issue on UI5. Is there anything I can do to get rid of this issue? The device can be old or new, it doesn’t seem to matter. Also, I don’t think it’s a mesh issue. Some of these devices have maybe about 20 neighbors associated with them, but they still fall off the network. Sometimes, they reconnect on their own the next day, and sometimes I manually have to re include them, and now with VeraPlus not having batteries, that’s even more difficult. Is anyone else experiencing this? Any solutions?


Vera Support:

“Can’t detect device” can no longer be associated with an issue in UI firmware. This is was an issue related to UI firmware and resolved a long while ago.

Second case, where this message is displayed, is on migrated setups, from older platforms (Vera3/Lite). Due to hardware limitations, battery operated devices will not have any return routes. Please consider starting fresh with the new setups, for best performance of your setup. Even in this scenario, Vera is signaling a problem with these devices. "Can’t detect device" is NOT a bug, but rather Vera’s way to tell you that there’s something wrong with a device.

Some people may say. Well, I didn’t have this issue back on UI5. You’re right, UI5 did not have a mechanism of checking and notifying the user, of any routing issues.

New situations where this message occurs, is telling you that there is an issue with that particular device.
Please open a dedicated topic with the device you are having issues with.

Thank you.

A couple of my door/window sensors, one 4 in 1 motion sensor have that message. It seems to happen overnight. I’m going to unpair and try to add them back with fingers crossed.

Sent from my SM-N920P using Tapatalk

I only have my Hue lights on one fibaro motion sensor setup but am seeing this as well (im a new to Vera since last weekend) My hue ridge was originally not being located (and the lights) and now the Fibaro motion sensor keeps popping up saying cannot detect device. The sensor was fine for the first 24/36 hours.

Well, I’ve been going around the house with two 100 foot cables and reconnecting all these disconnected devices. Last night I was down to 10 disconnected devices, but now I have 13… This VeraPlus couldn’t possibly be this unreliable. Would it make sense to just wipe out the entire network, and start fresh? I don’t wanna do that unless I know for sure it will fix these issues, because I have wayyyyyyyyyy too many scenes and apps and configuration to redo all over again.

Jumper, there is a method to clear the “Can’t Detect Device…” error. I found it on this forum but I can’t seem to recall where so I can’t reference it. It worked for me to clear some of those errors. The problem is one or two came back. Strange thing is even with those errors the devices still worked and configured. Anyway, I did a luup.set_failure (false, device_number) under Apps → Develop apps → Test Luup code. luup.set_failure (false, device_number) device_number being the actual device number you want to clear. I had 14 of those errors and got it down to 3. Try it on one device and reload to see if anything happens for you.

The grass is green, once you burn the current grass with fire, aerate, fertilize and reseed (I had the same issues and just excluded each device one at a time, looked up the re-pairing info, and paired it fresh to a fully factory reset plus – had nothing but trouble trying to migrate the current network). Still trying to get all my apps, and scenes up and re-configured, but the core of the system is working and haven’t had any devices flake out for several days now.

@lemrock, thanks for the command, I’ll give it a try to see how it goes before I wipe the entire system. The thing is that devices work one day and won’t another. Some still respond and some don’t, so it’s pretty sporadic and unstable right now.

@sortadan, that’s what I’m afraid of. It’s taken almost 4 years to put this system together and wiping it from scratch will be a massive undertaking. How many devices do you have? Maybe I should check back with you in a few days to see if you’ve experienced any hiccups, before I start redoing the whole thing. I’ve contacted support too. Maybe they’ll have a more practical solution other than a full wipeout.

I’m having the same problem with my deadbolt lock. I setup me Vera Plus fresh and the lock has been working fine for a week then tonight I get the Can’t Detect Device.

@jbfoster, is that the only device you have or do you have more? The door lock is not too far from the controller or other devices, is it?

Similar problem with both IE and Edge on Windows 10: out of 8 Schlage locks, 6 works, maybe 25 feet from Vera Edge and two plain interior walls in between (no foil insulation). Added repeaters, same…

Does the Schlage locks required Gen5 (encrypted) repeaters, or is the plain old Aeotec repeater OK? I’ve tried adding two Smart Switch 6 devices (Gen5) primarily as repeaters, still no go.

Also, the script (Vera UI7) runs very slow on my system; 10 seconds to load devices, plus?

I have my alarm, 2 door sensors, 1 appliance module, 1 lamp module, 1 micro sensor and my door lock. My door lock is about 15 feet from my controller. My door locks is the only one one with the Can’t Detect Device.

Jim

I ended up taking the day off from work yesterday, one by one went to about 70 devices, dragging a long cable around the house, and excluded every single one of them. Then I factory reset my VeraPlus (losing about 4 years worth of customization), and one by one started re including every single one of them. For a few hours, things were fine, then one device said, “Can’t Detect Device”, and now this morning, I have 5 of them saying that. This is absolutely ridiculous. This was 100% positively not an issue on UI5. Everything was rock solid. This must be happening to other people too and not just a handful of us here. Is no one else experiencing this?

I am also getting a on a few devices, its always the same ones, one id the fibaro dimmer 2 (never had any issue with any of my dimmer 1’s) had it with all my motion and door sensors until re-adding.

I’m actually just ignoring them because as soon as i send command to said problematic dimmer it works anyway.

I have the same issue on VeraPlus with all my Fibaro 2 dimmers. The dimmers works as they should. But as soon as the dimmers is operated the error message disappears, but re-appears after a couple of minutes. None of the dimmers had this issue on VeraLite UI7.

I hope they get this fixed soon. I have my deadbolt setup to notify me when my grand daughter gets home from school. I may have to go back to me Vera Lite. :‘( :’(

[url=http://forum.micasaverde.com/index.php/topic,36520.msg271657.html#msg271657]http://forum.micasaverde.com/index.php/topic,36520.msg271657.html#msg271657[/url]

Same problem here, see my post. But it is the only one I have since migration from Edge to Plus, and the devices (apart from the error message) work as they should, so I can live with this for the time being. I suppose this issue will be fixed by an update in the near future.

I also have the same problem on my Vera lite. Everything was OK with UI5. I had to migrate to UI7 for the smoke sensors and I now have 5 devices which often can’t be detected. If I reboot, the 5 devices come back on but usually fail the next night or so.
All devices are battery operated : 2 everspring motion sensors, 1 aeotec 4-in-4, 1 Fibaro smoke sensor and 1 Fibaro door sensor.

I have tried reconfiguring one device tonight and will see what happens. If this doesn’t get things fixed, I’ll try unpairing and reincluding one device…

Obviously, something is wrong with UI7.

Another day, another set of devices have fallen off the network, and so far Vera support hasn’t been very helpful. They want me to move the controller closer to some of the devices and stress test the devices that say, “can’t detect device”. To me, that’s pretty pointless. I have devices as far away as 200ft working fine and devices as close as 4 feet not working. Every day (or every few hours), a different set of devices fall on and off the network. Pretty much nothing in the house works reliably these days. It’s pretty pathetic if you ask me… Something is just very very very wrong with UI7 that they must fix.

I wonder if anyone with more than 20 or so devices has a rock solid VeraPlus (UI7 Lite, Edge) network these days? If so, how large is the area and what kind of devices do you have?

@jumper4000

For me, this issue is not related to UI7 but to VeraPlus. I migrated my Edge to Plus (backup Edge, restore to Plus) and suddenly these alerts appeared.

I have certainly more than 20 devices, and all are working (alltough some of them, 3 Fibaro dimmers and 1 XT-200 show this message) rather fine.

Regards,

Kristof.

I have been consistently getting this on two devices and currently have less than 20 devices attached to the VeraPlus. For both devices, I see this error in the logs:

ZWJob_PollNode::ReceivedFrame job job#3598 :pollnode #13 dev:68 (0x14b8c78) N:13 P:100 S:5 got FUNC_ID_APPLICATION_COMMAND_HANDLER node info expected 13 got 26 <0x773b2520>

For both devices, commands are working but the system insists that it can’t poll or communicate with the devices.