-
Trying to bridge openLuup with another openLuup using Verabridge and getting no Vera. Is this the correct way of linking the two?
-
I have read this someone before but I cannot find the answer again. I have several devices and scenes in Vera which have been deleted so now the issue is to identify which ones they are in openluup ALTUI and remove them. I thought there was a process where you would delete the bridge and then add it again but I cant remember. Can anyone point me in the right direction?
Thanks -
Hello,
Had a RPI laying around and saw the cheap razberry board so picked one up last week. Am trying to set up ALTUI and connect to my Vera Plus. Of the 80 or so devices it pulled in from my Vera, only about 14 look like they are functional. When I run the GetVeraFiles from the VeraBridge actions menu, I see a bunch of 503 errors in the log. If I open the URL that it is erroring on in the browser, it usually returns a valid image or page.Is there a way to attach logs to messages or is it acceptable to just paste in the entire thing as text? Let me know what info you need to see to point me in the right direction.
Thanks,
Roger -
Since Vera support sucks and I have this intermittent problem. Several devices which were included successfully and had always have instant status (updating vera directly when pressed locally) stop working every now and then. Vera support has 1 solution: exclude & include. And yes this works. But then after a while it starts all over and eventually I end up with a regular exclude include session which is unacceptable. Currently I am somewhere a around device number 1600 (no joke!).
Vera tells me they can set and association to 1 (lifeline) to try.
Is there any feasible solution which is stable to keep this working? Where to start? I only have Vera as zwave bridge...
SOLVED Get Vera files throwing errors
-
Actually, you want the development branch, not the master branch
-
Type in development in the box next to update before you hit the update button in more > plugins
-
This post is deleted! -
Well, that completely horked it.
Now I am getting this in out.log
lua5.1: ./openLuup/loader.lua:476: Implementation XML root element name is not 'implementation'
stack traceback:
[C]: in function 'error'
./openLuup/loader.lua:476: in function 'parse_impl_xml'
./openLuup/loader.lua:553: in function 'read_impl'
./openLuup/loader.lua:735: in function 'assemble_device'
./openLuup/chdev.lua:141: in function 'create'
./openLuup/userdata.lua:551: in function 'load'
openLuup/init.lua:244: in main chunk
[C]: ?Assume I can go to the dev branch on gethub and pull down the latest files?
-
That didn't work either. WIll wait for the experts to reply.
-
Got it to work again. Now I am on 20.5.1 of openLuup.
-
Just wondering if there are lessons for me to learn from this?
...is there something specifically you did wrong, and then right, to fix things?
-
@akbooer The master branch apparently has those implementation files still enabled.
-
I should clarify my last statement of "getting it to work". What I was referring to was getting past the error message and getting the ALTUI interface to load.
Here is the sequence of events from yesterday.- Deleted the cmh-ludl directory that I had originally installed in the /home/pi path.
Was having issues getting openLuup to run on startup based on the samples in the openLuup users guide. (more of a windows guy than linux). - Created a cmh-ludl in /etc, so that the install point matched the scripts in the doc.
- Ran sudo lua5.1 openLuup_install.lua which installed the v19.12.27
- Based on comments in thread added "development" to Update dialog box and ran update script. That completely broke everything. openLuup would not load.
- Tried to copy openLuup files from github to my RPI. That didn't work either.
- Reran sudo lua5.1 openLuup_install.lua and it installed the 20.5.1 version (at least that is what it says on the plugins page).
So the current state is that ALTUI runs. I can control a few switches through my Vera from ALTUI. The majority of my devices are displaying the generic z-wave icon and have no control buttons.
In devices, VeraBridge has a red title bar even though I can control it.When I try to run the GetVeraScenes action I get this in the LuaUPnP log:
"2020-05-03 09:36:17.169 luup_log:5: GetVeraScenes action called
2020-05-03 09:36:17.374 openLuup.server:: request completed (2581 bytes, 1 chunks, 16755 ms) tcp{client}: 0x29334d8
2020-05-03 09:36:19.706 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=463507015&Timeout=60&MinimumDelay=1500&_=1588522721664 HTTP/1.1 tcp{client}: 0x29334d8
2020-05-03 09:36:30.267 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x237b8d8
2020-05-03 09:36:30.469 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x21da810
2020-05-03 09:36:30.470 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x2a04e58
2020-05-03 09:36:30.470 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x24e02a0
"
When I run GetVeraFiles I get a bunch of these:
"2020-05-03 09:39:19.118 openLuup.client:: WGET error status: 503, request: http://192.168.0.143/port_3480/D_ReactorSensor_UI7.json
2020-05-03 09:39:19.118 luup_log:5: ERROR: D_ReactorSensor_UI7.json
2020-05-03 09:39:19.121 openLuup.client:: WGET error status: 503, request: http://192.168.0.143/port_3480/D_DelayLightTimer.xml
2020-05-03 09:39:19.122 luup_log:5: ERROR: D_DelayLightTimer.xml
2020-05-03 09:39:19.129 openLuup.client:: WGET error status: 503, request: http://192.168.0.143/port_3480/D_VenstarColorTouchThermostat1_F.json
2020-05-03 09:39:19.129 luup_log:5: ERROR: D_VenstarColorTouchThermostat1_F.json
2020-05-03 09:39:19.133 openLuup.client:: WGET error status: 503, request: http://192.168.0.143/port_3480/I_DelayLight.xml
2020-05-03 09:39:19.133 luup_log:5: ERROR: I_DelayLight.xml"I can, however, paste this, http://192.168.0.143/port_3480/I_DelayLight.xml, in the browser on my RPI and it returns the xml data.
Thanks for your assistance.
- Deleted the cmh-ludl directory that I had originally installed in the /home/pi path.
-
Ok, that's lots to go on.
I've just done a completely fresh install on a RPI of the development system (crrently v20.5.3, actually, but no material difference from what you're trying.) Donwloaded all files successfully from a Vera Edge, running 7.30.
I think that, at this stage, I'd like a copy of the startup log and the main log after a restart.
In addition, the listing provided by the openLuup console Startup page would be of use:
http://openLuupIP:3480/openLuup?page=startupI'm worried by the red banner on the VeraBridge device.
-
Here is the startup page:
Plugin Startup Jobs CPU usage (in startup order)date / time device priority status hh
ss.sss job # info notes1 2020-05-03 13:17:38.558 2 1 Done 0.004 1 plugin: openLuup sync in 21.9 s
2 2020-05-03 13:17:38.559 3 3 Done 0.000 2 plugin: Alternate UI
3 2020-05-03 13:17:41.731 5 5 Abort 2.793 4 plugin: VeraBridge ./openLuup/loader.lua:476: Implementation XML root element name is not 'implementation'
4 2020-05-03 13:17:41.847 6 5 Done 0.008 5 plugin: Z-Way OK
5 2020-05-03 13:17:41.848 4 Done 0.001 3 plugin: Alternate App Store OKLink for log files sent via chat.
-
OK, straight-forward error. How did you create the VeraBridge plugin? It doesn't have a correct implementation file. What do its device attributes look like?
-
I I created the VeraBridge by going into the app - Plugins and clicking the update button.
altid
category_num 1
cpu(s) 2.793128
device_file D_VeraBridge.xml
device_json D_VeraBridge.json
device_type VeraBridge
disabled 0
id 5
id_parent 0
impl_file I_VeraBridge.xml
invisible 0
ip 192.168.0.143
local_udn uuid:d764c8cc-e932-55c4-478d-7aa05d83f3ea
mac
manufacturer akbooer
model
name VeraBridge
plugin
room 0
status -1
subcategory_num 0
time_created 05/02/2020 04:29:14 PM
altuiid 0-5
favorite false
dirty false -
There are several inconsistencies here.
- The startup page shows a failure to read the implementation file, yet the details in the startup log show that the VeraBridge plugin has started correctly.
- The VeraBridge version as reported at the end of the startup log (19.12.12) is not consistent with the version number of the openLuup system.
If you look in the
cmh-ludlfolder, and in itsfilesfolder, do you find any VeraBridge files? There should be none. The only findable VeraBridge file should be theL_VeraBridge.luaone in the openLuup folder (20.4.30). If there are any others, delete them.I believe I know what went wrong, but the above should get you going OK.
-
There is only one Verabridge file on the cmh-ludl folder or any of the sub's located in the openLuup folder. File header is:
BOUT = {
NAME = "VeraBridge",
VERSION = "2019.12.12",
DESCRIPTION = "VeraBridge plugin for openLuup",
AUTHOR = "@akbooer",
COPYRIGHT = "(c) 2013-2019 AKBooer",
DOCUMENTATION = "https://github.com/akbooer/openLuup/tree/master/Documentation",
DEBUG = false,
LICENSE = [[
Copyright 2013-2019 AK Booer -
OK, this was overwritten because you updated it from the default (master) branch, rather than the development one. It’s entirely my fault that this is possible. Sorry.
Solution is to update openLuup from the development branch again. This should replace that file with the correct one. getVeraFiles should then work.
-
How do I specify that? Of should I just write development in the update box for the plugins?
No worries about the issue. Glad to help finding it, and currently am just playing with it. -
Got it. Thanks for your help.
Plugin Startup Jobs CPU usage (in startup order)date / time device priority status hh
ss.sss job # info notes1 2020-05-03 15:22:33.769 2 1 Done 0.004 1 plugin: openLuup sync in 86.7 s
2 2020-05-03 15:22:33.770 3 3 Done 0.000 2 plugin: Alternate UI
3 2020-05-03 15:22:39.200 5 5 Done 4.403 4 plugin: VeraBridge OK
4 2020-05-03 15:22:39.293 6 5 Done 0.008 5 plugin: Z-Way OK
5 2020-05-03 15:22:39.294 4 Done 0.001 3 plugin: Alternate App Store OK -
I am still getting a lot of 503 errors and have quite a few devices from Vera that do not have all the controls present and functioning. Any ideas on why that might be happening?
-
Perhaps Vera just can’t keep up, although I’ve never seen this before.
Are these always the same files, or are you incrementally getting what you need? I really don’t know what to suggest for this one... anyone else seen anything like this?
Which devices are not working? If it’s not too many, you can manually download.
Alternatively, you can add a parameter to the GetVeraFiles request in the form of a Lua search pattern.
For example
Binary
will download all files with "Binary" in the name.
