Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: November 21, 2020)

    • Migrating Zwave & ZigBee stuff to MQTT - guidance needed.

      A

      Currently I have a Vera and Hue hub all reliably controlled by openLuup with AltUI, plus any number of plugins. Been working really well for a few years now. However would like to head for a more MQTT based set up. Eliminate the Hue hub and hopefully eliminate Vera by using ZWAVE JS UI. Noting that Zwavejs2mqtt has been renamed to Z-Wave JS UI. Probably also run the stuff using Docker. Just because. Everything would end up on the one computer for easier management. Erhhh that's the hope.

      Some of the new Zigbee Aqara stuff is very good and inexpensive plus it fits in with HomeKit. Also the Aqara battery powered stuff looks to have a good battery lifetime: ie suggested up to five years. The battery operated Hue buttons I have; have lasted for ages. Would like to use zigbee2mqtt with a SonOff dongle, which would allow access to the over two and half thousand devices zigbee2mqtt now supports:

      | Zigbee2MQTT

      AK has the MQTT stuff working in openLuup. Have played around with it and it works well, as one would expect. Love the UDP to MQTT code.

      Shellys are great and also very inexpensive and they spit out & accept MQTT but I would prefer to stay away from WiFi. Not meshed and higher power consumption. Horses for courses.

      Now here's the query:
      Got about forty or more ZWave twin light switches, plus a few other ZWave bits & pieces such as blind controllers. Then there are the Hue devices on top of that. That's a lot of virtual devices to set up in openLuup. What's an appropriate way to do this?

      It seems there is no "auto magic bridge set up". Do I need to use say @therealdb's Virtual Devices plugin that supports MQTT or is there some other approach?

      I have to confess I still don't understand the master child approach in that plugin. Seems one light switch would have all the other light switches hanging off it? Helps Vera but not a problem with openLuup - why is that? Suspect AK's good coding beats Vera's?

      dbochicchio/vera-VirtualDevices dbochicchio/vera-VirtualDevices

      Virtual HTTP Devices plug-in for Vera and openLuup - dbochicchio/vera-VirtualDevices

      Setting up manually say 100 virtual devices is a bit much to ask. I had a look at hacking the user_data.json file. Good approach till you see all the UIDs and the individually numbered ControlURL and EventURLs that need to be set up.

      I need some way of say of creating about 80 light switches in "No room" or in say the "ZWave upgrade" room. Or say some sort of code that could go through all my existing bridged ZWAVE devices in openLuup and create virtual devices for each one. I caould then use the openLuup console to name them and place them in their rooms:

      openLuup_IP_address:3480/console?page=devices_table

      At that point I could hack the user_data.json file to insert the MQTT topics fairly easily for each? Plus any other fine tuning needed.

      Then the old ZWave stuff could be swapped over to ZWAVE JS UI and all the virtual MQTT devices would be ready to go or am I dreaming? Then delete all the old Vera bridged stuff. I'm not too fussed about scene code and the like, as a I have all my code in one block, that is set up in the openLuup start up.

      It seems that with ZWay you can create all the ZWave device by doing some sort of interrogation of ZWay's API? Seems also to be the case with the Shelleys?

      So any ideas, suggestions or code snippets are welcome on how to move towards MQTT and in particular ZWAVE JS UI and zigbee2mqtt.

      I'm in no hurry as openLuup is performing nicely, with the old Vera handling all my ZWave devices.

      openLuup

    • openLuup: Version Log

      akbooer

      A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:

      ...I want to work in a more open and stable [Vera] environment...

      ...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?

      1. UI
      2. scheduler
      3. web server
      4. Luup compatible API
      5. Device and Implementation xml file reader
      6. Zwave bridge to Vera
      7. runs most plugins without modification

      What we wouldn’t need is UPnP.

      What have we (nearly) got already?

      We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.

      Is it worth the effort? Probably not. Will I pursue this quest? Yes.

      openLuup was the result.

      DE2056BF-E548-4611-972B-40276F00BFEB.jpeg

      openLuup

    • Problem with luup.call_delay nexted in luup.call_timer

      M

      Hi Ak,

      Not sure when it started as it took me a while to notice.

      I have a function on a luup.call_timer to turn on a switch and then use a luup.call_delay to turn it off a minute later. This is done by the same global function, but on the luup.call_delay i get a message in the log : "luup.call_delay:: unknown global function name: HouseDevice1_PumpCommand"

      This is in the init function:

      luup.call_timer("HouseDevice1_PumpCommand", 2, "2:15:00", hm_Heating.PumpHealthRunDay, hm_Heating.PumpCMD.HEALTH.."1", true)

      This is in the function to schedule to off command giving the global function name not found:

      luup.call_delay("HouseDevice1_PumpCommand", hm_Heating.PumpHealthOnDuration, hm_Heating.PumpCMD.HEALTH.."0")

      Is it because I use the "TRUE" parameter that is openLuup specific so the timer does not fire just once?

      Running v21.7.25, may be time to update?

      Cheers Rene

      openLuup

    • OpenLuup installation

      N

      Hi, I have been trying to install OpenLuup on MacOS but I am failing, so far.
      Is there a step-by-step instruction (for MacOS) to follow?

      After installing LuaRocks, luasec, luafilesystem and luasocket I then try to run lua5.1 openLuup_install.lua and then get the messages below.

      Any ideas and proposals are appreciated.

      Regards
      Jan

      openLuup_install 2019.02.15 @akbooer
      lua5.1: openLuup_install.lua:18: module ‘socket.http’ not found:
      no field package.preload[‘socket.http’]
      no file ‘./socket/http.lua’
      no file ‘/usr/local/share/lua/5.1/socket/http.lua’
      no file ‘/usr/local/share/lua/5.1/socket/http/init.lua’
      no file ‘/usr/local/lib/lua/5.1/socket/http.lua’
      no file ‘/usr/local/lib/lua/5.1/socket/http/init.lua’
      no file ‘./socket/http.so’
      no file ‘/usr/local/lib/lua/5.1/socket/http.so’
      no file ‘/usr/local/lib/lua/5.1/loadall.so’
      no file ‘./socket.so’
      no file ‘/usr/local/lib/lua/5.1/socket.so’
      no file ‘/usr/local/lib/lua/5.1/loadall.so’
      stack traceback:
      [C]: in function ‘require’
      openLuup_install.lua:18: in main chunk

      openLuup

    • Unexpected stop of openLuup

      Crille

      Every now and then my openLuup stops responding. This is the LuaUPnP.log when it happens:

      2021-08-20 14:59:39.827 :: openLuup LOG ROTATION :: (runtime 11.0 days) 2021-08-20 14:59:39.831 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6023b8088 2021-08-20 14:59:39.853 openLuup.server:: request completed (49215 bytes, 4 chunks, 22 ms) tcp{client}: 0x55b6023b8088 2021-08-20 14:59:39.854 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6023b8088 2021-08-20 14:59:40.826 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600f46ab8 2021-08-20 14:59:40.829 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600f46ab8 2021-08-20 14:59:40.846 openLuup.server:: request completed (49215 bytes, 4 chunks, 16 ms) tcp{client}: 0x55b600f46ab8 2021-08-20 14:59:40.847 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600f46ab8 2021-08-20 14:59:41.827 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600d1ad98 2021-08-20 14:59:41.829 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600d1ad98 2021-08-20 14:59:41.838 openLuup.server:: request completed (49215 bytes, 4 chunks, 8 ms) tcp{client}: 0x55b600d1ad98 2021-08-20 14:59:41.838 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600d1ad98 2021-08-20 14:59:42.827 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6016b9848 2021-08-20 14:59:42.829 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6016b9848 2021-08-20 14:59:42.847 openLuup.server:: request completed (49215 bytes, 4 chunks, 17 ms) tcp{client}: 0x55b6016b9848 2021-08-20 14:59:42.876 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6016b9848 2021-08-20 14:59:43.054 luup.watch_callback:: 30003.DS18B20.Temperature called [37]virtualSensorWatchCallback() function: 0x55b600c2fff0 2021-08-20 14:59:43.054 luup.variable_set:: 38.urn:toggledbits-com:serviceId:VirtualSensor1.PreviousRawValue was: 28.3 now: 28.5 #hooks:0 2021-08-20 14:59:43.054 luup.variable_set:: 38.urn:toggledbits-com:serviceId:VirtualSensor1.RawValue was: 28.5 now: 28.4 #hooks:0 2021-08-20 14:59:43.054 luup.variable_set:: 38.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 28.5 now: 28.4 #hooks:0 2021-08-20 14:59:43.054 luup.variable_set:: 38.urn:toggledbits-com:serviceId:VirtualSensor1.PreviousValue was: 28.3 now: 28.5 #hooks:0 2021-08-20 14:59:43.054 luup.variable_set:: 38.urn:toggledbits-com:serviceId:VirtualSensor1.LastUpdate was: 1629464323 now: 1629464383 #hooks:0 2021-08-20 14:59:43.265 openLuup.server:: request completed (3193 bytes, 1 chunks, 5550 ms) tcp{client}: 0x55b60162e488 2021-08-20 14:59:43.267 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b60162e488 2021-08-20 14:59:43.278 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6023c8458 2021-08-20 14:59:43.278 openLuup.server:: GET /data_request?id=status&DataVersion=516611499&Timeout=15&MinimumDelay=100&output_format=json&_r=1629464383277 HTTP/1.1 tcp{client}: 0x55b6023c8458 2021-08-20 14:59:43.381 openLuup.server:: request completed (1091 bytes, 1 chunks, 102 ms) tcp{client}: 0x55b6023c8458 2021-08-20 14:59:43.381 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6023c8458 2021-08-20 14:59:43.392 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6013d6cc8 2021-08-20 14:59:43.393 openLuup.server:: GET /data_request?id=status&DataVersion=516611500&Timeout=15&MinimumDelay=100&output_format=json&_r=1629464383391 HTTP/1.1 tcp{client}: 0x55b6013d6cc8 2021-08-20 14:59:43.496 openLuup.server:: request completed (3196 bytes, 1 chunks, 4981 ms) tcp{client}: 0x55b601a37db8 2021-08-20 14:59:43.826 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601d05a08 2021-08-20 14:59:43.828 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b601d05a08 2021-08-20 14:59:43.844 openLuup.server:: request completed (49215 bytes, 4 chunks, 15 ms) tcp{client}: 0x55b601d05a08 2021-08-20 14:59:43.844 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b601d05a08 2021-08-20 14:59:44.524 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=516611500&Timeout=60&MinimumDelay=1500&_=1629292536029 HTTP/1.1 tcp{client}: 0x55b601a37db8 2021-08-20 14:59:44.828 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6023a7d18 2021-08-20 14:59:44.831 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6023a7d18 2021-08-20 14:59:44.844 openLuup.server:: request completed (49215 bytes, 4 chunks, 12 ms) tcp{client}: 0x55b6023a7d18 2021-08-20 14:59:44.844 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6023a7d18 2021-08-20 14:59:45.514 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1629292536030 HTTP/1.1 tcp{client}: 0x55b601ab8228 2021-08-20 14:59:45.617 openLuup.server:: request completed (1 bytes, 1 chunks, 102 ms) tcp{client}: 0x55b601ab8228 2021-08-20 14:59:45.827 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600b8de38 2021-08-20 14:59:45.828 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600b8de38 2021-08-20 14:59:45.834 openLuup.server:: request completed (49215 bytes, 4 chunks, 5 ms) tcp{client}: 0x55b600b8de38 2021-08-20 14:59:45.836 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600b8de38 2021-08-20 14:59:46.828 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6018a53f8 2021-08-20 14:59:46.830 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6018a53f8 2021-08-20 14:59:46.841 openLuup.server:: request completed (49215 bytes, 4 chunks, 11 ms) tcp{client}: 0x55b6018a53f8 2021-08-20 14:59:46.842 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6018a53f8 2021-08-20 14:59:47.829 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600d2d938 2021-08-20 14:59:47.832 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600d2d938 2021-08-20 14:59:47.854 openLuup.server:: request completed (49215 bytes, 4 chunks, 21 ms) tcp{client}: 0x55b600d2d938 2021-08-20 14:59:47.855 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600d2d938 2021-08-20 14:59:47.962 luup.variable_set:: 10086.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 28.3 now: 28.5 #hooks:0 2021-08-20 14:59:48.370 openLuup.server:: request completed (1359 bytes, 1 chunks, 4977 ms) tcp{client}: 0x55b6013d6cc8 2021-08-20 14:59:48.372 openLuup.server:: request completed (1359 bytes, 1 chunks, 3847 ms) tcp{client}: 0x55b601a37db8 2021-08-20 14:59:48.373 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6013d6cc8 2021-08-20 14:59:48.384 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601e62df8 2021-08-20 14:59:48.385 openLuup.server:: GET /data_request?id=status&DataVersion=516611502&Timeout=15&MinimumDelay=100&output_format=json&_r=1629464388383 HTTP/1.1 tcp{client}: 0x55b601e62df8 2021-08-20 14:59:48.813 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=516611502&Timeout=60&MinimumDelay=1500&_=1629292536031 HTTP/1.1 tcp{client}: 0x55b601a37db8 2021-08-20 14:59:48.829 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600c44bf8 2021-08-20 14:59:48.832 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600c44bf8 2021-08-20 14:59:48.854 openLuup.server:: request completed (49215 bytes, 4 chunks, 21 ms) tcp{client}: 0x55b600c44bf8 2021-08-20 14:59:48.856 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600c44bf8 2021-08-20 14:59:49.829 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600e1fea8 2021-08-20 14:59:49.830 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b600e1fea8 2021-08-20 14:59:49.835 openLuup.server:: request completed (49215 bytes, 4 chunks, 5 ms) tcp{client}: 0x55b600e1fea8 2021-08-20 14:59:49.835 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600e1fea8 2021-08-20 14:59:50.831 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601cfa118 2021-08-20 14:59:50.832 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b601cfa118 2021-08-20 14:59:50.837 openLuup.server:: request completed (49215 bytes, 4 chunks, 4 ms) tcp{client}: 0x55b601cfa118 2021-08-20 14:59:50.838 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b601cfa118 2021-08-20 14:59:51.833 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601462bb8 2021-08-20 14:59:51.835 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b601462bb8 2021-08-20 14:59:51.852 openLuup.server:: request completed (49215 bytes, 4 chunks, 17 ms) tcp{client}: 0x55b601462bb8 2021-08-20 14:59:51.854 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b601462bb8 2021-08-20 14:59:52.834 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6016b1c98 2021-08-20 14:59:52.836 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6016b1c98 2021-08-20 14:59:52.847 openLuup.server:: request completed (49215 bytes, 4 chunks, 11 ms) tcp{client}: 0x55b6016b1c98 2021-08-20 14:59:52.848 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6016b1c98 2021-08-20 14:59:53.193 luup.variable_set:: 10005.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 255 now: 255 #hooks:0 2021-08-20 14:59:53.193 luup.variable_set:: 10006.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.193 luup.variable_set:: 10094.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.193 luup.variable_set:: 10096.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 10 now: 10 #hooks:0 2021-08-20 14:59:53.193 luup.variable_set:: 10098.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 10 now: 10 #hooks:0 2021-08-20 14:59:53.193 luup.variable_set:: 10104.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 10 now: 10 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10106.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10109.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10112.urn:micasaverde-com:serviceId:DoorLock1.sl_UserCode was: UserID="4" UserName="Ella" now: UserID="4" UserName="Ella" #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10112.urn:micasaverde-com:serviceId:DoorLock1.sl_LockButton was: 1 now: 1 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10112.urn:micasaverde-com:serviceId:DoorLock1.sl_PinFailed was: 1 now: 1 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10112.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10131.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10132.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10133.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10165.urn:micasaverde-com:serviceId:HaDevice1.sl_Alarm was: SMOKE now: SMOKE #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10165.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 0 now: 0 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10188.urn:micasaverde-com:serviceId:HaDevice1.sl_TamperAlarm was: 1 now: 1 #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10188.urn:micasaverde-com:serviceId:HaDevice1.sl_Alarm was: TAMPER_ALARM now: TAMPER_ALARM #hooks:0 2021-08-20 14:59:53.194 luup.variable_set:: 10191.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 10 now: 10 #hooks:0 2021-08-20 14:59:53.299 openLuup.server:: request completed (5449 bytes, 1 chunks, 4485 ms) tcp{client}: 0x55b601a37db8 2021-08-20 14:59:53.505 openLuup.server:: request completed (5449 bytes, 1 chunks, 5119 ms) tcp{client}: 0x55b601e62df8 2021-08-20 14:59:53.511 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b601e62df8 2021-08-20 14:59:53.513 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=516611523&Timeout=60&MinimumDelay=1500&_=1629292536032 HTTP/1.1 tcp{client}: 0x55b601a37db8 2021-08-20 14:59:53.522 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600bc7068 2021-08-20 14:59:53.524 openLuup.server:: GET /data_request?id=status&DataVersion=516611523&Timeout=15&MinimumDelay=100&output_format=json&_r=1629464393521 HTTP/1.1 tcp{client}: 0x55b600bc7068 2021-08-20 14:59:53.834 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601b8cbe8 2021-08-20 14:59:53.835 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b601b8cbe8 2021-08-20 14:59:53.840 openLuup.server:: request completed (49215 bytes, 4 chunks, 5 ms) tcp{client}: 0x55b601b8cbe8 2021-08-20 14:59:53.841 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b601b8cbe8 2021-08-20 14:59:54.834 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6013dacd8 2021-08-20 14:59:54.836 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b6013dacd8 2021-08-20 14:59:54.849 openLuup.server:: request completed (49215 bytes, 4 chunks, 12 ms) tcp{client}: 0x55b6013dacd8 2021-08-20 14:59:54.850 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b6013dacd8 2021-08-20 14:59:55.835 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b602316198 2021-08-20 14:59:55.836 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b602316198 2021-08-20 14:59:55.841 openLuup.server:: request completed (49215 bytes, 4 chunks, 5 ms) tcp{client}: 0x55b602316198 2021-08-20 14:59:55.842 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b602316198 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601547598 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6016c7cf8 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b600b75158 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60187d188 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6011a5bf8 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60115ecd8 2021-08-20 15:00:10.955 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601018c18 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60175d068 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60224ced8 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b6017869d8 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601ab40e8 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601914178 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60100a228 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b60197a998 2021-08-20 15:00:10.956 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601103238 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600c62438 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601eaabf8 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6017c95b8 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600d6e508 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601dd2168 2021-08-20 15:00:10.956 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b60155eb68 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6016ddcd8 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b602384ca8 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b60230cc78 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6017e3338 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600965de8 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601e23608 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6018da2f8 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600c9aa08 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600bbf0f8 2021-08-20 15:00:10.957 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601334518 2021-08-20 15:00:10.958 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b60183b5f8 2021-08-20 15:00:10.958 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6015682a8 2021-08-20 15:00:10.958 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6018869e8 2021-08-20 15:00:10.958 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6008839c8 2021-08-20 15:00:10.958 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b60154ed58 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601a259e8 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b600f617c8 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6015884c8 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601c85fe8 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b602275ae8 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b60190ab88 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601692038 2021-08-20 15:00:10.959 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601fcea78 2021-08-20 15:00:10.960 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601ca7f28 2021-08-20 15:00:10.960 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b601fd37f8 2021-08-20 15:00:10.960 openLuup.io.server:: MQTT:1888 connection from 127.0.0.1 tcp{client}: 0x55b6020ec968 2021-08-20 15:00:10.961 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1629292536033 HTTP/1.1 tcp{client}: 0x55b601ab8228 2021-08-20 15:00:10.967 luup_log:0: 32Mb, 3.3%cpu, 11.0days 2021-08-20 15:00:10.972 openLuup.server:: request completed (3361 bytes, 1 chunks, 17459 ms) tcp{client}: 0x55b601a37db8 2021-08-20 15:00:10.973 openLuup.server:: request completed (3361 bytes, 1 chunks, 17449 ms) tcp{client}: 0x55b600bc7068 2021-08-20 15:00:10.990 luup.variable_set:: 10116.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 21.8 now: 21.9 #hooks:0 2021-08-20 15:00:10.990 luup.variable_set:: 10129.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 58.8 now: 58.7 #hooks:0 2021-08-20 15:00:10.991 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600ba45a8 2021-08-20 15:00:10.991 openLuup.mqtt:: closed tcp{client}: 0x55b600ba45a8 2021-08-20 15:00:10.992 openLuup.mqtt:: mqttthing_Klimat kllaren_838dee2e UNSUBSCRIBE from tele/Källartemp/SENSOR tcp{client}: 0x55b600ba45a8 2021-08-20 15:00:10.992 openLuup.mqtt:: ERROR publishing application message for mqtt:tele/Källartemp/SENSOR : closed 2021-08-20 15:00:10.992 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55b601c8c288 2021-08-20 15:00:10.992 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55b600bc7068 2021-08-20 15:00:10.992 openLuup.server:: GET /data_request?id=sdata HTTP/1.1 tcp{client}: 0x55b601547598 2021-08-20 15:00:10.993 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600a62818 2021-08-20 15:00:10.993 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600a62818 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Uttag garaget_6f4265a1 UNSUBSCRIBE from openLuup/update/10149/SwitchPower1/Status tcp{client}: 0x55b600a62818 2021-08-20 15:00:10.994 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600ba8428 2021-08-20 15:00:10.994 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600ba8428 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Takflkt hallen_6da387bf UNSUBSCRIBE from tele/TakfläktHall/LWT tcp{client}: 0x55b600ba8428 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Takflkt hallen_6da387bf UNSUBSCRIBE from stat/TakfläktHall/POWER2 tcp{client}: 0x55b600ba8428 2021-08-20 15:00:10.994 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600e59b88 2021-08-20 15:00:10.994 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600e59b88 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Klimat sovrummet_0d664e41 UNSUBSCRIBE from openLuup/update/20010/HumiditySensor1/CurrentLevel tcp{client}: 0x55b600e59b88 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Klimat sovrummet_0d664e41 UNSUBSCRIBE from openLuup/update/20021/TemperatureSensor1/CurrentTemperature tcp{client}: 0x55b600e59b88 2021-08-20 15:00:10.994 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600bd02d8 2021-08-20 15:00:10.994 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600bd02d8 2021-08-20 15:00:10.994 openLuup.mqtt:: mqttthing_Entrdrr_6acda58a UNSUBSCRIBE from openLuup/update/10095/SecuritySensor1/Tripped tcp{client}: 0x55b600bd02d8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600bb6cf8 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600bb6cf8 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Temperatur poolen_a589d192 UNSUBSCRIBE from tele/Pooltemp/SENSOR tcp{client}: 0x55b600bb6cf8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b6009ff868 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b6009ff868 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Rrelsesensor hallen_cf7c8293 UNSUBSCRIBE from openLuup/update/20013/SecuritySensor1/Tripped tcp{client}: 0x55b6009ff868 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600a23e28 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600a23e28 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Luftfuktighet badrum_d79a0ffb UNSUBSCRIBE from openLuup/update/10190/HumiditySensor1/CurrentLevel tcp{client}: 0x55b600a23e28 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600bb33b8 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600bb33b8 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Ljussensor hallen_19569c17 UNSUBSCRIBE from openLuup/update/20006/LightSensor1/CurrentLevel tcp{client}: 0x55b600bb33b8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600a136b8 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600a136b8 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Ljussensor trningsrum_ebf319c5 UNSUBSCRIBE from openLuup/update/20004/LightSensor1/CurrentLevel tcp{client}: 0x55b600a136b8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600babaa8 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600babaa8 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Solceller watt_e351a23b UNSUBSCRIBE from openLuup/update/10163/LightSensor1/CurrentLevel tcp{client}: 0x55b600babaa8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b6004a9de8 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b6004a9de8 2021-08-20 15:00:10.995 openLuup.mqtt:: mqttthing_Luftfuktighet dusch_91df9a58 UNSUBSCRIBE from openLuup/update/20008/HumiditySensor1/CurrentLevel tcp{client}: 0x55b6004a9de8 2021-08-20 15:00:10.995 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600b84628 2021-08-20 15:00:10.995 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600b84628 2021-08-20 15:00:10.996 openLuup.mqtt:: mqttthing_Altandrr kk_db6d3edd UNSUBSCRIBE from openLuup/update/10097/SecuritySensor1/Tripped tcp{client}: 0x55b600b84628 2021-08-20 15:00:10.996 openLuup.io.server:: MQTT:1888 connection closed tcp{client}: 0x55b600be6548 2021-08-20 15:00:10.996 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55b600be6548 2021-08-20 15:00:10.996 openLuup.mqtt:: mqttthing_Test datarum_adbe85e6 UNSUBSCRIBE from openLuup/update/20007/Dimming1/LoadLevelTarget tcp{client}: 0x55b600be6548 2021-08-20 15:00:10.996 openLuup.mqtt:: mqttthing_Test datarum_adbe85e6 UNSUBSCRIBE from openLuup/update/20007/SwitchPower1/Status tcp{client}: 0x55b600be6548

      And then in syslog:

      Aug 20 15:00:11 username systemd[1]: openluup.service: Control process exited, code=exited status=7 Aug 20 15:00:11 username systemd[1]: openluup.service: Failed with result 'exit-code'.
      openLuup

    • OpenLuup - problem with solar AZ and ALT variables?

      A

      Wanted to check if was day or night and figured I would use:

      local altitude = luup.variable_get(SID.SOLAR, 'ALT', ID.OPEN_LUUP)

      If altitude is positive it's day, else it's night. However when I read these variables they are incorrect for my locale. The actual values for sunset and midday are correct but do not occur at sunset or midday. I have checked the clock that openLuup uses and it's correct.

      Now the time for midday is one hour out and the time for sunset is 13 hours out.

      I checked this by getting the UNIX epoch for my location for both sunset and midday and then adding the hours of offset and then called:

      local ID = { OPEN_LUUP = 2 } local SID = { OPEN_LUUP = "openLuup", SOLAR = "solar" } --local localTime = my_epoch_for_midday + (3600*1) local localTime = my_epoch_for_sunset + (3600*13) local coords = {Epoch = localTime, '', Latitude = '', Longitude = ''} luup.call_action(SID.SOLAR, "GetSolarCoords", coords, ID.OPEN_LUUP) local altitude = luup.variable_get(SID.SOLAR, 'ALT', ID.OPEN_LUUP) local azimuth = luup.variable_get(SID.SOLAR, 'AZ', ID.OPEN_LUUP) print('New altitude: '..altitude) print('New azimuth: '..azimuth)

      and I get the right answers.

      Not sure what I'm doing wrong. Or perhaps there is some code mix up with UTC versus local time. I checked the documentation but no mention of the solar variables.

      If I look at the chart it looks like the whole thing is correct but shifted by my timezone. However I wouldn't expect the timezone to come into play in these calculations.

      Feature request: would like to see an openLuup variable that is true for day and false for night. eg IsDay

      openLuup

    • openLuup: MQTT server

      akbooer

      Feedback / issues with openLuup's built-in MQTT server

      openLuup

    • OpenLuup : Basic UI

      parkerc

      Creating a separate thread for anyone who is interested in using the basic (vera) smartphone UI with openLuup

      B834C005-6193-4954-95B0-6D020EAEEFDD.jpeg

      The actual L_sPhoneUI.lua file needed comes from the ‘ Smartphone Web Interface ’ that’s installed via the mios App Store.

      Once you’ve got the file and have uploaded it to openLuup, add the following to your Lua Startup

      dofile ("L_sPhoneUI.lua")

      FYI - all associated js, css and graphic files seem to be hosted at https://download1.mios.com/L_sPhoneUI_layout so not sure how long they will remain available there, but theoretically alternative hosting could be done..

      openLuup

    • Lua using do - end file

      parkerc

      Hi,

      I’ve got the L_sPhoneUI.lua file, which is the very basic Vera smartphone UI, and it’s just a do - end code construct. How do I make that work under OpenLuup?

      do .. then loads of code here.. end

      I’ve tried putting into the normal xml/json plugin space but it does seem to get picked up, as none of the handlers are registered?

      openLuup

    • luup.variable_watch

      B

      Hi AK,

      I can't find any info on how a variable watch actually ends.

      I have the following variable watch on an alarm panel plugin UPnP variable. The code is part of some extended startup lua:

      luup.variable_watch("waitForZoneToClose","urn:micasaverde-com:serviceId:EVL3VistaAlarmPanel1", "FaultedZoneNames", 7)

      In the same startup lua, the global function "waitForZoneToClose" is called when the "FaultedZoneNames" variable changes, but this same function is also called at the start of a routine that determines what zones are actually faulted on the alarm panel.

      openZoneCount= waitForZoneToClose(7, "urn:micasaverde-com:serviceId:EVL3VistaAlarmPanel1", "FaultedZoneNames" , "","")

      So although the luup watch variables are included in the function params, they are not used within the function:

      function waitForZoneToClose(dev_id, service, variable, old_val, new_val) openZoneCount = getOpenZones() --retrieves open zone names on panel, and zones to bypass per mode setting if openZoneCount > 0 then -- there are open zones buildReservedZonesTable() -- run routine to pop bypass and vent zones from the zonesToClose stack removeReservedZones() openZoneCount = tablelength(tZonesToClose) -- run the count again to see if any zone was popped off the stack during removeReservedZones end return openZoneCount end

      Because I run the function recursively ie. when the variable that holds the open zones changes, I rerun the function that detects open zones, and if any relevant zones are still open, the code for the same watch is ran again, to detect if any zones have changed status, this before trying to auto arm the panel. So there might be a situation where two or more zones need to be closed before the panel will arm, and it takes real time to physically close each zone, one by one, and as each closes, the callback would trigger again.

      Hope that makes sense.

      I wasn't clear if a variable watch ends when the watched variable changes and the code then proceeds. Or do you have to end the watch via code somehow? I was concerned about a possible condition where watch upon watch would be added to memory until a luup reload would clear the watches, or do the watches end and self-cleanup when the callback function is called.

      openLuup

    • openLuup : Kiosk (Touchscreen) Idea ?

      parkerc

      Hi,

      I have an old raspberry pi and 7" touchscreen gathering dust, and have started to explore how I could potentially use the openLuup feature to ‘specify my own’ index.html?

      The openLuup manual suggests it’s straightforward to set up, the challenge is going to be around how best to create a single html for just one of my plugins so i can use it in a kiosk type mode..

      As you can probably tell, html and web development are alien to me 🙂 - but I assume I can do something basic, like create buttons that just call luup.call_action - e.g. here’s one from a plugin I created.

      Luup

      luup.call_action("urn:nodecentral-net:serviceId:Matrix1","SYCall",{ action ="I3" },1083)

      Html

      <form action="https://google.com"> <input type="submit" value="Go to Google" /> </form>

      Not sure how that luup.call_action translate to a url, but I guess it’s something like this..

      http://ip_address:3480/data_request?id=action&output_format=xml&DeviceNum=1083&serviceId=urn:nodecentral-net:serviceId:SYMatrix1&SYCall={action=I3}

      Has anyone done anything like this already, and has any examples of their own html content they can share ?

      Is there maybe something out there that can translates any Vera static .json file into something presentable on a .html page. ? I had a quick look through @amg0 AltUi content on GitHub for inspiration but that is a way more comprehensive interface, compared to the single screen look I’m going for..

      Any suggestion/advice (examples ideally) would be much appreciated..

      openLuup

    • Luup reload required after server reboot

      A

      I noticed this morning something that have seen in the past but forgotten about.

      When I restart the OpenLuup server (in my case an Ubuntu PC) the Vera and Z-way bridges do not get in contact with the corresponding servers, i.e. are shown in red in AltUI. The solution for me is to make a "Relaod Luup engine" and then they are ok. I do not know if it is a general issue or only for my setup.

      To be honest it is not much of a problem since OpenLuup is so stable. If and when you restart the server the hazzle of reloading is not that big. In fact I had forgotten about it since it was so long ago I had to restart anything...

      The one use case I can think of is that the server gets restarted due to a power outage or something and if you are not at home the system does not fully recover without manual interaction. I my case I have the server on an UPS, but still a thought.

      Is this a known issue and is it something that can be addressed somehow? As I said low priority, at least for me. 🙂

      openLuup

    • luaJIT

      rafale77

      @akbooer,

      Have you ever considered running openLuup under LuaJIT instead of Lua5.1 interpreter?

      The LuaJIT Project

      For kicks, I switched my installation to the latest LuaJIT2.1 beta3 dating from 2017 and being a lua5.1 interpreter it is a drop in replacement. I had to move the lfs library from one folder to another likely because of an include path difference but I am seeing a further speed/efficiency improvement vs. lua5.1.
      My CPU load has dropped another 25% to now hover around 2.2% down from 2.8%. I have yet to make sure that everything else works but so far everything appears to be the same.
      The luajit site claims up to 5x speed increase through the interpreter and 120x improvement through the compiler vs the standard lua5.1.

      Screen Shot 2020-07-05 at 23.10.02.png

      My initial interest was from being able to access some ffi libraries to handle video streams...

      PS: Wow it is pretty impressive under load... browsing through ALTUI which used to cause spikes of CPU utilization from 2.8% to 4.8% now only go from 2.3% to 2.6%. It almost looks like noise. I am running it on a pretty fast x64 thread so it may not be that significant but this could make a big difference on ARM.

      Screen Shot 2020-07-05 at 23.11.47.png

      openLuup

    • Altui file not found errors

      B

      Here is a snippet of the log:

      2021-08-22 16:57:28.106 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/jquery-ui.css 2021-08-22 16:57:28.107 openLuup.server:: request completed (150 bytes, 0 chunks, 1 ms) tcp{client}: 0x564e387b57a8 2021-08-22 16:57:28.114 openLuup.server:: GET /etc/cmh-ludl/localcdn/font-awesome.min.css HTTP/1.1 tcp{client}: 0x564e38b3af28 2021-08-22 16:57:28.116 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/font-awesome.min.css 2021-08-22 16:57:28.116 openLuup.server:: request completed (157 bytes, 0 chunks, 1 ms) tcp{client}: 0x564e38b3af28 2021-08-22 16:57:28.117 openLuup.io.server:: HTTP:3480 connection from 10.17.1.100 tcp{client}: 0x564e385a7098 2021-08-22 16:57:28.123 openLuup.server:: GET /etc/cmh-ludl/localcdn/bootstrap.min.css HTTP/1.1 tcp{client}: 0x564e385a7098 2021-08-22 16:57:28.123 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/bootstrap.min.css 2021-08-22 16:57:28.124 openLuup.server:: request completed (154 bytes, 0 chunks, 0 ms) tcp{client}: 0x564e385a7098 2021-08-22 16:57:28.124 openLuup.server:: GET /etc/cmh-ludl/localcdn/jquery.bootgrid.min.css HTTP/1.1 tcp{client}: 0x564e387b57a8 2021-08-22 16:57:28.125 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/jquery.bootgrid.min.css 2021-08-22 16:57:28.126 openLuup.server:: request completed (160 bytes, 0 chunks, 0 ms) tcp{client}: 0x564e387b57a8 2021-08-22 16:57:28.127 openLuup.io.server:: HTTP:3480 connection from 10.17.1.100 tcp{client}: 0x564e38ea35a8 2021-08-22 16:57:28.127 openLuup.io.server:: HTTP:3480 connection from 10.17.1.100 tcp{client}: 0x564e3882e378 2021-08-22 16:57:28.133 openLuup.server:: GET /etc/cmh-ludl/localcdn/joint.css HTTP/1.1 tcp{client}: 0x564e3882e378 2021-08-22 16:57:28.134 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/joint.css 2021-08-22 16:57:28.135 openLuup.server:: request completed (146 bytes, 0 chunks, 0 ms) tcp{client}: 0x564e3882e378 2021-08-22 16:57:28.136 openLuup.io.server:: HTTP:3480 connection from 10.17.1.100 tcp{client}: 0x564e36e44d08 2021-08-22 16:57:28.136 openLuup.server:: GET /etc/cmh-ludl/localcdn/spectrum.min.css HTTP/1.1 tcp{client}: 0x564e38ea35a8 2021-08-22 16:57:28.137 openLuup.servlet:: file not found:etc/cmh-ludl/localcdn/spectrum.min.css 2021-08-22 16:57:28.137 openLuup.server:: request completed (153 bytes, 0 chunks, 0 ms) tcp{client}: 0x564e38ea35a8 2021-08-22 16:57:28.141 openLuup.server:: GET /etc/cmh-ludl/localcdn/jquery.min.js HTTP/1.1 tcp{client}: 0x564e36e44d08

      And here is a screen shot showing the files exist:

      Screenshot 2021-08-22 170642.png

      Altui will not load. Using the current openLuup dev version 2021.08.16 which was updated today. There is a forward slash in front of etc for the get but not for the file not found error.

      openLuup

    • luup.watch callback

      B

      Hoping someone can point me in the right direction. Per the code below, I am trying to run a function conditionally ("modeTableAction") when a watch callback triggers. In this case, the watch is on a reactor group. What I don't understand and cannot find any info on, is how to pass parameters to the function/callback. The lua file "myStartupLua" is called from openluup startup with a global require statement and this allows me to call the functions in the file from Reactor activities.

      Do I need to embed a function (that contains the parameters) within the callback function so that the callback then calls the embedded function and its parameters?

      module("myStartUpLua", package.seeall) function _G.turnOffModes(myMode) -- reactor 'and' group that checks for motion relay on and 'mode off' virtual switch is on. local porchSensorStatus = luup.variable_get("urn:toggledbits-com:serviceId:ReactorGroup", "GroupStatus_grp1a1dd8um", 160) -- modes and their device numbers local modeTable = { ['Office'] = '203', ['Garage'] = '204', ['Off'] = '223', ['Outdoors'] = '202', ['Guest'] = '190', ['Bedtime'] = '209', ['Morning'] = '217', ['Standard'] = '215', ['Party'] = '199', ['Manual'] = '206' } function modeTableAction( t, myMode ) for k, v in pairs( t ) do local lightDeviceID = v if ( k == myMode ) then local resultCode, resultString, job, returnArguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",{ newTargetValue="1" },lightDeviceID) luup.log('Turn on ' .. k .. ' ' .. lightDeviceID ,50) else local resultCode, resultString, job, returnArguments = luup.call_action("urn:upnp-org:serviceId:SwitchPower1","SetTarget",{ newTargetValue="0" },lightDeviceID) luup.log('Turn off ' .. k .. ' ' .. lightDeviceID ,50) end end end local function watchPorchRelay () if porchSensorStatus == 1 then -- motion relay on and 'mode off' virtual switch is on -- watch and wait for the vStatus to go to 0 luup.variable_watch("modeTableAction","urn:toggledbits-com:serviceId:ReactorGroup", "GroupStatus_grp1a1dd8um", 160) else -- proceed directly with turning off virtual switches. modeTableAction (modeTable, myMode) end end watchPorchRelay() end
      openLuup

    • AltUi device VeraBridge

      C

      OpenLuup version 2021.07.25
      ALTUI version v2.53c.2552

      1 - I have a problem with ALTUI:
      VeraBridge device / Actions: No more actions display

      e3c06163-0eee-469c-b8f6-9f3a4a3a0996-image.png

      2 - Problem with OpenLuup
      OPENLUUP does not automatically update the interface
      I have to refresh the page manually (under windows 10)

      openLuup

    • io module async ?

      R

      There is a little issue I'm currently facing with openluup and plugins that relies on io module.

      If openluup is watching a variable that belongs to a devices that relies on io module and there is an action attached that also relies on io module, when that watcher gets triggered, the action in question will get processed in openluup (it will show in the logs) but the parent device won't process it.

      I have a feeling that this could be due to io packets crossing between each others somehow modifying the final message received by the parent device. it's feels like the io communication is happening in the same room for all plugins and sometimes they get crossed. Wondering if anyone has experienced something of that sort and if there is a way to prevent it?

      openLuup

    • Long-overdue roll-up of the last year's development!!!

      A

      "akbooer: Master Branch: 2021 Release 7.25
      Long-overdue roll-up of the last year's development updates!"

      ak - congratulations on some great improvements coming to fruition. I can only hope you aren't running out of ideas! It's not easy.

      I'd still like to see an "App Store" plugin download count but the invisible hands still need to be invoked by someone - whoever that may be!!

      openLuup

    • "Tunnel" to MSR from Openluup?

      PerH

      Not sure which category to use, but it's about external access..

      I'm using Dataplicity to connect from the web to openluup, and i'd like a similar connection for MSR. Thats not something i would use on a phone, but from a laptop situated elsewhere in the world (faulty logic always appears when i'm far away from home!)

      I could offcourse do the same procedure (described in the lower part of this ) for MSR, but if I colud put a link somewhere in Openluup that would take me there (like the openluup console link?) that would be easier?

      Don't know if it will work to connect to a different port?

      Any ideas?

      openLuup

    • Openluup System ID 88800000?

      PerH

      I'm setting up an openluup system (again) at my cabin, and this time i also added the dataplicity wormhole for external access..

      I still use Imperihome to handle these on my phone, but ran into trouble when trying to add another "88800000" system, which seems to be the standard ID for openluup?

      Any way to change the 88800000?

      openLuup
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    Delay in luup requests

    openLuup
    3
    15
    152
    Loading More Posts
    • 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.
    • Elcid
      Elcid last edited by

      Hi,

      I have a couple of luup request, one is a request to VeraAlexa pluging to make alexa speak, the other updating a variable in reactor. They all seem to have a 10-20 second delay
      example request
      http://192.168.1.134:3480/data_request?id=action&DeviceNum=44&serviceId=urn:toggledbits-com:serviceId:ReactorSensor&action=SetVariable&VariableName=A_home&NewValue=1

      I can not figure out what is causing the delay, does anyone have any ideas?

      1 Reply Last reply Reply Quote 0
      • akbooer
        akbooer last edited by

        What does the log show?

        1 Reply Last reply Reply Quote 0
        • Elcid
          Elcid last edited by 

          26.399   openLuup.server:: POST /data_request?id=action&DeviceNum=11&serviceId=urn:toggledbits-com:serviceId:ReactorSensor&action=SetVariable&VariableName=A_home&NewValue=0 HTTP/1.1 tcp{client}: 0xfc90558
2020-11-17 14:53:31.400   luup.call_action:: 11.urn:toggledbits-com:serviceId:ReactorSensor.SetVariable 
2020-11-17 14:53:31.401   luup.call_action:: action will be handled by parent: 10
2020-11-17 14:53:31.414   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... now: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... #hooks:0
2020-11-17 14:53:31.419   openLuup.server:: error 'closed' sending 4 bytes to tcp{client}: 0xfc90558
2020-11-17 14:53:31.420   openLuup.server:: ...only 0 bytes sent
2020-11-17 14:53:31.420   openLuup.server:: error 'closed' sending 137 bytes to tcp{client}: 0xfc90558
2020-11-17 14:53:31.421   openLuup.server:: ...only 0 bytes sent
2020-11-17 14:53:31.421   openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0xfc90558
2020-11-17 14:53:31.422   openLuup.server:: ...only 0 bytes sent
2020-11-17 14:53:31.422   openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0xfc90558
2020-11-17 14:53:31.423   openLuup.server:: ...only 0 bytes sent
2020-11-17 14:53:31.423   openLuup.server:: request completed (137 bytes, 1 chunks, 23 ms) tcp{client}: 0xfc9055
          1 Reply Last reply Reply Quote 0
          • Elcid
            Elcid last edited by

            OK the issue is the POST request, it does not like it, if i make it GET everything is smooth.

            akbooer 1 Reply Last reply Reply Quote 0
            • akbooer
              akbooer last edited by

              No idea.

              • I would like to see earlier in the log where there should be an initial connection message from the server module.
              • also would like to see the HTTP Server page at http://openLuupIP:3480/openLuup?page=http
              • the exact 5 second delay between the first and second lines would indicate a timeout...
              • ... but a valid request appears to be received and acted upon (very quickly)

              No indication of 10-20 second delays in this case.

              Do you always get those errors?

              1 Reply Last reply Reply Quote 0
              • akbooer
                akbooer @Elcid last edited by

                @elcid said in Delay in luup requests:

                OK the issue is the POST request, it does not like it, if i make it GET everything is smooth.

                OK. Our messages crossed, but that's a good start.

                What is generating the request? Are you sure it's valid?

                1 Reply Last reply Reply Quote 0
                • Elcid
                  Elcid last edited by

                  A get request

                  2020-11-17 15:45:24.304   luup.variable_set:: 10186.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:1
2020-11-17 15:45:24.305   luup.watch_callback:: 10186.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped called [10]reactorWatch() function: 0xf0d38d0
2020-11-17 15:45:24.321   luup.variable_set:: 14.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"condpxw4kq6":{"evaledge":{"t":1605296162,"f":1605296163},"stateedge":{"t":1605296162,"f":1605296163},"id":"condpx... now: {"condpxw4kq6":{"evaledge":{"t":1605296162,"f":1605296163},"stateedge":{"t":1605296162,"f":1605296163},"id":"condpx... #hooks:0
2020-11-17 15:45:24.324   luup.variable_set:: 14.urn:toggledbits-com:serviceId:ReactorSensor.lastacc was: 1605627873 now: 1605627924 #hooks:0
2020-11-17 15:45:24.325   luup.variable_set:: 14.urn:toggledbits-com:serviceId:ReactorSensor.Message was: Not tripped now: Not tripped #hooks:0
2020-11-17 15:45:25.310   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296260928&Timeout=60&MinimumDelay=1500&_=1605627659979 HTTP/1.1 tcp{client}: 0xf3e3758
2020-11-17 15:45:25.427   openLuup.server:: request completed (40635 bytes, 3 chunks, 116 ms) tcp{client}: 0xf3e3758
2020-11-17 15:45:26.315   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296260933&Timeout=60&MinimumDelay=1500&_=1605627659980 HTTP/1.1 tcp{client}: 0xf3e3758
2020-11-17 15:45:28.614   luup.variable_set:: 10090.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1605627908 now: 1605627928 #hooks:0
2020-11-17 15:45:29.028   openLuup.server:: request completed (17279 bytes, 2 chunks, 2711 ms) tcp{client}: 0xf3e3758
2020-11-17 15:45:30.058   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296260935&Timeout=60&MinimumDelay=1500&_=1605627659981 HTTP/1.1 tcp{client}: 0xf3e3758
2020-11-17 15:45:38.635   openLuup.io.server:: HTTP:3480 connection from 192.168.1.10 tcp{client}: 0xff28f20
2020-11-17 15:45:38.638   openLuup.server:: GET /data_request?id=action&DeviceNum=11&serviceId=urn:toggledbits-com:serviceId:ReactorSensor&action=SetVariable&VariableName=A_home&NewValue=0 HTTP/1.1 tcp{client}: 0xff28f20
2020-11-17 15:45:38.639   luup.call_action:: 11.urn:toggledbits-com:serviceId:ReactorSensor.SetVariable 
2020-11-17 15:45:38.640   luup.call_action:: action will be handled by parent: 10
2020-11-17 15:45:38.652   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... now: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... #hooks:0
2020-11-17 15:45:38.657   openLuup.server:: request completed (137 bytes, 1 chunks, 18 ms) tcp{client}: 0xff28f20
2020-11-17 15:45:38.659   openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0xff28f20
2020-11-17 15:45:38.775   openLuup.server:: request completed (43132 bytes, 3 chunks, 8716 ms) tcp{client}: 0xf3e3758
2020-11-17 15:45:39.715   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... now: {"grpsplfxbw":{"evaledge":{"f":1605524998,"t":1605524998},"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplf... #hooks:0
2020-11-17 15:45:39.719   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.lastacc was: 1605627571 now: 1605627939 #hooks:0
2020-11-17 15:45:39.722   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {} now: {} #hooks:0
2020-11-17 15:45:39.724   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {} now: {"ctx11.scgrpv8xitp8.true":{"starttime":1605627939,"context":11,"scene":"grpv8xitp8.true","taskid":"ctx11.scgrpv8xi... #hooks:0
2020-11-17 15:45:39.727   luup_log:10: Reactor: "Reactor Sensor 1" (#11) Performing "Device Action" ("grpv8xitp8.true" group 1 step 1)
2020-11-17 15:45:39.729   luup.call_action:: 10165.urn:upnp-org:serviceId:SwitchPower1.SetTarget 
2020-11-17 15:45:39.731   luup.call_action:: action will be handled by parent: 5
2020-11-17 15:45:39.732   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {"ctx11.scgrpv8xitp8.true":{"starttime":1605627939,"context":11,"scene":"grpv8xitp8.true","taskid":"ctx11.scgrpv8xi... now: {"ctx11.scgrpv8xitp8.true":{"starttime":1605627939,"context":11,"scene":"grpv8xitp8.true","taskid":"ctx11.scgrpv8xi... #hooks:0
2020-11-17 15:45:39.735   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {"ctx11.scgrpv8xitp8.true":{"starttime":1605627939,"context":11,"scene":"grpv8xitp8.true","taskid":"ctx11.scgrpv8xi... now: {} #hooks:0
2020-11-17 15:45:39.736   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorGroup.GroupStatus_grpv8xitp8 was: 0 now: 1 #hooks:0
2020-11-17 15:45:39.738   luup.variable_set:: 11.urn:toggledbits-com:se

                  a post request

                  :10.738   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296261179&Timeout=60&MinimumDelay=1500&_=1605627660009 HTTP/1.1 tcp{client}: 0xf5f46e0
2020-11-17 15:48:28.610   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... now: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... #hooks:0
2020-11-17 15:48:28.614   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.lastacc was: 1605628086 now: 1605628108 #hooks:0
2020-11-17 15:48:28.615   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.Message was: Not tripped now: Not tripped #hooks:0
2020-11-17 15:48:28.644   luup.variable_set:: 10090.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1605628088 now: 1605628108 #hooks:0
2020-11-17 15:48:29.084   openLuup.server:: request completed (69817 bytes, 5 chunks, 18345 ms) tcp{client}: 0xf5f46e0
2020-11-17 15:48:30.151   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296261184&Timeout=60&MinimumDelay=1500&_=1605627660010 HTTP/1.1 tcp{client}: 0xf5f46e0
2020-11-17 15:48:48.627   luup.variable_set:: 10090.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1605628108 now: 1605628128 #hooks:0
2020-11-17 15:48:48.745   openLuup.server:: request completed (33122 bytes, 3 chunks, 18590 ms) tcp{client}: 0xf5f46e0
2020-11-17 15:48:49.782   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=296261186&Timeout=60&MinimumDelay=1500&_=1605627660011 HTTP/1.1 tcp{client}: 0xf5f46e0
2020-11-17 15:48:55.201   openLuup.io.server:: HTTP:3480 connection from 192.168.1.10 tcp{client}: 0xf8bd6d8
2020-11-17 15:48:55.202   openLuup.server:: POST /data_request?id=action&DeviceNum=11&serviceId=urn:toggledbits-com:serviceId:ReactorSensor&action=SetVariable&VariableName=A_home&NewValue=0 HTTP/1.1 tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.203   luup.call_action:: 11.urn:toggledbits-com:serviceId:ReactorSensor.SetVariable 
2020-11-17 15:49:00.204   luup.call_action:: action will be handled by parent: 10
2020-11-17 15:49:00.217   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... now: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... #hooks:0
2020-11-17 15:49:00.222   openLuup.server:: error 'closed' sending 4 bytes to tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.223   openLuup.server:: ...only 0 bytes sent
2020-11-17 15:49:00.224   openLuup.server:: error 'closed' sending 137 bytes to tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.224   openLuup.server:: ...only 0 bytes sent
2020-11-17 15:49:00.225   openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.225   openLuup.server:: ...only 0 bytes sent
2020-11-17 15:49:00.226   openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.226   openLuup.server:: ...only 0 bytes sent
2020-11-17 15:49:00.227   openLuup.server:: request completed (137 bytes, 1 chunks, 23 ms) tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.228   openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0xf8bd6d8
2020-11-17 15:49:00.753   openLuup.server:: request completed (58975 bytes, 4 chunks, 10970 ms) tcp{client}: 0xf5f46e0
2020-11-17 15:49:01.682   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... now: {"grpsplfxbw":{"statestamp":1605524998,"stateedge":{"f":1605524998,"t":1605524998},"id":"grpsplfxbw","evalstamp":16... #hooks:0
2020-11-17 15:49:01.687   luup.variable_set:: 11.urn:toggledbits-com:serviceId:ReactorSensor.lastacc was: 1605628108 now: 1605628141 #hooks:0
2020-11-17 15:49:01.688   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {} now: {} #hooks:0
2020-11-17 15:49:01.689   luup.variable_set:: 10.urn:toggledbits-com:serviceId:Reactor.runscene was: {} now: {"ctx11.scgrpv8xitp8.true":{"starttime":1605628141,"context":11,"scene":"grpv8xitp8.true","taskid":"ctx11.scgrpv8xi... #hooks:0
2020-11-17 15:49:01.691   luup_log:10: Reactor: "Reactor Sensor 1" (#11) Performing "Device Action" ("grpv8xitp8.true" group 1 step 1)
2020-11-17 15:49:01.691   luup.call_action:: 10165.urn:upnp-org:serviceId:SwitchPower1.SetTa

                  the server page is code 200 for all items wxcept favicon which is 404.

                  /cgi-bin/cmh/sysinfo.sh 	3 	200
/openLuup 	63 	200
D_ALTUI.xml 	7 	200
D_AltAppStore.xml 	7 	200
D_BinaryLight1.xml 	8 	200
D_BluetoothNetwork.xml 	6 	200
D_BroadLink_Mk2_1.xml 	6 	200
D_DimmableLight1.xml 	6 	200
D_DimmableRGBLight1.xml 	6 	200
D_DoorSensor1.xml 	6 	200
D_EzloBridge.xml 	6 	200
D_GenericSensor1.xml 	6 	200
D_LightSensor1.xml 	6 	200
D_MotionSensor1.xml 	6 	200
D_PowerMeter1.xml 	9 	200
D_Reactor.xml 	6 	200
D_ReactorDeviceInfo.json 	5 	200
D_ReactorSensor.xml 	6 	200
D_SceneController1.xml 	9 	200
D_SiteSensor1.xml 	6 	200
D_SmartHomeHelper.xml 	6 	200
D_Switchboard1.xml 	6 	200
D_TemperatureSensor1.xml 	6 	200
D_VeraAlexa1.xml 	6 	200
D_VeraBridge.xml 	6 	200
D_WindowCovering1.xml 	6 	200
D_ZWaveNetwork.xml 	6 	200
D_ZigbeeNetwork.xml 	6 	200
D_openLuup.xml 	10 	200
J_ALTUI_api.js 	12 	200
J_ALTUI_iphone.js 	12 	200
J_ALTUI_jquery.ui.touch-punch.min.js 	12 	200
J_ALTUI_multibox.js 	12 	200
J_ALTUI_plugins.js 	12 	200
J_ALTUI_uimgr.js 	12 	200
J_ALTUI_upnp.js 	12 	200
J_ALTUI_utils.js 	12 	200
J_ALTUI_verabox.js 	12 	200
J_ReactorSensor_ALTUI.js 	12 	200
J_ReactorSensor_UI7.js 	3 	200
J_Reactor_ALTUI.js 	12 	200
J_SiteSensor1_ALTUI.js 	12 	200
S_HaDevice1.xml 	1 	200
S_ReactorSensor.xml 	1 	200
S_SecuritySensor1.xml 	1 	200
S_SwitchPower1.xml 	1 	200
favicon.ico 	5 	404
icons/AltAppStore.svg 	7 	200
icons/VeraBridge.svg 	5 	200
icons/dimmable_light_10.png 	3 	200
icons/dimmable_light_100.png 	1 	200
icons/dimmable_light_20.png 	1 	200
icons/dimmable_light_50.png 	1 	200
icons/dimmable_light_off.png 	17 	200
icons/door_window_untripped.png 	15 	200
icons/light_sensor_default.png 	13 	200
icons/meter_default.png 	16 	200
icons/motion_sensor_tripped.png 	11 	200
icons/motion_sensor_untripped.png 	13 	200
icons/openLuup.svg 	66 	200
icons/switch_off.png 	14 	200
icons/switch_on.png 	13 	200
icons/temperature_sensor_default.png 	15 	200
icons/window_covering_10.png 	13 	200
icons/zwave_default.png 	15 	200
id=action 	807 	200
id=actions 	15 	200
id=lr_ALTUI_Handler 	36 	200
id=lr_ALTUI_LuaRunHandler 	154 	200
id=lr_HTTP_VeraBridgeMirror_192.168.1.11 	0 	
id=lr_Reactor 	24 	200
id=lr_SiteSensor 	0 	
id=lr_Switchboard 	0 	
id=lu_action 	2 	200
id=lu_status2 	2158 	200
id=scene 	1 	200
id=sdata 	9 	200
id=status 	3 	200
id=user_data 	13 	200
id=variableget 	16 	200
id=variableset 	12 	200
w3.css 	60 	200

                  having troble with this forum, not allowing image upload.

                  akbooer 1 Reply Last reply Reply Quote 0
                  • akbooer
                    akbooer @Elcid last edited by

                    @elcid said in Delay in luup requests:

                    having troble with this forum, not allowing image upload.

                    ...need to flag this to @DesT

                    DesT 1 Reply Last reply Reply Quote 0
                    • Elcid
                      Elcid last edited by

                      Automate is generating the requests when phone leaves home wifi.

                      1 Reply Last reply Reply Quote 0
                      • akbooer
                        akbooer last edited by akbooer

                        ...so it looks like Automate doesn't like chunked responses to the POST request.

                        The logs are a bit misleading, because action requests are processed asynchronously as jobs, so things don't always appear in the order that you might expect.. The timeouts should precede the action execution, and they are, almost definitely, what is delaying it.

                        1 Reply Last reply Reply Quote 0
                        • Elcid
                          Elcid last edited by

                          Ok i will have to edit my automate http request forwarder so i can specify request type in the payload. i.e post,get,put,etc

                          1 Reply Last reply Reply Quote 0
                          • DesT
                            DesT @akbooer last edited by

                            @akbooer said in Delay in luup requests:

                            @elcid said in Delay in luup requests:

                            having troble with this forum, not allowing image upload.

                            ...need to flag this to @DesT

                            Are you still having an issue ?

                            1 Reply Last reply Reply Quote 0
                            • Elcid
                              Elcid last edited by

                              @DesT
                              ye.
                              seems certain buttons are working.
                              none of the buttons/icons on reply page.
                              the 4 black icons to left of reply, above quick reply input.
                              Also the context menu chevron on the reply button/icon.
                              i can not edit or delete a post either.

                              1 Reply Last reply Reply Quote 0
                              • Elcid
                                Elcid last edited by

                                Dark mode has disappeared and there is no longer an icon in the title bar.

                                1 Reply Last reply Reply Quote 0
                                • Elcid
                                  Elcid last edited by

                                  Still not working for me @DesT

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post

                                  Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                                  Powered by NodeBB | Contributors
                                  Hosted freely by PointPub Media Communications Inc. | Contact us