Help: error in lua for scenes and events at boot.

Plugins & Plugin Development General Plugin Discussion
#1

Hi

I OCASIONALLY, so only now and then, i get a message in the blue message-bar declaring: error in lua for scenes and events when the lua has rebooted
How is it possible this does not happen each time… reloading thye lua should be the same every time right?
Can find somewhere what’s causing this?

Thanks!

#2

In my own adventures with Vera plugins I’ve noticed that the LUA vm can fail at seemingly random times. The only way to really know for sure is to log in and look at the log files :confused:

#3

I have the same problem. I can’t figure out what’s wrong since I only get this error randomly. To fix it I reload the lua engine - sometimes a couple of times - and then the error disappear.

Then my vera works fine in a period but suddenly the error comes back without anything has changed. And then all of my scenes are “broken” and won’t work correctly until I have done the above fix.

If anyone have a solution - please post.

#4

Hi all,

Can you fill out the form below and send us a trouble ticket when get this error once again. Also please send me an email with the ticket number and I will ask my colleagues form CC to prioritize it and take the logs from your units.

http://support.getvera.com/customer/portal/emails/new

Be sure to include your Vera unit serial number and the tech support access code. You can enable it by going to Settings > Tech Support and then clicking on the Enable button at the bottom of the page.

Thanks,

  • Andrei -
#5

Thanks

#6

Did anyone find the cause of this ‘error in lua for scenes and events’ issue?

#7

+1 looking for an answer. I see it every couple of days… depending on when I look as Luup crashes every 2 hours.

#8

+2 The Tech Support Team can’t figure it out… If it was coding it wouldn’t be random. What apps are you running?
My list is fairly lengthy… but I can post later.

#9

I have the same problem …

#10

Hi,

This is very likely to be caused by some coding error in one of your scenes. When luup gets reloaded it checks if any scene trigger is true and it will try to run the code. As the trigger statuses will vary from one restart to an other you will see these come and go.

Check you scenes LUA code and especially any dependencies it may have on other devices. Maybe you try to get the status of a device that has not fully initialized yet giving the error. Not simple to find, but there will be something in there.

Good luck with finding your needle.

Cheers Rene

#11

[quote=“reneboer, post:10, topic:189467”]Hi,

This is very likely to be caused by some coding error in one of your scenes. When luup gets reloaded it checks if any scene trigger is true and it will try to run the code. As the trigger statuses will vary from one restart to an other you will see these come and go.

Check you scenes LUA code and especially any dependencies it may have on other devices. Maybe you try to get the status of a device that has not fully initialized yet giving the error. Not simple to find, but there will be something in there.

Good luck with finding your needle.

Cheers Rene[/quote]

I was experiencing what Rene mentioned here and added a delay to load my custom code. seems that now whenever i restart or reload LUA, that error is gone. not sure if you are loading custom code, but this is all i did in my startup code:

[code]function startUp()
sebbyCode = require(“sebbyLuaCode”)
end

luup.call_delay(“startUp”, 20, “”)[/code]

#12

I think the problem is actually on the Vera side - I get the error report occasionally and if I check in /var/log/cmh for the Lua log, there is always errors relating to Sunrise / Sunset:

02 05/16/16 13:42:22.465 GetSunriseSunset error#1 sunrise: 1463285615/2016-05-15 05:13:35 sunset: 1463341770/2016-05-15 20:49:30 midnight: 1463353200/10076508 <0x776f6520>

I only started getting the error when I added a couple of scenes to switch the house mode which required use of the sunrise / sunset trigger.

Hopefully, if others can confirm then MCV can be pointed in the right direction to fix the issue.

#13

The problem is that Vera seems to seriously lack error reporting… so without decoding the log files it is impossible to know what the problem is. I get this problem all the time… reboots fix it sometimes. Right now I’m fighting an issue where I made a simple and small change to PLEG and it throwing this error every single time… and PLEG logic is not functioning properly now.