Oh no, just stumbled on this topic. I have exactly the same issue… I opened a support case, received the following reply but this did not help. the problems instantly started after the last firmware update.
I AM SURE THIS PROBLEM IS INTRODUCED SINCE LAST FIRMWARE UPDATE
VERA: Sorry for the late answer, I wasn’t in the office
You can change the autoconfigure value again to “Use default Value” → “Configure node right now” → “Wake up the sensor” → “Wait until the device creates the children” → Change the autoconfigure to “No” again so it won’t create any additional phantom device ,
ME: I have done exactly what you described below. An I may not swear, but F. Always something with this system. Now I only have a master device and no childs at all anymore à all logic broken again. I don’t want to have vera in support mode because everytime you (not you personally) went in something else is broken. What can I do? Is this device not supported in the right way anymore? These problems arised after the latest firmware. Please help me out despite I am very annoyed by this situation (as you may imagine).
VERA: The sensor is probably trying to reconfigure for some reason, you can go to the device settings and change the autoconfigure value to “no” after that you can go to advanced–>Commands–>Reconfigure node and that should delete the phantom device, you will need to wake up the device after that as well
ME: Hello, I have included the 3 motion sensors freshly. But now on one of them I have ghost devices appering with a higher device ID. _GET_LANG(generic_sensor,sensor) 1 Device type: FGMS-001 (v3.2) What is wrong again here?
ME: It did not work despite. I have taken the bite and reincluded the devices. Thank you for the support.
VERA: I have done some work on the controller, please try to wake up the sensors again, if that doesn’t work, I’m afraid you are going to need to un-pair and re add the devices as there is not much else I can do from my end, I’m sorry if these causes you any inconvinience,
VERA: Sorry for the late answer, I was out for the weekend, Can you please re-enable the tech support access?
ME: Ok thank you. The motion sensors still don’t work… what is the problem?
VERA: I honestly don’t remember to have uploaded a backup to your controller, I just made changes to the three sensors, but either way, if something that I did revert your settings somehow I deeply apologize, on the other hand, I always make a backup before doing any change to the controllers so you should be able to recover your settings, Attached is said backup,
ME: Doorsensor seems to work, although I hade to physically “shake” it to force tamper detection and now it shows motion.
ME: So I now just woke up “Tuin V Sensor Beweging Parkeerplaats” and immediately get Can’t Detect Device.
ME: Hi and thank you for the support till so far. I will wake them in a few hours. But what happened overnight!?!?! I have added a faulty shutter switch yesterday and installed a qubinu flush shutter and changed all my scenes, logics, etc. TOOK ME A FREAKIG LOT OF TIME! And now I see this devices is gone, logic is gone and the old device (deuwi) is back? Have you placed back an old backup? I may not swear.
VERA: I have done some work on the controller, Can you please wake up the two motion sensors? I think the door sensor should be working now, but if it’s not then wake up the device as well,
ME: Thank you for the support. The Sensor HZ Deur Motion with 1% is detecting motion but says Waiting for wakeup to configure device. The other 2 do nothing. All 3 have full and new batteries.
VERA: Can you please test the devices one more time? Let me know if they are working properly now
VERA: I’ve escalated your issue to my colleagues from a higher level. Please leave Techincal Support enabled - we’ll keep you posted as soon as we have a resolution on this matter. Thank you for your understanding and patience
ME: Hi, ofcourse I have done that… not helping. Though I do see that vera sees tampering (shaking) with device…
VERA: Can you please try bringing over your sensors close to the Vera controller and waking them all up by pressing the z-wave button on the sensor really fast a couple of times? I notice one of the sensors says “Waiting for wakeup to configure device” and signals that the battery is down to 1%. Can you please replace the battery on this device and after that bring it close to the unit and wake it up as well. Let me know if the problem persists.
ME: Hello, Since last firmware update all of my 3 sensors are not working anymore. It is directly linkable to the upgrade all was fine before.FGMS-001 not working anymore in 7.29 - General Vera Discussions - Ezlo Community