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. Quality of Life Request: Update Button
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

Quality of Life Request: Update Button

Scheduled Pinned Locked Moved Multi-System Reactor
28 Posts 13 Posters 3.0k Views 13 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.
  • G gwp1

    @black-cat Isn't homeseer a walled garden like Hubitat, Ezlo, etc.? You buy their hub and live within their infrastructure.

    That's not MSR. MSR works on various OS/hardware and communicates with multiple hubs.

    Whilst I appreciate your POV, it's not apples>apples comparison you're making here.

    Black CatB Offline
    Black CatB Offline
    Black Cat
    wrote on last edited by Black Cat
    #19

    @gwp1 said in Quality of Life Request: Update Button:

    You buy their hub and live within their infrastructure.

    Nup, you can use any old Laptop or RasPi. Runs on Windows or Lynx. i'd love to promote MSR to Homeseer users but it lacks the simplicity hence the backing of the request.
    Realistically, I'm not going to see it happen which is a shame as Patrick has put a lot of time into development for the 2%.

    aka Zedrally

    G toggledbitsT 2 Replies Last reply
    0
    • S SweetGenius

      I personally do not think the update process on Synology docker is that bad. A few more clicks than an easy button but not horrible. All my other docker containers are updated the same way. I like the docker image though. I am not familiar with the other platforms so I can’t comment on those update processes.

      tunnusT Offline
      tunnusT Offline
      tunnus
      wrote on last edited by
      #20

      @sweetgenius I agree, Synology Docker container upgrade process is not too bad.

      I frequently keep both MSR and Synology UI open on separate browser tabs and either do a quick upgrade using "reset" or a bit careful upgrade using "duplicate settings" and retaining old container as a backup/rollback option.

      Originally I favored a simple update button for MSR, but after Patrick's explanations I realized it's not that simple after all.

      Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

      1 Reply Last reply
      0
      • Black CatB Black Cat

        @gwp1 said in Quality of Life Request: Update Button:

        You buy their hub and live within their infrastructure.

        Nup, you can use any old Laptop or RasPi. Runs on Windows or Lynx. i'd love to promote MSR to Homeseer users but it lacks the simplicity hence the backing of the request.
        Realistically, I'm not going to see it happen which is a shame as Patrick has put a lot of time into development for the 2%.

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

        @black-cat Interesting, I guess I missed that it's available as a paid download for install on whatever platform.

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

        *HASS 2025.6.0
        w/ ZST10-700 fw 7.18.3

        *Prod MSR in docker/portainer
        MSR: latest-25139-fbd67abc
        MQTTController: 25139
        ZWave Controller: 25139

        Black CatB 1 Reply Last reply
        0
        • Black CatB Black Cat

          @gwp1 said in Quality of Life Request: Update Button:

          You buy their hub and live within their infrastructure.

          Nup, you can use any old Laptop or RasPi. Runs on Windows or Lynx. i'd love to promote MSR to Homeseer users but it lacks the simplicity hence the backing of the request.
          Realistically, I'm not going to see it happen which is a shame as Patrick has put a lot of time into development for the 2%.

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #22

          @black-cat said in Quality of Life Request: Update Button:

          Realistically, I'm not going to see it happen which is a shame as Patrick has put a lot of time into development for the 2%.

          I completely understand this position and I want you (all of you) to understand where I currently stand on this (boy, that's a lot of standing)...

          First, I agree that the upgrade issue is important. My long missive wasn't meant to say "not doing it," it was meant to communicate that it's not a simple issue, and isn't one of those features that suddenly appears in the next build after a couple of posts. There are some real issues with usability and stability that have to be taken into account. What I definitely don't want is to have it be a feature that bricks users when they've gotten small parts of the installation wrong, or their system is set up in some weird way. It's a nightmare for the user, obviously, to have their automation suddenly not working, and it's also a nightmare for me to remote-troubleshoot a system where I have no idea what's been done to it, how it got to where it is, what flailing may have happened since it went down, etc. Troubleshooting inside Reactor is hard enough; troubleshooting the rest of the universe around it is not a business I want to be in. I am confident that I can sufficiently engineer, at least for Linux users, a sufficiently robust pre-flight check of the system to reduce the risk of an upgrade going wrong, and that is where a lot of time will be spent. As I said, I already have a running upgrade facility in the recent builds. It does not have the depth of pre-flight that I feel it needs to make me confident that you can be confident in using it... yet.

          Backup and restore is a similar issue, although a slightly more contained problem. I already have a running backup facility in the system. What is not there is a UI for restore, and I've mentioned before, very often the UI for things is as much or more code than the feature itself. It's also a lot harder to test, not just because there are multiple browsers that have to be considered, but because the core features of the product are easy to write automated test tools for, while UI testing tends more toward spending screen time.

          The real usability issue for me, about which I am most concerned, is none of these, though. The real usability issue for me is settings. I don't want you to have to spend time learning or editing YAML (or JSON). I have long had a plan to write a settings subsystem for the UI. This is an incredibly complex problem to solve, and I've prototyped several approaches and, so far, not been satisfied with the results — it's very easy to back yourself into a corner. It cannot be done without changes in core as well, many of which will have to be evolved into the system over time. Evidence of this complexity can be seen in the Home Assistant world, where their team has literally spent years making the transition from YAML configuration of entities and integrations to UI-based.

          I've already read between the lines on this thread, and the backup thread. My current engineering plan is to focus entirely on these three usability issues for the foreseeable future. You will, for some time to come, see a minimum of new core features. I will continue bug-fix and device support updates, but I would guess at this point that you won't see any new major feature upgrades until late Q1 or early Q2 2023. It's going to be a long road. But I believe that the settings issue, in particular, is the real big mover in terms of getting me out of @Black-Cat 's "2%". Adding backup/restore and upgrade will put me on track to an appliance-ready product, which is really my long-term goal.

          Core functionality has been the focus for over two years. I agree it's time to make "expert mode" an option, not a requirement.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          therealdbT 1 Reply Last reply
          5
          • toggledbitsT toggledbits

            @black-cat said in Quality of Life Request: Update Button:

            Realistically, I'm not going to see it happen which is a shame as Patrick has put a lot of time into development for the 2%.

            I completely understand this position and I want you (all of you) to understand where I currently stand on this (boy, that's a lot of standing)...

            First, I agree that the upgrade issue is important. My long missive wasn't meant to say "not doing it," it was meant to communicate that it's not a simple issue, and isn't one of those features that suddenly appears in the next build after a couple of posts. There are some real issues with usability and stability that have to be taken into account. What I definitely don't want is to have it be a feature that bricks users when they've gotten small parts of the installation wrong, or their system is set up in some weird way. It's a nightmare for the user, obviously, to have their automation suddenly not working, and it's also a nightmare for me to remote-troubleshoot a system where I have no idea what's been done to it, how it got to where it is, what flailing may have happened since it went down, etc. Troubleshooting inside Reactor is hard enough; troubleshooting the rest of the universe around it is not a business I want to be in. I am confident that I can sufficiently engineer, at least for Linux users, a sufficiently robust pre-flight check of the system to reduce the risk of an upgrade going wrong, and that is where a lot of time will be spent. As I said, I already have a running upgrade facility in the recent builds. It does not have the depth of pre-flight that I feel it needs to make me confident that you can be confident in using it... yet.

            Backup and restore is a similar issue, although a slightly more contained problem. I already have a running backup facility in the system. What is not there is a UI for restore, and I've mentioned before, very often the UI for things is as much or more code than the feature itself. It's also a lot harder to test, not just because there are multiple browsers that have to be considered, but because the core features of the product are easy to write automated test tools for, while UI testing tends more toward spending screen time.

            The real usability issue for me, about which I am most concerned, is none of these, though. The real usability issue for me is settings. I don't want you to have to spend time learning or editing YAML (or JSON). I have long had a plan to write a settings subsystem for the UI. This is an incredibly complex problem to solve, and I've prototyped several approaches and, so far, not been satisfied with the results — it's very easy to back yourself into a corner. It cannot be done without changes in core as well, many of which will have to be evolved into the system over time. Evidence of this complexity can be seen in the Home Assistant world, where their team has literally spent years making the transition from YAML configuration of entities and integrations to UI-based.

            I've already read between the lines on this thread, and the backup thread. My current engineering plan is to focus entirely on these three usability issues for the foreseeable future. You will, for some time to come, see a minimum of new core features. I will continue bug-fix and device support updates, but I would guess at this point that you won't see any new major feature upgrades until late Q1 or early Q2 2023. It's going to be a long road. But I believe that the settings issue, in particular, is the real big mover in terms of getting me out of @Black-Cat 's "2%". Adding backup/restore and upgrade will put me on track to an appliance-ready product, which is really my long-term goal.

            Core functionality has been the focus for over two years. I agree it's time to make "expert mode" an option, not a requirement.

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

            @toggledbits I have a small script running in background to update msr via docker, at my command, when I'm outside and I don't want to ssh into the machine. I for one will love a flag or similar to know a new version is available and do my own thing. I've not looked at the entities, to be honest.

            Semplification (such as automatic device discovery and a click to add to the engine) is what will make a huge difference for the average brother in-law trying to lightly automate stuff - I agree.

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

            toggledbitsT 1 Reply Last reply
            0
            • therealdbT therealdb

              @toggledbits I have a small script running in background to update msr via docker, at my command, when I'm outside and I don't want to ssh into the machine. I for one will love a flag or similar to know a new version is available and do my own thing. I've not looked at the entities, to be honest.

              Semplification (such as automatic device discovery and a click to add to the engine) is what will make a huge difference for the average brother in-law trying to lightly automate stuff - I agree.

              toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #24

              @therealdb said in Quality of Life Request: Update Button:

              I for one will love a flag or similar to know a new version is available and do my own thing. I've not looked at the entities, to be honest.

              Check out the reactor_system.update_available attribute on the Reactor System (reactor_system>system) entity.

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              G 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @therealdb said in Quality of Life Request: Update Button:

                I for one will love a flag or similar to know a new version is available and do my own thing. I've not looked at the entities, to be honest.

                Check out the reactor_system.update_available attribute on the Reactor System (reactor_system>system) entity.

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

                @toggledbits @therealdb I've used this to create a Pushover notification to my watch. This also surfaces in the Current Alerts pane.

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

                *HASS 2025.6.0
                w/ ZST10-700 fw 7.18.3

                *Prod MSR in docker/portainer
                MSR: latest-25139-fbd67abc
                MQTTController: 25139
                ZWave Controller: 25139

                CatmanV2C 1 Reply Last reply
                2
                • G gwp1

                  @toggledbits @therealdb I've used this to create a Pushover notification to my watch. This also surfaces in the Current Alerts pane.

                  CatmanV2C Offline
                  CatmanV2C Offline
                  CatmanV2
                  wrote on last edited by
                  #26

                  @gwp1 said in Quality of Life Request: Update Button:

                  @toggledbits @therealdb I've used this to create a Pushover notification to my watch. This also surfaces in the Current Alerts pane.

                  I'm getting Telegram.....

                  I'd have Alexa tell me, but I have no idea what time of day updates might be made available 😉

                  C

                  The Ex-Vera abuser know as CatmanV2.....

                  1 Reply Last reply
                  0
                  • G gwp1

                    @black-cat Interesting, I guess I missed that it's available as a paid download for install on whatever platform.

                    Black CatB Offline
                    Black CatB Offline
                    Black Cat
                    wrote on last edited by Black Cat
                    #27

                    @gwp1 said in Quality of Life Request: Update Button:

                    I guess I missed that it's available as a paid download for install on whatever platform.

                    So, there is no misconception about paid or free software, Homeseer is available as a 30-day free trial for anyone to test, it often comes up on special as well .
                    Just to ease any further concerns it has also been around for over 20 years - try the freebie you might be surprised how good it is as an OS for HA.

                    aka Zedrally

                    1 Reply Last reply
                    0
                    • Black CatB Offline
                      Black CatB Offline
                      Black Cat
                      wrote on last edited by
                      #28

                      @toggledbits , thank you for your in-depth reply, there is no need to rush as there are no Raspberrys available (in our region) until mid-March (if we are lucky).

                      aka Zedrally

                      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

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        94

                      • Stop the MSR by an external switch on Hubitat.
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        16

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        86

                      • Reset attribute value of entity in event handler
                        R
                        RHCPNG
                        0
                        5
                        170

                      • Need help figuring out how to delay a reset on reaction
                        G
                        gwp1
                        0
                        22
                        860

                      • Way to search for rules (rule state) in other rules
                        T
                        tamorgen
                        0
                        3
                        92

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        78

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        419

                      • Wiring Samotech SM308-S into light fitting
                        akbooerA
                        akbooer
                        0
                        2
                        136

                      • Errors after updating to MQTTController build 25139
                        toggledbitsT
                        toggledbits
                        0
                        6
                        232

                      • 🎉 My very first MSR controller: OpenSprinkler
                        therealdbT
                        therealdb
                        5
                        13
                        898

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        246
                      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