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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. [Resolved] Day mode implementation question
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
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
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
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
[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
[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
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

[Resolved] Day mode implementation question

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 5 Posters 5.6k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • therealdbT Offline
    therealdbT Offline
    therealdb
    wrote on last edited by
    #20

    I don't known why you're all setting a mode like this, but I'm still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions. I'm curious to understand why you prefer this approach.

    --
    On a mission to automate everything.

    My MS Reactor contrib
    My Luup Plug-ins

    PablaP G 2 Replies Last reply
    0
    • therealdbT therealdb

      I don't known why you're all setting a mode like this, but I'm still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions. I'm curious to understand why you prefer this approach.

      PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #21

      @therealdb My house modes are simple: Night/Home/Away/Vacation. All them are configured very simply, based on if the alarm is turned on (either stay or away) and who's home. That way there is no accidental/unexpected mode changes

      G 1 Reply Last reply
      0
      • therealdbT therealdb

        I don't known why you're all setting a mode like this, but I'm still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions. I'm curious to understand why you prefer this approach.

        G Offline
        G Offline
        gwp1
        wrote on last edited by
        #22

        @therealdb said in Day mode implementation question:

        still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions.

        This is exactly what I'm driving at. I use Mode followed by a number of what I call "shared rules" (Wake-up times, cloudy day, temp < 40º, presence, etc.) that can be/are referenced in many other rulesets. Where I'm hitting my wall is the actual triggering of the modes (Day, Away, Evening, Night).

        My curiosity is around how you're actually triggering the modes themselves. The rest... I've got that nailed down.

        *Hubitat C-7 2.5.1.142
        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

        *HAOS
        Core 2026.7.4
        w/ HA Connect ZWA-2
        FW: v1.1
        SDK: v7.23.1

        *Prod MSR in docker/portainer
        MSR: latest-26193-8dd8f854
        MQTTController: 25139
        ZWave Controller: 25139

        therealdbT 1 Reply Last reply
        0
        • PablaP Pabla

          @therealdb My house modes are simple: Night/Home/Away/Vacation. All them are configured very simply, based on if the alarm is turned on (either stay or away) and who's home. That way there is no accidental/unexpected mode changes

          G Offline
          G Offline
          gwp1
          wrote on last edited by gwp1
          #23

          So I went back in time to when I first set modes up. Here's my current settings:

          b383c52d-84a6-43bd-bb3b-f298f25642f8-image.png

          3d099145-a298-4314-af18-d612321024c9-image.png

          53c7b6b5-eedb-40b6-a955-140c9ae469eb-image.png 9c58c5b8-bf57-474a-9fe8-d8c71d9c1200-image.png

          3827169b-c2e7-44f2-9d14-9b1d6f3764f7-image.png

          I will use Wake Up Times internally with other rulesets rather than trying to use it to drive at the higher Mode level. Presence will be in those rulesets as well.

          *Hubitat C-7 2.5.1.142
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HAOS
          Core 2026.7.4
          w/ HA Connect ZWA-2
          FW: v1.1
          SDK: v7.23.1

          *Prod MSR in docker/portainer
          MSR: latest-26193-8dd8f854
          MQTTController: 25139
          ZWave Controller: 25139

          1 Reply Last reply
          0
          • G gwp1

            @therealdb said in Day mode implementation question:

            still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions.

            This is exactly what I'm driving at. I use Mode followed by a number of what I call "shared rules" (Wake-up times, cloudy day, temp < 40º, presence, etc.) that can be/are referenced in many other rulesets. Where I'm hitting my wall is the actual triggering of the modes (Day, Away, Evening, Night).

            My curiosity is around how you're actually triggering the modes themselves. The rest... I've got that nailed down.

            therealdbT Offline
            therealdbT Offline
            therealdb
            wrote on last edited by
            #24

            @gwp1 I'm using the alarm to drive modes, as @Pabla
            I'm also triggering wakeup mode from the alexa's alarm, so it's possible to move the time and automatically execute actions.

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

            G 1 Reply Last reply
            0
            • therealdbT therealdb

              @gwp1 I'm using the alarm to drive modes, as @Pabla
              I'm also triggering wakeup mode from the alexa's alarm, so it's possible to move the time and automatically execute actions.

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #25

              @therealdb Interesting approach, using the Echo devices. I'd be concerned over any outage potential, has that been an issue?

              *Hubitat C-7 2.5.1.142
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HAOS
              Core 2026.7.4
              w/ HA Connect ZWA-2
              FW: v1.1
              SDK: v7.23.1

              *Prod MSR in docker/portainer
              MSR: latest-26193-8dd8f854
              MQTTController: 25139
              ZWave Controller: 25139

              therealdbT 1 Reply Last reply
              0
              • G gwp1

                @therealdb Interesting approach, using the Echo devices. I'd be concerned over any outage potential, has that been an issue?

                therealdbT Offline
                therealdbT Offline
                therealdb
                wrote on last edited by
                #26

                @gwp1 I'm in my 3rd year with this automation and it never failed, but I have fallbacks. the alarm is working even if offline, and the house alarm will override the wake-up mode anyway (if the holiday flag is not set). The only minor drawback is that the announcements will not be turned on coordinated with the alarm, but I can live with that.

                --
                On a mission to automate everything.

                My MS Reactor contrib
                My Luup Plug-ins

                G 1 Reply Last reply
                0
                • therealdbT therealdb

                  @gwp1 I'm in my 3rd year with this automation and it never failed, but I have fallbacks. the alarm is working even if offline, and the house alarm will override the wake-up mode anyway (if the holiday flag is not set). The only minor drawback is that the announcements will not be turned on coordinated with the alarm, but I can live with that.

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by
                  #27

                  @therealdb this idea intrigues me because I occasionally have to wake up on a weekend morning very, very early for a software deployment. As such, I set my usual physical alarm (an ancient Bose Wave radio) as well as adding in a failsafe alarm from my Echo devices.

                  I don't see in my integration between Hubitat and Alexa anything to do with alarms, however. Are you using Alexa Routines for this? That would require manually editing the routine each time, no?

                  *Hubitat C-7 2.5.1.142
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HAOS
                  Core 2026.7.4
                  w/ HA Connect ZWA-2
                  FW: v1.1
                  SDK: v7.23.1

                  *Prod MSR in docker/portainer
                  MSR: latest-26193-8dd8f854
                  MQTTController: 25139
                  ZWave Controller: 25139

                  therealdbT 1 Reply Last reply
                  0
                  • G gwp1

                    @therealdb this idea intrigues me because I occasionally have to wake up on a weekend morning very, very early for a software deployment. As such, I set my usual physical alarm (an ancient Bose Wave radio) as well as adding in a failsafe alarm from my Echo devices.

                    I don't see in my integration between Hubitat and Alexa anything to do with alarms, however. Are you using Alexa Routines for this? That would require manually editing the routine each time, no?

                    therealdbT Offline
                    therealdbT Offline
                    therealdb
                    wrote on last edited by
                    #28

                    @gwp1 yes. I have a routing setting a virtual flag on when the alarm is triggered. My Alexa UI is localized in Italia, but this should be a trigger named "When alarm goes off" or similar. I'm also getting next alarm time during the night routine, and I'll probably use it to prototype some dynamic lights before the scheduled alarm. Plenty of ideas, so little time 🙂

                    --
                    On a mission to automate everything.

                    My MS Reactor contrib
                    My Luup Plug-ins

                    G 1 Reply Last reply
                    0
                    • therealdbT therealdb

                      @gwp1 yes. I have a routing setting a virtual flag on when the alarm is triggered. My Alexa UI is localized in Italia, but this should be a trigger named "When alarm goes off" or similar. I'm also getting next alarm time during the night routine, and I'll probably use it to prototype some dynamic lights before the scheduled alarm. Plenty of ideas, so little time 🙂

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #29

                      @therealdb Where are you pulling "next alarm time" from?

                      *Hubitat C-7 2.5.1.142
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HAOS
                      Core 2026.7.4
                      w/ HA Connect ZWA-2
                      FW: v1.1
                      SDK: v7.23.1

                      *Prod MSR in docker/portainer
                      MSR: latest-26193-8dd8f854
                      MQTTController: 25139
                      ZWave Controller: 25139

                      therealdbT 1 Reply Last reply
                      0
                      • G gwp1

                        @therealdb Where are you pulling "next alarm time" from?

                        therealdbT Offline
                        therealdbT Offline
                        therealdb
                        wrote on last edited by therealdb
                        #30

                        @gwp1 I have this script integrated into my system since day 0 https://github.com/thorsten-gehrig/alexa-remote-control

                        I'm parsing some JSON from "query notifications" command. It's natively supported under HA integrations, but this script is working very well for me, and I am not motivated to change it. I still must set the alarm manually, since there's not easy API to schedule it. Check your integrations, it could be already supported.

                        --
                        On a mission to automate everything.

                        My MS Reactor contrib
                        My Luup Plug-ins

                        G 1 Reply Last reply
                        1
                        • therealdbT therealdb

                          @gwp1 I have this script integrated into my system since day 0 https://github.com/thorsten-gehrig/alexa-remote-control

                          I'm parsing some JSON from "query notifications" command. It's natively supported under HA integrations, but this script is working very well for me, and I am not motivated to change it. I still must set the alarm manually, since there's not easy API to schedule it. Check your integrations, it could be already supported.

                          G Offline
                          G Offline
                          gwp1
                          wrote on last edited by
                          #31

                          @therealdb This bears investigation - thank you!

                          *Hubitat C-7 2.5.1.142
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HAOS
                          Core 2026.7.4
                          w/ HA Connect ZWA-2
                          FW: v1.1
                          SDK: v7.23.1

                          *Prod MSR in docker/portainer
                          MSR: latest-26193-8dd8f854
                          MQTTController: 25139
                          ZWave Controller: 25139

                          1 Reply Last reply
                          0
                          • toggledbitsT toggledbits locked this topic on
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          Recent Topics

                          • [Solved] DynamicGroupController updating members issue
                            CrilleC
                            Crille
                            0
                            5
                            73

                          • Reactor (Multi-System/Multi-Hub) Announcements
                            toggledbitsT
                            toggledbits
                            5
                            148
                            129.1k

                          • DynamicGroupController and attributes
                            therealdbT
                            therealdb
                            1
                            5
                            89

                          • Arming Envisalink panel from MSR
                            toggledbitsT
                            toggledbits
                            0
                            5
                            112

                          • Upgrade Issues
                            T
                            tbully
                            0
                            9
                            219

                          • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                            toggledbitsT
                            toggledbits
                            0
                            10
                            233

                          • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                            G
                            gwp1
                            0
                            5
                            117

                          • openLuup console disappeared - 500 - Internal Server Error
                            A
                            a-lurker
                            0
                            2
                            169

                          • Logon screen timeout
                            G
                            gwp1
                            0
                            5
                            190

                          • [MSR] Copy&past of actions and/or drag&drop between set/reset
                            toggledbitsT
                            toggledbits
                            0
                            9
                            354

                          • Upgrade advice - upgrade from aarch64 to ARM64 image
                            toggledbitsT
                            toggledbits
                            0
                            4
                            211
                          Powered by NodeBB | Contributors
                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                          • Login

                          • Don't have an account? Register

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