Skip to content

openLuup

The goodness of vera without the bad. Discuss installation problems and improvements.

186 Topics 3.0k Posts

Subcategories


  • Discuss your other openLuup plugins here

    44 Topics
    871 Posts
    M

    Hi Ak,
    Not sure what the issue is for me then. I first had it running on Pi3 with Debian, now on Pi4 with Ubuntu, same issue of not getting the token. I did copy the user_data.json, so maybe something in that.
    As a test I tried on my openLuup clean test install running in a container and that is working. So must be something at my end.
    Thanks again anyway, I have a new workaround :-).

  • The vera integration of openLuup

    8 Topics
    102 Posts
    parkercP

    Just wanted to add that my Vera Bridges stopped working, I can’t be sure exactly when, maybe after a reboot ? But wanted to share here as they were working fine..

    850065d5-00f8-44e6-b75d-5ae9a21a272d-image.png

    The Variable for the RemotePort on both is /port_3480

    Updating to :3480 fixes it..

    @akbooer - not sure why this worked first and then stopped..

  • 0 Topics
    0 Posts
    No new posts.
  • The Z-way integration for openLuup

    20 Topics
    418 Posts
    akbooerA

    You only get that lucky once in every four years!

  • 4 Topics
    73 Posts
    akbooerA

    It doesn’t really matter, but it does need to have the executable permission.

  • BlueIris, MQTT and openLuup

    6
    0 Votes
    6 Posts
    302 Views
    therealdbT

    @buxton feel free to grab the code, or use one of the devices. I’m still adding and tweaking things, but it’s working for 90% of the use cases.

  • call_action SendConfig

    52
    0 Votes
    52 Posts
    3k Views
    akbooerA

    Ah, indeed, this is how (and where) we left it...

    @akbooer said in Renaming device name...:

    Actually, it seems that I lied...

    ...I've just checked the code and the device name update is not implemented. I recall, now, that I did look at it and stopped because, rather surprisingly, it seemed too hard to do at the time.

    I’ll check once again and remind myself why this is so hard...

  • Migration from debian -> ubuntu

    8
    0 Votes
    8 Posts
    282 Views
    DesTD

    @akbooer There's no problem with 5.1, just curious about using the latest version! But luajit is faster, so using luajit now 😉

  • OpenLuup via the command line

    8
    0 Votes
    8 Posts
    312 Views
    parkercP

    @akbooer 😂

  • Rapidjson instead of cjson and dkjson

    31
    0 Votes
    31 Posts
    5k Views
    rafale77R

    Just finished tinkering with my installation and pushed to my fork. I am only now pretty formatting a few selected encoding calls from the "scene.lua" and "console.lua" files

  • Openluup control of Alexa

    23
    0 Votes
    23 Posts
    876 Views
    CatmanV2C

    @akbooer said in Openluup control of Alexa:

    @catmanv2

    Any reason not to be using the latest openLuup version (from the development branch) ?

    None other than I wasn't keeping track of what was available!

    Now on 21.4.20 TYVM

    C

  • openLuup won't upgrade from 2020.05.22

    8
    0 Votes
    8 Posts
    201 Views
    akbooerA

    No. The master branch (which is the default) is back on 2020.05.22. It’s usually behind the development version, but not usually that far. I should roll up all the latest changes to it soon.

  • Restoring OpenLuup

    19
    0 Votes
    19 Posts
    605 Views
    M

    If there is some reason the initial http response to pull the full controller config for ALTUI takes longer than the configured in the ALTUI ControlTimeout mS you will see this. I set this variable to 9000 and that is sufficient, even via a pihole remote connection. Setting it too long I have seen it holding other openLuup/plugin http requests in case of a delay for what ever reason. So it looks like finding a balance for your setup a bit.

    Cheers Rene

  • OpenLuup unavailable

    88
    0 Votes
    88 Posts
    6k Views
    akbooerA

    I’m entirely dependant now on openLuup’s MQTT server, and it seems to be performing flawlessly for me under Synology docker and Homebridge.

  • My newbie questions

    22
    0 Votes
    22 Posts
    974 Views
    CrilleC

    Ah, brilliant! Thank you.

  • AltUI and Console gui

    15
    0 Votes
    15 Posts
    431 Views
    A

    @akbooer yepp, now it displays the value, thanks for that!

  • New to openLuup, issues with scenes

    13
    0 Votes
    13 Posts
    372 Views
    akbooerA

    @rafale77 said in New to openLuup, issues with scenes:

    Note that the scene trigger mechanism is probably the major difference with the vera in terms of setup

    Indeed!

    There is additionally, in fact, an in-built trigger mechanism that is a sort of a blend of the two, in that the trigger happens when a variable changes, but, unlike AltUI and just like Vera, each trigger can have its own Lua code and the scenes have full Lua code capability too (not just a logical variable.). The best of both worlds, IMHO.

    However, I haven't developed the console interface for it, since I really think that scenes are becoming a rather out-moded concept, in favour of the amazing work the @toggledbits is doing with Reactor / MSR.

  • Wrong dimmer value in gui

    35
    0 Votes
    35 Posts
    1k Views
    rafale77R

    Ohh. yeah they are managed by the J_ALTUIplugins.js file... Not my design. They indeed do not make use of the device json so I have tinkered with that file in the past as well.

  • Vera Decoupled from the cloud services

    12
    0 Votes
    12 Posts
    395 Views
    M

    @rafale77 thanks I will read that first

  • Custom device for dimmer

    6
    0 Votes
    6 Posts
    243 Views
    therealdbT

    I have a version working to draw the inside panel, but the main one (in the device page) is blank, because ALTUI is using Javascript to render it (I remembered it was trying to display standard json device file, but I was wrong and @akbooer was obviously right :)).

    a6ae4b98-2de6-4c63-960b-dfe867513632-image.png

    I could attach it anyway, if you want, while I'm trying to create a more general way to render plugins using the json device file, a promise Vera failed to deliver but that will really simplify the plug-in experience under ALTUI/openLuup.

  • Odd console display for triggers

    2
    0 Votes
    2 Posts
    118 Views
    akbooerA

    This is taken from the AltUI variable VariablesToWatch. It may be that I am parsing it incorrectly (I do wish that it was in JSON format!)

    I'll try to fix it, but I wouldn't worry about it too much. Thanks for reporting it.

  • websocket

    8
    0 Votes
    8 Posts
    281 Views
    rafale77R

    Would be nice to get this fixed as it is quite distracting on MSR but could also be some wasted CPU clock when using ALTUI. For sure the scenes seem to update without running at all and so are the rooms.

  • Security Sensor LastTrip behavior

    23
    0 Votes
    23 Posts
    790 Views
    rafale77R

    @therealdb

    You are right, I just went back to the ALTUI code and I can see that it's hard to do. I am not so verse in JS so I tried avoiding it. It makes for more changes but it is the safer route.

    @akbooer

    to answer your question, let me test further to see if we can think of even better ways to do it.

  • Missing App store contents in openLuup

    8
    0 Votes
    8 Posts
    293 Views
    A

    WARNING: DO THIS WRONG AND IT ALL GOES BADLY WRONG.

    Following refers to openLuup running on Jessie, on a RasPi with openSSL version:

    OpenSSL 1.0.1t 3 May 2016

    I made the mistake of running this command in the hope of it fixing the Telegram and the GitHub app store access problems I was having:

    sudo luarocks install luasec

    No good - can't find what's needed. So do this:

    sudo luarocks install luasec OPENSSL_LIBDIR=/usr/lib/arm-linux-gnueabihf/

    All goes OK - reboot the RasPi. And then errors:

    /etc/cmh-ludl$ /etc/cmh-ludl/openLuup_reload lua5.1: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.1/ssl.so': /usr/local/lib/lua/5.1/ssl.so: undefined symbol: X509_get_signature_nid stack traceback: [C]: ? [C]: in function 'G_require' openLuup/init.lua:86: in function 'require' /usr/local/share/lua/5.1/ssl.lua:8: in main chunk [C]: in function 'G_require' openLuup/init.lua:86: in function 'require' /usr/local/share/lua/5.1/ssl/https.lua:10: in main chunk [C]: in function 'G_require' openLuup/init.lua:86: in function 'require' ./openLuup/client.lua:39: in main chunk [C]: in function 'G_require' openLuup/init.lua:86: in function 'require' ./openLuup/luup.lua:85: in main chunk [C]: in function 'G_require' openLuup/init.lua:86: in function 'require' openLuup/init.lua:93: in main chunk

    Many hours later after much bashing of keyboard - removed luasec:

    luarocks remove luasec

    And install the most recent version of luasec version 0.7 that will work with the old openSSL version "OpenSSL 1.0.1t 3 May 2016":

    sudo luarocks install luasec 0.7 OPENSSL_LIBDIR=/usr/lib/arm-linux-gnueabihf/

    Note this this link where it says:

    Notice:

    LuaSec 0.8 requires at least OpenSSL 1.0.2. For old versions of OpenSSL, use LuaSec 0.7.

    Telegram and App Store access now fixed but I did so much messing around in between, it's hard to say if this is the actual fix!

  • Generic support for external plug-ins in different languages

    21
    1 Votes
    21 Posts
    993 Views
    akbooerA

    As you may have seen, it’s available in the latest development release.

Recent Topics