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.
W

whyfseeguy

@whyfseeguy
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
10
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • TTS in MSR?
    W whyfseeguy

    It is working now with your recipe. I had too many "data" in data field. I was following the examples above and got confused.

    Multi-System Reactor

  • TTS in MSR?
    W whyfseeguy

    What did I do wrong?

    The service works in HA scripts but not in Reactor
    cf98e30f-bc95-4b3c-8e3f-60ea0d96d470-image.png

    Multi-System Reactor

  • Wait for http response before running the next http request
    W whyfseeguy

    In my work flow, I send a number of http requests to my device. Is it possible to wait for a http response of the current action before executing the next http request action?

    Thanks.

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    W whyfseeguy

    Here is an example of what I did with my Hikvision camera settings using MSR and ISAPI to change the scheduled switch (day/night) based on sunrise/sunset daily etc. Nearly all configurable options on the Hikvision can be changed with ISAPI.

    HTTP Request: PUT
    Request URL: http://user:pass@ipcamaddr:80/ISAPI/Image/channels/1/ISPMode
    Request Header: Content-Type: application/xml
    Request Body:

    <ISPMode xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
    <mode>schedule</mode>
    <Schedule>
    <scheduleType>day</scheduleType>
    <TimeRange>
    <beginTime>${{hikvision_sunrise}}</beginTime>
    <endTime>${{hikvision_sunset}}</endTime>
    </TimeRange>
    </Schedule>
    </ISPMode>
    

    Capture response to:
    text_response

    set the following expressions:

    text_response=
    
    hikvision_sunrise=strftime( "%R" , ( getEntity( "reactor_system>sun" ).attributes.suninfo.sunrise + ( 30 * 60 * 1000 ) ) )
    
    hikvision_sunset=strftime( "%R", ( getEntity( "reactor_system>sun" ).attributes.suninfo.sunset - ( 30 * 60 * 1000 ) ) )
    

    I offset the sunrise and sunset time by 30 mins both ways (30 * 60 * 1000). You can use civil dusk and civil dawn too if that works better for you.

    For IRCut Filter, which is where the supplemental light setting is located, set it to ON then control it with the scheduled switch (there is no ISAPI to set it on/off unfortunately)

    Request:
    http://user:passipcamaddr:80/ISAPI/Image/channels/1/IrcutFilter
    Header is the same as above
    Body:

    <IrcutFilter xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
    	<IrcutFilterType>schedule</IrcutFilterType>
    	<nightToDayFilterLevel>4</nightToDayFilterLevel>
    	<nightToDayFilterTime>5</nightToDayFilterTime>
    	<Schedule>
    		<scheduleType>day</scheduleType>
    		<TimeRange>
    			<beginTime>${{hikvision_sunrise}}</beginTime>
    			<endTime>${{hikvision_sunset}}</endTime>
    		</TimeRange>
    	</Schedule>
    </IrcutFilter>
    

    With ISAPI, there are many more things you can set on the camera without using the GUI.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    I did a pull, now running 21257. Import seems to be working. The import tool created a bunch of rules from Vera Reactor. I will go through them 1 at a time to make the necessary changes. I will report back later if there are issues related to this.

    Thanks again.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    Yes I am using Vera Geofencing.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    Hi Patrick,

    Running MSR on docker.

    Trying to import the reactor config from Vera.

    My workflow is:

    1. docker exec -it reactor /bin/sh
    2. /opt/reactor # node tools/import_reactor_backup.js /var/reactor/reactor-config-backup.json vera

    Got the following error: (After restarting, no reactor config from Vera was imported)
    Fetching current rulesets...
    Pass 1: Translating...
    ReactorSensor 134 Auto (un)lock doors
    Creating ruleset for ReactorSensor 134 Auto (un)lock doors
    Creating rule rule-134
    ReactorSensor 139 Auto Lights
    Creating ruleset for ReactorSensor 139 Auto Lights
    Creating rule rule-139
    ReactorSensor 143 Somfy Control
    Creating ruleset for ReactorSensor 143 Somfy Control
    Creating rule rule-143
    ReactorSensor 167 Blue Iris Control
    Creating ruleset for ReactorSensor 167 Blue Iris Control
    Creating rule rule-167
    ReactorSensor 183 Towel and Heater Sch
    Creating ruleset for ReactorSensor 183 Towel and Heater Sch
    Creating rule rule-183
    ReactorSensor 208 Geofencing Action
    Creating ruleset for ReactorSensor 208 Geofencing Action
    Creating rule rule-208
    (node:639) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:185:82)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:438:13
    at Array.forEach (<anonymous>)
    at /opt/reactor/tools/import_reactor_backup.js:402:34
    (Use node --trace-warnings ... to show where the warning was created)
    (node:639) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:639) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

    Any help will be appreciated. The worst case scenario is to re-do all the triggers and conditions in MSR from the ground up.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    I updated to 21256 (docker). The http put is working for me now. Thank you for the quick fix to the issue.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    Hi Patrick,

    I got a 403 when the body is empty, indicating it has passed through the MSR, it got rejected by the camera. So I say it is working without the body as MSR did not throw an error.

    Thanks.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    Using MSR on Docker. The automation is to send xml body to my Hikvision camera to change the WDR based on the time of day. But getting the following error:

    TypeError: Cannot read property 'length' of undefined
    at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:1319:192)
    at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:1114:100)

    My MSR rule:

    HTTP Request: PUT

    HTTP Request: http://camipaddr/ISAPI/Image/channels/1/WDR/day
    HTTP Header: Content-Type: application/xml; charset="UTF-8"
    HTTP Body:
    <?xml version="1.0" encoding="UTF-8"?>
    <WDR version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
    <mode>open</mode>
    <WDRLevel>40</WDRLevel>
    </WDR>

    Any idea why I am getting the above error?

    Thanks.

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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