-
Hello - the new pi has arrived with uzb. As an installation shortcut is there a way of 'factory resetting' openluup if I cloned the working image on my other pi ... or is that a really bad idea?
-
Do you think it could be possible to have a custom device for "dimmer" that instead of having the slider from 0 to 99 will give us Off/Low/Medium/High and will send 0,30,60,90 ?
-
I'm a fan of the SendConfig call action in a couple of scene...
Did you implement something like GetConfig ?
I have a couple of scene that I would need to do a GetConfig to do something based on the value...
-
I was trying to change the ID of a couple of scenes and came to the conclusion you can't do this without stopping openLuup, hacking user_data.json and restarting openLuup, which is a pain. (May be this could be added to openLuup ie be able change any scene ID to a non used one.)
So I figured I would try and clone some of the scenes with the idea that I could then manually swap their contents around. Why would I want to do this? Just to make my scene management a bit more simple as all my scenes call the one pile of Lua code. I also wanted to make use of unused scene IDs sprinkled through the scene ID list.
My understanding was the clone would occupy the first unused scene ID. Using AltUI, it just adds the clone on to the end of the list of scene IDs. In openLuup using the console page it failed to create the clone. Hits the URL OK:
http://openLuup:3480/console?action=clone&scene=14Says this in the log:
GET /console?action=clone&scene=14 HTTP/1.1 tcp{client}: 0x2c05008Searched high and low and no clones to be found.
I see that AltUI does a create when it clones:
openLuup.server:: GET /data_request?id=scene&action=create&json=WITH_ALL_THE_SCENE_INFO_HEREAny ideas?
-
I woke up to one of the lights in the hallway dimming up and down constantly.. when i tried to open reactor logic summary, there was something weird with the GUI?
The "Tools" tab resizes so i can't reach the logic summary button:
24f6b3f7-cfca-45ba-b568-7c6f5a31ddd7-image.pngThe Reactor instance in Altui pages was also empty, no buttons or text on them, only the icon..
I have a virtual switch to turn on all lights using reactor, and that one worked from the tablet in the kitchen, so reactor was functioning OK..
I reloaded luup and hard refreshed the browser, and all but the "Tools" page is now back to normal.. @toggledbits ?
EDIT: Theres supposed to be some text in the headers on this page, isn't it?
70159d9d-85fc-4606-b38b-49f2909dce72-image.png -
Have you ever considered running openLuup under LuaJIT instead of Lua5.1 interpreter?
The LuaJIT Project
For kicks, I switched my installation to the latest LuaJIT2.1 beta3 dating from 2017 and being a lua5.1 interpreter it is a drop in replacement. I had to move the lfs library from one folder to another likely because of an include path difference but I am seeing a further speed/efficiency improvement vs. lua5.1.
My CPU load has dropped another 25% to now hover around 2.2% down from 2.8%. I have yet to make sure that everything else works but so far everything appears to be the same.
The luajit site claims up to 5x speed increase through the interpreter and 120x improvement through the compiler vs the standard lua5.1.Screen Shot 2020-07-05 at 23.10.02.png
My initial interest was from being able to access some ffi libraries to handle video streams...
PS: Wow it is pretty impressive under load... browsing through ALTUI which used to cause spikes of CPU utilization from 2.8% to 4.8% now only go from 2.3% to 2.6%. It almost looks like noise. I am running it on a pretty fast x64 thread so it may not be that significant but this could make a big difference on ARM.
-
Windows Subsystem for Linux (WSL) is a compatibility layer for running Linux binary executables natively on Windows 10.
This is one way to run openLuup under Windows without having to worry whether any of your plugins require a Unix/Linux environment – this way, they actually get one.
Many flavours of Linux are available for WSL from the Microsoft Store – my favourite, to date, is Alpine WSL, which is a tiny (~8 Mb) and lightweight WSL distro based on musl, uses busybox, and just contains the most important things to be functional.
Here's a rough guide to getting openLuup going under Alpine WSL
Enable WSL on via the Windows control panel Install the Alpine WSL app from the Microsoft Store Start the Alpine application Install Lua and some libraries:Alpine comes with a really full set of Lua libraries available for install. You need to be su to install them:
# apk add curl # apk add lua5.1 # apk add lua5.1-md5 # apk add lua5.1-cjson # apk add lua5.1-filesystem # apk add lua5.1-bitop # apk add lua5.1-sec You need to make the file system permanent: $ cd /mnt/c/ $ mkdir cmh-ludl $ cd cmh-ludl Now get and install openLuup and AltUI: $ wget https://github.com/akbooer/openLuup/raw/master/Utilities/openLuup_install.lua $ lua5.1 openLuup_install.luaWhen finished (it won't yet return to the command prompt)
access openLuup via the URL: IP:3480/openLuup Update to latest version (Plugins page, type development in Update box) Install VeraBridge (Device Table > Create D_VeraBridge.xml / I_VeraBridge.xml) Add IP of Vera to VeraBridge attributes Reload VeraBridge device > Actions > GetVeraFiles (wait ~2 minutes) ReloadSimple!
-
A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:
...I want to work in a more open and stable [Vera] environment...
...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?
1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modificationWhat we wouldn’t need is UPnP.
What have we (nearly) got already?
We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.Is it worth the effort? Probably not. Will I pursue this quest? Yes.
openLuup was the result.
-
Evening, all. Hope you're all well.
Did the logging line count / rotation challenge ever get sorted? I'm needing to look back at some historical events and my oldest log is barely 3 hours ago. (Not that I can recall how to try and change the line numbers etc)
Cheers!
C
-
I've been fiddling with the zigate plugin, as the dongle arrived.. I installed the app from appstore, and saw that the plugin files were not installed properly.
Downloaded the zip files and put all luup files in the cmh_ludl folder. Reloaded luup, and it was in and looking ok
I then entered the IP for it to communicate with the dongle, and reloaded luup.Now the openluup service is running, but i can't get into either altUI or openluup console.
I tried rebooting, stopping and starting the service, no effect.
the logs doesnt seem to be updated either. Now what?
-
I'm trying to do this now that I have migrated the siren to Zway. Here's the thread from the Vera forums on how to do it with a Vera: https://community.getvera.com/t/playing-sounds-on-the-zooz-siren-zse19/211318
I'm guessing something needs to change in the code since previously it was calling out the vera specifically.
Here's what shows up in the logs when I tried to use Reactor for the SendData. Zway plugin is device 18. And my siren is device number 95 in my Zway network.
2020-12-01 15:37:27.052 openLuup.server:: POST /data_request HTTP/1.1 tcp{client}: 0x56194138c448 2020-12-01 15:37:27.052 luup.call_action:: 18.urn:micasaverde-com:serviceId:ZWaveNetwork1.SendData 2020-12-01 15:37:27.053 openLuup.server:: request completed (151 bytes, 1 chunks, 0 ms) tcp{client}: 0x56194138c448 2020-12-01 15:37:27.079 luup_log:18: ZWay: http://127.0.0.1:8083/ZWaveAPI/Run/SendData(95,x79 8 35) 2020-12-01 15:37:27.079 luup_log:18: ZWay: SyntaxError: Unexpected number 2020-12-01 15:37:27.184 openLuup.server:: request completed (8606 bytes, 1 chunks, 5939 ms) tcp{client}: 0x561941d02fe8 -
While i wait for a replacement app for my local UI devices, i want to use imperihome as long as I can.. But i'm missing a lot of devices!
All Z-Way bridge devices, all security/smoke and motion sensors (local RFXtrx child devices)..
Found the "include vera bridge" in imperihome.lua, what else could cause this?
-
I downloaded ZeroBrane Studio to see if I could make sense of this lua language. @akbooer mentioned that this is what he uses for development, and i thought i could learn alot from seeing how openluup runs.
How do I proceed in order to run openluup in zerobrane? I guess i need to do that to see how scripts like the imperihome ISS script works?
I installed on a windows machine, will I have to run it in linux for it to work?
-
Hi @mrFarmer,
I also have a question about ImperiHome:
I'm trying to configure imperihome with openluup.
Imperihome recognizes the new system, with all devices, status feedback is perfect.
If I turn on something on imperihome, it will seem to be temporarily turned on and then turn off. Device does not actually change.
Can you help me with what could be the problem?
Thanks.
Krisztian -
Hi,
I have a couple of luup request, one is a request to VeraAlexa pluging to make alexa speak, the other updating a variable in reactor. They all seem to have a 10-20 second delay
example request
http://192.168.1.134:3480/data_request?id=action&DeviceNum=44&serviceId=urn:toggledbits-com:serviceId:ReactorSensor&action=SetVariable&VariableName=A_home&NewValue=1I can not figure out what is causing the delay, does anyone have any ideas?
-
-
Hi guys,
I was wondering what you guys use for push notifications on openluup. I still use VeraAlerts on my vera, but am searching for an alternative that runs on openluup.
Thanks!
-
I'm using RulesEngine plugin for a while, couple of years, and of course, the plugin is not getting any update as @vosmont stop to update/upgrade this plugin!
I attached one rule, if, by any chance, I would like to convert all my rules to something "native" in openLuup...
is it something possible ?
In the PDF you can see what a rule looks...ALTUI.pdf -
I have some code failing on Vera from time to time. All I got is:
attempt to call a string valueand usually a luup.reload will fix it. It should be something related to startup and scene collision.
Is there a way to really trace lua calls? I'm a DIY regarding LUA and I'm sure there should be a better way to trace and debug errors.
I'll try to code something in order to detect this situation and reload luup, because it's blocking my scenes.
Yes, I know I should migrate all my logic to openLuup, but I can't at the moment.
-
Hi guys,
I’m researching the move away from Vera and z-way has the most chance at this point. However, I came across the geolocation aspect of my setup.
I now use Vera Proximity. It works, but is not the most ideal solution. This won’t be an option anymore after I’ve migrated, so I was wondering what you guys use for geolocation.
AltUI/Reactor issue?
-
I woke up to one of the lights in the hallway dimming up and down constantly.. when i tried to open reactor logic summary, there was something weird with the GUI?
The "Tools" tab resizes so i can't reach the logic summary button:
The Reactor instance in Altui pages was also empty, no buttons or text on them, only the icon..
I have a virtual switch to turn on all lights using reactor, and that one worked from the tablet in the kitchen, so reactor was functioning OK..
I reloaded luup and hard refreshed the browser, and all but the "Tools" page is now back to normal.. @toggledbits ?
EDIT: Theres supposed to be some text in the headers on this page, isn't it?
-
I see the same after installing the latest ALTUI version.
-
My conclusion is that the jquery 3.5.1 has some changes that cause this. The Reactor showGroupStatus function is not populating the text as it did before.
-
@mrfarmer
May be related.
Occasionally, (indeed happened on the latest ALTUI update), after updating ALTUI, a Reactor will lose the buttons at the bottom. The picture below attempts to illustrate.
At this point, I do not dig into the reactor UI to see any other oddness like (maybe) the screenshots posted above. Instead, when I see this, I'll reset ALTUI by . . .
Reload & refresh the luup engine / browser, and Reactor is back to normal.
. . . Just a guess
DCMChrissy -
Did you get back the full "Tools" page on the reactors as well? I didn't..
-
This is related to the recent updates to jQuery and Bootstrap, and has particular effect on Firefox, less so on Chrome. I'm working at fixing this, but as you might realize, it requires a fairly extensive review and I have to check every function on every browser, so it's going to be a while. I recommend downgrading your ALTUI to the version you were previously running if you need to get back on the air right away. I'm also going to publish the supported versions of ALTUI in the CHANGELOG of future releases, and enforce it in the code.
-
@perh
No, I did not notice. I guess I would have realized it the next time I wanted to look at a logic summary!Crap
Guess I should figure a way to roll back . . .
On Chrome by the way.
-
Rolling back AltUI under openLuup is trivial: simply type the tagged release number into the Plugins page AltUI Update box and click to update. Recent tagged releases are 2550 and 2545.
-
rolled back to 2545, but i guess not everything rolled back, cause the issue is still there.. Do i have to go commando line then?
-
Reset ALTUI and hard refresh browser worked for me.
-
@elcid said in AltUI/Reactor issue?:
hard refresh browser
Indded, critical when you're dealing with a JavaScript issue.
-
strange, i'm at version "2.52." and the pop-up for new altui version comes up. I did Ctrl+F5 in chrome, and even tried to open it in edge, and the problem with reactor persists.. Reactor version github.stable
-
@perh said in AltUI/Reactor issue?:
2.52.
Well, you’re at version 2.52.nnnn, and it’s the four digit build number that will be tagged. Not all of them are, indeed the latest one (2552) is not (yet.)
-
OK gang. I have what I think is complete, and about halfway tested. Things are looking good on Windows at this point, at least, and lately it's been pretty rare to find Mac-specific issues. You can install the stable branch release for the latest. The easiest way to do that, I think, is to go to the Plugins page, type "stable" in the version field and hit the update button. You'll need a Luup reload and a browser refresh when it's done. The version stamp is 20345. If you don't see that in the footer of various tabs (e.g. Tools is a good place), your upgrade didn't succeed. Please report any other bugs you find to me here, or on that other forum.
-
I am likely the one who caused all of this ALTUI troubles. Sorry, I run ALTUI on local CDN and noticed a bunch of missing and erroneous ones from my browser console so I went on a rampage to update all of them and pushed my updates to ALTUI which then prompted @amg0 to also update the remote cdn versions. On the bright side, it fixed some minor errors for local CDNs and bootstrap feels much faster.
-
Not my project to manage, but I did ask @amg0 to consider making a separate development or stable branch from which interim releases can be done periodically and followed, so we can get an early view of what's coming and be prepared for it, and it's not a fire-drill to catch up with whatever changes when a new release suddenly hits the master branch.
I would also ask that you both keep in mind that ALTUI already has some significant differences in the implementation of the UI7 API emulation and, even before these upgrades, the jQuery and Bootstrap. This makes it very difficult to create a JS UI of any complexity that runs well and has good layouts on both platforms, without having completely divergent code bases between them (Reactor's UI is more than 50% of its total code). Even for more basic plugins than Reactor, these upgrades may yet be discovered to have broken their many UIs; we'll see. But if the project keeps running and tracking to the latest external libraries, it will arrive at a point where someone in my (plugin) position can no longer maintain a common code base, and at that point, one of the big incentives to move to openLuup (its "out of the box" compatibility with existing plugins) goes away. That needs to be considered. It's just a hazard of the position both @akbooer and @amg0 came from and are in right now. When Vera is well and truly gone, then it can be gloves off and anything goes, and I look forward to seeing what changes come from their imaginations and dreams when those restraints are removed. But for the moment, I think these steps need to be more measured.
My 2p only.
-
That fixed all UI issues inside the reactors for me, the buttons on the widget is gone though.
Never use them myself, and if i need them they're available in the status tab.
Thanks! -
@perh This is what the widget now looks like for me. Are you seeing different? Did you do the hard refresh of your browser after upgrading?
There are no buttons on the master device (and this is as it should be).
-
-
And what's the version number reported in the footer of the Tools tab of that ReactorSensor?