VeraBridge Issues (user error)

I accidentally deleted the device VeraBridge, which was working fine.

Since then, I uninstalled and reinstalled VeraBridge from the plugins update, and I cannot get openluup to communicate with the Vera. I filled in the IP directly under IP, and saved it, and tried the Misc Reload Luup Engine, and it still says No Vera, and no devices synced.

Any help appreciated. Accessed the logs under /etc/cmh-ludl (LuaUPnP.log, and LuaUPnP_startup.log) say nothing.

Any help would be appreciated. Thanks.

[ul][li]Is there still a L_VeraBridge.lua file in the openLuup directory?[/li]
[li]Is the VeraBridge entirely missing from the Startup log?[/li]
[li]Is there a L_VeraBridge.lua file in cmh_ludl/ ?[/li][/ul]

There was no need to uninstall, just a click on the install button should have worked, but I don’t think that this would be the issue.

I’ll look shortly when I have access remotely. In the meantime. Is there an easy way to reset the whole thing? I’d like to start from scratch.

In addition, since I am running it on Esxi, I started another fresh install under Ubuntu server but there was an error when running the install just script under list.1 that said there was a broken ssl dependency to github.

Yes. If you want to throw everything you set up away, then, assuming the openLuup flies are intact, you can exit then running instance (with an HTTP request) and start it again from the shell using

./openLuup_reload AltUI&
In addition, since I am running it on Esxi, I started another fresh install under Ubuntu server but there was an error when running the install just script under list.1 that said there was a broken ssl dependency to github.

This may mean that the Lua image you are running doesn?t have up to date libraries, or that the OS image doesn’t have an up to date SSL (possibly openSSL?). GitHub has updated its security access a while ago and now uses tslv1.2, IIRC.

This one is my fault… I haven’t updated the install file for the tslv1.2 protocol.

Fix in progress. Apologies.

This one is my fault… I haven’t updated the install file for the tslv1.2 protocol.

Fix in progress. Apologies.[/quote]

[tt]openLuup._install.lua[/tt] now fixed in v19.2.12 in both master and development branches.

I did the reset and now get this:

No handler for data_request?id=lr_ALTUI_Handler

I did ./openLuup_reload AltUI&

That resulted in the above handler.

[quote=“akbooer, post:2, topic:200580”][ul][li]Is there still a L_VeraBridge.lua file in the openLuup directory?[/li]
[li]Is the VeraBridge entirely missing from the Startup log?[/li]
[li]Is there a L_VeraBridge.lua file in cmh_ludl/ ?[/li][/ul][/quote]

  1. no

