Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Running Lua Code ? And watching device properties?
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor

Running Lua Code ? And watching device properties?

Scheduled Pinned Locked Moved Multi-System Reactor
69 Posts 7 Posters 5.1k Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT toggledbits

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

    cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #54

    @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.

    1 Reply Last reply
    0
    • T Tarkus

      I have been running Lua within my Vera reactor pretty successfully. In some cases the reason was to have some conditional logic on the activity side. I found that this enabled me to keep the condition side a bit simpler and clean. I was also running lua to send Global Cache IR codes to my older Tv's. I now am trying the CG plugin that Patrick sorted out for me. The small issue with that is I need to convert all my Global Cache codes to pronto hex. I only mention so others know it does not support CG codes. There is also some lua that I use to turn off my computer. 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 understand that this may be issues with my Vera, etc... . I also had lua in Vera reactor activities that preceded delays or other devices commands and by moving the lua into a Vera scene will that mess with the timing? Will there be a lag on the Vera side in invoking the scene while MSR continues with the reaction? The bottom line for me is I will try to make this work and eliminates much of the lua that I can. Having some legacy devices with IR contol does not help the situation I still have a lot of work to do so I can't say if everything will work out. It will be a matter of functionality and stability for me otherwise I will just stick with Vera reactor until I can't anymore. I will say that I do wish there was lua support in MSR.

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #55

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

      I now am trying the CG plugin that Patrick sorted out for me. The small issue with that is I need to convert all my Global Cache codes to pronto hex. I only mention so others know it does not support CG codes.

      Were you not using the GC100 plugin before? Because if you were, it should not work any differently through MSR. MSR only passes the string in whatever format. If GC100 understood other code types before (even though the action has "Pronto" in the name), it would still now. MSR doesn't modify or interpret that data.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      T 1 Reply Last reply
      0
      • toggledbitsT toggledbits

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

        I now am trying the CG plugin that Patrick sorted out for me. The small issue with that is I need to convert all my Global Cache codes to pronto hex. I only mention so others know it does not support CG codes.

        Were you not using the GC100 plugin before? Because if you were, it should not work any differently through MSR. MSR only passes the string in whatever format. If GC100 understood other code types before (even though the action has "Pronto" in the name), it would still now. MSR doesn't modify or interpret that data.

        T Offline
        T Offline
        Tarkus
        wrote on last edited by
        #56

        @toggledbits No I was using Lua in Vera Reactor to pass the Global Cache codes. I have played around with the GC Plugin in the past but I have not used it in years up until MSR.

        1 Reply Last reply
        0
        • cw-kidC 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.

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #57

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

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

          I think you're missing what I'm saying. You don't need change your library structure or not do what @therealdb has suggested. It's a good, clean way to go. But if you do this from MSR right now as a Request action (that's what I assume you are doing) to run the function:

          http://ip-address:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunLua&Code=VeraScenes.turnLightsOn%28nil%29
          

          You can (21063 and after) just do this, assuming you've loaded the library in startup Lua:

          b0bdb14a-a210-4520-b606-1f09a6d50ff2-image.png

          And if you haven't loaded it in startup Lua, you can just bring it in with the code, like this:

          368aff16-fc39-4515-8410-778d753e89a4-image.png

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          T cw-kidC 2 Replies Last reply
          3
          • K Offline
            K Offline
            kfxo
            wrote on last edited by
            #58

            @toggledbits This looks great. So much easier then having to write out the http request.

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

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

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

              I think you're missing what I'm saying. You don't need change your library structure or not do what @therealdb has suggested. It's a good, clean way to go. But if you do this from MSR right now as a Request action (that's what I assume you are doing) to run the function:

              http://ip-address:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunLua&Code=VeraScenes.turnLightsOn%28nil%29
              

              You can (21063 and after) just do this, assuming you've loaded the library in startup Lua:

              b0bdb14a-a210-4520-b606-1f09a6d50ff2-image.png

              And if you haven't loaded it in startup Lua, you can just bring it in with the code, like this:

              368aff16-fc39-4515-8410-778d753e89a4-image.png

              T Offline
              T Offline
              Tarkus
              wrote on last edited by
              #59
              This post is deleted!
              1 Reply Last reply
              0
              • toggledbitsT toggledbits

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

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

                I think you're missing what I'm saying. You don't need change your library structure or not do what @therealdb has suggested. It's a good, clean way to go. But if you do this from MSR right now as a Request action (that's what I assume you are doing) to run the function:

                http://ip-address:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunLua&Code=VeraScenes.turnLightsOn%28nil%29
                

                You can (21063 and after) just do this, assuming you've loaded the library in startup Lua:

                b0bdb14a-a210-4520-b606-1f09a6d50ff2-image.png

                And if you haven't loaded it in startup Lua, you can just bring it in with the code, like this:

                368aff16-fc39-4515-8410-778d753e89a4-image.png

                cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by cw-kid
                #60

                @toggledbits

                I thought you meant we could actually put the LUA code itself in to a MSR action "Set Reaction" and some how you were going to pass that to Vera.

                But I see what you meant now, so we still need to edit the VeraScenes.lua file and add our functions / LUA code etc.

                I can confirm the Play button works and the code is executed on my Vera Plus

                965d2f66-8c91-44f6-b0a4-f4d95b5ec031-image.png

                So instead of sending a HTTP Request to Vera to initiate the function we can now just specify the function in the MSR rule actions.

                toggledbitsT 1 Reply Last reply
                0
                • cw-kidC cw-kid

                  @toggledbits

                  I thought you meant we could actually put the LUA code itself in to a MSR action "Set Reaction" and some how you were going to pass that to Vera.

                  But I see what you meant now, so we still need to edit the VeraScenes.lua file and add our functions / LUA code etc.

                  I can confirm the Play button works and the code is executed on my Vera Plus

                  965d2f66-8c91-44f6-b0a4-f4d95b5ec031-image.png

                  So instead of sending a HTTP Request to Vera to initiate the function we can now just specify the function in the MSR rule actions.

                  toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #61

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

                  I thought you meant we could actually put the LUA code itself in to a MSR action "Set Reaction" and some how you were going to pass that to Vera.

                  You can, and that's exactly what's happening. Your call to your preloaded function is Lua code. You can also put this in and it will run on the Vera:

                  function later()
                      luup.log("I'm running five seconds later!", 2)
                  end
                  
                  luup.log("I'm running now!")
                  luup.call_delay( "later", 5 )
                  

                  You can put in any Lua you want. You can open a socket, send data, and close it. You can reload Luup (intentionally). You can write a file. No limits.

                  The code structure proposed by @therealdb makes good sense and is just a better way to encapsulate those functions than to bury them in Reactor rules. It will make your maintenance easier to structure your code that way.

                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                  1 Reply Last reply
                  1
                  • cw-kidC Offline
                    cw-kidC Offline
                    cw-kid
                    wrote on last edited by
                    #62

                    Even better then ! Best of both worlds.

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      This is how it will go:

                      faf26da0-6165-4668-b1d8-04053ea24b72-image.png

                      That said, this won't work today, because I haven't yet connected the expressions to the action parameters (the {master_level} value in the dimming action won't work yet). That's coming, but not yet. You can, however, do exactly this in Vera Reactor to see how it works. It will work the same way in MSR.

                      Edit... let me explain how it works (on both Vera Reactor and MSR):

                      The expression keeps the current value of the master dimmer. So on my system, vera>device_105 is named "Virtual Dimmer 18". The trigger condition looks for any change in the dimming level of that dimmer. When it changes, the set reaction sets the current value (from the expression master_level) on the slave dimmer "Virtual Dimmer 20". Bob's your uncle.

                      cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #63

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

                      That said, this won't work today, because I haven't yet connected the expressions to the action parameters (the {master_level} value in the dimming action won't work yet)

                      Hi

                      Is this related to PR 0000005 ? "Set Variable action not yet implemented" Which is now Closed.

                      Thanks

                      1 Reply Last reply
                      1
                      • therealdbT therealdb

                        @cw-kid here we go: https://github.com/dbochicchio/vera/tree/master/Library

                        I've added a sample to RunLua as well, so this should serve well our future us when in need of it 😉

                        T Offline
                        T Offline
                        Tarkus
                        wrote on last edited by
                        #64

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

                        @cw-kid here we go: https://github.com/dbochicchio/vera/tree/master/Library

                        I've added a sample to RunLua as well, so this should serve well our future us when in need of it 😉

                        Does this work with lua that is using functions? The following runs as standalone code but will not run from the library. I tested another block of lua without functions and that works in the library.

                        module("VeraScenes", package.seeall) -- TODO: personalize it
                        
                        -- Function / Samsung_tv_power_on
                        function matrixtest() 
                            luup.log('VeraScenes.matrixtest')
                        local socket = require("socket")
                        
                        function tcpclose(tcp)
                         tcp:close()
                        end
                        
                        function Delay1()
                        --[[HDMI Matrix B1--]]
                        tcp = assert(socket.connect("192.168.255.204", 4998))
                        tcp:send("sendir,1:3,1,38000,1,69,341,171,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,21,22,21,22,64,22,21,22,64,22,21,22,21,22,21,22,64,22,64,22,21,22,64,22,21,22,64,22,64,22,64,22,1493,341,85,22,3669" .. "\r\n")
                        luup.call_delay("tcpclose", 1050, tcp)
                        end
                        
                        luup.call_delay("Delay1", 1)
                        
                        function Delay2()
                        --[[HDMI Matrix B2--]]
                        local socket = require("socket")
                        tcp = assert(socket.connect("192.168.255.204", 4998))
                        tcp:send("sendir,1:3,1,38000,1,69,343,171,21,21,22,21,22,21,22,21,21,21,22,21,22,21,21,21,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,21,22,63,22,21,21,21,22,21,22,21,21,22,21,21,22,63,22,21,22,63,22,63,22,63,22,1528,342,85,22,1528" .. "\r\n")
                        luup.call_delay("tcpclose", 1050, tcp)
                        end
                        
                        luup.call_delay("Delay2", 10)
                        end	
                        
                        cw-kidC 1 Reply Last reply
                        0
                        • T Tarkus

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

                          @cw-kid here we go: https://github.com/dbochicchio/vera/tree/master/Library

                          I've added a sample to RunLua as well, so this should serve well our future us when in need of it 😉

                          Does this work with lua that is using functions? The following runs as standalone code but will not run from the library. I tested another block of lua without functions and that works in the library.

                          module("VeraScenes", package.seeall) -- TODO: personalize it
                          
                          -- Function / Samsung_tv_power_on
                          function matrixtest() 
                              luup.log('VeraScenes.matrixtest')
                          local socket = require("socket")
                          
                          function tcpclose(tcp)
                           tcp:close()
                          end
                          
                          function Delay1()
                          --[[HDMI Matrix B1--]]
                          tcp = assert(socket.connect("192.168.255.204", 4998))
                          tcp:send("sendir,1:3,1,38000,1,69,341,171,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,21,22,21,22,64,22,21,22,64,22,21,22,21,22,21,22,64,22,64,22,21,22,64,22,21,22,64,22,64,22,64,22,1493,341,85,22,3669" .. "\r\n")
                          luup.call_delay("tcpclose", 1050, tcp)
                          end
                          
                          luup.call_delay("Delay1", 1)
                          
                          function Delay2()
                          --[[HDMI Matrix B2--]]
                          local socket = require("socket")
                          tcp = assert(socket.connect("192.168.255.204", 4998))
                          tcp:send("sendir,1:3,1,38000,1,69,343,171,21,21,22,21,22,21,22,21,21,21,22,21,22,21,21,21,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,21,22,63,22,21,21,21,22,21,22,21,21,22,21,21,22,63,22,21,22,63,22,63,22,63,22,1528,342,85,22,1528" .. "\r\n")
                          luup.call_delay("tcpclose", 1050, tcp)
                          end
                          
                          luup.call_delay("Delay2", 10)
                          end	
                          
                          cw-kidC Offline
                          cw-kidC Offline
                          cw-kid
                          wrote on last edited by
                          #65

                          @tarkus I have also seen the same issue / limitation.

                          Seems if your LUA code has functions within it already, you can't use that code in the VeraScenes.lua file as it doesn't run the code.

                          I've had to run from MSR some Vera scenes with that LUA code instead for now.

                          Perhaps we are both doing it incorrectly which is quite possible.

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by toggledbits
                            #66

                            It's not a limitation. It's the way Lua works, combined with one way Luup is broken.

                            The problem is that you are declaring your delay callback/handler function in a module. It is therefore not a global function, it is a module function -- it is scoped within the module, not globally. To access functions inside a module, you have to use modulename.functionname(arguments), as you know, and the same is true for the delay handler/callback.

                            But the way Vera implemented luup.call_delay(), it takes a function name as a string, rather than a function reference. The function, therefore, has to be global. And it's not global, it's in a module.

                            One way to solve this problem (which all plugins experience, too, by the way) is to make a global alias. That means in your startup Lua, you do something like this:

                            mymodule = require( "mymodule" )         -- this line loads your module
                            
                            -- Create a global alias for my delay handler
                            mymodule_delayhandler = mymodule.delayhandler
                            

                            Then, in your module, instead of doing luup.call_delay( 'delayhandler', 5 ) you have to do luup.call_delay( 'mymodule_delayhandler', 5 ). This makes the delay use your global alias instead of the function name directly (which it can't).

                            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                            cw-kidC 1 Reply Last reply
                            3
                            • T Offline
                              T Offline
                              Tarkus
                              wrote on last edited by
                              #67

                              So further testing seems to indicate that it is not the function causing the issue but rather either the multiple delays or just something in the structure of my code.

                              1 Reply Last reply
                              0
                              • cw-kidC Offline
                                cw-kidC Offline
                                cw-kid
                                wrote on last edited by
                                #68

                                Thanks I will try that Global alias in my code. Both myself and Tarkus have a lot of delays in our code I think.

                                1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  It's not a limitation. It's the way Lua works, combined with one way Luup is broken.

                                  The problem is that you are declaring your delay callback/handler function in a module. It is therefore not a global function, it is a module function -- it is scoped within the module, not globally. To access functions inside a module, you have to use modulename.functionname(arguments), as you know, and the same is true for the delay handler/callback.

                                  But the way Vera implemented luup.call_delay(), it takes a function name as a string, rather than a function reference. The function, therefore, has to be global. And it's not global, it's in a module.

                                  One way to solve this problem (which all plugins experience, too, by the way) is to make a global alias. That means in your startup Lua, you do something like this:

                                  mymodule = require( "mymodule" )         -- this line loads your module
                                  
                                  -- Create a global alias for my delay handler
                                  mymodule_delayhandler = mymodule.delayhandler
                                  

                                  Then, in your module, instead of doing luup.call_delay( 'delayhandler', 5 ) you have to do luup.call_delay( 'mymodule_delayhandler', 5 ). This makes the delay use your global alias instead of the function name directly (which it can't).

                                  cw-kidC Offline
                                  cw-kidC Offline
                                  cw-kid
                                  wrote on last edited by cw-kid
                                  #69

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

                                  It's not a limitation. It's the way Lua works, combined with one way Luup is broken.
                                  The problem is that you are declaring your delay callback/handler function in a module. It is therefore not a global function, it is a module function -- it is scoped within the module, not globally.

                                  To access functions inside a module, you have to use modulename.functionname(arguments), as you know, and the same is true for the delay handler/callback.

                                  But the way Vera implemented luup.call_delay(), it takes a function name as a string, rather than a function reference. The function, therefore, has to be global. And it's not global, it's in a module.

                                  One way to solve this problem (which all plugins experience, too, by the way) is to make a global alias. That means in your startup Lua, you do something like this:

                                  mymodule = require( "mymodule" ) -- this line loads your module

                                  -- Create a global alias for my delay handler
                                  mymodule_delayhandler = mymodule.delayhandler

                                  Then, in your module, instead of doing luup.call_delay( 'delayhandler', 5 ) you have to do luup.call_delay( 'mymodule_delayhandler', 5 ). This makes the delay use your global alias instead of the function name directly (which it can't).

                                  Just trying this "Global Alias" for function delays, for the first time, but I can't get it working. I must be doing something wrong.

                                  In the top of my VeraScenes.lua file I have added this code:

                                  module("VeraScenes", package.seeall) -- TODO: personalize it
                                  mymodule = require( "mymodule" ) -- this line loads your module
                                  
                                  -- Create a global alias for my delay handler
                                  mymodule_delayhandler = mymodule.delayhandler
                                  
                                  --Away Mode Scene
                                  function mymodule_delayhandler()
                                  local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", 419) --Status of Safe to Arm virtual switch
                                  if status == "0" then --Safe to Arm
                                    luup.inet.wget("http://SEND-TTS-MESSAGE1")
                                    
                                  else --Not Safe to Arm
                                    luup.inet.wget("http://SEND-TTS-MESSAGE2")
                                  end
                                  end
                                  luup.call_delay( 'mymodule_delayhandler', 30 )
                                  

                                  The test code checks the status of a virtual switch and sends a different HTTP request / TTS announcement etc.

                                  I wanted a 30 second delay before anything happens at all.

                                  When I call this function from a MSR rule by using

                                  VeraScenes.mymodule_delayhandler()
                                  

                                  I can hear the TTS announcement right away, so my 30 second delay is not happening.

                                  What am I doing wrong?

                                  @Tarkus Did you get this working?

                                  Thanks

                                  1 Reply Last reply
                                  1
                                  • toggledbitsT toggledbits locked this topic on
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  Recent Topics

                                  • Errors after updating to MQTTController build 25139
                                    toggledbitsT
                                    toggledbits
                                    0
                                    2
                                    10

                                  • Set Reaction > Script Action
                                    toggledbitsT
                                    toggledbits
                                    0
                                    4
                                    26

                                  • Wiring Samotech SM308-S into light fitting
                                    F
                                    Freemanator
                                    0
                                    1
                                    10

                                  • Advice reqeusted to migrate MSR from Bare Metal to Container
                                    T
                                    tamorgen
                                    0
                                    5
                                    75

                                  • Reactor (Multi-System/Multi-Hub) Announcements
                                    toggledbitsT
                                    toggledbits
                                    5
                                    122
                                    37.3k

                                  • Z-Wave Future....
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    5
                                    163

                                  • Can´t restart or upgrade/deploy MSR
                                    toggledbitsT
                                    toggledbits
                                    0
                                    4
                                    112

                                  • [Solved] Limit HA Entity in MSR
                                    wmarcolinW
                                    wmarcolin
                                    0
                                    7
                                    233

                                  • Disaster recovery and virtualisation
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    5
                                    689

                                  • Remote access of Zwave stick from Z-wave server
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    3
                                    407

                                  • Organizing/ structuring rule sets and rules
                                    G
                                    gwp1
                                    0
                                    5
                                    396
                                  Powered by NodeBB | Contributors
                                  Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                  • Login

                                  • Don't have an account? Register

                                  • Login or register to search.
                                  • First post
                                    Last post
                                  0
                                  • Categories
                                  • Recent
                                  • Tags
                                  • Popular
                                  • Unsolved