Vera PushOver notification with image

[akbooer]

• openLuup has no dependency on Vera hardware at all. It is simply a reliable implementation of the Luup API.
• I don’t think ZWay has a free trial. In openLuup it is just used as middleware to connect to the ZWave stack.

[Black Cat]

Homeseer software is free for 30 days, Plug Ins vary, some are free to trial some not.
The PI description will tell you the status.

[krisztianszabo]

@akbooer

I bought the Pi!
I'm right there now
#wget https://github.com/akbooer/openLuup/raw/master/Utilities/openLuup_install.lua

For some reason he writes to me that:
openLuup_install.lus: permission denied.

What do I have to do now?

[PerH]

mabye putting "sudo" in front of it? you may have to stand in the /Downloads folder as well, and then copy the downloaded file to /etc later..

[krisztianszabo]

It was key !!
"saved"
Thanks.
I'm going on my way ...

[krisztianszabo]

one more problem ...
the installation stalled here.

pi@raspberrypi:/etc/cmh-ludl $ sudo lua5.1 openLuup_install.lua
openLuup_install   2019.02.15   @akbooer
getting openLuup version tar file from GitHub branch master...
un-zipping download files...
mv: 'openLuup-master/openLuup/'-t can't remove here: './openLuup': The directory is not empty
getting dkjson.lua...
creating required files and folders
initialising...
downloading and installing AltUI...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 29170  100 29170    0     0  90309      0 --:--:-- --:--:-- --:--:-- 90309
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6570  100  6570    0     0  32364      0 --:--:-- --:--:-- --:--:-- 32364
lua5.1: openLuup/init.lua:291: openLuup - is another copy already running?  Unable to start HTTP server on port 3480
stack traceback:
	[C]: in function 'error'
	openLuup/init.lua:291: in main chunk
	[C]: ?
openLuup downloaded, installed, and running...
visit http://192.168.0.159:3480 to start using the system
pi@raspberrypi:/etc/cmh-ludl $ lua5.1: openLuup/init.lua:291: openLuup - is another copy already running?  Unable to start HTTP server on port 3480
stack traceback:
	[C]: in function 'error'
	openLuup/init.lua:291: in main chunk
	[C]: ?  "

If I try to open it in a browser the message is:
"This XML file does not appear to have any style information associated with it. The document tree is shown below."

What should I do?

[akbooer]

@krisztianszabo said in Vera or not vera?:

openLuup - is another copy already running?

It means exactly what it says.

Try accessing it with AltUI URL. If it’s an old copy running, you can abort it with the exit command, as described in the documentation...

http://openLuupIP:3480/data_request?id=exit

[krisztianszabo]

with openluup ip, the browser prints the following (in black on a red background):
"Waiting Initial Data"
... but nothing has happened for a long time ...

[akbooer]

Look for errors in the log file.

You should be able to access the native openLuup UI with

http://openLuupURL:3480/openLuup/

...in order to access the logs.

The most common issue here is that your computer locale setting specifies a language which AltUI does not implement. The error log should clarify this. A workaround is to copy the English language file to one with your country extension OR set your language to one which is implemented.

[krisztianszabo]

Language really was the problem. Thanks.
I got past that, but here's another one ....
The two files were born in the right places (etc / cmh-ludl and systemd / system) with good content.
When I type that:

pi@raspberrypi:/etc/cmh-ludl $ sudo systemctl enable openLuup
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

[krisztianszabo]

@Akbooer
I copied this from the startup_log.
Something was not filled properly?
Could the above error message be the cause?

2020-11-05 15:35:49.788 openLuup.init:: Cjson not installed - using openLuup.json.Lua.decode() instead
2020-11-05 15:35:49.789 luup.create_device:: [1] D_ZWaveNetwork.xml / / ()
2020-11-05 15:35:49.789 openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
2020-11-05 15:35:49.804 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json (openLuup)
2020-11-05 15:35:49.804 openLuup.init:: loading configuration user_data.json
2020-11-05 15:35:49.804 openLuup.userdata:: loading user_data json...
2020-11-05 15:35:49.812 luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0
2020-11-05 15:35:49.812 openLuup.userdata:: loading rooms...
2020-11-05 15:35:49.812 openLuup.userdata:: ...room loading completed
2020-11-05 15:35:49.812 openLuup.userdata:: loading devices...
2020-11-05 15:35:49.813 luup.create_device:: [1] D_ZWaveNetwork.xml / / ()
2020-11-05 15:35:49.813 openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.starts' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.altui_split' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.template' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.trim' (a function value)
2020-11-05 15:35:49.909 luup.create_device:: [3] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json (urn:schemas-upnp-org:device:altui:1)
2020-11-05 15:35:49.917 luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json (urn:schemas-upnp-org:device:AltAppStore:1)
2020-11-05 15:35:49.917 openLuup.userdata:: loading scenes...
2020-11-05 15:35:49.917 openLuup.userdata:: number of scenes = 0
2020-11-05 15:35:49.917 openLuup.userdata:: ...scene loading completed
2020-11-05 15:35:49.917 openLuup.userdata:: loading installed plugin info...
2020-11-05 15:35:49.917 openLuup.userdata:: [openLuup] openLuup (20.5.22)
2020-11-05 15:35:49.917 openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30)
2020-11-05 15:35:49.917 openLuup.userdata:: [VeraBridge] VeraBridge (not.installed)
2020-11-05 15:35:49.917 openLuup.userdata:: [8246] Alternate UI (GitHub.master)
2020-11-05 15:35:49.917 openLuup.userdata:: [Z-Way] Z-Way (not.installed)
2020-11-05 15:35:49.918 openLuup.userdata:: [Arduino] MySensors (not.installed)
2020-11-05 15:35:49.918 openLuup.userdata:: ...user_data loading completed
2020-11-05 15:35:49.918 openLuup.init:: running openLuup_STARTUP
2020-11-05 15:35:49.918 luup_log:0: startup code completed
2020-11-05 15:35:49.918 openLuup.init:: init phase completed
2020-11-05 15:35:49.918 :: openLuup LOG ROTATION :: (runtime 0.0 days)