2019-02-12 04:49:25.270 :: openLuup STARTUP :: /etc/cmh-ludl 2019-02-12 04:49:25.270 openLuup.init:: version 2018.03.21 @akbooer 2019-02-12 04:49:25.285 openLuup.scheduler:: version 2018.03.21 @akbooer 2019-02-12 04:49:25.287 openLuup.wsapi:: version 2017.01.12 @akbooer 2019-02-12 04:49:25.287 openLuup.servlet:: version 2018.02.22 @akbooer 2019-02-12 04:49:25.287 openLuup.server:: version 2018.03.22 @akbooer 2019-02-12 04:49:25.288 openLuup.rooms:: version 2016.06.23 @akbooer 2019-02-12 04:49:25.289 openLuup.scenes:: version 2018.02.19 @akbooer 2019-02-12 04:49:25.290 openLuup.chdev:: version 2018.03.18 @akbooer 2019-02-12 04:49:25.290 openLuup.userdata:: version 2018.03.02 @akbooer 2019-02-12 04:49:25.290 openLuup.requests:: version 2018.02.18 @akbooer 2019-02-12 04:49:25.290 openLuup.gateway:: version 2018.03.05 @akbooer 2019-02-12 04:49:25.292 openLuup.smtp:: version 2018.03.20 @akbooer 2019-02-12 04:49:25.292 openLuup.io:: version 2018.03.22 @akbooer 2019-02-12 04:49:25.292 openLuup.luup:: version 2018.03.22 @akbooer 2019-02-12 04:49:25.327 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / 2019-02-12 04:49:25.329 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json 2019-02-12 04:49:25.329 openLuup.init:: loading configuration user_data.json 2019-02-12 04:49:25.339 openLuup.userdata:: loading user_data json... 2019-02-12 04:49:25.345 openLuup.userdata:: loading rooms... 2019-02-12 04:49:25.345 openLuup.userdata:: room#1 'MiOS-50002965' 2019-02-12 04:49:25.345 openLuup.userdata:: room#2 'Fountain' 2019-02-12 04:49:25.345 openLuup.userdata:: ...room loading completed 2019-02-12 04:49:25.345 openLuup.userdata:: loading devices... 2019-02-12 04:49:25.346 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / 2019-02-12 04:49:25.395 luup.create_device:: [3] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json 2019-02-12 04:49:25.404 luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json 2019-02-12 04:49:25.415 luup.create_device:: [7] D_ZWay.xml / I_ZWay.xml / D_ZWay.json 2019-02-12 04:49:25.442 luup.create_device:: [8] D_DataYours.xml / I_DataYours.xml / D_DataYours.json 2019-02-12 04:49:25.455 luup.create_device:: [9] D_Arduino1.xml / I_Arduino1.xml / D_Arduino1.json 2019-02-12 04:49:25.457 luup.create_device:: [10] D_VeraBridge.xml / I_VeraBridge.xml / D_VeraBridge.json 2019-02-12 04:49:25.457 openLuup.userdata:: loading scenes... 2019-02-12 04:49:25.457 openLuup.userdata:: number of scenes = 0 2019-02-12 04:49:25.457 openLuup.userdata:: ...scene loading completed 2019-02-12 04:49:25.457 openLuup.userdata:: loading installed plugin info... 2019-02-12 04:49:25.457 openLuup.userdata:: [openLuup] openLuup (18.3.23) 2019-02-12 04:49:25.457 openLuup.userdata:: [8246] Alternate UI (GitHub.2501) 2019-02-12 04:49:25.457 openLuup.userdata:: [AltAppStore] Alternate App Store (18.2.27) 2019-02-12 04:49:25.457 openLuup.userdata:: [Z-Way] Z-Way (18.7.16) 2019-02-12 04:49:25.457 openLuup.userdata:: [Arduino] MySensors (GitHub.master) 2019-02-12 04:49:25.457 openLuup.userdata:: [8211] DataYours (16.10.4) 2019-02-12 04:49:25.457 openLuup.userdata:: [VeraBridge] VeraBridge (18.9.26) 2019-02-12 04:49:25.457 openLuup.userdata:: ...user_data loading completed 2019-02-12 04:49:25.457 openLuup.init:: running _openLuup_STARTUP_
3) yes

I reverted to the snapshot I made after screwing it up but before I received the Althandler error. Please disregard that post.

In this version, my vera’s ip address is showing in the device, but doesn’t register even after reboot.

Thanks,

Drex

Does the VeraBridge device have a variable called RemotePort?

Try moving L_VeraBridge.lua to cmh-ludl/openLuup/ and then reload.

please let me clarify my situation.

I reverted back to the version before the reload/reset. I no longer have the issue loading Alt UI. I am back to seeing the vera as a device with the attribute set to the correct IP but it fails to connect to the vera…

Part 2:
In the second new VM, openluup still won’t install. It errors here after wiping out the old install Lua file and whetting the latest version:

download failed with tlsvl alert protocol version traceback [C}: in function ‘assert’ openluup_install.lua:30 in main chunk [c]: ? and fails…

I don’t know but suspect others trying to install openloop are having the same issue…

It seems that you are not using the latest install. You need to get it manually from GitHub.

Will do.

In the meantime, in my existing running image, how do I get vera ridge to connect correctly? It says it can’t; the correct IP address was entered under attributes and won’t despite restarts connect to my veraplus?

What does the console Scheduler > Startup Jobs show?

not sure where to find scheduler.

on the new machine, I manually downloaded openLuup_install, and it still fails.

vera@veraplus:/etc/cmh-ludl$ lua5.1 openLuup_install
openLuup_install   2019.02.12   @akbooer
getting openLuup version tar file from GitHub branch master...
lua5.1: openLuup_install:31: GitHub download failed with code tlsv1 alert protocol version
stack traceback:
        [C]: in function 'assert'
        openLuup_install:31: in main chunk
        [C]: ?
