I’m looking to have a play and install OpenLuup onto my Raspberry PI, it’s already used as a HDMI switcher via Vera, so I’m not keen to use one of the images available (time saver as they are)
I’m sorry if this is an obvious question, and I’m embarrassed to say, but using the User Guide, I’m stuck after Step 2.
I’ve run the lua installs, and created the directories, and downloaded the OpenLuup files from GitHub - but now what ?
I tried to copy elements over so I can run the required openluup_check and I’ve also done the transfer of file from my Vera - but I feel I’m missing something obvious
I’m looking to have a play and install OpenLuup onto my Raspberry PI, it’s already used as a HDMI switcher via Vera, so I’m not keen to use one of the images available (time saver as they are)
I’m sorry if this is an obvious question, and I’m embarrassed to say, but using the User Guide, I’m stuck after Step 2.
I’ve run the lua installs, and created the directories, and downloaded the OpenLuup files from GitHub - but now what ?
I tried to copy elements over so I can run the required openluup_check and I’ve also done the transfer of file from my Vera - but I feel I’m missing something obvious
[ul][li]You have, of course, read the guide through a couple of times before starting?[/li]
[li]Are you stuck on step 3, page 5?[/li]
[li]Have you taken a look at the “Suggested commissioning steps” on page 9 and following?[/li][/ul]
You should be at the stage of generating a ‘factory reset’ system and checking out the functionality there.
Thanks CudaNet, I’ll check your Linux_Aptitude guide out…
Hi @Akbooer - I have read the guide a few times, hence I was embarrassed to raise this post, but felt I should…
I guess the gap for me is where to put all the files from the GitHub package, as thats not clear for me, here are my notes from following each step
Step 1 - Lua Install - Done
Step 2 - Create Host Tree - Done
Step 3 - AltUI - What, hold on, where/how do I do that, when all I have done is step 1 & 2 ?
Step 4 - Not applicable to me, not using Arduino
Step 5 - Vera Bridge - ok, I can do that as those files are in the GitHub package, so copied over - Done
Step 6 - Vera Get Files - ok, I can find the file OpenLuup_getfiles from the GitHub package, so I’ve run that - Done
Step 7 - Not sure what to do here, but will come back to it.
The problem the guide is fantastic and written by a genius…
However, us simpletons need to understand his logic… ;D
You might be using the pdf thats in the Github… Cudnet wrote a more detailed one…
Carry on through the guide and near the bottom you have this section
Suggested Commissioning Steps
Try that stuff and you will win
I have reattached CudaNets guide here
Not being a Linux expert, I really do look to the guides to take me through every step, and looking at the OpenLuup User Guide compared to the Linux Apitude guide, the install requirements alone are different.
I’ve installed them all now, and am moving on to the folders, which I had created, yet the Linux_Appitude suggests a slightly different approach, which I will try to adapt to, but as I only use root, it suggests I will need to create a new user…
OpenLuup User Guide
/etc/cmh-ludl/
/etc/chh-ludl/icons/
/var/log/cmh/
Linux Apitude guide
/home/{user}/vera
/home/{user}/vera/cmh
/home/{user}/vera/cmh-ludl
/home/{user}/vera/cmh-ludl/icons
/home/{user}/vera/cmh-ludl/files
I’m not a UNIX expert at all, and in the guide I put only what I found necessary on the three very different systems I’ve tried: Mac OS, OpenWRT, Debian.
The additional ‘requirements’ from @CudaNet are mostly to do with both the install tools he’s actually using and to support some ‘exotic’ plugins. openLuup doesn’t, itself, need them.
It all depends what you want to do.
The difference in directory structure is simply that you can run from any base directory. The additional ones are created anyway by the openLuup utilities.
No critism taken, I had a Rasp Pi not doing much (other than acting as a HDMI switcher via Vera) so K thought I’d have a go and add OpenLuup to it too
As I had already created directories in /etc/ based on the OpenLuup user guide, and imported the Vera files - I get the following when I copy over and run openLuup_check.lua ?
root@raspberrypi:/etc/cmh-ludl# lua5.1 openLuup_check.lua
module 'mime'
module 'socket'
module 'socket.http'
module 'ssl.https'
module 'ltn12'
module 'dkjson'
not found: /www
... port 80 HTTP server may not work properly
not found: /www/cmh/skins/default/icons
... UI5 icon directory missing
not found: /www/cmh/skins/default/img/devices/device_states
... UI7 icon directory missing
not found: user_data.json
... no user_data configuration file
root@raspberrypi:/etc/cmh-ludl#
That’s an old version of openLuup_check. Port 80 is not used any more, nor /www, nor are the two icon directories. user_data.json should be created on the first run of openLuup.
I’ve updated the openLuup_check version in the DEVELOPMENT branch. It has fewer checks now because there’s no dependence on a port 80 HTTP server and the ckassic icon directory structures are not needed either.
It turns out that it’s AltUI which now has a dependence on dkjson.
Ok, some progress has been made certain http requests (alive, user_data) are now returning information, which is good. The only thing that I can’t seem to make work is to get the AltUI (http://192.168.1.77:3480/data_request?id=altui)
That does not work for me.
Running $ ./openLuup_reload reset brings up
Sun Apr 10 21:35:04 2016 device 0 '_system_' requesting reload
Looking at the command line, mentioned above more entries are added. (Example the same as in the Linux guide, but the dates and gap different, I allowed it to run for 10 plus minutes and did multiple reloads)
Sun Feb 28 21:35:04 2016 device 0 '_system_' requesting reload
Sun Feb 28 21:35:50 2016 device 0 '_system_' requesting reload
Sun Feb 28 21:35:50 2016 device 3 'ALTUI' requesting reload
Sun Feb 28 21:36:08 2016 device 0 '_system_' requesting reload
Sun Feb 28 21:36:34 2016 device 0 '_system_' requesting reload
Sun Feb 28 21:37:27 2016 device 0 '_system_' requesting reload
Sun Feb 28 21:38:47 2016 device 0 '_system_' requesting reload