Recently started to receive the dreaded “Startup Lua Failed” error message from my PLEG plugin. I have tried to reinstall the PLEG (I pressed the backup option before the problems started but now I do not know how to restore, I just get a “Command failed:ERROR: Device not ready”) but still get the same error.
I understand you need to view the log to find the cause? I do not really know how to find the log? If I chose “Debug in Standalone File” under Control → Log → Current Debug Status I get this in the pop-up window:
File not found: /var/log/cmh/PLEG-252.logdata
Where FileSpec is relative to /tmp/log/cmh or a full spec.
N is # of Lines. If N from start else if -N from end.
GrepSepc is used to filter the file.
If I choose “Debug in Vera Log file” I get this in the pop-up window:
For the Startup LUA … you need to put the Log in the Vera Log (Your last option) … then restart Vera.
Then post the log … I (or others) will interpret it … It’s not something a casual user will need or want to know about.
Richard, this is an issue. I beg you… remove the check. It is buggy and causes failures frequently. Only a power-down fixes it … how many months are we supposed to endure this? At what point do you allow those of us having the problem to get code that does not cause us constant failures?
I will need to see the log files … I need to fix this … If I remove the check it is basically unlicensed.
Make sure the Debug to Vera Log File is set to one that is having the problem. If they are all having the problem … the lowest device ID would be preferred.
I need to see the entire LOG from restart to the problem …
Just want to confirm I’m having issues with the registration system on PLEG too.
My home has been working sporadically ever since the registration system was introduced in PLEG and it’s been quite frustrating. MCV issues pale in comparison to the stability of PLEG post registration module. I think Richard has taken a deaf ear to my complaints in the PL License Thread (which is the second longest thread on the PL forum). I’m glad others share my frustration.
However, this is the risk you take when you use unsupported, undocumented products PLEG to “save you time”. The source code is even encrypted, so you can’t see what it’s doing or fix it yourself.
I understand Richard does a lot for a little…I do respect his work and talent…and that is why I switched my whole home to use PLEG in January. However, this change has made thousands or hours of research and programming to a registration failure every other day. I think some focus on making the registration rock solid would go a long way to build trust in the solution…and hopefully long term profits. I wouldn’t mind paying more for a version without registration, at least until there is 6+ months of no registration failures.
Don?t know how to update, but I uninstalled the PLC and re-installed it. That seems to have worked. I lost my settings of the PLEG though. I assume I can?t restore because it is a new instance after the reinstall.
Thank you RichardTSchaefer for the help.
I assume the problems started with an automatic update of either the PLC or PLEG. Because my home automation now relies on PLEG instead of Veras built-in scenes it seems risky to let the plugins auto update when it could break a configuration that works properly.