Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
C

cubs2b23

@cubs2b23
openLuup console disappeared - 500 - Internal Server Error
A
Love openLuup - it just keeps working perfectly. I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me. All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages. I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console. Bit stumped on this one. Not sure how to debug. Any ideas?
Plugins
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
Ezlo Paid Subscription for Vera Cloud Services
toggledbitsT
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago. If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship. I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid). These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
General Discussion
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
Farewell, oh good and faithful servant!
CatmanV2C
Today marks another milestone in my Home Automation journey. After tripping the main breaker once, and shedding more blood than is normally recommended, the underfloor heating (which was the last Z-wave device on my system) has been replaced with a Zigbee one. Edited reactor.conf Disabled z-way-server Disabled Openluup Z-wave is no more.... C
General Discussion
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor
ReferenceError with Home Assistant data & build 26140
tunnusT
Topic thumbnail image
Multi-System Reactor
About
Posts
23
Topics
5
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Wall mount tablet plug-in
    C cubs2b23

    I'm doing something similar. Using FullyKiosk, TheHomeRemote and Dakboard running on a Kindle FIre 8HD. Using a MakesByMike mount as well. My wife let me "upgrade" our wall decor to be a bit more functional 😁

    IMG_1034.jpg

    Hardware

  • Getting status update from device
    C cubs2b23

    I see things like this in my setup now that I've moved to z-way instead of Vera. Like it missed the status update. I can click on the "Update All" button from the Z-way Expert UI and then everything is accurate again. And it's not missing every status update and not even for the same devices. Just one maybe two. I've often wondered if there is a way to manually send the "Update All". But that status on my lock is definitely one that often incorrect.

    @rafale77, would it be possible for you to go into more explanation of hacking the z-way lock plugin?

    Z-Wave.me

  • (Need Help) Migrate off Vera
    C cubs2b23

    @rafale77 said in (Need Help) Migrate off Vera:

    I think the best recommendation I can give you given the fact that you "only" have 30 zwave devices is to start from scratch using z-way since you already have a license for it.

    For less complicated reasons I abandoned Vera with about this many devices. It wasn’t awful to start from scratch but I’m not going to lie and say it wasn’t frustrating to have to get to that point. I moved all zwave devices to Zway with only a few hiccups.

    Vera

  • Playing sounds on the Zooz Siren ZSE19
    C cubs2b23

    I think I'm going to try excluding and including the device again. I was trying a few Get/Set commands from the Zway Expert interface last night and the Set command seems to keep failing. I've also emailed Zooz to see if they have anything to suggest.

    openLuup

  • Playing sounds on the Zooz Siren ZSE19
    C cubs2b23

    This is what is posted also on the Zooz website. Of course the article is geared toward using it on a Vera. But if it works on Vera then I'd have to think it should work outside of it. Maybe they didn't need to specify it as 0x79. I'll give it a shot.

    openLuup

  • Playing sounds on the Zooz Siren ZSE19
    C cubs2b23

    Yea that makes sense that it was formatted with Vera in mind. Here was the luup call that was also given:

    luup.call_action( "urn:micasaverde-com:serviceId:ZWaveNetwork1", "SendData", { Node="ddd", Data="x79 8 nn" }, 1 )

    So how do I modify that to work with zway?

    openLuup

  • Playing sounds on the Zooz Siren ZSE19
    C cubs2b23

    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
    
    openLuup

  • Status Board - What’s your HA Information Dashboard ?
    C cubs2b23

    Today I tried to use Fully Kiosk on an old Samsung tablet but the AltUI wouldn’t fully loaded. But it would load fine in the regular Chrome app

    General Discussion

  • Yamaha Plugin
    C cubs2b23

    That worked! Thanks @akbooer

    Vera/openLuup plugins

  • Yamaha Plugin
    C cubs2b23

    Running it on Ubuntu 20. I’ll give that a shot anyway

    Vera/openLuup plugins

  • Yamaha Plugin
    C cubs2b23

    Here's what I found in the log when installing the plugin.

    2020-11-22 12:52:18.628   openLuup.chdev:: [string "L_YamahaRxHTTP1.lua"]:40: module 'lxp' not found:
    	no field package.preload['lxp']
    	no file './lxp.lua'
    	no file '/usr/local/share/lua/5.1/lxp.lua'
    	no file '/usr/local/share/lua/5.1/lxp/init.lua'
    	no file '/usr/local/lib/lua/5.1/lxp.lua'
    	no file '/usr/local/lib/lua/5.1/lxp/init.lua'
    	no file '/usr/share/lua/5.1/lxp.lua'
    	no file '/usr/share/lua/5.1/lxp/init.lua'
    	no file '../cmh-lu/lxp.lua'
    	no file 'files/lxp.lua'
    	no file 'openLuup/lxp.lua'
    	no file './lxp.so'
    	no file '/usr/local/lib/lua/5.1/lxp.so'
    	no file '/usr/lib/x86_64-linux-gnu/lua/5.1/lxp.so'
    	no file '/usr/lib/lua/5.1/lxp.so'
    	no file '/usr/local/lib/lua/5.1/loadall.so'
    
    Vera/openLuup plugins

  • Yamaha Plugin
    C cubs2b23

    Is that in the Variables section? Mine is blank right now

    Vera/openLuup plugins

  • Telegram Plug-in to send text, images and video notifications
    C cubs2b23

    I'm seeing this as well with the dropdowns in both Firefox and Chrome. Running stable version of Reactor and v2.50 of ALTUI

    Plugins

  • Yamaha Plugin
    C cubs2b23

    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.

    Vera/openLuup plugins

  • Set/Get Yale Lock Pin Codes
    C cubs2b23

    New to Z-way and it's interface and inner workings. How do I get the list of codes already set for my lock when I was using Vera? And then how do I set new ones? Should I be looking in the standard UI or the Expert UI?

    Z-Wave.me

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    C cubs2b23

    Just to update: I decided to bite the bullet and just manually move everything over from Vera to Z-way. Still a couple of outstanding devices to transition. It went mostly smooth. I have a couple of devices that aren't responding as they did with the Vera network. Shouldn't be an issue of coverage.

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    C cubs2b23

    No go on the second attempt. So what are my other options if I don’t want to exclude/include everything?

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    C cubs2b23

    I might try the whole thing again. I just did a restore because at some point after I thought that none of it worked all my devices names were reset and all sitting in 'No Room'. Of course this was after I had switched the port back to the default Vera device. So something was happening maybe just at a snail's pace? Also how do I check the Vera's SDK version?

    Vera

  • (Problem) Migration Z-Wave NW from Vera to UZB1 dongle
    C cubs2b23

    Looks like I'm running into the same things @Trexx in migrating things over from the Vera. Stuck at the dongle.restore not being removed upon engine reload. I'm not sure if I saw if there was a resolution.

    Vera

  • Push notifications
    C cubs2b23

    Anything in particular that I'm missing to get Prowl to work in Reactor? I'm trying to move everything off the Vera but I am getting a 404 error in the LuaUPnP log. Using the same Prowl API key that Vera used. Even created a new one and tested that it worked on the Vera.

    openLuup
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved