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 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.

Development Branch: 2020 Release 5.1

• Startup log shows JSON module version information (thanks @a-lurker)

If you have installed Cjson then the startup log should include:

2020-05-01 13:00:56.780 openLuup.json:: version 2020.04.16 @akbooer
2020-05-01 13:00:56.780 openLuup.init:: using Cjson 2.1.0 for fast decoding

If not, then:

2020-05-01 12:54:47.675 openLuup.json:: version 2020.04.16 @akbooer
2020-05-01 12:54:47.675 openLuup.init:: Cjson not installed - using openLuup.json.Lua.decode() instead

Development Branch: 2020 Release 5.10

• native image panel for openLuupCamera1 device
• category 6 for ditto
• file counts in Luup files page menu

The openLuup console Luup Files page offers a very fast way to browse and view all the Luup device files that the system knows about. A click on the file name opens a Viewer on the file itself. The file filter menu now shows a count of each file type. I seem to have a total of 772 such files on my development system...

Development Branch: 2020 Release 7.4

INDEPENDENCE DAY Edition

...nothing to do with the USA, but the day in the UK when Covid-19 restrictions are reduced, and more shops and businesses can open!

• added Required Files sub-page to the Plugins page group, showing which files/modules are required by plugins (and how many times.)

This is in preparation for being able to specify replacement modules without altering the plugin code itself. Applications include replacing dkjson with RapidJSON, and the like.

Not fixed:

• the log file customisation in Lua Startup (sorry @CatmanV2, next time.)

@ArcherS said in Home water pressure sensor:

One solution that I can think of is to use MySensors. https://www.mysensors.org/

Yes, I have used these. I even posted about openLuup on their site a while ago. My favourite system, for a while, was a mySensors gateway running on the Arduino on a Yûn board with its SBC running OpenWRT and openLuup. Worked a treat. Since then, their firmware has been updated, but so has their plugin.

@ArcherS said in Home water pressure sensor:

I stopped using it because of that each time the Vera rebooted the gateway was lost

This, you have to blame on Vera’s poor luup.io module, which lacks the capability to restart a lost connection. Should be a fairly easy work-around to fix that on openLuup, which currently runs their gateway plugin with no modification, IIRC.

No, this is all my fault. The original ZWay plugin was prototyped four years ago, but in the last six months , with the way Vera was going, we ( @rafale77, @DesT, and some others) had a bit of a push to revive it and make it really functional. In the process, of course, documentation was not done.

My fault, too, that when you said

@JMK said in Help with Z-Way plugin:

On the same Raspberry Pi3 I have installed openLuup on which I have installed the Z-Way plugin.

...I assumed that it had all gone according to plan.

So now you see your Fibaro switch, and it works...?

“Can you give me an example of how to get archive_video to work, I can’t find it anywhere?”

As an HTTP request, it’s documented here:

Luup Requests - MiCasaVerde

It’s also available directly as a device action either manually through the device Actions page, or from Lua:

 luup.call_action ("urn:micasaverde-com:serviceId:Camera1", "ArchiveVideo", {Format=1}, devNo)

openLuup only supports Format=1, which saves a single frame snapshot to the images/ folder.

Development Branch: 2020 Release 5.12

• don't disable devices in Room101 (thanks @kfxo)
• add command class 1 updater (thanks @ArcherS)

Development Branch: 2020 Release 5.20

• fix for cjson.null in decoded structures
• thanks @reneboer (and @mrFarmer !)

As usual, an earlier update breaks something. This probably wouldn't have been spotted for a while, since it doesn't impact VeraBridge or the ZWave bridge, but thanks to @reneboer's vigilance, it's found and fixed.

A little more detail. The Cjson module decodes Json null as the private data structure cjson.null. The following code snippet shows the problem:

local json = require "openLuup.json"
local J = json.encode {1, nil, 3}
local L = json.Lua.decode(J)
local C = json.C.decode(J)

print("JSON", J)
print("Lua", pretty(L))
print("C", pretty(C))

writes the output:

JSON 	[1,null,3]
Lua 	{1,nil,3}
C 	{1,userdata: (nil),3}

However, the default openLuup json.decode() function has now been fixed, when it's using the Cjson module:

local D = json.decode(J)
print ("json.decode [using Cjson]", pretty(D))

now gives:

json.decode [using Cjson] 	{1,nil,3}

Kudos again to @reneboer and @mrFarmer !

@a-lurker said in openLuup: Suggestion:

is it possible to somehow profile openLuup [code]

Due to the amazingly parsimonious and elegant design of Lua, it's possible to write a profiler for any Lua code (openLuup, or otherwise) in just a few tens of lines.

Here's a profiler which counts function calls (but doesn't time them.) You use it like this:

local profile = require "miniprofiler"
profile "on"     -- start profiling

-- run whatever code you want here

profile "off"      -- turn off profiling
print (profile)    -- print the result

