Sorry if this has been covered before, just curious why triggers in openluup are not consistent..
I looked at a scene i’d created a while back via ALTUI using the Console view and noticed it didn’t show any Triggers, which was strange as it was my main front door event 🙂 . So I added the door tripped trigger again, but I’ve just noticed I now how two tiggers using this view.
25bfe00a-d63e-4dc1-a501-23e779c64379-image.png
In ALTUI it shows this.
AK. Was doing an openLuup install and the installer errored with:
openLuup_install 2019.02.15 @akbooer getting openLuup version tar file from GitHub branch master... un-zipping download files... getting dkjson.lua... lua5.1: openLuup_install.lua:45: GitHub download failed with code 500 stack traceback: [C]: in function 'assert' openLuup_install.lua:45: in main chunk [C]: ?The installer code was executing this URL:
http://dkolf.de/src/dkjson-lua.fsl/raw/dkjson.lua?name=16cbc26080996d9da827df42cb0844a25518eeb3Running it manually gives:
dkolf.de The script could not be run error-free. Please check your error log file for the exact error message. You can find this in the KIS under "Product Management > *YOUR PRODUCT* > *CONFYGUAR* > Logfiles". Further information can be found in our FAQ. The script could not be executed correctly. Please refer to your error log for details about this error. You find it in your KIS under item "Product Admin > *YOUR PRODUCT* > *CONFIGURE* > Logfiles". Further information can also be found in our FAQ.I'm thinking the dkjson code URL has been changed. On dkolf.de there is a download link:
http://dkolf.de/dkjson-lua/dkjson-2.8.luaand dkjson code also seems to be in GitHub (I presume this is the same code?):
https://github.com/LuaDist/dkjson/blob/master/dkjson.luaI'm don't know what dkolf.de looked like previously but I do see the dkjson code has been updated as of 2024-06-17. Hope this helps.
Oh - and by the way the dkjson.lua file seems to have been downloaded OK by the installer - error or no error, so go figure.
It’s been a while since I looked at openLuup as it had been running nicely and quietly in the background doing some basic tasks. With my VeraPlus looking like it’s finally succumbing to old age, I want to shift a number of the global module I have over to openLuup.
To do this, I have added the files (example would be xxpushover.lua to the cmh-ludl folder and the following to the startup
require “xxpushover”
The xxpushover.lua file itself starts with the following..
module("xxpushover", package.seeall)
And I always have a line in these files to allow me to check it’s been read in the start up related logs, which in this case it is..
The challenge I’m having is that when I try to call any of the functions within the module, it returns the following error..
"[string "ALTUI - LuaRunHandler"]:1: attempt to index global 'xxpushover' (a nil value)”
I’m no doubt missing something obvious, can anyone help me find out what it is ? Many thanks
Currently I have some Whisper files used by DataYours that been working well for ages and do what I want.
One of the files is called Watts_L1.d.wsp and uses this retention from "storage_schemas_conf" in openLuup file virtualfilesystem.lua:
[day] pattern = \.d$ retentions = 1m:1dInside the actual "Watts_L1.d.wsp" file is a header like so:
1, 86400, 0, 1 84, 60, 1440The 1, 86400 is one minute & one day (in minutes) as per the retention listed above. As a side issue I would like to know what the other header values mean ie what's the syntax here?
New challenge: I now have three Shelly variables named:
em1/0/act_power
em1/1/act_power
em1/2/act_power
with a device ID of "10006" and a SID of "shellypro3em"
And I would like to plot them using the Historian, just like I do with Watts_L1.d.wsp in DataYours. So I need a file in the history directory for the data. So I looked at doing this:
local whisper = require "openLuup.whisper" -- Syntax: history/0.deviceNumber.shortServiceId.variableName local filename = "history/0.10006.shellypro3em.em1/0/act_power.wsp" local archives = "1m:1d" whisper.create (filename,archives,0)Problem is that the variable names contains forward slashes, which are invalid filename characters. What to do?
Also should the retentions now be (to suit the latest openLuup software)?:
local archives = "1m:1d,10m:7d,1h:30d,3h:1y,1d:10y"Also "shellypro3em" is not a "shortServiceID" as per those listed in "servertables.lua". So can "shellypro3em" be used instead? ie can both short and long service IDs be used in the above call to whisper.create?
To try and minimized the frequency of writing to the SD card I want to move these log files to a RAM drive, like I already do with /var/log. Is there an 'official' way of doing this?
_John.
A list of openLuup releases including the latest developments…
master – stable, and infrequently updated, development – latest updates and bug fixes, testing – use only when advised!A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine.
Now rehosted at https://community.ezlo.com/t/openluup-running-unmodified-plugins-on-any-machine/187412
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.
Hoping you could tell us a bit about your experiences with ZWaveJS and MQTT.
Akbooer: it would be good if openLuup was added to the awesome mqtt resources list.
How to contribute is described here.
Looks like the GetSolarCoords() doesn't return the correct results. Right Ascension (RA) and
Declination (DEC) look OK. They presumably must be, as I have a light that goes on at sunset at the correct time for years.
Altitude and Azimuth look incorrect. They both have the hour angle in common, so I'm wondering if it's incorrect and hence the sidereal time. Should be able to convert the angle to hours and check it against this clock:
The formula used looks like Compute sidereal time on this page. Might be some mix up between JD2000 that has a 12 hour offset. Could also be some issue with the hour angle.
I'm assuming all Right Ascension (RA) and
Declination (DEC) are degrees plus & minus from north.
Likewise Altitude (ALT) and Azimuth (AZ) are in degrees?
Bit of caution: I haven't looked at this too closely, so may be barking up the wrong tree. It probably doesn't help living near Greenwich.
This site may also be helpful.
PS did you have a look at the link in my last PM?
Set up:
a) Many many many many kms from home: laptop connected to modem router. Router running wireguard client to create a virtual network.
b) Home: modem router running wireguard server. openLuup pi4 connect to router and also a PC and other stuff, etc.
The problem: When accessing charts, AltUI or the openLupp console the web pages are returned OK up to the point where they are truncated and therefore fail to display anything useful.
Note this all works fine over short distances eg around a major city (I tested it) but not seemingly at world wide distances. ie network delays seem to be the issue here? Windows TeamViewer works fine overy the exact same network/wireguard set up. That's how I was able to get the openLuup logs shown below.
Here is any example of openLuup trying to return a chart:
2023-09-04 21:31:20.463 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x55aed35038 2023-09-04 21:31:20.464 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=316885191&Timeout=60&MinimumDelay=1500&_=1692128389970 HTTP/1.1 tcp{client}: 0x55ae538348 2023-09-04 21:31:20.465 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=316885191&Timeout=60&MinimumDelay=1500&_=1692129024374 HTTP/1.1 tcp{client}: 0x55addbe1e8 2023-09-04 21:31:20.477 openLuup.server:: GET /data_request?id=lr_render&target={temp_first_floor.w,temp_ground_floor.w,temp_back_wall_of_office.w,temp_inside_roof.w,temp_jps_bedrm_north.w,temp_outside.w}&title=Temperatures&height=750&from=-y&yMin=0&yMax=40 HTTP/1.1 tcp{client}: 0x55aed35038 2023-09-04 21:31:20.478 luup_log:6: DataGraph: drawing mode: connected, draw nulls as: null 2023-09-04 21:31:20.502 luup_log:6: DataGraph: Whisper query: CPU = 23.122 mS for 2016 points 2023-09-04 21:31:20.532 luup_log:6: DataGraph: Whisper query: CPU = 22.952 mS for 2016 points 2023-09-04 21:31:20.561 luup_log:6: DataGraph: Whisper query: CPU = 22.738 mS for 2016 points 2023-09-04 21:31:20.575 luup_log:6: DataGraph: Whisper query: CPU = 9.547 mS for 2016 points 2023-09-04 21:31:20.587 luup_log:6: DataGraph: Whisper query: CPU = 9.569 mS for 2016 points 2023-09-04 21:31:20.598 luup_log:6: DataGraph: Whisper query: CPU = 9.299 mS for 2016 points 2023-09-04 21:31:20.654 luup_log:6: visualization: LineChart(2016x7) 196kB in 51mS 2023-09-04 21:31:20.655 luup_log:6: DataGraph: render: CPU = 51.219 mS for 6x2016=12096 points 2023-09-04 21:31:20.755 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:20.855 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.037 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.138 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.332 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.432 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 196367 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 144000 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 0 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 0 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: request completed (196367 bytes, 10 chunks, 1030 ms) tcp{client}: 0x55aed35038 2023-09-04 21:31:21.517 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55aed35038 2023-09-04 21:31:22.824 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x55aea22c88Re: socket.select() not ready to send
Is there some sort of timeout I change; to see if this can make this work?
Note that openLuup is still running everything flawlessly for ages now, including the more recent addtions of ZigBee stuff. Much appreciated.
Hi @akbooer
Just bringing this over as suggested..
I’ve started to use the console view a lot more, mainly for it’s look and simplicity , but I noticed it does not do any live updates compared to ALTUI, you have to do a full browser reload. Is that by design, or is mine not working?
Also if I want to go strait to the console view, rather than into ALTUI, I recall seeing something abut altering that in the guide by for the life of me I can’t find it. Is it possible to do, if so how would I do that..
You suggested this was something you were looking at ? Also you said You don't need a "full browser reload", just click on the display menu item to refresh the screen. - what do you mean by `display menu?
Very minor issue: was messing about renaming a few rooms and ended up with a room being listed twice. One with the room's contents and the other with no room contents.
It simply turns out one room name had a trailing space. It is possible in both AltUI and the openLuup console to create a room name with a trailing space. Once having done so chaos then ensues, as the rooms are not necessarily treated as different and become difficult to manipulate.
Just need to trim white space off room names. Haven't tested if it's possible to add in leading spaces. That may also be possible.
Hey guys...
Long time... 😉
Since my first day with Vera, I'm using RulesEngine from @vosmont to handle complex rules that will do something based on multiple condition base on "true/false" and also based on time.
Do you think I will be able to do that directly with LUA in openLuup ?
For example..
IF bedroom-motion1 is not detecting motion for 15 minutes
AND
IF bedroom-motion2 is not detecting motion for 15 minutes
AND
IF current-time is between 6am and 11pm
AND
IF binary-light1 is OFF
AND
IF binary-light2 is OFF
THEN
execute LUA code
WAIT 2 minute
execute LUA code
BUT IF any "conditions" failed while in the "THEN" , It need to stop...
I currently have around 60 rules like that 😞
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?
GitHub - dbochicchio/vera-VirtualDevices: Virtual HTTP Devices plug-in for Vera and openLuup
GitHub - dbochicchio/vera-VirtualDevices: Virtual HTTP Devices plug-in for Vera and openLuup
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.
Hi
Just wondering if it’s possible when writing plugins to set if the text shown via DisplayLine1/2 can be left, right or centre aligned ?
Bit of an odd one this:
Bare metal install on Debian Bullseye (Intel NUC)
I've noticed when travelling, I connect to my L2TP VPN and I cannot get AltUI to update. I just get 'Waiting Initial Data'
Specifically this is in Chrome:
Version 108.0.5359.94 (Official Build) (x86_64)
In Chrome I can access and control everything via the Openluup console.
In Chrome I can also access and control everything via the Z-Wave expert UI and Z-Wave UI
In Safari I get a more complete view of AltUI but loads of errors along the lines of:
the module or function ALTUI_PluginDisplays.drawBinaryLight does not exist, check your configuration
Homewave on my iOS devices is fine across the same VPN config,
I can ssh into all my servers
Not a huge issue, just curious if anyone has any thoughts of what I might tweak to resolve it?
(FWIW I also access my IMAP and SMTP servers across the same VPN with no issues, as well as remote desktop. Also MS Reactor on the same host as Openluup)
TIA for any thoughts
C
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
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
Delay in luup requests
-
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 -
-
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?
-
-
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:sea 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.SetTathe 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 200having troble with this forum, not allowing image upload.
-
-
...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.
-
@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 ?
