We are working hard to make the new UI7 better and more stable than UI5. As you all know, UI7 is still in development and inevitable not everything is working as it should. “Can’t detect device” issue is one of them and we want to fix it as soon as possible, but for this we need your help too. If you are willing to help us solve this issue, please submit a ticket to our support (go to “Users & Account info/Tech Support” and click on “Contact Support” button) with the following additional information :
Tech Support access code that is displayed after clicking on “Enable” button form the same location mentioned above;
“Subject” field should be : Can’t detect device issue
Manufacturer/name/type or other information about the device with this issue;
A description for the issue, steps to reproduce;
Other additional information you consider useful;
For speeding up this process you can send us the log from your unit like this:
i) Enable Verbose Logging on your unit : run the following request in your browser : http://VERA_IP/cgi-bin/cmh/log_level.sh?command=enable&log=VERBOSE or enable “Verbose logging” check-box from “Settings/Logs”;
ii) Reproduce the issue;
iii) Run the following request in your browser : http://VERA_IP/cgi-bin/cmh/services.sh?service=rotate_logs and tell us the approximate time for this(unit time).
In fact, I was first thinking about Z-Wave devices. Several of my Z-wave devices show this error with version 1.7.388 while everything is ok using 1.5.622.
Specific devices provided by developers is another story, but my priority would be standard Z-wave devices.
I began seeing 1-2 devices reporting “Can’t Detect Device”.
So I ran a repair/heal and now almost all battary driven devices are reporting “Can’t Detect Device”.
Waking up the devices manually have no effect.
I’m running Vera3 UI7.
I’ve also tried to migrate to my new VeraEdge. I can migrate all devices, scenes etc. etc. The final step of the migration process is a heal/repair of the Z-Wave Network and after this step VeraEdge has the same error of all battery driven devices reporting “Can’t Detect Device”.
So I ran a repair/heal and now almost all battary driven devices are reporting “Can’t Detect Device”.
Waking up the devices manually have no effect.
I’m running Vera3 UI7.
I’ve also tried to migrate to my new VeraEdge. I can migrate all devices, scenes etc. etc. The final step of the migration process is a heal/repair of the Z-Wave Network and after this step VeraEdge has the same error of all battery driven devices reporting “Can’t Detect Device”.[/quote]
I had the same problem; turned out to be an antenna issue. It is worth a couple minutes disassembling your Vera 3 (under the four rubber feet are four small phillips) and checking that the Zwave antenna (the one connected to the small daughter board) is firmly attached. Don’t be afraid to pop the cable off and re-seat it.
So I ran a repair/heal and now almost all battary driven devices are reporting “Can’t Detect Device”.
Waking up the devices manually have no effect.
I’m running Vera3 UI7.
I’ve also tried to migrate to my new VeraEdge. I can migrate all devices, scenes etc. etc. The final step of the migration process is a heal/repair of the Z-Wave Network and after this step VeraEdge has the same error of all battery driven devices reporting “Can’t Detect Device”.[/quote]
I had the same problem; turned out to be an antenna issue. It is worth a couple minutes disassembling your Vera 3 (under the four rubber feet are four small phillips) and checking that the Zwave antenna (the one connected to the small daughter board) is firmly attached. Don’t be afraid to pop the cable off and re-seat it.[/quote]
Thanks for the tip. The antenne seemed fine but it gave me the idea to try and place the Vera3 in a different location in the house and that seemed to make a difference.
I had this issue after I tried to do a heal, all battery devices showing Can’t Detect Device\configure, I ended up doing a backup from a couple days back and everything went back to normal again, thinking is something to do with the heal process
VeraEdge : 1.7.906
I will do a backup then try to do a heal this weekend and see if breaks it again
[quote=“JS007, post:11, topic:184081”]I tried these options, took ten hours to run, at first it looked like ran ok, but then the battery items started showing as failed again
I get “Waiting for wakeup to configure device”
even opening and closing the door doesn’t correct it, but the state change does show in vera web gui[/quote]
So now that when I goto home.getvera.com it takes me to a MiOS screen when I login. It states it does not see my device. I have tried everything and then some to get it to work to no avail. Tech support has recently been accessing my device to help with another issue. I am getting very frustrated with vera. Why make updates when they dont work!!!??? Do you have suggestions on how to resolve my issue?
Kevin
[quote=“mcv.andrei, post:1, topic:184081”]Hi all,
We are working hard to make the new UI7 better and more stable than UI5. As you all know, UI7 is still in development and inevitable not everything is working as it should. “Can’t detect device” issue is one of them and we want to fix it as soon as possible, but for this we need your help too. If you are willing to help us solve this issue, please submit a ticket to our support (go to “Users & Account info/Tech Support” and click on “Contact Support” button) with the following additional information :
Tech Support access code that is displayed after clicking on “Enable” button form the same location mentioned above;
“Subject” field should be : Can’t detect device issue
Manufacturer/name/type or other information about the device with this issue;
A description for the issue, steps to reproduce;
Other additional information you consider useful;
For speeding up this process you can send us the log from your unit like this:
i) Enable Verbose Logging on your unit : run the following request in your browser : http://VERA_IP/cgi-bin/cmh/log_level.sh?command=enable&log=VERBOSE or enable “Verbose logging” check-box from “Settings/Logs”;
ii) Reproduce the issue;
iii) Run the following request in your browser : http://VERA_IP/cgi-bin/cmh/services.sh?service=rotate_logs and tell us the approximate time for this(unit time).
[quote=“JS007, post:13, topic:184081”]I did not, already restored from backup, it’s every battery backup device, even a test one I have about 5 foot from the vera
they work fine before heal and after restore from backup, only fail after a restore
gonna run heal again with default options, will try to remove battery and see what happens[/quote]
I went through this same issue with my battery powered devices. I found it necessary to exclude the device, then use http://:3480/data_request?id=device&action=delete&device= to make sure it was deleted, then reset the device and include it… one by one… had to rebuild a few scenes too but it was worth it.
[quote=“chuck1026, post:15, topic:184081”][quote=“JS007, post:13, topic:184081”]I did not, already restored from backup, it’s every battery backup device, even a test one I have about 5 foot from the vera
they work fine before heal and after restore from backup, only fail after a restore
gonna run heal again with default options, will try to remove battery and see what happens[/quote]
I went through this same issue with my battery powered devices. I found it necessary to exclude the device, then use http://:3480/data_request?id=device&action=delete&device= to make sure it was deleted, then reset the device and include it… one by one… had to rebuild a few scenes too but it was worth it.[/quote]
I did not do a upgrade, I rebuilt the veraedge from scratch, is weird that would have no issues before do the heal
You need to wake up the device for Vera to configure. Most of the time the devices will wake on there own. To speed it up you can wake then up manually by pressing their inclusion button.
so wasn’t aware the problem exists there too. Quite serious then.