-
Posted this in Vera forum with no response:
Seeing this in reactor UI:
A newer version of the device information database is available. Please use the update function on the Tools tab to get it. This process is quick and does not require a Luup reload or browser refresh–you can immediately come back here and go right back to work! The new version is 865.877, and you are currently using 557.352…Hit update in Tools and get an error: “The update could not be retrieved. If this problem persists, consult the documentation.”
Looked through logs and not seeing anything specific. You have a keyword I should search for?
-
Hi Rene @mrFarmer just thought i would let you know that the new broadlink app from Ezlo causes an error in log, It does not stop the bridge.
luup.variable_set:: 24.urn:rboer-com:serviceId:EzloBridge1.Ezlo_deviceMap was: {"603a8896122335165e686cb3":29,"5fe26c71122335120f05323e":23,"603a8896122335165e686cb7":30,"5fd354fc12233516e1e0c3b... now: {"603a8896122335165e686cb3":29,"5fe26c71122335120f05323e":23,"603a8896122335165e686cb7":30,"603a869b122335165e686cb... #hooks:0 2021-04-14 20:15:47.641 luup_log:24: EzloBridge_error: No device found for device id 32. 2021-04-14 20:15:47.642 luup_log:24: EzloBridge_error: No device found for device id 32. 2021-04-14 20:15:47.643 luup_log:24: var.SetString: wrong data type (number) for variable TamperAlarm 2021-04-14 20:15:47.644 luup_log:24: creating device numbers: [20016,20029,20023,20009,20021,20030,20031] 2021-04-14 20:15:47.645 luup_log:24: linking to remote scenes... 2021-04-14 20:15:47.645 luup.variable_set:: 24.urn:upnp-org:serviceId:altui1.DisplayLine1 was: Getting devices and scenes... now: 7 devices, 4 scenes #hooks:0 2021-04-14 20:15:47.646 luup.variable_set:: 24.urn:upnp-org:serviceId:altu
here is the logTried excluding the device but not sure what number to put tried 32 and the longer ezlo device id, but caused ezlo bridge to fail.
-
Hey @toggledbits updated to Reactor 3.9develop-21009.1600 on my VP running 7.32 and I keep getting this pop up and can't change anything in my reactor sensors because of it. I am running Alt UI 2.52 and there are no updates for it. Screen Shot 2021-03-31 at 8.33.47 PM.png
-
@toggledbits On my veraplus I try to use the plugin switchboard. On my veraplus I use a virtual window covering which can also be used in google home with tts. Now I also use openluup. The virtual window covering is not visible in openluup. Is this correct? I also use reactor in openluup. If this virtual window covering is not visible in openluup, I cannot use it in reactor either
-
Is there any chance of @amg0 becoming an active member, do you think?
He appears to be not responding on GitHub (I opened my licensing query a month back)
There are also some challenges around how things like thermostats behave in their display which would be great if we could get them fixed. Well beyond my capability 😞C
-
While i wait for MSR to arrive, i'm trying to get better control over my zigbee devices. Looked over the fence to Domoticz, and they have a really good plugin for Zigate, and as there was a domoticz bridge here, i thought i'd use that instead..
This plugin have bben abandoned for some years though, and when I installed it, it won't start properly.. looking at the startup log, it looks like OpenLuup might have had some changes that needs to be handled in the plugin? (@akbooer ?)
2021-01-26 22:31:37.457 luup.create_device:: [833] D_DomoticzBridge.xml / I_DomoticzBridge.xml / D_DomoticzBridge.json (DomoticzBridge) 2021-01-26 22:31:37.457 openLuup.chdev:: [string "L_DomoticzBridge.lua"]:59: module 'openLuup.rooms' not found: no field package.preload['openLuup.rooms'] no file './openLuup/rooms.lua' no file '/usr/local/share/lua/5.1/openLuup/rooms.lua' no file '/usr/local/share/lua/5.1/openLuup/rooms/init.lua' no file '/usr/local/lib/lua/5.1/openLuup/rooms.lua' no file '/usr/local/lib/lua/5.1/openLuup/rooms/init.lua' no file '/usr/share/lua/5.1/openLuup/rooms.lua' no file '/usr/share/lua/5.1/openLuup/rooms/init.lua' no file '../cmh-lu/openLuup/rooms.lua' no file 'files/openLuup/rooms.lua' no file 'openLuup/openLuup/rooms.lua' no file './openLuup/rooms.so' no file '/usr/local/lib/lua/5.1/openLuup/rooms.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/openLuup/rooms.so' no file '/usr/lib/lua/5.1/openLuup/rooms.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './openLuup.so' no file '/usr/local/lib/lua/5.1/openLuup.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/openLuup.so' no file '/usr/lib/lua/5.1/openLuup.so' no file '/usr/local/lib/lua/5.1/loadall.so' -
Morning, all
Couple of AltUI issues.
On this machine AltUI correctly reports its licensed status. On another machine, it claims to be unlicensed, and not of my favourites etc are reflected. Is this correct behaviour? Surely it doesn't need a licence per browser? Neither machine will upgrade to the latest version, if I select it from the pop up. Should I be doing it another way?TIA
C
-
rafale77/Amcrest-Dahua-Openluup rafale77/Amcrest-Dahua-OpenluupPlugin for Amcrest/Dahua Cameras on openLuup. Contribute to rafale77/Amcrest-Dahua-Openluup development by creating an account on GitHub.
-
So, I was bored to see all those "device not responding" banners in the Alexa app and I created a new plug-in:
dbochicchio/Vera-HABridge dbochicchio/Vera-HABridgeLuup plugin to syncronize Vera/openLuup status to HA-Bridge and Alexa. - dbochicchio/Vera-HABridge
This will update your devices' status to HA-Bridge and Alexa will finally reflect the correct status!
Just install, insert the HA-Bridge IP and port and you're done. It will work with lights and scenes (scene just to update the status and remove the "device not responding" banner). Colors are not supported, because
It will work with Vera bridged on openLuup, but HA-Bridge accessing the Vera's device directly (there's a special variable, look at the logs).
Very beta, feedback appreciated as always 🙂
I hope they'll add a way to query the status via voice soon 😉
-
The latest/working version of OpenSprinkler for openLuup, is it the one from @therealdb ?
-
Anyone using the Yamaha plugin currently? I installed it from the AltAppStore and put in the IP in the Attribute field but it never connects to it. This was working fine on the Vera side.
Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup
-
@toggledbits On my veraplus I try to use the plugin switchboard. On my veraplus I use a virtual window covering which can also be used in google home with tts. Now I also use openluup. The virtual window covering is not visible in openluup. Is this correct? I also use reactor in openluup. If this virtual window covering is not visible in openluup, I cannot use it in reactor either
-
You have to install the device type files on openLuup. Once the device type is recognized, Switchboard will let you create a device for it.
-
@toggledbits I just installed the switsboard plugin on my veraplus because vera can communicate with google home via tts visa versa. This works well with the virtual window covering created by switchboard on vera. Openluup does not have a google home plugin and cannot communicate with google home via tts. I had hoped that the virtual window covering through the verabridge would be visible in openluup so that I can program it with reactor in openluup.
-
@akbooer, since I'm not a VeraBridge user, can you provide additional guidance? I've forgotten where the magic tool is...
-
You have two options to get plugin/device files that you may need:
- pull them all down from Vera using the VeraBridge action
GetVeraFiles(no need for any Files parameter) - install the plugin whose files you need from Alt App Store (Switchboard is there)
In the case of #2, it will install a copy of the plugin, which you may not need (so can delete.)
Hope I've understood the question correctly.
- pull them all down from Vera using the VeraBridge action
-
@akbooer said in Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup:
install the plugin whose files you need from Alt App Store (Switchboard is there)
I think he already has it under openLuup. The issue is that he has no device file for the window covering, option 1 is what I was trying to remember.
-
In which case, #1 above should do it.
-
@akbooer This is not what I mean. i try to explain it again.
On my vera I created a virtual device by using switchboard. The device is a window covering device with id # 1149
In openluup I don't see this device but I can call him with luacode (device id #11149)luup.call_action("urn:upnp-org:serviceId:Dimming1", "SetLoadLevelTarget", {["newLoadlevelTarget"] = "50"},11149)
If the device is not visible in openluup I cannot use it in reactor
-
Are you sure it’s not there? Different room? ... the one named after the linked Vera?
Have you restarted openLuup so that the bridge picks up the change?
-
Thanks for quick respons
You're right. They are in a different room. I have a lot of divices so it was hard to find them but I found them in the MIOS room. -
@akbooer I did point 1 but now all my icons are no longer visible. Only the zwave icon is still visible. How can I fix this?
-
What openLuup version are you running? There was an earlier error in downloading icons that was fixed fairly recently.
Alternatively, you can simply download the icon manually and put it in openLuup’s icon/ folder.
-
Version 20.5.22.
Where can I download the icons? it's been a while since i installed openluup -
Try to update openLuup to the latest version by typing development into the Update box against openLuup on the Plugins page and clicking the update button. Then try #1 above, again.
-
Thanks! It works
-
@akbooer I've been using version 21.3.2 for a few days now, but the connection drops frequently. http: // IP: 3480 / cannot be called, so reactor doesn't work either and the lights and other things don't turn on / off automatically. Node Red can be called so my RP4 is well connected to wifi. Is it possible to go back to the old version; 20.5.22?
-
It would be really helpful if I could get a log file from you which might highlight the problem. I've not come across this difficulty myself, nor (yet) had any other reports. Has anything else changed in your system?
Does the system remain up sufficiently long for you to get the logs and also revert? You can revert to any version manually by retrieving the files in the openLuup folder from the openLuup project in GitHub:
I've fallen out of the habit of tagging releases, so there's not a sufficiently recent one that you can revert to automatically.
I really would like to get to the root of this problem, though, rather than just trying to avoid it.
-
Correction: the master branch is the version you were running, so simply updating from the Plugins page to that branch will do what you want. (It would still be good to understand what's going wrong for you in the latest.)
Edit: this release is now also tagged as v20.5.22 so you can always return to it easily by typing that into the Plugin Update box.
-
@akbooer I can't remember changing anything except installing a new version at your request. Now I am back to 20.5.22 I still have the problem. I will send a log file.
- Which log file do you want?
- Do you want the log file after I can access openluup again?
- How will I send it to you?
-
Both the startup and the main log showing, hopefully, some sort of error?
Email to openLuup @ icloud . com
Edit: maybe the latest and the .1 versions.
akbooer/openLuup
