Following up, I’ve disabled zone name fetching (as I do not have any set nor do I have LCD keypads) and dropped the baud down to 9600, but LUA continues to fail very early.
I’m wondering if the issue I’m experiencing is because I do not have an LCD keypad. It seems plugins for other HA systems have had this problem as well.
I can only give a short response at the moment: your attached log shows a successful startup without any unrecoverable errors. If you are getting Lua failures then they will appear in the log. Catching these failures will mean lying in wait for the error to happen and catching that part of the log.
I have only LED keypads. You seem to have set up the interface properly.
Fascinating. The docs say that luup.set_failure() takes an integer. In Lua, boolean types are not just sugar-coated integers as they are in C-like languages, hence my surprise.
Yet the plugin code already has a mix of boolean and integer parameters to that function, and most searches on the forum show code with booleans rather than integers. So this would seem to be a long-running confusion with the function.