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
Truncated web pages using wireguard over long distances
-
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.
-
I’m no network expert, but I do note that openLuup uses chunked transfers for large amounts of data. I do, very occasionally, see the odd socket not ready error even on a LAN. This proved very hard to investigate, but I recall it being deeply embedded in issues within the Luasocket module. This doesn’t help you, but it begins to nudge my memory about the internal workings.
There are a couple of timeout parameters (something else which Luasocket is not very good at) which could be played with. I’ll take a look and get back on this.
-
The openLuup HTTP server has some user-configurable parameters:
{ Backlog = 2000, ChunkedLength = 16000, CloseIdleSocketAfter = 90, Port = 3480, SelectWait = 0.1 }These can be changed with code in Lua Startup. The obvious one to try is SelectWait, but ChunkedLength might be relevant too. I'd suggest trying waits up to, say, a few seconds, and halving or doubling the chunk length.
Curiously, the syntax I'd recommend is
luup.attr_get "openLuup.HTTP" .SelectWait = 0.5But, equally, something like:
luup.attr_set("openLuup.HTTP.SelectWait", 0.5)should work too (the difference is whether the parameter is stored as a string or a number.)
There are other things to play with, but more deeply embedded. However, this indicates something a bit fragile somewhere along the line.
-
I looked at the ping times I was getting to remote servers using the likes of speedtest.net etc
On one speed tester I was getting pings arounf 250 msec, on another about 490 msec.
To send a message around half the world and back takes:
40075/300000=136 msecSo put in a few indirect cable runs and misc switches & buffers (but hopefully no satellites) then you can imagine ping times can get rather high. Window's TeamViewer is definately a bit laggy.
So inserted this into the start up code and then restarted openLuup:
luup.attr_set("openLuup.HTTP.SelectWait", 0.5)
and it all started working - so for the log example above I now get:
2023-09-06 21:30:13.155 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559b738498 2023-09-06 21:30:13.156 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}: 0x559b738498 2023-09-06 21:30:13.158 luup_log:6: DataGraph: drawing mode: connected, draw nulls as: null 2023-09-06 21:30:13.168 luup_log:6: DataGraph: Whisper query: CPU = 10.703 mS for 2016 points 2023-09-06 21:30:13.184 luup_log:6: DataGraph: Whisper query: CPU = 10.810 mS for 2016 points 2023-09-06 21:30:13.197 luup_log:6: DataGraph: Whisper query: CPU = 10.616 mS for 2016 points 2023-09-06 21:30:13.209 luup_log:6: DataGraph: Whisper query: CPU = 10.168 mS for 2016 points 2023-09-06 21:30:13.222 luup_log:6: DataGraph: Whisper query: CPU = 9.872 mS for 2016 points 2023-09-06 21:30:13.234 luup_log:6: DataGraph: Whisper query: CPU = 9.746 mS for 2016 points 2023-09-06 21:30:13.299 luup_log:6: visualization: LineChart(2016x7) 196kB in 60mS 2023-09-06 21:30:13.299 luup_log:6: DataGraph: render: CPU = 59.805 mS for 6x2016=12096 points 2023-09-06 21:30:14.086 openLuup.server:: request completed (196300 bytes, 13 chunks, 929 ms) tcp{client}: 0x559b738498Not sure what the optimum value for the delay should be - I'm not keen to mess around with it remotely. Does the above log suggest a value? Or this log below:
Here's AltUI being loaded:
2023-09-06 21:49:23.723 luup.variable_set:: 10071.urn:micasaverde-com:serviceId:ZWaveNetwork1.LastPollSuccess was: 1694000093 now: 1694000963 #hooks:0 2023-09-06 21:49:23.836 openLuup.server:: request completed (6975 bytes, 1 chunks, 1700 ms) tcp{client}: 0x559aa2ee28 2023-09-06 21:49:23.957 openLuup.server:: request completed (6975 bytes, 1 chunks, 1146 ms) tcp{client}: 0x559bb50cb8 2023-09-06 21:49:24.217 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748913&Timeout=60&MinimumDelay=1500&_=1694000029638 HTTP/1.1 tcp{client}: 0x559aa2ee28 2023-09-06 21:49:24.979 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748913&Timeout=60&MinimumDelay=1500&_=1692128444563 HTTP/1.1 tcp{client}: 0x559bb50cb8 2023-09-06 21:49:25.158 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x559aa2ee28 2023-09-06 21:49:25.428 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559b19a458 2023-09-06 21:49:25.430 openLuup.server:: GET /data_request?id=lr_ALTUI_Handler&command=home HTTP/1.1 tcp{client}: 0x559b19a458 2023-09-06 21:49:25.449 openLuup.server:: request completed (19761 bytes, 2 chunks, 19 ms) tcp{client}: 0x559b19a458 2023-09-06 21:49:25.951 openLuup.server:: GET /J_ALTUI_jquery.ui.touch-punch.min.js HTTP/1.1 tcp{client}: 0x559b19a458 2023-09-06 21:49:26.210 openLuup.server:: request completed (31597 bytes, 2 chunks, 258 ms) tcp{client}: 0x559b19a458 2023-09-06 21:49:26.221 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559c240428 2023-09-06 21:49:26.222 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559a9b66a8 2023-09-06 21:49:26.222 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559a49aec8 2023-09-06 21:49:26.222 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559bb54098 2023-09-06 21:49:26.223 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:26.224 openLuup.server:: GET /J_ALTUI_utils.js HTTP/1.1 tcp{client}: 0x559c240428 2023-09-06 21:49:26.970 openLuup.server:: request completed (202128 bytes, 13 chunks, 745 ms) tcp{client}: 0x559c240428 2023-09-06 21:49:26.970 openLuup.server:: GET /J_ALTUI_api.js HTTP/1.1 tcp{client}: 0x559a9b66a8 2023-09-06 21:49:27.498 openLuup.server:: request completed (55724 bytes, 4 chunks, 527 ms) tcp{client}: 0x559a9b66a8 2023-09-06 21:49:27.499 openLuup.server:: GET /J_ALTUI_upnp.js HTTP/1.1 tcp{client}: 0x559a49aec8 2023-09-06 21:49:27.760 openLuup.server:: request completed (22906 bytes, 2 chunks, 261 ms) tcp{client}: 0x559a49aec8 2023-09-06 21:49:27.761 openLuup.server:: GET /J_ALTUI_verabox.js HTTP/1.1 tcp{client}: 0x559bb54098 2023-09-06 21:49:28.500 openLuup.server:: request completed (97222 bytes, 7 chunks, 739 ms) tcp{client}: 0x559bb54098 2023-09-06 21:49:28.501 openLuup.server:: GET /J_ALTUI_multibox.js HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:28.753 openLuup.server:: request completed (40237 bytes, 3 chunks, 251 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:28.764 openLuup.server:: GET /J_ALTUI_plugins.js HTTP/1.1 tcp{client}: 0x559b19a458 2023-09-06 21:49:29.532 openLuup.server:: request completed (231053 bytes, 15 chunks, 767 ms) tcp{client}: 0x559b19a458 2023-09-06 21:49:29.532 openLuup.server:: GET /J_ALTUI_iphone.js HTTP/1.1 tcp{client}: 0x559c240428 2023-09-06 21:49:29.535 openLuup.server:: request completed (22770 bytes, 2 chunks, 1 ms) tcp{client}: 0x559c240428 2023-09-06 21:49:29.536 openLuup.server:: GET /J_ALTUI_uimgr.js HTTP/1.1 tcp{client}: 0x559a9b66a8 2023-09-06 21:49:30.827 openLuup.server:: request completed (717146 bytes, 45 chunks, 1291 ms) tcp{client}: 0x559a9b66a8 2023-09-06 21:49:30.840 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1692128444564 HTTP/1.1 tcp{client}: 0x559b6dee78 2023-09-06 21:49:30.943 openLuup.server:: request completed (1 bytes, 1 chunks, 102 ms) tcp{client}: 0x559b6dee78 2023-09-06 21:49:31.281 openLuup.server:: GET /favicon.ico HTTP/1.1 tcp{client}: 0x559b19a458 2023-09-06 21:49:31.283 openLuup.server:: request completed (15086 bytes, 0 chunks, 1 ms) tcp{client}: 0x559b19a458 2023-09-06 21:49:31.284 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x559b19a458 2023-09-06 21:49:31.451 openLuup.server:: GET /data_request?id=user_data&output_format=json&DataVersion=undefined&_=1694000965692 HTTP/1.1 tcp{client}: 0x559a9b66a8 2023-09-06 21:49:32.569 openLuup.server:: request completed (1560409 bytes, 98 chunks, 1117 ms) tcp{client}: 0x559a9b66a8 2023-09-06 21:49:34.392 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x5599e944b8 2023-09-06 21:49:34.392 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x559a7b2ba8 2023-09-06 21:49:34.392 openLuup.server:: GET /luvd/D_GenericZigbeeDevice.xml HTTP/1.1 tcp{client}: 0x559c240428 2023-09-06 21:49:34.393 openLuup.server:: request completed (299 bytes, 0 chunks, 0 ms) tcp{client}: 0x559c240428 2023-09-06 21:49:34.393 openLuup.server:: GET /luvd/D_openLuup.xml HTTP/1.1 tcp{client}: 0x559a9b66a8 2023-09-06 21:49:34.393 openLuup.server:: request completed (754 bytes, 0 chunks, 0 ms) tcp{client}: 0x559a9b66a8 2023-09-06 21:49:34.393 openLuup.server:: GET /luvd/D_InfoViewer1.xml HTTP/1.1 tcp{client}: 0x559a49aec8 2023-09-06 21:49:34.393 openLuup.servlet:: file not found:D_InfoViewer1.xml 2023-09-06 21:49:34.394 openLuup.server:: request completed (132 bytes, 0 chunks, 0 ms) tcp{client}: 0x559a49aec8 2023-09-06 21:49:34.394 openLuup.server:: GET /luvd/D_BinaryLight1.xml HTTP/1.1 tcp{client}: 0x559bb54098 2023-09-06 21:49:34.394 openLuup.server:: request completed (1031 bytes, 0 chunks, 0 ms) tcp{client}: 0x559bb54098 2023-09-06 21:49:34.394 openLuup.server:: GET /luvd/D_SmartHomeHelper.xml HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:34.394 openLuup.servlet:: file not found:D_SmartHomeHelper.xml 2023-09-06 21:49:34.395 openLuup.server:: request completed (136 bytes, 0 chunks, 0 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:34.404 openLuup.server:: GET /data_request?id=lr_ALTUI_Handler&command=getCustomPages&_=1694000965693 HTTP/1.1 tcp{client}: 0x5599e944b8 2023-09-06 21:49:34.405 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x559c240428 2023-09-06 21:49:34.405 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x559a9b66a8 2023-09-06 21:49:34.405 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x559bb54098 2023-09-06 21:49:34.405 openLuup.server:: GET /data_request?id=lr_ALTUI_Handler&command=getWorkflows&_=1694000965694 HTTP/1.1 tcp{client}: 0x559a7b2ba8 2023-09-06 21:49:34.507 openLuup.server:: request completed (2 bytes, 1 chunks, 102 ms) tcp{client}: 0x5599e944b8 2023-09-06 21:49:34.507 openLuup.server:: request completed (2 bytes, 1 chunks, 101 ms) tcp{client}: 0x559a7b2ba8 2023-09-06 21:49:34.807 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1694000965697 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:34.908 openLuup.server:: request completed (1 bytes, 1 chunks, 101 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:35.613 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=1&Timeout=60&MinimumDelay=1500&_=1694000965698 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:37.431 openLuup.server:: request completed (882908 bytes, 56 chunks, 1817 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:37.442 luup.variable_set:: 10191.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1694000916 now: 1694000976 #hooks:0 2023-09-06 21:49:37.454 openLuup.server:: request completed (6972 bytes, 1 chunks, 12474 ms) tcp{client}: 0x559bb50cb8 2023-09-06 21:49:37.982 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748913&Timeout=60&MinimumDelay=1500&_=1694000965699 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:38.095 openLuup.server:: request completed (6972 bytes, 1 chunks, 112 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:38.468 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748915&Timeout=60&MinimumDelay=1500&_=1694000965700 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:38.486 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748915&Timeout=60&MinimumDelay=1500&_=1692128444565 HTTP/1.1 tcp{client}: 0x559bb50cb8 2023-09-06 21:49:39.406 luup.zigbee2mqtt:0: Topic ignored: zigbee2mqtt/bridge/logging 2023-09-06 21:49:39.733 openLuup.server:: request completed (7069 bytes, 1 chunks, 1264 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:39.744 openLuup.server:: request completed (7069 bytes, 1 chunks, 1257 ms) tcp{client}: 0x559bb50cb8 2023-09-06 21:49:40.130 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748918&Timeout=60&MinimumDelay=1500&_=1694000965701 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:40.771 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748918&Timeout=60&MinimumDelay=1500&_=1692128444566 HTTP/1.1 tcp{client}: 0x559bb50cb8 2023-09-06 21:49:41.819 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1692128444567 HTTP/1.1 tcp{client}: 0x559b6dee78 2023-09-06 21:49:41.922 openLuup.server:: request completed (1 bytes, 1 chunks, 102 ms) tcp{client}: 0x559b6dee78 2023-09-06 21:49:45.188 openLuup.server:: GET /data_request?id=variableget&DeviceNum=0&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&Variable=Mode&_=1694000965702 HTTP/1.1 tcp{client}: 0x559a49aec8 2023-09-06 21:49:45.292 openLuup.server:: request completed (1 bytes, 1 chunks, 102 ms) tcp{client}: 0x559a49aec8 2023-09-06 21:49:48.690 luup.variable_set:: 10224.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1694000688 now: 1694000988 #hooks:0 2023-09-06 21:49:48.702 openLuup.server:: request completed (6972 bytes, 1 chunks, 7930 ms) tcp{client}: 0x559bb50cb8 2023-09-06 21:49:49.127 openLuup.server:: request completed (6972 bytes, 1 chunks, 8996 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:49.725 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748920&Timeout=60&MinimumDelay=1500&_=1692128444568 HTTP/1.1 tcp{client}: 0x559bb50cb8 2023-09-06 21:49:50.410 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748920&Timeout=60&MinimumDelay=1500&_=1694000965703 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:51.623 luup.variable_set:: 10149.urn:micasaverde-com:serviceId:EnergyMetering1.KWHReading was: 1694000944 now: 1694000991 #hooks:0 2023-09-06 21:49:52.049 openLuup.server:: request completed (6972 bytes, 1 chunks, 2323 ms) tcp{client}: 0x559bb50cb8 2023-09-06 21:49:52.060 openLuup.server:: request completed (6972 bytes, 1 chunks, 1649 ms) tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:52.428 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=999748922&Timeout=60&MinimumDelay=1500&_=1694000965704 HTTP/1.1 tcp{client}: 0x559bf9b2d8 2023-09-06 21:49:52.460 openLuup.server:: GET /console?page=log HTTP/1.1 tcp{client}: 0x559bb50cb8Anyway good result. I can now control anything that needs controlling. Ak -thanks for the help once again.
