Hey everyone, I’ve been dealing with a bit of a headache with my Aeon Labs Window/Door Sensor. It’s been causing my Vera Light LuaUPnP engine to crash sporadically, and I finally figured out that it’s happening whenever Vera tries to poll the sensor. The error code is 139, which I’m not entirely sure what it means, but it’s been a consistent issue.
I’ve been going through the logs, and I noticed that every time Vera tries to configure the sensor or poll it, the system reboots. Here’s a snippet of what I found in the logs:
08 06/20/12 20:00:48.112 JobHandler_LuaUPnP::AlarmCallback Ran scene:1 Thermostat Poll (automated) / timer:5MinPoll next at 1340247948 now 1340247648 <0x2b25f680>
02 06/20/12 20:00:51.343 [33;1mZW_Send_Data node 26 USING ROUTE 255.112.75.184[0m <0x2b65f680>
06 06/20/12 20:00:52.612 Device_Variable::m_szValue_set device: 28 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: [35;1mCurrentTemperature[0m was: 71 now: 71 #hooks: 2 upnp: 0 v:0xba4f48/NONE duplicate:1 <0x2b25f680>
I’ve tried resetting the sensor multiple times, updating the firmware, and even reconfiguring the Vera system, but nothing seems to resolve the issue. It’s frustrating because the sensor works fine in terms of functionality, but the constant crashes are making it unreliable.
Has anyone else encountered similar problems with Aeon Labs sensors or other Z-Wave devices causing LuaUPnP crashes? I’m curious if there’s a known fix or workaround for this. I’d really appreciate any insights or suggestions from the community on how to stabilize this setup.
On a positive note, I’ve learned a lot about troubleshooting Z-Wave devices and Vera’s inner workings through this process. It’s been a bit of a learning curve, but I’m determined to get this sorted out!
Looking forward to hearing from you all.