New to the forum
-
If you just want to experiment, install windows subsystem for linux. My dev pc is a Windows machine but thanks to WSL I have a true Linux environment running side by side on Windows. That’s what I’m using to develop for openluup (and for my Linux dev needs in general).
-
Great introduction. The background can really help when we’re giving suggestions.
It’s not the case that you need massively capable hardware to run openLuup. The most popular platform is, perhaps, Raspberry Pi, and even then it only uses a few 10s of Mbytes and ~5% cpu. But there are many options, and I’m about to follow a route that others have forged previously to run openLuup under Docker on a Synology NAS... so we’ll all be learning something new over the next few weeks.
Lua 5.1.5 is, indeed, ‘Lua 5.1’, and the best choice. Necessary additional Lua modules may come with your initial installation, or need to be added. There’s a list in the User Guide.
-
Nice,
ok, well I installed the Linux subsystem, Lua 5.1 and the dependencies.
@therealdb thanks for the suggestion. It seems to be running alright. Any pointers on how I can have this start with Windows? The user guide only mentions scripts for Linux systems in the appendix. -
Just search for wsl 2 and you’ll find everything you need.
It’s just going to Windows Store and install your favorite distro, ie Ubuntu.
-
@therealdb Yes, I did that already. I'm just wondering if I need to open the Bash console and start OpenLuup every time I reboot or if I can set it to start with each boot.
Everything seemed to go alright, but when I open AltUI, I immediately get a message box that says "fail". The weather is showing Paris, and I can't control any of my LIFX bulbs that I imported from the Vera using VeraBridge.
Also, the app store is blank. I haven't finished reading the user guide yet though. -
If you access your system through the openLuup console...
http://openLuupIP:3480/openLuup...then you should have a fairly familiar interface quite independently of any AltUI configuration issues. This also gives you access to the log files, which may help.
-
Don't burn you stuff guys... :). There is actually nothing wrong with the vera hardware which I found to be actually quite well designed. (much better than the junk eZLO put out). It's the firmware/software which is to blame.
@Quixote, it should cost you nothing to start on windows and tinker with openLuup. I have reused the vera from quite some time for its zigbee radio and could have used its zwave radio as well. The zigbee antenna just happens to be quite weak on it. In order to use them you will however will need a radio host controller. For zigbee, I found home-assistant's zha component to work quite well. For zwave, openzwave (openhab, domoticz, home-assistant), homeseer all can use it. Unfortunately there is no bridge to openluup for these controllers. -
@rafale77, I will not be branching out into Zigbee. I figure the less complicated the system, the more reliable and the less problems to troubleshoot. Maybe if I had gone with Hue instead of LIFX, but I'm pretty happy with the brightness and vivid colors of these lights.
I had every intention of continuing to use the Vera for Zwave with openLuup, but it's becoming apparent that I'd be a lot better off just biting the bullet and buying a UZB dongle and a license for Z-Way. My VeraBridge does not seem to be cooperating, though to be honest I only tested it with my LIFX bulbs and I think I missed a crucial step (like importing the LIFX plugin or something). The plugin is not listed on the store. I tried the sliders that appear for the lights, but they are very unpredictable and do not include any options for color changes. -
Have you got AltUI going correctly? Don’t expect the openLuup console to be a complete replacement, particularly for fancy UI things.
If AltUI is not working correctly, then something fairly basic is probably wrong with the configuration. One of the first thing to look at is the locale setting on your machine.
-
Quixotereplied to akbooer on Dec 6, 2020, 8:36 PM last edited by Quixote Dec 6, 2020, 3:39 PM
@akbooer
I stopped trying to get AltUI working since using openLuup's UI seemed to work. Plus I can't see myself paying a recurring subscription fee for a UI that ideally I will never have to see or use after getting everything set up correctly. I'm too cheap to pay a year's subscription for something that I may use for 3 hours after the initial programming. Now, if it were a one time version fee...Loading AltUI gives me a popup box that says simply, "fail". That hurts my feelings.
When I installed Lua and the dependencies, everything went smoothly. Installing openLuup seemed to hang near the end of the installation, but I was able to start it and display AltUI in windows Firefox (with the "fail" message). I was able to update VeraBridge, which seems to have installed it. With VeraBridge I hit "GetVeraFiles" and observed the devices listed. I see a device for LIFX Plugin, but playing with the sliders/power icons for those lights does not yield the correct results. Strangely, I can make the coinciding light do unpredictable things though sometimes.
The locale setting that you mentioned would be set in the Linux subsystem? or within AltUI? I never use any other language but English, but it's possible that my system is trying to use French since I reside in Quebec, Canada.
Thanks -
Yes, the Linux locale. French or English would be OK, since it has language files for both, so perhaps this is not the issue.
The JavaScript used by plugins for AltUI will not run in the openLuup console interface.
-
My Locale is set to en_US.utf8, so I'm all good in that regard.
@akbooer said in New to the forum:
The JavaScript used by plugins for AltUI will not run in the openLuup console interface.
Ok, and what's that in English?
-
The openLuup console is not an all-singing and all-dancing UI, doesn’t support fancy browser-based extensions, and isn’t meant as an everyday replacement for AltUI, which remains the primary user-interface for openLuup. Indeed, it’s currently necessary for defining new scenes and variable-watch triggers.
If it’s not running, there’s probably something wrong with your system configuration, although that may have something to do with not having a licence. On the scale of HA installations, it’s not a big cost.
-
Quixotereplied to akbooer on Dec 7, 2020, 8:42 AM last edited by Quixote Dec 7, 2020, 3:47 AM
@akbooer fair enough, but, at the risk of sounding ungrateful, I've barely left the starting gate here -- no new scenes, "variable-watch triggers": I have no idea but probably since you brought them up.
Not sure why I would need a license immediately, but in any case, to me it's like paying a yearly subscription for an Echo. When I bought it, it did what it did. Any other developments are the choice of the developer to invest the time into that in order to entice more clients and keep existing ones from leaving for something more appealing. Again, I'm not against a one time fee, but a reoccurring fee doesn't work for me. I also understand that it's in your best interest to have a developer that is well-versed in your project and fully capable of complimenting it on so many levels, however, a dependency on a commercial entity pretty much means that you are no longer "open".
Am I way out of line here?
Oh, and just by the way, if you need icons or anything, I'm willing to help you with that. I have a background in graphic design. -
It’s a fact of history that openLuup would not have existed without AltUI. There’s no way I have the skills to make a modern web interface with asynchronous updates, etc. As my frustrations with Vera grew, AltUI was a huge innovation, which kept me with Vera. TBH, I can’t really imagine using Vera without it, now. After further frustration with the performance and behaviour of the Vera Luup engine, I realised that I did have the skills to develop openLuup.
It’s entirely open, and so BTW is AltUI. Everything is available on GitHub. I don’t consider @amg0 to be a commercial entity, but I take your point, and eschew subscription arrangements for most things. But needs must.
You can certainly continue up to a point with the openLuup interface, but I’m just pointing out that it has its limitations, and the LIFX interface is one such. I’m sure we can get around this, since you imply that you want to control this through one app or other. How is everything else working?
-
You don't have to pay for 95% of the functions of AltUI as long as you can live with an "unregistered" banner at the bottom. I did that for years, not sure if i actually had to register for how i use it.
On the other side, i'm now so happy with it, that I thought a donation was in order.
try this:[IP]:3480/data_request?id=lr_ALTUI_Handler&command=home&lang=en
That forces use of english. -
Quixotereplied to akbooer on Dec 8, 2020, 10:11 AM last edited by Quixote Dec 8, 2020, 5:13 AM
@akbooer Unfortunately, not great. I've been trying to set it up so that it will run on boot, but since I followed therealdb's advice and installed WSL on my Windows 10 installation, I've discovered that it doesn't use systemd and it appears I'm on my own in figuring this out now. At this point I'm feeling quite stupid and can't even figure out how to start openLuup again, but I must just be having a bad day.
The other obstacle is that I really don't have that many Zwave devices and my alarm system isn't even set up at this point, so even if I were able to get some traction, every Zwave trigger I have (motion sensor, Wallmote quad) leads to a LIFX light action. I was not able to get those to work, so at this point my tests will generally be meaningless.
@PerH thank you for the tip. I'll look at that once I can get it started again without following the install method all over again that's the only way I've seen in the manual, (aside from scripts for other system types). -
There are three alternatives for starting at boot time documented in the User Guide. I don’t know if either of the alternatives are suitable for your use case. To run openLuup, you just need to run the openLuup_reload.bat file, which wraps Lua in a loop which allows Luup reloads to work.
-
I thought batch files were exclusive to a DOS/Windows environment.
I had attempted to set up loading at boot using the the Systemctl approach listed in the appendix, but WSL rejects Systemctl/Stystemd. Everything I've read online states that it's not needed, however fails to mention what to do instead.
25/81