[akbooer]

Looks great to me. No problem with the missing file, really.

Is everything working?

[akbooer]

I do notice that you haven’t installed the VeraBridge plugin, so there will be no link to Vera.

[krisztianszabo]

The main problem is one post up. I'm still standing on "openLuup Start on Bootup Lua", unfortunately.
(I was just guessing why it didn't work)

[krisztianszabo]

@akbooer
The main problem is one post up. I'm still standing on "openLuup Start on Bootup Lua", unfortunately.
(I was just guessing why it didn't work)

[krisztianszabo]

Hello @akbooer,

I’ve been working on the system a lot in recent days.
(altui starts with "pi", I have the tools with all the icons and also the rooms, language file copied. I'm still in the process of installing the vera plugins and moving the reactor scenes (sensors).

1, What I noticed:

• startup lua error:

2020-11-09 09: 24: 00.644 openLuup.init :: Cjson not installed - using openLuup.json.Lua.decode () instead

2, I have read the openluup manual you wrote several times unfortunately, yet one or two things are not clear.

Settings for the user_data.json file:

• the actual location of the backup and log directory on the pi must be specified. Right?

• "ditto Lines and Versions - number of lines before log rotation, number of versions saved"
  i don't know what to change here ....

• "openLuup.UserData.Checkpoint - number of minutes between each user_data.json save."
  here the number 60 should be changed to 6?

3, Altui for some reason identifies my wife's name in the system. he writes that
"unregistered version for" my wife's login name "Why do I log in with this?

[akbooer]

@krisztianszabo said in Vera or not vera?:

2020-11-09 09: 24: 00.644 openLuup.init :: Cjson not installed - using openLuup.json.Lua.decode () instead

It's not an error, it's just an information message. It's an extension to the system that you don't need.

@krisztianszabo said in Vera or not vera?:

Settings for the user_data.json file

Nothing needs changing here – all the defaults are just fine. What problem are you trying to solve?

@krisztianszabo said in Vera or not vera?:

Altui for some reason identifies my wife's name in the system.

Do you have VeraBridge up and running and linked to your Vera yet? openLuup receives its username information from Vera via the bridge. There is a well-known problem with AltUI/Vera in the case that there are multiple registered users, since it's not clear which one will be picked by Altui to check the licence. This is not an openLuup issue unless you are trying to run without an attached Vera. In which case I can provice a licence key, if you are actually licensed with AltUI, and you send me a screen snapshot of your AltUI footer, showing the licence information.

[krisztianszabo]

Thank you for your response @akbooer.

"Nothing needs changing here – all the defaults are just fine. What problem are you trying to solve?"

I'm following the openluup briefing.
I found there: "Appendix: Configuring key openLuup parameters at Startup"

From this I thought something had to be changed in user_data.json.
Don't I have to be change someting there?
Or don't have to?
I'm starting to lose a little bit of the yarn between a lot of information ... sorry.

[krisztianszabo]

"Do you have VeraBridge up and running and linked to your Vera yet? openLuup receives its username information from Vera via the bridge. There is a well-known problem with AltUI/Vera in the case that there are multiple registered users, since it's not clear which one will be picked by Altui to check the licence. This is not an openLuup issue unless you are trying to run without an attached Vera. In which case I can provice a licence key, if you are actually licensed with AltUI, and you send me a screen snapshot of your AltUI footer, showing the licence information."

VeraBridge, installed, bridge, running, connection good, devices taken over.

I'm trying to run with Vera for now and I don't have an Altui license. Then it's so good. Right?

[akbooer]

@krisztianszabo said in Vera or not vera?:

I found there: "Appendix: Configuring key openLuup parameters at Startup"

This is entirely optional, and just describes a way to change things if you want to... but you don't, so nothing to do here!

I'm sorry the manual is perhaps not as clear as it could be. It has rather grown over time as features got added, so the organisation of it is not ideal. I did try to put everything necessary in the early chapters and additional documentation in the Appendices.

@krisztianszabo said in Vera or not vera?:

VeraBridge, installed, bridge, running, connection good, devices taken over.

That's great.

@krisztianszabo said in Vera or not vera?:

I'm trying to run with Vera for now and I don't have an Altui license. Then it's so good. Right?

OK, that explains it. If you want to get rid of the message, then you need to contact @amg0 about a licence. You should ask for it in the login name that it is trying to use, in this case, your wife's. Then openLuup will pick up this information too, and if you keep Vera attached all will be well. If, someday, you remove Vera, having transferred all your ZWave devices to ZWay, say, then you will need a licence key from me to enable you to keep your AltUI licence running, but openLuup, itself, requires no licence.