Reactor-Editor / Reactor-ui-Status Errors

[Tarkus]

Yeah, scenes run but the Vera goes haywire.

[Tarkus]

[toggledbits]

If that's the case, it probably goes haywire when the scene are run from the Vera UI as well, since MSR and the Vera UI use the same mechanism to start the scene. In fact, pretty much everything MSR does with Vera is enabled by the same mechanisms that the Vera UI (and Imperihome, etc.) use. There's nothing MSR can do to mess up those scenes. It just asks that they run.

I would start at the Vera UI scenes tab for troubleshooting. Lua code on Vera can be very particular, as you know. Long delays will cause deadlocks and reloads. If you're opening sockets or making HTTP requests without appropriate timeouts and error handling, you're going to get into trouble. If you open sockets or files and are not taking steps to close them properly in all conditions, even when errors occur, you're going to exhaust limited resource handles and cause a reload or even a reboot. You really need to understand and know what you're doing, and unfortunately, there's just a lot of bad Lua copy-pasta on the forums.

[cw-kid]

@toggledbits said in Running Lua Code ? And watching device properties?:

How are you running the scene?

I opened a PR with screen shot.

https://reactor.toggledbits.com/mantisbt/view.php?id=80

[cw-kid]

Well least you can run the Vera scenes I cannot at the moment.

I see these in the MSR log:

VeraController:ERR [VeraController:performOnEntity] action request failed
VeraController:CRIT Error: Request failed: 401 Error

[Tarkus]

I understand and I will try to test keeping MSR out of the equation. Having said that the same lua in Vera reactor did not cause any issues. What i will do is take a segmented approach and not try to finish the complete MSR project at once. If I hit trouble i will try to remedy as well as I can. I am not a coder, not great at understanding code syntax. I am good at the logical part or reactor just not lua and coding in general. I have no idea whether my code is up to par or not. It was created by copying and pasting peoples samples from the forums with some modification that I picked up from online tutorials etc. All i know is is seems to work in Vera Reactor. My Vera reactor setup is quite complex and there is a lot going on. Is running a scene outside of reactor a true test absent of the other things reactor is doing concurrent to running a scene via Vera reactor or MSR? I will try with whatever skills I can muster up but when it comes down to it and speaking of Vera Reactor and my conditional logic needs if it isn't broken dont' fix it or at least dont go crazy trying to.

[kfxo]

@tarkus said in Running Lua Code ? And watching device properties?:

In preliminary testing the big issue I see with lua in Vera scenes is stability. I tried moving some of my lua into scenes and invoking the scenes thru MSR and everything just became real unstable with Luup restarts.

I think you already discovered the problem. Running the lua through scenes is probably not a good idea. Have you attempted what was suggested by @therealdb in this thread defining a library at startup and calling your lua through that? IMO this is the correct way to do it.

[toggledbits]

@cw-kid said in Running Lua Code ? And watching device properties?:

VeraController:ERR [VeraController:performOnEntity] action request failed
VeraController:CRIT Error: Request failed: 401 Error

Have you looked at the Vera log corresponding to the time to see what it's logging? Also what happens when you run it via the Vera UI?

[Tarkus]

@kfxo I did scan thru that approach. I will definitely try to implement this before proceeding with anything else. Thanks

[cw-kid]

@toggledbits

luvd_get_info_data_request starting /data_request?SceneNum=null&DeviceNum=86&id=action&serviceId=urn%3Amicasaverde-com%3AserviceId%3AHomeAutomationGateway1&action=RunScene&output_format=json&_r=1614868227818 pMem 0x3473000/54996992 diff: 39190528 <0x6cd27520>
08	03/04/21 14:30:27.829	JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x6cd27520>
08	03/04/21 14:30:27.829	JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=null <0x6cd27520>
08	03/04/21 14:30:27.829	JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=86 <0x6cd27520>
08	03/04/21 14:30:27.830	JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x6cd27520>
08	03/04/21 14:30:27.830	JobHandler_LuaUPnP::HandleActionRequest argument action=RunScene <0x6cd27520>
08	03/04/21 14:30:27.831	JobHandler_LuaUPnP::HandleActionRequest argument _r=1614868227818 <0x6cd27520>
02	03/04/21 14:30:27.831	JobHandler_LuaUPnP::RunAction device -1 action urn:micasaverde-com:serviceId:HomeAutomationGateway1/RunScene failed with 401/Invalid Scene <0x6cd27520>

Strange it says its an invalid scene.

"Fan On" is scene number 86 in Vera and that is the scene I selected to run in my "Set Reaction" run script.

If I run the "Fan On" scene actually in Vera on the UI7 web GUI it works the scene runs OK.

Why does it have a device number and scene number is null ?

SceneNum=null&DeviceNum=86

[cw-kid]

@Tarkus

John, what version of MSR are you currently running? 0.1.21062 ?

Thanks

[toggledbits]

@tarkus That helps. Open a PR. The scene ID isn't being passed correctly. That's a quick fix you can do in place in a minute. I'll post what you need on the PR.

[cw-kid]

@toggledbits said in Running Lua Code ? And watching device properties?:

The scene ID isn't being passed correctly

You talking to me ?

There is a PR open already.

https://reactor.toggledbits.com/mantisbt/view.php?id=80

[Tarkus]

@cw-kid yes 0.1.21062 but it seems that my scenes are not getting invoked by MSR today as well. I did test when I initially installed the other day and they did work.

[cw-kid]

@tarkus Right I see, we are both in the same boat then. Its a bug on todays MSR build.

Fingers crossed for a hot fix !

[toggledbits]

Both, and yes, I see the PR. I hadn't looked at my email or Mantis yet this morning, still getting off the ground here, so I didn't see it get opened. All good and thank you. Discussion on that thread shortly.

[toggledbits]

FYI, I'm also trying to implement the "run lua" action for the (vera-specific) system device. That does not mean Lua will run in MSR -- it does not, can not, and will not. But Vera does give me the ability to pass it Lua and have it execute it. That fills me with dread, frankly, but if it's what you need, it can be done. It will also need a UI change to support it, since typing Lua into a small entry field won't due. If it works, it should make invoking functions in a Lua module (built as @therealdb has shown you to do) pretty easy.

[toggledbits]

Update, if you haven't already been notified by Mantis: patch is up on PR#80.

[cw-kid]

@toggledbits said in Running Lua Code ? And watching device properties?:

FYI, I'm also trying to implement the "run lua" action for the (vera-specific) system device. That does not mean Lua will run in MSR -- it does not, can not, and will not. But Vera does give me the ability to pass it Lua and have it execute it. That fills me with dread, frankly, but if it's what you need, it can be done. It will also need a UI change to support it, since typing Lua into a small entry field won't due. If it works, it should make invoking functions in a Lua module (built as @therealdb has shown you to do) pretty easy.

I'm sure this will be very handy for some users.

I am good at the moment however, using the method therealdb showed me. Its working currently.

[cw-kid]

@toggledbits said in Running Lua Code ? And watching device properties?:

Update, if you haven't already been notified by Mantis: patch is up on PR#80.

Confirmed as working again thanks.