I’ve just bought a new Powermax complete with RS232 and connected up to my vera lite running the latest 1.5.622 firmware.
Vera appeared to connect and see the panel but took some time to pick up the zones and create them. It then started to show Powermax Alarm Panel: Startup Lua Failed.
Having read some of the previous posts I suspected the old prolific serial adapter i used so purchased a new FTDI adaptor. After clearing the CommExceptions field it appeared to connect but is now showing Startup Lua failed again.
When it does appear to to be connecting i’m not seeing the zone status updates, or it’s incredibly delayed when it does. How quickly should vera update with zone status changes?
I’ve attached my LuaUPnP file, I’d be very grateful for any assistance
@Gjones: sorry to hear it is not running smoothly.
From the log file you posted I can see the following.01 03/13/13
21:35:12.346 LuaInterface::CallFunction_Startup-1 device 53 function
startup failed [string "module("L_Powermax", package.seeall)..."]:732:
bad argument #2 to 'tonumber' (base out of range) <0x2b549680>
Once there is a communication exception the time that this happens is captured in the variable ‘CommLastException’. Apparently the value in this variable is now not a number, which is very change…
Please take the following steps.
[ul][li]Make sure plugin debug logging is on[/li]
[li]Let me know what the values in the variables ‘CommExceptions’ and ‘CommLastException’ are[/li]
[li]Clear both variables (‘CommExceptions’ and ‘CommLastException’)[/li]
[li]Save (and thus Reload)[/li]
[li]Wait for the plugin startup to finish (or for a next reload in case of an error)[/li]
[li]Send the log file to ‘vera.powermax atgmail.com’[/li]
[li]Set the Settings option to ‘Force Standard mode’[/li][/ul]
We first need to figure out why you get the communication errors. Hopefully there is a clue in the LuaUPnP.log file. Communication should go OK if we use the Standard mode for the moment.
I’m getting the same error, could you give me a hint when the new code will be available for download.
LuaInterface::CallFunction_Startup-1 device 65 function startup failed [string "module("L_Powermax", package.seeall)..."]:732: bad argument #2 to 'tonumber' (base out of range) <0x2b935680>
@Hutre: don’t know if is the same issue why the startup fails. To check please send the LuaUPnP.log file. The zone name fix (i.e. if you are using zone types ‘Home Delay’, ‘Temperature’ or ‘Outdoor’) is available as r66 in the trunk.
I ahve been running Vera lIte in a happy cooperation with the Powermax Pro for 1 year. It has been working as a dream. But after the Powermax Plugin update 1.0 I have big problem.
I get the message:
Powermax Alarm Panel[103] : Startup Lua Failed
Actually if I uninstall and install it work for some hours. That is that I can Arm or Disarm my Powermax from Vera. But after some hours I get the Startup Lua Fail. I dont know what to do except reinstall all the time which is very fustrating. Please would anybody give me a hint or a little support.
brds
Jorn
After using it successfully for weeks I’ve broken it. I tried to enroll a hardwired zone 30 and set it to delay 1. This seems to have caused the same ‘Startup Lua Failed’ message.
Does the pluggin support hard wired zones?
Even worse I have reverted all of the settings on the panel for zone 30 and still get ‘Startup Lua failed’
Clearing both variables (‘CommExceptions’ and ‘CommLastException’) allows connection again but commands are very delayed getting to the panel and sensor status us not updated in vera.
@Gjones: please follow the steps of reply 1 (so please send me the logs). I have found an issue with wired zones in the meantime, but they should not lead to the plugin crashing as far as I know.
I am the proud new owner of a Vera Lite and Powermax Complete security system. Everything looked like it was working beautifully until I experienced the same symptoms as described here - over time I get the error Startup Lua Failed, all sensors vanish and panel stops responding through Vera.
Clearing the 2 variables allows reconnection, everything is happy again until eventually it all goes bad again
I would like to follow your steps but being a noob to the system I’m not sure the best method of getting to the logs or the process of updating files successfully from the trunk. I have tried uploading them but nothing seemed to change.
Sorry for being so dumb - I’m digging through the threads and learning as quickly as possible
@PlowmanG: sorry to hear about the issues you have. Sensors vanishing is not something I recognize, so I’m curious to know what is going on.
Have a look at the introduction topic. This has some links to how to get the debug logs. Another option is to use r67 from the trunk. This has the possibility to get the log file via the browser. Use http://<vera_ip>/port_3480/data_request?id=lr_GetLuaLogFile.
Unfortunatly I’ve got the same problem. I’m still in the progress of programming the Powermax and Vera so maybe that could give some problems? I did the procedure of the first post and most of the time it works for a while, but at some point I get the startup failure again. I ordered the FTDI adapter, but for now I’m still using the my old prolific adapter.
Where can I find the Lua log file to send you via email? Thanks in advance.
The links on how to obtain the logs are introduction topic (you read that, right?). Try to install version 1.1 from the trunk to see if it fixes your issue. That version also creates a ‘crash’ file in case the plugin needs to restart. You can download that file through the URL http://<vera_ip>/port_3480/data_request?id=lr_GetCrashLogFile123 (where <vera_ip> is your vera’s IP address and 123 is the device id of the PowerMax Panel). With “http://<vera_ip>/port_3480/data_request?id=lr_GetLuaLogFile” you can download the LuaUPnP.log file.
I don’t know what’s happening but suddenly I systematically get a startup error !
I touch nothing with the panel and the plugin.
Here is the error I get in the logs:
50 05/18/13 13:12:42.351 luup_log:160: POWERMAX: loading library L_Powermax... <0x2c08f680>
50 05/18/13 13:12:42.456 luup_log:160: POWERMAX: library L_Powermax loaded __LEAK__ this:106496 start:413696 to 0x1475000 <0x2c08f680>
01 05/18/13 13:12:42.457 LuaInterface::CallFunction_Startup-1 device 160 function startup failed [string "module("L_Powermax", package.seeall)..."]:732: bad argument #2 to 'tonumber' (base out of range) <0x2c08f680>
01 05/18/13 13:12:42.458 LuImplementation::StartLua running startup code for 160 I_Powermax.xml failed <0x2c08f680>
Ok, I cleared both variables ‘CommExceptions’ and ‘CommLastException’ and then reload, and the problem is now fixed.
For info, my ‘CommExceptions’ value was “4”.
@lolodomo: looks like you are using version 1.0, so it will be hard to find the cause. If you are using version 1.1, then a ‘powermax_crash’ log file should be created. This should contain a hint to why the plugin had to restart 4 times (after which it gives up and does not start anymore). You can also retrieve the file via http://<vera_ip>/port_3480/data_request?id=lr_GetCrashLogFile160.
