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
-
5% peak load? Shameful!
I’ve been stress testing too, and haven’t been able to make anything crash recently. I’m crafting a new Docker to take over from my main, and ageing, BeagleBone Black system, and the I/O there just whistles along with cpu at under 0.2%. I also see that RapidJson is available as a standard install of Alpine, so I may include that.
My conclusion, following yours, is that this is low-level LuaSocket issues on out of date libraries, which only show a problem when moderately stressed. I don’t think there’s anything more I can do at the openLuup coding level.
-
@akbooer said in OpenLuup unavailable:
5% peak load? Shameful!
I know! right? lol! As you know I optimize things to the edge... running on luajit, having turned JIT back on and rapidjson which I highly recommend over cjson because it enables not having to failover to dkjson if you so desire. I also regularly look at library updates which admittedly for lua, are sadly rare. I even tested a number of forks of luajit and found nothing worth the trouble at this point.
-
@rafale77 @akbooer two days ago the system was quite slow and non-responsive. I then decided to disable the Mqtt server in OpenLuup to see what would happen. Now after two days no crash, so it seems as if this is somehow casing the crashes. Small progress perhaps.
Edit:
What I still have noticed is that the system has been quite slow on v21.3.25b and v2.3.24b with at times very long response times. Much worse that what it was 3-4 days ago for some reason, before updating from v2.3.21 to v2.3.24b.
On 2.3.21 the system was quite snappy, but after some time crashed without warning.
Now I updated to 21.3.26 and so far it seems much more responsive that on v2.3.24b / v21.3.25b.I thought I would updated the Lua sockets libraries, LuaFileSystem etc to the latest versions, but now I cannot find the openLuup > System > Required list list.
This is what I had alst time I checked a week ago:
Hints on what to update and how to do it much appreciated.
Edit: The update to 21.3.26 initially seems to have made the system more repsonsive for whatevere reason. Good news, let's see if it stays like that.
I see that I am on LuaFileSystem 1.6.3 that seems to be from 2015 and @rafale77 you are on 1.8.0 that is from 2020. This seems like something that could need updating. -
-
Just in case you would want to know how to update these libraries:
Need to install luarocks. This depends on what machine you are using but assuming you are on a debian base,sudo apt-get install luarocks
will do it. then you can start upgrading things:
-
@archers said in OpenLuup unavailable:
Much worse that what it was 3-4 days ago for some reason. Then the system was quite snappy, but after some time. This was on v21.3.25b, now I updated to 21.3.26, I will see if ot continues to be slow.
OK, I have a possible answer to that. The system wait for up to a specified period of time if it fins that a socket is not ready to send. Initially, I used a timeout of zero (v21.3.24) bad choice, since most things timed out. Changed it to 0.2 seconds (v21.3.24b) , and later, then to 1.0 seconds (v21.3.26).
I will rever to something smaller, perhaps 0.1s. But you can change this (for the HTTP server) with:
luup.attr_set ("openLuup.HTTP.SelectWait", 0.1)Again, apologies, but your excellent reporting of the effect of these changes is a very efficient way for me to zero in on issues, for which, thanks.
-
@akbooer thanks! I see that my text above got a bit incomplete.
This is how it should be ( I think, many updates lately
) :
What I still have noticed is that the system has been quite slow on v21.3.25b and v2.3.24b with at times very long response times. Much worse that what it was 3-4 days ago for some reason, before updating from v2.3.21 to v2.3.24b.
On 2.3.21 the system was quite snappy, but after some time crashed without warning.
Now I updated to 21.3.26 and so far it seems much more responsive that on v2.3.24b / v21.3.25b.For clarity I edited the post above also.
-
-
A short status update.
Yesterday evening I updated OpenLupp to v21.3.26 and LuaFileSystem to 1.8.0.
I have since then left the system up and running as-is, i.e. without Mqtt re-enabled and with most of the http updates from my various Tasmota devices turned off.So far so good, the system seems as responsive as it has been earlier for the past approx 20 hours.
I have not changed the http server waiting time, it is at the default value for v21.3.26.When looking in the logs, it looks ok. Usually quite fast responses and no errors.
I found two similar lines that had a bit longer response time:
2002 lines, 0 errors, max gap 41s @ 2021-03-28 17:30:00.131 2021-03-28 17:29:18.910 luup.variable_set:: 10909.urn:micasaverde-com:serviceId:HaDevice1.sl_BatteryAlarm was: 0 now: 0 #hooks:0 2021-03-28 17:30:00.131 luup_log:0: 40Mb, 3.5%cpu, 0.8days 2021-03-28 17:30:00.646 luup.variable_set:: 68.urn:toggledbits-com:serviceId:ReactorSensor.cstate was: {"cond0":{"evaledge":[],"stateedge":[],"valuestamp":1615722020,"id":"cond0","statestamp":0,"lastvalue":0},"vars":{"... now: {"cond0":{"evaledge":[],"stateedge":[],"valuestamp":1615722020,"id":"cond0","statestamp":0,"lastvalue":0},"vars":{"... #hooks:0 2002 lines, 0 errors, max gap 65s @ 2021-03-28 16:54:07.724 2021-03-28 16:53:02.682 luup.variable_set:: 244.urn:toggledbits-com:serviceId:VirtualSensor1.LastUpdate was: 1616943122 now: 1616943182 #hooks:0 2021-03-28 16:54:07.724 luup_log:0: 44Mb, 1.5%cpu, 0.7days 2021-03-28 16:54:07.755 luup.variable_set:: 122.urn:toggledbits-com:serviceId:DelayLightTimer.Message was: Delay Off 9m now: Delay Off 8m #hooks:0I will keep off the system until tomorrow to see that it is stable over time before I restart the Mqtt server.
-
I looked in the logs again after I had some slow responses in the system and found some errors. The IP address 192.168.1.127 this my iPhone and Homewave. I tested with Homewave on my iPad and got a similar set of errors for that IP address. These errors seem to be in the direction of what @rafale77 mentioned.
Edit: Still had some errors so I changed it to 0.1 which seems to give even fewer errors.
I changed the http server wait to0.20.1 from 1.0 withluup.attr_set ("openLuup.HTTP.SelectWait", 0.1)and it seems as if it may have helped removing the errors. I will check some more later on and see if the errors return.From the log file:
2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 6 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 858578 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.149 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 20:01:02.561 openLuup.server:: error 'closed' sending 4 bytes to tcp{client}: 0x55979f3f9768 2021-03-28 20:01:02.561 openLuup.server:: error 'closed' sending 104 bytes to tcp{client}: 0x55979f3f9768 2021-03-28 20:01:02.561 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55979f3f9768 ... 2021-03-28 19:58:21.155 openLuup.io.server:: HTTP:3480 connection from 192.168.1.127 tcp{client}: 0x55979ef92ba8 2021-03-28 20:01:00.882 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x55979f3f9768 2021-03-28 19:58:22.954 luup_log:203: VirtualBinaryLight[2.40@203]:[updateMeters] Watts Path: "meters[1].power" - Value: 0 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: ...only 0 bytes sent 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 6 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: ...only 0 bytes sent 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 858578 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: ...only 64000 bytes sent 2021-03-28 19:58:23.148 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.148 openLuup.server:: ...only 0 bytes sent 2021-03-28 19:58:23.149 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x55979ef92ba8 2021-03-28 19:58:23.149 openLuup.server:: ...only 0 bytes sent 2021-03-28 19:58:23.149 openLuup.server:: request completed (858578 bytes, 5 chunks, 446 ms) tcp{client}: 0x55979ef92ba8 -
I have now had the Mqtt server up and running for approx 30 hours without any crashes so far, a step in the right direction as it seems.
I am still on OpenLuup version: v21.3.26 and LuaFileSystem v1.8.0 (luasec not updated), want to keep the setup as-is to see what happens over longer time.
So far only one Tasmota device connected via Mqtt reporting every minute.
No errors in the log files (except for Homewave, see below), max response time usually approx 16 seconds. Changing the http wait to 0.1 was a big change. With 1.0 OpenLuup was sluggish and there is a noticable difference also when comparing to 0.2.
With 0.1 the system is much better.Messages as displayed by MqttExplorer:
I have noticed two brief Mqtt disconnects during this time.
Log file:1575 lines, 0 errors, max gap 75s @ 2021-03-29 13:35:48.179 2021-03-29 13:34:33.581 luup.variable_set:: 216.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 25.3 now: 25.4 #hooks:0 2021-03-29 13:34:33.582 luup.variable_set:: 228.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 36.1 now: 36.1 #hooks:0 2021-03-29 13:35:48.179 openLuup.io.server:: MQTT:1883 connection from 192.168.1.60 tcp{client}: 0x5652106f2f48 2021-03-29 13:35:48.180 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x56520e9d91c8 2021-03-29 13:35:48.180 openLuup.io.server:: MQTT:1883 connection closed EXPIRED tcp{client}: 0x565210622978 2021-03-29 13:35:48.180 openLuup.mqtt:: mqtt-explorer-22233d66 UNSUBSCRIBE from # tcp{client}: 0x565210622978 2021-03-29 13:35:48.180 openLuup.mqtt:: mqtt-explorer-22233d66 UNSUBSCRIBE from $SYS/# tcp{client}: 0x565210622978Log from the Tasmota device console:
12:43:08 MQT: tele/tasmota_test/SENSOR = {"Time":"2021-03-29T12:43:08","AM2301":{"Temperature":25.4,"Humidity":36.1,"DewPoint":9.3},"TempUnit":"C"} 12:43:33 MQT: Attempting connection... 12:43:48 MQT: Connect failed to 192.168.1.107:1883, rc -4. Retry in 10 sec 12:43:59 MQT: Attempting connection... 12:44:10 MQT: Connected 12:44:10 MQT: tele/tasmota_test/LWT = Online (retained) 12:44:10 MQT: cmnd/tasmota_test/POWER = 12:44:33 MQT: tele/tasmota_test/STATE = {"Time":"2021-03-29T12:44:33","Uptime":"0T01:05:15","UptimeSec":3915,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":4,"Wifi":{"AP":1,"SSId":"BeachAC","BSSId":"FC:EC:DA:D1:7A:64","Channel":11,"RSSI":100,"Signal":-50,"LinkCount":1,"Downtime":"0T00:00:03"}}It reconnected without problem quite fast, so that seems to be fine.
I have not used Homewave very much during this time, but it also seems to work ok. However I do see errors for it when I use it. So something is not 100% right there perhaps. I got more errors with a longer http wait (1.0 >> 0.2 > 0.1).
Log file:2021-03-30 20:10:47.908 openLuup.server:: request completed (5907 bytes, 1 chunks, 194 ms) tcp{client}: 0x565210f173b8 2021-03-30 20:10:48.260 openLuup.server:: GET /data_request?output_format=json&id=lu_status HTTP/1.1 tcp{client}: 0x5652108936d8 2021-03-30 20:10:48.484 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x5652108936d8' sending 2 bytes to tcp{client}: 0x5652108936d8 2021-03-30 20:10:48.563 openLuup.server:: request completed (858554 bytes, 54 chunks, 302 ms) tcp{client}: 0x5652108936d8 2021-03-30 20:10:48.932 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=14594009&Timeout=60&MinimumDelay=1500&_=1617014398016 HTTP/1.1 tcp{client}: 0x565210f173b8 2021-03-30 20:10:49.068 openLuup.server:: request completed (5909 bytes, 1 chunks, 135 ms) tcp{client}: 0x565210f173b8 -
Well, that seems like a step in the right direction.
I, too, have been pressing on MQTT, and all seems well. Disconnects happen when the iMac that I’m using to run Explorer goes to sleep, but reconnects when it wakes up, as expected. Current stats look like this:
-
@akbooer today I got another crash unfortunately.
I had it up and running with two Mqtt devices reporting during approx 24 hours before the crash. Before that approx 2 days with one device.
This morning 4 hours before the crash it looked like this:
When looking through the log I can find the a lot of errors building up the last 2.5 hours before the crash.
2021-04-01 10:10:20.698 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb5a9b48 2021-04-01 10:10:20.698 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb5a9b48 2021-04-01 10:10:20.698 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bb5a9b48 2021-04-01 10:10:20.698 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8bb5a9b48 2021-04-01 10:10:20.698 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb5a9b48 ... 2021-04-01 10:10:20.707 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bae0e948 2021-04-01 10:10:20.707 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bae0e948 ... 2021-04-01 10:10:20.709 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb8a48a8 2021-04-01 10:10:20.709 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb8a48a8 2021-04-01 10:10:20.709 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb8a48a8 2021-04-01 10:10:20.709 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb8a48a8 2021-04-01 10:10:20.709 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8bb8a48a8 2021-04-01 10:10:20.741 openLuup.io.server:: MQTT:1883 connection from 192.168.1.50 tcp{client}: 0x55d8bad50918 2021-04-01 10:10:20.744 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:10:20.746 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:10:20.752 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:10:20.770 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8bad50918 2021-04-01 10:10:20.770 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bad50918 2021-04-01 10:10:20.771 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bad50918 ... 2021-04-01 10:13:26.365 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb6e71e8 2021-04-01 10:13:26.365 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb6e71e8 2021-04-01 10:13:26.365 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bab0a8d8 2021-04-01 10:13:26.365 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bab0a8d8 .. 2021-04-01 10:13:26.368 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bad50918 2021-04-01 10:13:26.368 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bad50918 2021-04-01 10:13:26.368 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bad50918 2021-04-01 10:13:26.368 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8bad50918 2021-04-01 10:13:26.368 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bad50918 2021-04-01 10:13:26.368 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb53f518 2021-04-01 10:13:26.368 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb53f518 2021-04-01 10:13:26.368 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:13:26.368 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:13:26.368 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8bb53f518 2021-04-01 10:13:26.374 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8bacf35d8 2021-04-01 10:13:26.379 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bacf35d8 2021-04-01 10:13:26.386 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bacf35d8 2021-04-01 10:13:26.397 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8bad3fc48 2021-04-01 10:13:26.400 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bad3fc48 2021-04-01 10:13:26.406 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bad3fc48 .. 2021-04-01 10:35:23.058 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bacf35d8 2021-04-01 10:35:23.059 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bacf35d8 2021-04-01 10:35:23.059 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bacf35d8 2021-04-01 10:35:23.059 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8bacf35d8 2021-04-01 10:35:23.059 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bacf35d8 ... 2021-04-01 10:35:23.088 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb736018 2021-04-01 10:35:23.088 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb736018 2021-04-01 10:35:23.088 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb7380c8 2021-04-01 10:35:23.089 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb7380c8 ... 2021-04-01 10:35:23.096 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bad3fc48 2021-04-01 10:35:23.096 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bad3fc48 2021-04-01 10:35:23.096 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bad3fc48 2021-04-01 10:35:23.096 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bad3fc48 2021-04-01 10:35:23.096 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8bad3fc48 2021-04-01 10:35:25.955 openLuup.io.server:: MQTT:1883 connection from 192.168.1.50 tcp{client}: 0x55d8b9bd4838 2021-04-01 10:35:25.973 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8b9bd4838 2021-04-01 10:35:25.977 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8b9bd4838 2021-04-01 10:35:25.977 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8b9bd4838 2021-04-01 10:35:29.040 openLuup.io.server:: MQTT:1883 connection from 192.168.1.60 tcp{client}: 0x55d8bb605448 2021-04-01 10:35:29.058 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8bb605448 2021-04-01 10:35:29.062 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bb605448 2021-04-01 10:35:29.063 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb605448 ... 2021-04-01 10:39:23.441 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8b9bd4838 2021-04-01 10:39:23.441 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8b9bd4838 2021-04-01 10:39:23.441 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8b9bd4838 2021-04-01 10:39:23.441 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8b9bd4838 2021-04-01 10:39:23.441 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8b9bd4838 ... 2021-04-01 10:39:29.585 openLuup.io.server:: MQTT:1883 connection from 192.168.1.60 tcp{client}: 0x55d8b8fedf68 2021-04-01 10:39:29.585 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8baee2da8 2021-04-01 10:39:29.585 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8baee2da8 2021-04-01 10:39:29.585 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8baacc308 2021-04-01 10:39:29.585 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8baacc308 ... 2021-04-01 10:39:35.729 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb605448 2021-04-01 10:39:35.729 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb605448 2021-04-01 10:39:35.729 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb605448 ... 2021-04-01 10:40:49.043 openLuup.context_switch:: ERROR: [dev #106] table: 0x55d8bb856790 2021-04-01 10:40:49.043 luup.incoming_callback:: function: 0x55d8bacaad00 ERROR: table: 0x55d8bb856790 ... 2021-04-01 10:43:20.159 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb0f87b8 2021-04-01 10:43:20.159 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb0f87b8 ... 2021-04-01 10:43:20.161 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8b8fedf68 2021-04-01 10:43:20.161 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8b8fedf68 2021-04-01 10:43:20.161 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8b8fedf68 2021-04-01 10:43:20.161 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8b8fedf68 2021-04-01 10:43:20.161 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8b8fedf68 2021-04-01 10:43:20.161 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb46f488 2021-04-01 10:43:20.161 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb46f488 2021-04-01 10:43:20.161 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bb46f488 2021-04-01 10:43:20.162 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8bb46f488 2021-04-01 10:43:20.162 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb46f488 2021-04-01 10:43:20.254 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:43:20.258 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:43:20.258 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:43:20.260 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8bb83d468 2021-04-01 10:43:20.260 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bb83d468 2021-04-01 10:43:20.260 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb83d468 ... 2021-04-01 10:51:25.662 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8baaa6608 2021-04-01 10:51:25.662 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8baaa6608 2021-04-01 10:51:25.663 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8badfb488 2021-04-01 10:51:25.663 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8badfb488 ... 2021-04-01 10:51:25.665 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb83d468 2021-04-01 10:51:25.665 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bb83d468 2021-04-01 10:51:25.665 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb83d468 2021-04-01 10:51:25.665 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb83d468 2021-04-01 10:51:25.665 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8bb83d468 2021-04-01 10:51:25.665 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8ba375f28 2021-04-01 10:51:25.665 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8ba375f28 2021-04-01 10:51:25.665 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:51:25.665 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:51:25.665 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8ba375f28 2021-04-01 10:51:25.735 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:51:25.739 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:51:25.739 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:51:25.844 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8baf3baa8 2021-04-01 10:51:25.847 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8baf3baa8 2021-04-01 10:51:25.851 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8baf3baa8 ... 2021-04-01 10:54:32.113 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8baf3baa8 2021-04-01 10:54:32.113 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8baf3baa8 2021-04-01 10:54:32.113 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8baf3baa8 2021-04-01 10:54:32.113 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8baf3baa8 2021-04-01 10:54:32.113 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8baf3baa8 2021-04-01 10:54:32.113 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8ba738ad8 2021-04-01 10:54:32.113 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8ba738ad8 2021-04-01 10:54:32.113 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:54:32.113 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:54:32.113 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8ba738ad8 2021-04-01 10:54:32.175 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum/# tcp{client}: 0x55d8ba6ce668 2021-04-01 10:54:32.178 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test/# tcp{client}: 0x55d8bb6b8028 2021-04-01 10:54:32.185 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8bb6b8028 2021-04-01 10:54:32.185 openLuup.mqtt:: tasmota_test SUBSCRIBE to cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb6b8028 2021-04-01 10:54:32.190 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/tasmotas/# tcp{client}: 0x55d8ba6ce668 2021-04-01 10:54:32.190 openLuup.mqtt:: TasmotaUterum SUBSCRIBE to cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8ba6ce668 ... <<<<repeats itself every 3rd minute or so>>>> ... 2021-04-01 12:42:40.786 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bb0f87b8 2021-04-01 12:42:40.786 openLuup.mqtt:: closed tcp{client}: 0x55d8bb0f87b8 2021-04-01 12:42:40.786 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test_fb/# tcp{client}: 0x55d8bb0f87b8 2021-04-01 12:42:40.786 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bb0f87b8 2021-04-01 12:42:40.786 openLuup.mqtt:: tasmota_test UNSUBSCRIBE from cmnd/tasmota_test/# tcp{client}: 0x55d8bb0f87b8 2021-04-01 12:42:40.786 openLuup.mqtt:: ERROR publishing application message for mqtt:cmnd/tasmota_test/POWER : closed 2021-04-01 12:42:40.786 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55d8bab88d38 2021-04-01 12:42:40.786 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55d8bab88d38 2021-04-01 12:42:40.786 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum_fb/# tcp{client}: 0x55d8bab88d38 2021-04-01 12:42:40.786 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/TasmotaUterum/# tcp{client}: 0x55d8bab88d38 2021-04-01 12:42:40.786 openLuup.mqtt:: TasmotaUterum UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55d8bab88d38 <<<<crashed>>>>In addition to the above I also found the following in the log, during one period (approx 20 times during a few minutes, two hours before the crash) "no route to host" for the Zway server (it is not on the same server as OpenLuup) and another error (only once), see below.
2021-04-01 10:39:23.440 luup_log:106: ZWay ASYNC request: No route to host 2021-04-01 10:40:49.043 openLuup.context_switch:: ERROR: [dev #106] table: 0x55d8bb856790 2021-04-01 10:40:49.043 luup.incoming_callback:: function: 0x55d8bacaad00 ERROR: table: 0x55d8bb856790Now I have disabled the Mqtt and restarted the server to see what happens.
-
