Vera restarting - Ghost devices?


I have been getting occasional Vera restarts. When I caught one this morning, I noticed this immediately preceding the restart:

06 10/04/14 7:09:59.251 Device_Variable::m_szValue_set device: 145 service: urn:micasaverde-com:serviceId:HaDevice1 variable: ^[[35;1mLastUpdate^[[0m was: 07:09:29 now: 07:09:59 #hooks: 0 upnp: 0
01 10/04/14 7:10:23.009 ^[[31;1mFailed to get lock(0xf5e6e4) ThreadedClass: …/ZWave/ZWaveJobHandler.cpp:235 last used …/ZWave/ZWaveJobHandler.cpp:825 first used …/ZWave/ZWaveJobHandler.cpp:825
02 10/04/14 7:10:23.013 ^[[33;1mDumping 32 locks^[[0m <0x2b732000>

When I listed all my devices, 145 does not exist. I wonder if it is possible for deleted devices to leave artefacts behind that cause this? Could it be I am trying to refer to an incorrect device ID in one of my PLEG devices? It seems to detect when devices are deleted, but wondering if I may have missed something and its trying to find a device that no longer exists?

Any advice appreciated.


This is not a “ghost device”. In this case 145 is a service, I don’t know which. The device is HaDevice1, the Vera itself.

The actual issue, if any, in this log snippet is the Failed to get lock(0xf5e6e4) ThreadedClass: …/ZWave/ZWaveJobHandler.cpp My guess would be that you have a poorly behaved plugin, bad PLEG recipe, or some bad Lua code in a scene.