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
OpenLuup unavailable
-
This error counting in the log is a great idea. It triggered my OCD tendencies and got me to track down a couple of typos along with loading the upnp proxy server... not as a plugin but as a systemd service to get rid of the sonos errors in the log.
Suggestion @akbooer: Don't isolate the lines showing errors. Instead it would be nice if they could be highlighted or colored on the log visualization page.
-
@mrfarmer said in OpenLuup unavailable:
The Ezlo json responses include the word error even is there is none
What does one of those responses actually look like (around the part that says error.). I could search for just an isolated word...
-
-
Working great! Thanks for the quick turnaround.
Something very strange is going on though. Without the MQTT server enabled at all, I have observed the same problem as @ArcherS twice today. The only major change I made was to enable the LuaUPnP proxy for the sonos app. Prior to this, I have had no memory of openLuup hanging this way for quite some time, probably a year. Looked at the logs and found nothing useful. I seem to remember having some strange problems with the luasocket the last time I had seen this while trying to get fix another plugin. I will keep an eye on this.
The only errors I am currently seeing look like this:
openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x7f49d5fe98f8Whereby it seems like openLuup is trying to send bytes to an incoming tcp connection which has been closed by the client. I have several such servers sending http commands to openLuup.
Link to the previous thread about it https://smarthome.community/topic/105/openluup-hangs
-
Thanks for raising this issue... I nearly missed it because you edited a previous post rather than started a new one.
We need to nail down this issue, which is clearly genuine, but infrequent and difficult to replicate at will. It’s good to note that it’s not apparently connected with MQTT. The strange thing is that, with very minor exceptions, none of the major server modules have been changed for over a year. Are we all just stressing our system a bit more these days?
I have introduced some extra socket checks specifically into the MQTT code, so my first line of attack will be to retrofit these to HTTP transactions. This gets me thinking again that it would be great to use a real HTTP server, rather than one I have written myself. But it’s a bit daunting to consider the installation and configuration needed to do that. Ideally, I’d need something that supports the WSAPI CGI interface. Apache does, as, I believe, does lighttpd.
-
Hi AK,
No longer seeing the high error count, great work as always.
What I notice is that the longest gaps are always for a poll to one of my Vera's even though that is set for async poll (running on Debian PI cone VM). I do not see that on my main V20.4.30 running on a PI3 with Debian.
Cheers Rene
-
@akbooer I have have the system up and running over two nights in a row without doing any changes and without any crashes. Today at approx 12:24 the system however crashed again. I think it is no single device that causes the crash but instead that a socket overload or something similar.
The current setup I have for the sensors pushing data via http adds up to quite a lot of http requests, since one sensor can update a number of OpenLuup devices (approx foru to eight) at one occation. Mqtt will reduce this quite a lot since all data for that sensor will be in one message.
I will install v21.3.24 and see if anything changes.
When looking in the log a few minutes before the crash I can see the following in the log, don't know if this could give more clues.
... 2021-03-24 12:21:22.883 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=181&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=11.1 HTTP/1.1 tcp{client}: 0x557824e372d8 2021-03-24 12:21:22.883 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=183&id=variableset&serviceId=urn:micasaverde-com:serviceId:LightSensor1&Variable=CurrentLevel&Value=1181 HTTP/1.1 tcp{client}: 0x5578241755b8 2021-03-24 12:21:22.883 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=182&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=48.9 HTTP/1.1 tcp{client}: 0x5578246d66f8 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=180&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=0.7 HTTP/1.1 tcp{client}: 0x557825862ea8 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=184&id=variableset&serviceId=urn:micasaverde-com:serviceId:GenericSensor1&Variable=CurrentLevel&Value=1006.9 HTTP/1.1 tcp{client}: 0x557824e808c8 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=152&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=12.6 HTTP/1.1 tcp{client}: 0x5578254dba88 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=153&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=44.7 HTTP/1.1 tcp{client}: 0x557824553b88 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=173&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=14.7 HTTP/1.1 tcp{client}: 0x557825687348 2021-03-24 12:21:22.884 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=188&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=23.0 HTTP/1.1 tcp{client}: 0x557825adb228 2021-03-24 12:21:22.885 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=154&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=0.9 HTTP/1.1 tcp{client}: 0x557824a5b168 2021-03-24 12:21:22.885 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=151&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=11.5 HTTP/1.1 tcp{client}: 0x557823bcd248 2021-03-24 12:21:22.885 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=175&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=45.0 HTTP/1.1 tcp{client}: 0x5578255cb878 2021-03-24 12:21:22.885 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=189&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=29.7 HTTP/1.1 tcp{client}: 0x55782415ca68 2021-03-24 12:21:22.885 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=150&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=41.8 HTTP/1.1 tcp{client}: 0x557824fdc308 2021-03-24 12:21:22.886 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=174&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=2.9 HTTP/1.1 tcp{client}: 0x55782411d778 2021-03-24 12:21:22.886 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=190&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=2.7 HTTP/1.1 tcp{client}: 0x5578243ea368 2021-03-24 12:21:22.886 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=149&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=-1.1 HTTP/1.1 tcp{client}: 0x557824eed778 2021-03-24 12:21:22.886 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=164&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=8.5 HTTP/1.1 tcp{client}: 0x5578249a9f38 2021-03-24 12:21:22.887 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x5578245a37b8 2021-03-24 12:21:22.887 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x5578245a37b8 2021-03-24 12:21:22.887 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x5578245a37b8 2021-03-24 12:21:22.887 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x5578245a37b8 2021-03-24 12:21:22.887 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x5578245a37b8 2021-03-24 12:21:22.887 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x557824be7628 2021-03-24 12:21:22.887 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x557824be7628 2021-03-24 12:21:22.887 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An_fb/# tcp{client}: 0x557824be7628 2021-03-24 12:21:22.887 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An/# tcp{client}: 0x557824be7628 2021-03-24 12:21:22.887 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x557824be7628 ... 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824e372d8 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578241755b8 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578246d66f8 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557825862ea8 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824e808c8 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578254dba88 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824553b88 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557825687348 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557825adb228 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824a5b168 2021-03-24 12:21:22.928 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557823bcd248 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578255cb878 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55782415ca68 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824fdc308 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55782411d778 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578243ea368 2021-03-24 12:21:22.929 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824eed778 2021-03-24 12:21:22.930 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x557823c0f808 2021-03-24 12:21:22.930 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x557823c0f808 2021-03-24 12:21:22.930 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax/# tcp{client}: 0x557823c0f808 2021-03-24 12:21:22.930 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x557823c0f808 2021-03-24 12:21:22.930 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax_fb/# tcp{client}: 0x557823c0f808 2021-03-24 12:21:22.971 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578249a9f38 2021-03-24 12:21:23.001 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x5578247df8a8 2021-03-24 12:21:23.002 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x5578247df8a8 2021-03-24 12:21:23.002 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x5578247df8a8 2021-03-24 12:21:23.004 openLuup.mqtt:: TasmotaCO2Ax SUBSCRIBE to cmnd/TasmotaCO2Ax/# tcp{client}: 0x55782502f428 2021-03-24 12:21:23.004 openLuup.mqtt:: TasmotaCO2Ax SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55782502f428 2021-03-24 12:21:23.005 openLuup.mqtt:: TasmotaCO2Ax SUBSCRIBE to cmnd/TasmotaCO2Ax_fb/# tcp{client}: 0x55782502f428 2021-03-24 12:21:23.005 openLuup.mqtt:: TasmotaCO2An SUBSCRIBE to cmnd/TasmotaCO2An/# tcp{client}: 0x557825ca05a8 2021-03-24 12:21:23.006 openLuup.mqtt:: TasmotaCO2An SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x557825ca05a8 2021-03-24 12:21:23.006 openLuup.mqtt:: TasmotaCO2An SUBSCRIBE to cmnd/TasmotaCO2An_fb/# tcp{client}: 0x557825ca05a8 2021-03-24 12:21:23.020 openLuup.io.server:: HTTP:3480 connection from 192.168.1.53 tcp{client}: 0x557824728c98 ... 2021-03-24 12:24:27.723 openLuup.io.server:: HTTP:3480 connection from 192.168.1.54 tcp{client}: 0x5578254b0b78 2021-03-24 12:24:27.723 openLuup.io.server:: HTTP:3480 connection from 192.168.1.54 tcp{client}: 0x557824f80ef8 2021-03-24 12:24:27.723 openLuup.io.server:: HTTP:3480 connection from 192.168.1.51 tcp{client}: 0x557824f83988 2021-03-24 12:24:27.723 openLuup.io.server:: HTTP:3480 connection from 192.168.1.54 tcp{client}: 0x557824df10c8 2021-03-24 12:24:27.723 openLuup.io.server:: HTTP:3480 connection from 192.168.1.51 tcp{client}: 0x557824fb0048 2021-03-24 12:24:27.724 openLuup.io.server:: HTTP:3480 connection from 192.168.1.54 tcp{client}: 0x557824fb21e8 2021-03-24 12:24:27.724 openLuup.io.server:: HTTP:3480 connection from 192.168.1.51 tcp{client}: 0x557824e52928 2021-03-24 12:24:27.724 openLuup.io.server:: HTTP:3480 connection from 192.168.1.54 tcp{client}: 0x557824fd5f48 2021-03-24 12:24:27.724 openLuup.io.server:: HTTP:3480 connection from 192.168.1.52 tcp{client}: 0x557824fd7ff8 2021-03-24 12:24:27.724 openLuup.io.server:: HTTP:3480 connection from 192.168.1.52 tcp{client}: 0x5578241ee5a8 2021-03-24 12:24:27.725 openLuup.io.server:: HTTP:3480 connection from 192.168.1.55 tcp{client}: 0x557824d0f778 2021-03-24 12:24:27.725 openLuup.io.server:: HTTP:3480 connection from 192.168.1.52 tcp{client}: 0x557824d11828 2021-03-24 12:24:27.725 openLuup.io.server:: HTTP:3480 connection from 192.168.1.55 tcp{client}: 0x5578251ff6f8 2021-03-24 12:24:27.725 openLuup.io.server:: HTTP:3480 connection from 192.168.1.55 tcp{client}: 0x557825201b18 2021-03-24 12:24:27.726 openLuup.io.server:: HTTP:3480 connection from 192.168.1.50 tcp{client}: 0x55782562a688 2021-03-24 12:24:27.726 openLuup.io.server:: MQTT:1883 connection from 192.168.1.60 tcp{client}: 0x5578257d3ec8 2021-03-24 12:24:27.726 openLuup.io.server:: MQTT:1883 connection from 192.168.1.61 tcp{client}: 0x5578257d5f78 2021-03-24 12:24:27.727 openLuup.io.server:: MQTT:1883 connection from 192.168.1.62 tcp{client}: 0x5578252531e8 2021-03-24 12:24:27.728 luup_log:0: 50Mb, 2.1%cpu, 2.0days ... 2021-03-24 12:24:29.281 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=181&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=11.3 HTTP/1.1 tcp{client}: 0x5578254b0b78 2021-03-24 12:24:29.281 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=183&id=variableset&serviceId=urn:micasaverde-com:serviceId:LightSensor1&Variable=CurrentLevel&Value=1125 HTTP/1.1 tcp{client}: 0x557824f80ef8 2021-03-24 12:24:29.282 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=173&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=14.8 HTTP/1.1 tcp{client}: 0x557824f83988 2021-03-24 12:24:29.282 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=182&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=49.3 HTTP/1.1 tcp{client}: 0x557824df10c8 2021-03-24 12:24:29.282 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=175&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=45.0 HTTP/1.1 tcp{client}: 0x557824fb0048 2021-03-24 12:24:29.283 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=180&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=1.0 HTTP/1.1 tcp{client}: 0x557824fb21e8 2021-03-24 12:24:29.284 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=174&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=3.0 HTTP/1.1 tcp{client}: 0x557824e52928 2021-03-24 12:24:29.284 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=184&id=variableset&serviceId=urn:micasaverde-com:serviceId:GenericSensor1&Variable=CurrentLevel&Value=1006.8 HTTP/1.1 tcp{client}: 0x557824fd5f48 2021-03-24 12:24:29.285 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=188&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=23.9 HTTP/1.1 tcp{client}: 0x557824fd7ff8 2021-03-24 12:24:29.285 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=189&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=29.2 HTTP/1.1 tcp{client}: 0x5578241ee5a8 2021-03-24 12:24:29.286 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=151&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=11.7 HTTP/1.1 tcp{client}: 0x557824d0f778 2021-03-24 12:24:29.286 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=190&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=2.9 HTTP/1.1 tcp{client}: 0x557824d11828 2021-03-24 12:24:29.287 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=150&id=variableset&serviceId=urn:micasaverde-com:serviceId:HumiditySensor1&Variable=CurrentLevel&Value=41.5 HTTP/1.1 tcp{client}: 0x5578251ff6f8 2021-03-24 12:24:29.287 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=149&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=-1.0 HTTP/1.1 tcp{client}: 0x557825201b18 2021-03-24 12:24:29.288 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=152&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=12.9 HTTP/1.1 tcp{client}: 0x55782562a688 2021-03-24 12:24:29.289 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x557825ca05a8 2021-03-24 12:24:29.289 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x557825ca05a8 2021-03-24 12:24:29.289 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An_fb/# tcp{client}: 0x557825ca05a8 2021-03-24 12:24:29.289 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An/# tcp{client}: 0x557825ca05a8 2021-03-24 12:24:29.289 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x557825ca05a8 2021-03-24 12:24:29.290 luup_log:203: VirtualBinaryLight[2.40@203]:[updateMeters] KWH Path "meters[1].total" - Raw Value: 2805119 - Transformed Value: 4852230.7604 2021-03-24 12:24:29.290 luup.variable_set:: 203.urn:micasaverde-com:serviceId:EnergyMetering1.KWH was: 4852184.0084 now: 4852230.7604 #hooks:0 2021-03-24 12:24:29.291 luup_log:203: VirtualBinaryLight[2.40@203]:[updateMeters] Watts Path: "meters[1].power" - Value: 0 2021-03-24 12:24:29.291 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55782502f428 2021-03-24 12:24:29.291 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55782502f428 2021-03-24 12:24:29.291 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax/# tcp{client}: 0x55782502f428 2021-03-24 12:24:29.291 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55782502f428 2021-03-24 12:24:29.291 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax_fb/# tcp{client}: 0x55782502f428 ... 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578254b0b78 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824f80ef8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824f83988 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824df10c8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824fb0048 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824fb21e8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824e52928 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824fd5f48 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824fd7ff8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578241ee5a8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824d0f778 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557824d11828 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5578251ff6f8 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557825201b18 2021-03-24 12:24:29.367 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55782562a688 2021-03-24 12:24:29.368 openLuup.server:: GET /data_request?id=lu_action&DeviceNum=164&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=8.6 HTTP/1.1 tcp{client}: 0x5578249f1658 2021-03-24 12:24:29.368 luup.variable_set:: 164.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 8.6 now: 8.6 #hooks:0 2021-03-24 12:24:29.368 openLuup.server:: request completed (2 bytes, 1 chunks, 0 ms) tcp{client}: 0x5578249f1658 2021-03-24 12:24:29.371 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x5578247df8a8 2021-03-24 12:24:29.371 openLuup.mqtt:: closed tcp{client}: 0x5578247df8a8 2021-03-24 12:24:29.371 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x5578247df8a8 2021-03-24 12:24:29.371 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x5578247df8a8 2021-03-24 12:24:29.371 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x5578247df8a8 2021-03-24 12:24:29.371 openLuup.mqtt:: ERROR publishing application message for mqtt:cmnd/tasmota_test/POWER : closed -
I have been searching around and it appears to be a common yet infrequent problem reported for the luasocket. For good measure I updated my version of luasocket again to the latest development version (scm-2) but given how stagnant the development has been, I am wondering whether this would be the time to look for a different library... I have tinkered with libcurl in the past but I think it is only for POSIX platforms. I am sure there is a better lua library out there.
-
OK, that was clearly a BAD IDEA.
2021-03-24 14:49:58.979 openLuup.server:: GET /J_ALTUI_verabox.js HTTP/1.1 tcp{client}: 0x1cb6160 2021-03-24 14:49:58.982 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x1cb6160' sending 2 bytes to tcp{client}: 0x1cb6160 2021-03-24 14:49:58.982 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x1cb6160' sending 6 bytes to tcp{client}: 0x1cb6160 2021-03-24 14:49:58.982 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x1cb6160' sending 97222 bytes to tcp{client}: 0x1cb6160 2021-03-24 14:49:58.982 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x1cb6160' sending 2 bytes to tcp{client}: 0x1cb6160 2021-03-24 14:49:58.983 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x1cb6160' sending 5 bytes to tcp{client}: 0x1cb6160I've reverted that commit, so simply updating to development again (from the console!) should fix that.
-
I've pushed a new v21.3.24b release which includes the new checks, but, hopefully, without the deleterious effect on AltUI (or anything else.)
To make it easy to revert, I've also tagged the v21.3.23 version, so you can always revert to that by typing it into the update box.
-
Have not upgraded to 24b yet but this is what I am seeing:
2021-03-24 12:36:01.348 openLuup.io.server:: HTTP:3480 connection from 192.168.0.55 tcp{client}: 0x7fb153b396c8 2021-03-24 12:36:01.350 openLuup.server:: GET /data_request?id=variableset&serviceId=urn:upnp-org:serviceId:VSwitch1&Variable=Text2&DeviceNum=22&Value=10 HTTP/1.1 tcp{client}: 0x7fb153b396c8 2021-03-24 12:36:01.350 luup.variable_set:: 22.urn:upnp-org:serviceId:VSwitch1.Text2 was: 9 now: 10 #hooks:0 2021-03-24 12:36:01.351 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x7fb153b396c8 2021-03-24 12:36:01.351 openLuup.server:: ...only 0 bytes sent 2021-03-24 12:36:01.351 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x7fb153b396c8 2021-03-24 12:36:01.351 openLuup.server:: ...only 0 bytes sent 2021-03-24 12:36:01.351 openLuup.server:: request completed (2 bytes, 1 chunks, 1 ms) tcp{client}: 0x7fb153b396c8 2021-03-24 12:36:01.351 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x7fb153b396c8I am nearly 100% convinced that the hangs are due to luasocket error or timeout handling. You can see here that likely the client which here is home-assistant sending an http call to update a device on openLuup, apparently closed the tcp connection to which openLuup is trying to send something. As a result, I am getting an error. The humor is that both home assistant and openLuup are on the same machine. I am seeing this type of errors a few times a day but have not had a hang up since my previous post (I have updated luasocket and luasec since by the way) so I don't know if they are related to this error. However my previous experience from last year seem to indicate a bug in luasocket causing it to hold up the entire lua thread.
-
@akbooer Upgraded to v21.2.24b, it works as supposed so far.
Also I modified my strategy a bit. I have now turned off the http reporting from the sensors. They generate quite a lot of http calls, the screenshot below is from approx 13:00 to 22:00.
Worth noting is that they have been doing this http reporting for a few months without any stability problems, the traffic they generate could however be part of seeing the problems on my particular server perhaps.
The three test devices reporting over Mqtt are left on, we will see what happens.
-
Today at 12:08 it crashed again.
Not many Mqtt calls since the restart yesterday evening.
Also very few http server sockets:
Log file errors before the crash:
.. 2021-03-25 12:05:33.879 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca4502428 2021-03-25 12:05:33.879 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x563ca4502428 2021-03-25 12:05:33.879 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An_fb/# tcp{client}: 0x563ca4502428 2021-03-25 12:05:33.879 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x563ca4502428 2021-03-25 12:05:33.879 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An/# tcp{client}: 0x563ca4502428 2021-03-25 12:05:33.891 openLuup.mqtt:: TasmotaCO2An SUBSCRIBE to cmnd/TasmotaCO2An/# tcp{client}: 0x563ca41ea188 2021-03-25 12:05:33.894 openLuup.mqtt:: TasmotaCO2An SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x563ca41ea188 .. 2021-03-25 12:08:44.921 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca41ea188 2021-03-25 12:08:44.921 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x563ca41ea188 2021-03-25 12:08:44.921 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An_fb/# tcp{client}: 0x563ca41ea188 2021-03-25 12:08:44.921 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x563ca41ea188 2021-03-25 12:08:44.921 openLuup.mqtt:: TasmotaCO2An UNSUBSCRIBE from cmnd/TasmotaCO2An/# tcp{client}: 0x563ca41ea188 2021-03-25 12:08:44.925 openLuup.server:: request completed (11424 bytes, 1 chunks, 3813 ms) tcp{client}: 0x563ca3ebc488 .. 2021-03-25 12:08:44.935 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca3b9d058 2021-03-25 12:08:44.935 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x563ca3b9d058 2021-03-25 12:08:44.935 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca3f8a488 2021-03-25 12:08:44.935 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x563ca3f8a488 ... 2021-03-25 12:08:44.938 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca47549f8 2021-03-25 12:08:44.938 openLuup.mqtt:: closed tcp{client}: 0x563ca47549f8 2021-03-25 12:08:44.938 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x563ca47549f8 2021-03-25 12:08:44.938 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x563ca47549f8 2021-03-25 12:08:44.938 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x563ca47549f8 2021-03-25 12:08:44.938 openLuup.mqtt:: ERROR publishing application message for mqtt:cmnd/tasmota_test/POWER : closed 2021-03-25 12:08:44.939 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x563ca428dc98 2021-03-25 12:08:44.939 openLuup.mqtt:: closed tcp{client}: 0x563ca428dc98 2021-03-25 12:08:44.939 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax/# tcp{client}: 0x563ca428dc98 2021-03-25 12:08:44.939 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x563ca428dc98 2021-03-25 12:08:44.939 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax_fb/# tcp{client}: 0x563ca428dc98 2021-03-25 12:08:44.939 openLuup.mqtt:: ERROR publishing application message for mqtt:cmnd/TasmotaCO2Ax/POWER : closed -
The log sequences for MQTT seem normal, simply denoting that a connection has been dropped by the client, so then it's unsubscribed. A while later, presumably in the bits you've edited out, it reconnects. Might be interesting to know if there were any successful transactions going on in between. What's the KeepAlive configured as on your clients?
But I'm thinking this is not a very fruitful way forward. I am really, really struggling to think what may have changed, other than the fact that there is simply more I/O going on in the system. I tend to agree with @rafale77 above.
I have not fully run out of options with the LuaSocket library, so there will be a bit more experimentation. I'm hoping that a eureka moment will strike and I realize that this is something stupid that I've done (wouldn't be the first time.)