profile "clear"      -- clear the results to start again

Note that the same object is used to configure the profile, hold the data, and format the output. I just love Lua.

...and here's the code for the profiler module itself (miniprofiler.lua)...

-- miniprofiler.lua

-- simple profiler for function calls
-- @akbooer  June 2020

--Use:
--  local profile = require "miniprofiler"
--  profile "on"       -- start profiling
--  profile "off"      -- stop  profiling
--  profile "clear"    -- reset counts
--  print (profile)    -- show  results
  
local calls = 0
local funcs = {}
local hook = debug.sethook

local function profile(event)
  if event == "call" then
    calls = calls + 1 
    local i = debug.getinfo (2, 'n')
    local n = table.concat {(i.name or '?'), '/', i.namewhat}
    funcs[n] = (funcs[n] or 0) + 1
  end
end

local function report()
  local fcts = {}
  for n,v in pairs (funcs) do fcts[#fcts+1] = {n,v} end       -- make name index
  table.sort (fcts, function (a,b) return b[2] < a[2] end)    -- alphabetize
  local result = "%12s   %-8s   %s"
  local out = {result: format (calls, "TOTAL","Function calls")}
  local split = "^([^/]+)/(.*)"
  for _, x in ipairs(fcts) do
    local f, w = x[1]: match (split)
    out[#out+1] = result: format (x[2], w, f)
  end
  out[#out+1] = ''
  return table.concat (out, '\n')
end

local function call (_, x)
  local f = {
    on    = function () hook (profile, 'c') end,
    off   = function () hook () end,
    clear = function () for x in pairs(funcs) do funcs[x] = nil end calls = 0 end}
  do (f[x] or f.clear) () end
end
  
return setmetatable (funcs, {__call = call, __tostring = report})

-----

Yes, that's about it. Here's an example from openLuup's client.lua file:

local OKmd5,md5 = pcall (require, "md5")                -- for digest authenication (may be missing)

...so then I can write:

    if not OKmd5 then
      return nil, "MD5 module not available for digest authorization"
    end

which very readable and understandable.

@a-lurker said in Sun position or light sensor for blinds?:

If you look at the AltApp store in AltUI it shows up.

Yes, but have you tried to install it from there? I haven't, but I'm just looking at the raw database.

@a-lurker said in Sun position or light sensor for blinds?:

It may be an idea to start an alt App Store thread

Excellent idea! Not a specific openLuup issue... wonder where the best place would be?? @DesT ?

@a-lurker

There seems to be no repository information in the Alt App Store for the Heliotrope plugin? I can fix this, having found your GitHub version of it, unless you want to change it yourself.

@Buxton said in openLuup log files - LuaUPnP.log and LuaUPnP_startup.log:

The first is a horizontal scroll bar for the running log as I have numerous log entries that extend well past the right hand side of the screen

Actually, I hate web pages which scroll sideways. Would wrapping the text help? In fact, also, many log entries are truncated as a matter of course. What’s producing long lines?

@Buxton said in openLuup log files - LuaUPnP.log and LuaUPnP_startup.log:

The second is a startup configuration option specifying the number of log pages to save before deleting the oldest and rolling over

There is one, but noting the discussion here, there is currently a bug in implementation... I must fix it!

https://smarthome.community/topic/173/logging-and-rotation?_=1596321655453

Thanks for that. Signed up to a few sessions. Not clear to be where 'failures' would be discussed... did I miss something? Must go back and take a closer look.

They’re not used by the system – possibly by certain plugins, although I think that latitude and longitude are more likely candidates for weather and geofencing applications.

I see that Vera, these days uses GBP (if applicable) rather than £.

@rafale77 said in MQTT Plugin:

The fundamental problem is that setting up an MQTT client to listen to the broker blocks the luasocket and therefore openLuup.
The two libraries use different approaches to the problem.

This just sounds like a lack of understanding on behalf of the module authors, ...or possibly me. I can’t believe that it could possibly be so difficult.

These are the two libraries you referenced st the start?

...if you excuse a link to the other place:

May 11, 2019

openLuup: Asynchronous I/O

The latest openLuup development release has a new file in the openLuup/ folder: http_async.lua. This now implements asynchronous HTTP and HTTPS requests (depending on which scheme is provided in the requested URL.) If you want to use it, you simply require it in your code like this: local async...

Yes, it already works on Vera.

@therealdb said in MQTT Plugin:

I wish it was simpler - let's say - to execute 3 HTTP calls under Vera in parallel, each having its own response handler inline.

So this isn't good enough...?

local async = require "http_async"

async.request ("http://request1",
  function  (response, code, headers, statusline)
    -- response code 1 here
  end)

async.request ("http://request2",
  function  (response, code, headers, statusline)
    -- response code 2 here
  end)

async.request ("http://request3",
  function  (response, code, headers, statusline)
    -- response code 3 here
  end)