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

CatmanV2

@CatmanV2
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
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
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
1.2k
Topics
117
Shares
0
Groups
1
Followers
0
Following
0

Posts

Recent Best Controversial

  • Reactor (Multi-System/Multi-Hub) Announcements
    CatmanV2C CatmanV2

    @toggledbits said in Reactor (Multi-System/Multi-Hub) Announcements:

    Reaction Editor: when editing the Set or Reset reaction of a Rule, the Copy From... button will now list the contra-reaction at the top of the list, making it easier to find and copy the reaction within the current Rule.
    UI: The condition and action editors now support a right-click context menu on conditions and actions. The menu provides copy-paste of individual conditions and actions. Other menu actions are added where they make sense. Thank @therealdb for this power-user feature!

    Oh My! That is very cool indeed!

    C

    Multi-System Reactor announcements

  • [MSR] Copy&past of actions and/or drag&drop between set/reset
    CatmanV2C CatmanV2

    Now I have to say even I know about the button 🙂

    C

    Multi-System Reactor

  • Alexa for MSR, any interest?
    CatmanV2C CatmanV2

    @wmarcolin FWIW Home Assistant and Alexa Media Player can give you what you (and so much more) in about an hour's set up.

    C

    Multi-System Reactor

  • [RESOLVED] Telegram notification broke with latest update
    CatmanV2C CatmanV2

    As ever, my thanks. Upgraded to 26177 and all is well!

    C

    Multi-System Reactor

  • [RESOLVED] Telegram notification broke with latest update
    CatmanV2C CatmanV2

    I came here as I was seeing the same Telegram behaviour. I only have one profile. so am happy that the fix will resolve it for me

    C

    Multi-System Reactor

  • Alexa for MSR, any interest?
    CatmanV2C CatmanV2

    I think this makes sense if you're starting afresh. Personally I've exposed my devices from MSR via HA Bridge and it works really well for me

    Multi-System Reactor

  • Farewell, oh good and faithful servant!
    CatmanV2C CatmanV2

    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

  • Integrations and 'Loaded'
    CatmanV2C CatmanV2

    Perfect! Thanks (again)

    C

    Multi-System Reactor

  • Integrations and 'Loaded'
    CatmanV2C CatmanV2

    Thanks again for the recent release. One thing I wanted to ask about integrations and their 'loaded' condition:

    Is there something similar that applies to the entire controller? So if I have (for example) a helper in HA that is used to trigger an automation in MSR, is it possible to effectively exclude it until MSR is 'happy' that HA is stable and its values can be trusted?

    This, actually goes back to the issue I had. I've got a use case where a 30 second delay from triggering is a bit of a PITA (sustained for...) and was just wondering if there's a way of knowing that 'native' HA functions are working correctly.

    Probably asking wrong, or it's hideously obvious, but...

    TIA

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    Thanks, installed and working.

    Although after the first restart there were some virtual switches in HA that were not being accurately reflected in MSR, but I restarted MSR again, and everything looks fine.

    Thanks again for your help. Next time I'll upload the logs to start with!

    C

    Multi-System Reactor

  • Reactor (Multi-System/Multi-Hub) Announcements
    CatmanV2C CatmanV2

    You are an absolute gent, sir

    C

    Multi-System Reactor announcements

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    Fabulous!

    I've actually just put reset delays in the two rules that are triggered. The 'set' is heating on so it's the reset that's a PITA. That should cover it.

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    Of course. I'm not sure what I'd do without him!

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    @therealdb that would rather force (in this case) all the heating off (or on), wouldn't it?

    I like the idea of a 30 second delay though.

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    Thanks, helpful input!

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    OK I've just done some digging: When HA restarts, all three sensors

    sensor.rachel_primary_region
    

    Go 'unknown'

    Someone Home (fairly logically) goes 'Off'

    The period of 'Unknown' is about 5-10 seconds before the correct status is realised.

    Here's the data from the last restart

    binary_sensor.someone_home	unknown	2026-05-19T12:06:55.461Z
    binary_sensor.someone_home	off	2026-05-19T12:07:04.582Z
    binary_sensor.someone_home	on	2026-05-19T12:07:11.505Z
    
    

    TIA

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    I don't believe so, It's been used in several places in HA without issue across restarts. I will see if I can double check that however, as it may simply not have been noticed if it's coming up 'off' and immediately tripping to the correct state.

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    This was a Claude.AI creation ('cos obviously it's way beyond me!) The specific sensor is at the end but I've posted the whole thing in case...

    #################################################
    # OwnTracks MQTT Package (inregions-based)
    # Phones: Catman & Rachel
    #################################################
    
    mqtt:
      sensor:
    
    
    
        ###############################################
        # CATMAN — iPhone
        ###############################################
    
        - name: "Catman In Regions"
          state_topic: "owntracks/catman/catmaniphone"
          icon: mdi:map-marker-multiple
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined %}
              {{ value_json.inregions | join(', ') }}
            {% else %}
              {{ states('sensor.catman_in_regions') }}
            {% endif %}
    
        - name: "Catman Primary Region"
          state_topic: "owntracks/catman/catmaniphone"
          icon: mdi:map-marker
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined
                  and value_json.inregions | length > 0 %}
              {{ value_json.inregions[0] }}
            {% else %}
              away
            {% endif %}
    
        - name: "Catman Location Last Update"
          state_topic: "owntracks/catman/catmaniphone"
          device_class: timestamp
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.tst is defined %}
              {{ value_json.tst | int | timestamp_local }}
            {% else %}
              {{ states('sensor.catman_location_last_update') }}
            {% endif %}
    
        - name: "Catman At Home"
          state_topic: "owntracks/catman/catmaniphone"
          icon: mdi:home
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined %}
              {{ 'home' in value_json.inregions | map('lower') | list }}
            {% else %}
              {{ states('sensor.catman_at_home') }}
            {% endif %}
    
        ###############################################
        # RACHEL — iPhone
        ###############################################
    
        - name: "Rachel In Regions"
          state_topic: "owntracks/rachel/racheliphone"
          icon: mdi:map-marker-multiple
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined %}
              {{ value_json.inregions | join(', ') }}
            {% else %}
              {{ states('sensor.rachel_in_regions') }}
            {% endif %}
    
        - name: "Rachel Primary Region"
          state_topic: "owntracks/rachel/racheliphone"
          icon: mdi:map-marker
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined
                  and value_json.inregions | length > 0 %}
              {{ value_json.inregions[0] }}
            {% else %}
              away
            {% endif %}
    
        - name: "Rachel Location Last Update"
          state_topic: "owntracks/rachel/racheliphone"
          device_class: timestamp
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.tst is defined %}
              {{ value_json.tst | int | timestamp_local }}
            {% else %}
              {{ states('sensor.rachel_location_last_update') }}
            {% endif %}
    
        - name: "Rachel At Home"
          state_topic: "owntracks/rachel/racheliphone"
          icon: mdi:home
          value_template: >
            {% if value_json._type == 'location'
                  and value_json.inregions is defined %}
              {{ 'home' in value_json.inregions | map('lower') | list }}
            {% else %}
              {{ states('sensor.rachel_at_home') }}
            {% endif %}
    
    #################################################
    # TEMPLATE SENSORS (merged correctly)
    #################################################
    
    template:
      - sensor:
          - name: "Household Presence"
            icon: mdi:account-group
            state: >
              {% set catman = states('sensor.catman_primary_region') | lower %}
              {% set rachel = states('sensor.rachel_primary_region') | lower %}
    
              {% set cm =
                '🏠' if catman == 'home' else
                '🏢' if catman == 'office' else
                '🚗'
              %}
    
              {% set ra =
                '🏠' if rachel == 'home' else
                '🏢' if rachel == 'office' else
                '🚗'
              %}
    
              Catman {{ cm }} | Rachel {{ ra }}
    
      - binary_sensor:
          - name: "Someone Home"
            icon: mdi:home-account
            state: >
              {{ states('sensor.catman_primary_region') | lower == 'home'
                 or states('sensor.rachel_primary_region') | lower == 'home' }}
                
    
    
            
    

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    I did indeed do a reload. Never done it before, but was trying to work out how to get them back in sync as it were.

    C

    Multi-System Reactor

  • Possible mismatch between binary_sensor in HA and MSR
    CatmanV2C CatmanV2

    Copy attributes button

    C

    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