vera@veraplus:/etc/cmh-ludl$

It’s under the console pages menu. You can get there with the URL [tt]http://your_openLuup_IP:3480/console?page=startup[/tt]

on the new machine, I manually downloaded openLuup_install, and it still fails.

Yes, my fault (again.) A case of ‘more haste, less speed.’ I uploaded the wrong file!

It’s been fixed in both branches again. Sorry once more.

Still not right. New VM/totally new install oi ubuntu this morning. Just wget new file. from link in install docs.

Error now in line 30, same error, same chunk.

lua5.1 openLuup_install.lua
openLuup_install 2019.02.12 @akbooer
getting openLuup version tar file from GitHub branch master…
lua5.1: openLuup_install.lua:30: GitHub download failed with code tlsv1 alert protocol version
stack traceback:
[C]: in function ‘assert’
openLuup_install.lua:30: in main chunk
[C]: ?
vera@veraplus:/etc/cmh-ludl$

[quote=“Drex, post:14, topic:200580”]not sure where to find scheduler.

on the new machine, I manually downloaded openLuup_install, and it still fails.

vera@veraplus:/etc/cmh-ludl$ lua5.1 openLuup_install openLuup_install 2019.02.12 @akbooer getting openLuup version tar file from GitHub branch master... lua5.1: openLuup_install:31: GitHub download failed with code tlsv1 alert protocol version stack traceback: [C]: in function 'assert' openLuup_install:31: in main chunk [C]: ? vera@veraplus:/etc/cmh-ludl$ [/quote]

What does the console Scheduler > Startup Jobs show?[/quote]

7 2019-02-16 08:50:45 10 Abort[1] job#7 :plugin VeraBridge [string “openLuup/L_VeraBridge.lua”]:440: attempt to call field ‘create’ (a nil value)

btw, There is a L_VeraBridge.lua in the directory /ec/cmh-ludl already…

from the detailed log:

2019-02-16 08:50:45.089 luup_log:10: Vera info received!
2019-02-16 08:50:45.089 luup_log:10: MiOS-500XXXX
2019-02-16 08:50:45.089 openLuup.context_switch:: ERROR: [string “openLuup/L_VeraBridge.lua”]:440: attempt to call field ‘create’ (a nil value)
2019-02-16 08:50:45.089 openLuup.scheduler:: job aborted : [string “openLuup/L_VeraBridge.lua”]:440: attempt to call field ‘create’ (a nil value)
2019-02-16 08:50:45.089 luup_log:3: ALTUI: UPNPregisterDataProvider(3,datayours,http://127.0.0.1:3480/data_request?id=lr_DataWatcherRelay&target={0},[{
“default”:“unknown”,
“key”:“target”,
“label”:“Metric Name”,
“type”:“text”
},{
“default”:“/data_request?id=lr_render&target={0}&hideLegend=true&height=250&from=-y”,
“key”:“graphicurl”,
“label”:“Graphic Url”,
“type”:“url”
}])

Sigh…

Something has got really screwed up here. You should not have a L_VeraBridge.lua anywhere other than the openLuup/ folder. Delete the one in /cmh-ludl/. Then just click the openLuup update button of the Plugins page to ensure that you are using the latest master release.

If you still have problems, I need the startup log and the initial regular log after starting up. Give it a minute or so after restart.


Edit: I take it that the other clean install went OK.

in regards to fresh install, as reported above, the error moved down a line… but unable to fresh install (on new virigin built from scratch vm…

Error now in line 30, same error, same chunk.

lua5.1 openLuup_install.lua
openLuup_install 2019.02.12 @akbooer
getting openLuup version tar file from GitHub branch master…
lua5.1: openLuup_install.lua:30: GitHub download failed with code tlsv1 alert protocol version
stack traceback:
[C]: in function ‘assert’
openLuup_install.lua:30: in main chunk
[C]: ?
vera@veraplus:/etc/cmh-ludl$

I’m so sorry. You must have taken this from the master branch, which, for some reason, had failed to merge with the development. Both now should be up to date at version 2019.02.15.

Can you try one more time…?

I’ll work on the other issue now. In future it might help to separate the two issues into separate posts.