openLuup: running the latest builds on Raspian Stretch

Plugins & Plugin Development openLuup
1

I’m having issues on a Raspberry Pi running the latest builds on Raspian Stretch.

Raspberry Pi 2 (and 3 is the same)
Raspian Stretch - latest image
update and install pre-reqs (Linux_Aptitude form post on openLuup turnkey images up to the point where openLuup is loaded)
install openLuup as per the ‘openLuup User Guide’
Setup to start openLuup at boot (/etc/rc.local)
Reboot, AltUI starts witth no problems.
Install VeraBridge, Set ip address of Vera and restart Luup, devices are successfully loaded from the vera.
In VeraBridge, in Actions, load files from vera, wait for log to indicate all files loaded.
Activity in the log indicates devices being updated, AltUI web interface still working fine.
Reload Luup Engine - Error in log:
2017-12-09 16:44:24.105 openLuup.luup:0: device 0 ‘system’ requesting reload
2017-12-09 16:44:24.105 luup.reload:0: saving user_data
2017-12-09 16:44:24.504 openLuup.luup:0: exiting with code 42 - after 0.0 hours
Web interface to AltUI still working.
Ctl-F5 to reload web.
Web interface now shows
This site can?t be reached

vera2.xxxxxxxx.xxxxxxx refused to connect.
Search Google for vera2 xxxxxx xxxx 3480 data request
ERR_CONNECTION_REFUSED

On the pi console I get the following:
device 0 ‘system’ requesting reload
rc.local[431]: lua5.1: ./openLuup/userdata.lua:600 attempt to index local ‘dev’ (a nil value)
rc.local[431]: stack traceback:
rc.local[431]: ./openLuup/userdata.lua:600: in function ‘load’
rc.local[431]: openLuup/init.lua:189 in main chunk
rc.local[431]: [C]: ?

Have also tried this on Ubuntu 17 on a laptop with the same results.
Have also posted under Alternate UI to U17 as “Problems after 2245 update” but amg0 unable to help

Thanks
Peter.

2

The status 42 is a final shutdown from the openLuup system, so it’s expected that you would receive no response after that. WHY it has done that is not clear to me from your information.

It would be helpful to get a log, which will have useful diagnostic information in it. Could you also confirm the actual version that you are running?

3

Thanks for the reply, I included the LuaUPnP.log in my last post. If you need more, please let me know what you want and I will try to get it for you.

Peter.

4

So you did… my bad!

I’ll take look.

5

Can I get a copy of the startup log? … should be in cmh_ludl/logs/LuaUPnP_startup.log

At first sight, everything looks quite normal. You’ve tried rebooting? What does the log look like then?

6

Attached, in zip file, startup log before reboot and after reboot.
Also included my user_data.json.

Peter.

7

OK, I’ve downloaded the files and removed the attachments, in case they contain sensitive information.

8

The startup logs tell me that this is an extremely old version of openLuup… I guess the one tht came in the original turnkey image.

Essential to download the latest files from the development branch before we do any further investigations:

Latest version is 17.11.14

9

Hi, this did not come from a turnkey image, I downloaded the files as per the instructions in the openLuup User Guide (dated March 2017).

wget https://github.com/akbooer/openLuup/raw/master/Utilities/openLuup_install.lua

lua5.1 openLuup_install

I will now download the files from the development branch and let you know.

Peter.

Update. Downloaded all the files in development branch (29 files all .lua) and overwrote the files in my cmh-ludl/openLuup folder.
Rebooted
Error on console:
rc.local[424]: lua5.1: openLuup/init.lua:7 unexpected symbol near ‘<’

No new LuaUPnP.log or LuaUPnP_startup.log

init.lua has on the 7th line
lines 1 to 6 are empty.

Peter.

10

So clearly there is something amiss with the downloaded files since, looking at the GitHub version, the init.lua file does not contain that line.

I’ll try and look more closely at this tomorrow.

11

Yes, my unfamiliarity with GitHub and to some extent Linux.
Have downloaded the files again and verified them Following on console on reboot:
rc.local[434]: lua5.1: ./openLuup/userdata.lua:604: attempt to index local ‘dev’ (a nil value)
rc.local[434]: stack traceback:
rc.local[434]: ./openLuup/userdata.lua:604: in function ‘load’
rc.local[434]: openLuup/init.lua:200 in main chunk
rc.local[434]: [C]: ?

LuaUPnP_startup.log attached.

Thanks Peter.

12

OK, so what is device 80 on your Vera?

This is likely to be some sort of audio playback device? The corresponding file does not exist on your /etc/cmh-ludl/ directory under openLuup.

Can you delete the device for the time being?

13

Hi,
The device was a ‘Huawei Home Gateway’, my internet router. This had also spawned several other devices such as a ‘WAN device’ and a ‘LAN device’.
I could only find these devices by using Event Watcher on the Vera, as they were not showing in the device list.

I have disabled UPnP scanning and have deleted all of these devices using web requests.

Just rebuilding the openLuup system at the moment and will let you know what happens.

Peter.

Update: now rebuilt and all is running:
RaspberryPi Stretch
openLuup 17.11.14
AltUI 2.06.2267

Many thanks for your help

Peter.

14
I have disabled UPnP scanning and have deleted all of these devices using web requests.

A wise move! UPnP is more trouble than it’s worth.

Glad all is now well.