-
"akbooer: Master Branch: 2021 Release 7.25
Long-overdue roll-up of the last year's development updates!"ak - congratulations on some great improvements coming to fruition. I can only hope you aren't running out of ideas! It's not easy.
I'd still like to see an "App Store" plugin download count but the invisible hands still need to be invoked by someone - whoever that may be!!
-
A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:
...I want to work in a more open and stable [Vera] environment...
...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?
1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modificationWhat 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.
-
Not sure which category to use, but it's about external access..
I'm using Dataplicity to connect from the web to openluup, and i'd like a similar connection for MSR. Thats not something i would use on a phone, but from a laptop situated elsewhere in the world (faulty logic always appears when i'm far away from home!)
I could offcourse do the same procedure (described in the lower part of this ) for MSR, but if I colud put a link somewhere in Openluup that would take me there (like the openluup console link?) that would be easier?
Don't know if it will work to connect to a different port?
Any ideas?
-
I'm setting up an openluup system (again) at my cabin, and this time i also added the dataplicity wormhole for external access..
I still use Imperihome to handle these on my phone, but ran into trouble when trying to add another "88800000" system, which seems to be the standard ID for openluup?
Any way to change the 88800000?
-
akbooer - sometimes when I'm looking at the graphs via the Data Historian in-memory Cache page; I hit the cache clear icon (circle with arrow head) instead of the graph icon (bar chart icon). Hence I have just destroyed what I wanted too look at. I just sometimes make some vague mental leap that the two icons are just one single "refresh chart" icon. Or perhaps it's just my big fat fingers.
However, I would like to suggest to make the icons further apart from each other and perhaps change the clear cache icon to a garbage icon. Sometimes known as a "trash" icon. Which I suppose it's a bit like a "freedom unit" 😉 .
-
Feedback / issues with openLuup's built-in MQTT server
-
I'm working on a very slow migration from DataYours to Historian and am wondering if there is a list of cache devices that can be modified to include some that are missing, specifically several voltage variable monitors in service EnergyMetering1.
Just checked again and a couple showed up. It could be that these populate slowly after a Vera reboot?
I would also like to modify the storage-aggergation, it is possible to edit that .conf file directly and reboot openLuup?
-
Hi AK,
I have my BlueIris NVR sending MQTT messages to openLuup for various triggers that occur in the NVR. Rather than configure start-up lua to subscribe to each and every BlueIris topic (there are many system topics as well as topics for each camera), I'd like instead to build an MQTT device specific to BlueIris, similar to the generic tasmota device type, to capture and display in variables, each topic and message sent from Blue Iris.
This way, I could then use Reactor to watch and act on message changes.
I've looked at the tasmota bridge code and believe I could re-purpose some of it to build such a device, but before I get into such an effort, is this something that can be done in an easier way? In general terms, I'm thinking of a an MQTT flag in the luup device creation that would specify an MQTT device and then the device would look for messages based on message filters established on a device configure page. Or perhaps a template of some sort that would act as a starting point for creating MQTT devices specific to an endpoint device.
-
I'm a fan of the SendConfig call action in a couple of scene...
Did you implement something like GetConfig ?
I have a couple of scene that I would need to do a GetConfig to do something based on the value...
-
I'm currently migrating everything from debian to the same VM using Ubuntu, 'cause z-way handle Ubuntu better than debian!
So here some question about openLuup 😉
1- Having some error on the console about GetNetworkState.sh (can't find file)
2- Is there a reason why openLuup can't handle lua5.3 instead of 5.1 ? -
Hi
I’ve been finding myself using the command line more with other applications and I’ve been enjoying the experience, learning basic shell/bash scripting etc.
What command line options are available with openluup?
-
@akbooer, have you thought about using rapidjson instead of cjson?
xpol/lua-rapidjson xpol/lua-rapidjsonA JSON module for Lua based on the very fast RapidJSON library. - xpol/lua-rapidjson
I am testing it on ALTUI and doesn't appear to be as strict as cjson while being even faster.
miloyip/nativejson-benchmark miloyip/nativejson-benchmarkC/C++ JSON parser/generator benchmark. Contribute to miloyip/nativejson-benchmark development by creating an account on GitHub.
Benchmarks comparing dkjson, cjson and rapidjson halfway down the page:
Performance compared to lua-cjson. · Issue #275 · Tencent/rapidjson Performance compared to lua-cjson. · Issue #275 · Tencent/rapidjsonI have write a json module for lua based on RapidJSON. The performance test result over lua-cjson is: On windows: My json module performance a bit slower than cjson when processing booleans nulls s...
performance/nulls.json: (x10000) module decoding encoding dkjson 1.5754740238 0.0276830196 cjson 0.0551309586 0.0487358570 rapidjson 0.0545330048 0.0497119427 performance/booleans.json: (x10000) module decoding encoding dkjson 1.4916000366 0.5738999844 cjson 0.0556819439 0.0495460033 rapidjson 0.0491378307 0.0377278328 performance/guids.json: (x10000) module decoding encoding dkjson 2.3570721149 3.0556299686 cjson 0.1626739502 0.1092689037 rapidjson 0.1135668755 0.0830221176 performance/paragraphs.json: (x10000) module decoding encoding dkjson 8.5023150444 31.5211300850 cjson 0.8555159569 0.6739630699 rapidjson 0.3181121349 0.1543619633 performance/floats.json: (x10000) module decoding encoding dkjson 2.1173479557 1.7756278515 cjson 0.1096220016 0.3009288311 rapidjson 0.0733149052 0.1116719246 performance/integers.json: (x10000) module decoding encoding dkjson 1.7672340870 1.3564231396 cjson 0.0811710358 0.2808339596 rapidjson 0.0581030846 0.0484278202 performance/mixed.json: (x10000) module decoding encoding dkjson 16.8118801117 13.2526481152 cjson 1.3187069893 0.7380268574 rapidjson 1.3779308796 0.4688320160Edit: I have implemented it across all of my plugins without the openLuup.json wrapper and have been running error free. Will let you know in a couple of days if I would recommend this but it is looking very good so far... It can completely and seemlessly replace dkjson.
installation instruction:
luarocks install rapidjson --server https://luarocks.org/devThen run a replace of dkjson and cjson to rapidjson in every lua file in the openluup and plugin lua file folder.
-
Very happy getting Alexa to control Openluup devices. I'm wondering if there's any way to get Openluup to control Alexa only devices (such as wifi enabled light bulbs?
TIA
C
-
Hello,
Having issues updating to latest version. Is there documentation on it anywhere? -
I thought I would test and migrate my OpenLuup installation from my current old i3 Ubuntu server to a new Raspberry Pi 4.
I have set up the new Pi with a fresh install of openLuup and it works as it should.
As I have understood it I should install all the plugins I have on my old installation and then restore a backup file from my old installation onto the new server. Is this correct or should I do some more steps before migrating? When I see that everything is working the plan is to swap the IP, but initially the new server will have another IP.
When I tried to test the resore procedure on the new server from a backup file of the new server I got an error and the restore script hangs.
After reboot OpenLuup is back.What I did was type:
./openLuup_reload backup/backup.openLuup-88800000-2021-04-12.lzap
in the Terminal from inside cmh-ludl ( I found this procedure in an old thread).When doing this I get the following error message:
rm: can not remove '/www/altui/altui*': The file of catalogue does not exist (free-hand translated from Swedish)@akbooer am I missing something here?
-
The last three mornings OpenLuup for some reason has been unavailable. In other words it has not been responding when trying to connect via AltUI or Console.
I have been trying to investigate a bit around what this could be but not got it pinned down.
I run OpenLuup with one Zway bridge and two Vera bridges. The Zway and Veras have all been available every time, so that should not be the problem.
When the problems started I had updated OpenLuup with Mqtt and added a few Mqtt devices. At the same time I also updated AltUI to the latest version. At the same time I also removed some devices from Room 101.
The Mqtt devices are normally reporting data as they should.In Lua startup I have added the following entries related to Mqtt:
luup.attr_set ("openLuup.MQTT.Port", 1883) luup.attr_set ("openLuup.MQTT.Username", "luup") luup.attr_set ("openLuup.MQTT.Password", "openluup") luup.attr_set ("openLuup.MQTT.PublishDeviceStatus", "0") -- ================================== Mqtt functions below: local json = require "openLuup.json" function MyMQTThandler (topic, message) local info = json.decode (message) local t = info.AM2301.Temperature local h = info.AM2301.Humidity luup.variable_set ("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", t, 216) luup.variable_set ("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel", h, 228) end luup.register_handler ("MyMQTThandler", "mqtt:tele/tasmota_test/SENSOR") function TasmotaCO2Axel (topic, message) local info = json.decode (message) local t = info.BME280.Temperature local h = info.BME280.Humidity local p = info.BME280.Pressure local c = info.MHZ19B.CarbonDioxide luup.variable_set ("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", t, 229) -- set temp to device luup.variable_set ("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel", h, 230) -- set humidity to device luup.variable_set ("urn:micasaverde-com:serviceId:GenericSensor1", "CurrentLevel", p, 232) -- set air pressure to device luup.variable_set ("urn:micasaverde-com:serviceId:GenericSensor1", "CurrentLevel", c, 231) -- set CO2 to device end luup.register_handler ("TasmotaCO2Axel", "mqtt:tele/TasmotaCO2Ax/SENSOR") function TasmotaCO2Anton (topic, message) local info = json.decode (message) local t = info.BME280.Temperature local h = info.BME280.Humidity local p = info.BME280.Pressure local c = info.MHZ19B.CarbonDioxide luup.variable_set ("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", t, 233) -- set temp to device luup.variable_set ("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel", h, 234) -- set humidity to device luup.variable_set ("urn:micasaverde-com:serviceId:GenericSensor1", "CurrentLevel", p, 235) -- set air pressure to device luup.variable_set ("urn:micasaverde-com:serviceId:GenericSensor1", "CurrentLevel", c, 236) -- set CO2 to device end luup.register_handler ("TasmotaCO2Anton", "mqtt:tele/TasmotaCO2An/SENSOR") -- =======================================================================This morning it seems as if OpenLuup stopped working at 06:24, I kept MqttExporer up and running over night and it the data reporting had stopped at that time. (The image shows the last reported data and then it shows that it commences again after I restarted OpenLuup at 07:19.
20210318MqttExplorer.pngBefore restarting I grabbed all the log files, the last few entries in the log are:
2021-03-18 06:24:09.712 luup.variable_set:: 149.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: -10.6 now: -10.5 #hooks:0 2021-03-18 06:24:09.712 openLuup.server:: request completed (2 bytes, 1 chunks, 4 ms) tcp{client}: 0x55ca8d503438 2021-03-18 06:24:09.721 luup.variable_set:: 229.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 20.4 now: 20.4 #hooks:0 2021-03-18 06:24:09.721 luup.variable_set:: 230.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 46.7 now: 46.7 #hooks:0 2021-03-18 06:24:09.721 luup.variable_set:: 232.urn:micasaverde-com:serviceId:GenericSensor1.CurrentLevel was: 1016.5 now: 1016.5 #hooks:0 2021-03-18 06:24:09.721 luup.variable_set:: 231.urn:micasaverde-com:serviceId:GenericSensor1.CurrentLevel was: 2010 now: 2020 #hooks:0 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8cb5cf68 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8c855e68 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8d2daa08 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8c7c3218 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8ca87948 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8d312d98 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8c7e95f8 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8c74a218 2021-03-18 06:24:09.754 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8bfefea8 2021-03-18 06:24:09.755 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55ca8c6ebce8 2021-03-18 06:24:09.756 openLuup.io.server:: MQTT:1883 connection closed tcp{client}: 0x55ca8c4dfe48 2021-03-18 06:24:09.756 openLuup.mqtt:: closed tcp{client}: 0x55ca8c4dfe48 2021-03-18 06:24:09.756 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax/# tcp{client}: 0x55ca8c4dfe48 2021-03-18 06:24:09.756 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/tasmotas/# tcp{client}: 0x55ca8c4dfe48 2021-03-18 06:24:09.756 openLuup.mqtt:: TasmotaCO2Ax UNSUBSCRIBE from cmnd/TasmotaCO2Ax_fb/# tcp{client}: 0x55ca8c4dfe48 2021-03-18 06:24:09.756 openLuup.mqtt:: ERROR publishing application message for mqtt:cmnd/TasmotaCO2Ax/POWER : closedThe last rows are a bit strange to me, them seem to indicate that something goes wrong with the Mqtt for that device?
@akbooer I assume that it could be more of interest in the logs, I can of course email them if needed. Also let me know if any more information is missing.
-
Creating my own topic for newbie questions about openLuup and AltUi 🙂
Trying to create a scene with a timer to turn on device 1 at given time IF device 2 is Off.
Wrote Lua to return false if device 2 is On.
Log states "scene prevented from running by local scene Lua" but action is performed anyway, device 1 is turned On.
Suggestions? -
I found some really minor gui issues in AltUI and in the Console.
Once more it is not that much of a problem for me as I use them only for admin purposes. I thought I'd post them anyway so that they are known for future releases, depending on priorities of course. 🙂
The first is related to the rounding of humidity devices in AltUI. It seems as if these numbers are always rounded down:
AltUI:
cae85b7d-8f20-440a-9ca2-8d568b63f00c-bild.pngConsole:
8100685e-9389-4f5f-b1e7-96a25fbabe84-bild.pngThe second issue is that the value for generic sensors seems not to be visible in the Console:
AltUI:
7909f921-2a09-4687-9550-331640e32244-bild.png -
I got tired on waiting for a stable release of Vera FW so finally took the leap to installing openLuup.
Unfortunately I haven't even got a simple scene to work.
Trigger - If device 1 is turned on
Action - Delay 2 seconds and turn device 2 on.I see the call to turn device 1 on in log but nothing else related after that.
What am I doing wrong? -
I noticed this morning something that have seen in the past but forgotten about.
When I restart the OpenLuup server (in my case an Ubuntu PC) the Vera and Z-way bridges do not get in contact with the corresponding servers, i.e. are shown in red in AltUI. The solution for me is to make a "Relaod Luup engine" and then they are ok. I do not know if it is a general issue or only for my setup.
To be honest it is not much of a problem since OpenLuup is so stable. If and when you restart the server the hazzle of reloading is not that big. In fact I had forgotten about it since it was so long ago I had to restart anything...
The one use case I can think of is that the server gets restarted due to a power outage or something and if you are not at home the system does not fully recover without manual interaction. I my case I have the server on an UPS, but still a thought.
Is this a known issue and is it something that can be addressed somehow? As I said low priority, at least for me. 🙂
openLuup: MQTT server
-
Feedback / issues with openLuup's built-in MQTT server
-
I just tested the broker and... the cpu utilization went from 1.5% to 90%... only getting home assistant connected to it without even subscribing a topic...
-
Interesting. I've tried it on three different systems and not seen this. Anything available from the log?
I should say, though, that the only MQTT clients I have been able to test with so far are the Shellies themselves.
-
The odd thing is that it seems to work fine. I am manually testing by sending messages from a mosquitto client command line tool. I reverted back to the mosquitto broker which uses <0.1% CPU. Could it be because I am using luajit?
-
I’m using LuaJIT in development, so that’s one of the systems I am testing under. That typically runs at 0.2% CPU, as does the system on my Synology NAS, although I seem to be having a few issues there with IP address mapping. Are you running this under a VM?
-
Yes I am running in inside a VM. I am not having any IP address mapping issues though... puzzling.
See my openLuup cpu load. I am also checking it with "top" and the openLuup process goes nuts hovering between 87% and 92% when I uncomment the server launch code from the lua startup. Commenting it brings the CPU load back to normal.
-
I updated to dev branch and added
luup.attr_set ("openLuup.MQTT.Port", 1883)to LUA startup on my docker project machine now.
Stays at about .2 CPU here.. I'll try to get some data in later. -
Any plans on a GUI for MQTT server control? i would love a status window with topics and activity.
-
For inspiration, this is Home Assistant:
Edit: This is really weird, I am not seeing the cpu load problem anymore. Just retried it... and it seems to work just fine. The CPU load is a little higher but by a few decimals. Not sure what happened previously.
-
I'll test it over the week-end, since snow is expected. I'll just relay all the traffic from my broker. I'll report back soon.
-
@perh said in openLuup: MQTT server:
Any plans on a GUI for MQTT server control? i would love a status window with topics and activity.
Er, yes. It's already there in the openLuup console Server pages. I added a new one for MQTT, from which I notice that the same client IP is subscribed twice. I've not yet implemented UNSUBSCRIBE !! (but will do so now.)
-
Ok, think i found an issue?
All I did in openluup was to start MQTT in the lua_startup.
Then tried to connect something, and suddenly it started running wild with alot of these messages (and CPU at 95%):
2021-02-12 17:50:51.847 luup.incoming_callback:: function: 0x55694ad24e40 ERROR: table: 0x55694b5b18a0 2021-02-12 17:50:51.847 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b2257c0 2021-02-12 17:50:51.847 luup.incoming_callback:: function: 0x55694ac43980 ERROR: table: 0x55694b2257c0 2021-02-12 17:50:51.847 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b225ea0 2021-02-12 17:50:51.847 luup.incoming_callback:: function: 0x55694ad24e40 ERROR: table: 0x55694b225ea0 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b13bae0 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ac43980 ERROR: table: 0x55694b13bae0 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b13c200 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ad24e40 ERROR: table: 0x55694b13c200 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b139d60 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ac43980 ERROR: table: 0x55694b139d60 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b13a440 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ad24e40 ERROR: table: 0x55694b13a440 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b9519a0 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ac43980 ERROR: table: 0x55694b9519a0 2021-02-12 17:50:51.848 openLuup.context_switch:: ERROR: [dev #0] table: 0x55694b952080 2021-02-12 17:50:51.848 luup.incoming_callback:: function: 0x55694ad24e40 ERROR: table: 0x55694b952080When I stopped the sender (stopped the container it was running in), the errors kept coming until I reloaded luup.
The sender was this, which is a program that parses data from Tibber Pulse into JSON. Tibber Pulse sends instant power data from my house power input.
It has two tobpics, do i have to establish these in the broker first? -
Already a feature request: could the broker force users to use credentials like mosquitto does?
-
@rafale77 said in openLuup: MQTT server:
could the broker force users to use credentials like mosquitto does?
Absolutely not a problem. How would you like to be able to specify the credentials.
On your other problem... I’m working on it.
-
Credentials: Could be attributes of openLuup? somehow encoded?
-
Question: does the broker have to have the topics ready, or will it create them when some unit connects with topics?
-
I believe topics are created by subscribers/publishers. They are a "header" to the "message".
-
The server/broker needs no configuration aside from the port number (except, soon, for defining login credentials.)
The joy of MQTT is that you don’t need to know who is listening, where they are (IP address), who is sending, or what they’re sending. It’s just that if you’re subscribed to a topic, and someone publishes an application message with that topic, then you receive it.
-
The latest development release of openLuup, v21.2.16 should have fixed the error condition that you were seeing. I was using the socket.try() function incorrectly in an attempt to catch errors in a better way!
I’ve also fixed the multiple subscriber issue that I was seeing. Still some more to do, including login credentials, but would appreciate any feedback at this stage.
The Shelly bridge also seems to be working well with it... very responsive.
-
Sounds good, Will get on it in the next few hours. I just finished refactoring a bunch of my scene lua code moving a couple of global state variables into virtual switch devices. I am trying to not convolute too many changes.
