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

noelab

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

Posts

Recent Best Controversial

  • Release 1.0.0
    N noelab

    Hi everybody!
    I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
    I just installed MSR and I am excited to try it out!

    Multi-System Reactor

  • Dashboard extended to guests with visible/hidden icons - an idea?
    N noelab

    Hi, I like a lot the MSR Dashboard: it's quick and easy without an authentication system and this is great.

    Not really a good idea if I give this possibility to my wife to power off all switches included the nas with MSR or to a guest to power off the light in my room.

    Is it scheduled to have a main dashboard and a guest dashboard? as a sub-dashboard

    Maybe from the main dashboard, using a built-in GUI editors that can set icons as visible or hidden and automatically reflect on a guest dashboard with a different ip

    Just an idea 🙂 for MSR

    Multi-System Reactor

  • Merry Christmas/Happy Holidays
    N noelab

    Happy Holidays and very best wishes for a wonderfull and reactor New Year! 🙂

    General Discussion

  • Synology Docker installation
    N noelab

    @librasun yes, of course I agree with you. In Vera I based my logic using a virtual dimmer (Switchboard Plugin) per room to interact with Alexa commands behind conditions/rules in a Reactorsensor per room and only some global reactor for the house. In this way it is possible to have until 100 voice commands per room associated to 100 preset rules per dimmer, controlling them in web gui, in mobile app or alexa. So at the moment trying to understand if there is a new approach in MSR to emulate virtual devices or to find another way.

    Multi-System Reactor

  • Plugin InfluxFeed - Selecting Capabilities for Export - how to
    N noelab

    Thanks to you!
    The fix is working.
    Now I can truck energy consuption on Influxdb. The idea is to try to make in MSR what in HA is doing with utility_meter, Trend and Lovelace UI togheter. Maybe in future we will see a standard MSR energy plugin too.

    Home Assistant

    Utility Meter

    Utility Meter

    Instructions on how to integrate the Utility Meter into Home Assistant.

    Home Assistant

    Trend

    Trend

    Instructions on how to integrate Trend binary sensors into Home Assistant.

    Multi-System Reactor

  • Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
    N noelab

    Hi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.

    L Bulb FibaroDimmer2
    ezlo>device_61425874129e29124dfcd75e
    0.65
    7:30:07 PM
    dimming.level=0.65
    dimming.step=0.1
    energy_sensor.units="KWh"
    energy_sensor.value=11.3400001525879
    power_sensor.units="W"
    power_sensor.value=6.90000009536743
    power_switch.state=true
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer="Fibaro"
    x_ezlo_device.model="FGD-212"
    x_ezlo_device.parent=""
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="613e2024129e2912114c093b"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_in_wall"
    x_ezlo_device.type_id="271_258_4096"
    x_ezlo_item.dimmer=65
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.electric_meter_kwh=11.3400001525879
    x_ezlo_item.electric_meter_watt=6.90000009536743
    x_ezlo_item.hw_state="hardware_failure"
    x_ezlo_item.load_error_state="unknown"
    x_ezlo_item.meter_reset=0
    x_ezlo_item.over_current_state="unknown"
    x_ezlo_item.over_load_state="unknown"
    x_ezlo_item.power_surge_state="no_surge"
    x_ezlo_item.switch=true
    x_ezlo_item.voltage_drop_drift_state="unknown"
    x_ezlo_object.id="61425874129e29124dfcd75e"
    zwave_device.capabilities=null
    zwave_device.failed=false
    zwave_device.manufacturer_info=["Fibaro","FGD-212",null]
    zwave_device.node_id=27
    zwave_device.version_info=null
    Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
    Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
    

    another

    K Bulb Domitech
    ezlo>device_61423589129e29124dfcd756
    0.65
    7:35:42 PM
    dimming.level=0.65
    dimming.step=0.1
    power_switch.state=true
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer="Domitech"
    x_ezlo_device.model="ZE27EU"
    x_ezlo_device.parent=""
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="613e2020129e2912114c093a"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_bulb"
    x_ezlo_device.type_id="526_19522_12596"
    x_ezlo_item.dimmer=65
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.switch=true
    x_ezlo_object.id="61423589129e29124dfcd756"
    zwave_device.capabilities=null
    zwave_device.failed=false
    zwave_device.manufacturer_info=["Domitech","ZE27EU",null]
    zwave_device.node_id=26
    zwave_device.version_info=null
    Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
    Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
    

    another

    H Bulb Widom dimmer
    ezlo>device_6147578c129e29124dfcd814
    1
    7:36:56 PM
    dimming.level=1
    dimming.step=0.1
    energy_sensor.units="KWh"
    energy_sensor.value=0.651000022888184
    power_sensor.units="W"
    power_sensor.value=2.47000002861023
    power_switch.state=true
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer="Unknown"
    x_ezlo_device.model="Unknown"
    x_ezlo_device.parent=""
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="613e2012129e2912114c0938"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_in_wall"
    x_ezlo_device.type_id="329_4628_2560"
    x_ezlo_item.dimmer=100
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.electric_meter_kwh=0.651000022888184
    x_ezlo_item.electric_meter_watt=2.47000002861023
    x_ezlo_item.meter_reset=0
    x_ezlo_item.switch=true
    x_ezlo_object.id="6147578c129e29124dfcd814"
    zwave_device.capabilities=null
    zwave_device.failed=false
    zwave_device.manufacturer_info=["Unknown","Unknown",null]
    zwave_device.node_id=41
    zwave_device.version_info=null
    Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
    Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
    
    Multi-System Reactor

  • Need Testers
    N noelab

    @toggledbits happy to help!

    I'm running Reactor>Docker>Synology NAS

    Multi-System Reactor

  • ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
    N noelab

    040 = L Bulb Ball 1 Z-RGBW2
    036 = R3 Bulb Roof 1 HKZW-RGB01
    033 = R3 Bulb Wall 1 A-ZWA002

    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