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

therealdb

@therealdb
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
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
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
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
About
Posts
1.0k
Topics
97
Shares
0
Groups
1
Followers
2
Following
0

Posts

Recent Best Controversial

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    @toggledbits is alarm() a new thing? What's the best example to understand its use? IE: A global variable named christmas_time, that will be updated every hour/day with dateparts()? Thanks.

    Multi-System Reactor

  • Shelly Wall Display XL
    therealdbT therealdb

    Thanks! I managed to get the 4 buttons, a nice feature for the wife.

    Unfortunately, it's not POE, but it was easy for me to pull a cable. It has a relay, but I'm not using it ATM.

    In the coming weeks I'll mount the second one on the second floor. The custom firmware has both MQTT and HTTP APIs, so it's easy to synchronize them.

    Hardware

  • Shelly Wall Display XL
    therealdbT therealdb

    Here we go. This wall is still original, so height is temporary. Since it's concrete, I'll address this later and I'll move it lower.

    3442a9be-6d2c-4fdc-9644-44380afa4d8e-image.png

    c454df4e-2b94-4b99-8a1a-9b962b279257-image.png

    c9d408df-980d-40fe-9ef4-d985191e535c-image.png

    Our house is very bright, so the photos are not good, but in person it's OK.

    Hardware

  • Shelly Wall Display XL
    therealdbT therealdb

    I don't know if you guys are into dashboards, but I am.

    For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer.

    Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate

    I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor.

    I also have a new build in the works with support for buttons inside HA.
    I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable).

    This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.

    Hardware

  • Handling Dead Entities and Renamed Entities
    therealdbT therealdb

    I don't know if there's a UI option, but when I migrated things, I just stopped reactor, opened the files and removed everything from reactor/storage/entities/zwavejs (after a backup). And start again, of course. It's brutal for sure, but it worked.

    Multi-System Reactor

  • Strange behavior for MQTT templates using payload and attributes
    therealdbT therealdb

    @toggledbits said in Strange behavior for MQTT templates using payload and attributes:

    See the problem now?

    You have control over the order in which the attributes are processed for the topic/event.

    I see it! Thanks! (Never code in a hurry while doing 100 other things).

    Multi-System Reactor

  • [MSR] reactor-mqtt-contrib package for additional MQTT templates
    therealdbT therealdb

    25272: Fixes for shelly_scenecontroller to better handle multiple pushes of the same button.

    Multi-System Reactor

  • Strange behavior for MQTT templates using payload and attributes
    therealdbT therealdb

    No joy from the logs. I added parens but no joy. The only thing that worked was a delete of the entity/restart of Reactor.

    [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:599> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 associated with Array(1)[ "shelly_gatebutton" ]
    [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:601> MQTTController#mqtt dispatching shellies/shelly-gatebutton/input_event/0 to shelly_gatebutton
    [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:1152> MQTTController#mqtt handling shellies/shelly-gatebutton/input_event/0 (event shellies/shelly-gatebutton/input_event/0) for shelly_gatebutton: {"event":"","event_cnt":2}
    [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1168> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 affects entity shelly_gatebutton attributes value_sensor.value, button.since, scene_activation.since, button.state, scene_activation.scene_id, x_mqtt_device.online
    [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton value_sensor.value=2
    [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton button.since={"event":"","event_cnt":0}
    [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton scene_activation.since={"event":"","event_cnt":0}
    [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton button.state=unknown
    [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton scene_activation.scene_id=
    [latest-25272]2025-09-30T14:49:47.417Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton x_mqtt_device.online=true
    [latest-25272]2025-09-30T14:49:47.417Z <MQTTController:5:MQTTController.js:1905> MQTTController#mqtt _handle_ext_event() shellies/shelly-gatebutton/input_event/0 matches 0 subscriptions
    

    Maybe it's something that when it's corrupted with json, doesn't work as expected. I'm reporting as an edge case, but it's very hard to reproduce. Thanks anyway. New build for my MQTT-contrib incoming.

    Multi-System Reactor

  • Strange behavior for MQTT templates using payload and attributes
    therealdbT therealdb

    I'm re-writing my shelly_scenecontroller mqtt template because I added a new pushbutton and I had strange results. Basically, in the last couple of days, it fired itself, because of the way the logic works. Everytime I'm pushing a button, an "S" is sent as the event, so the button.state never changes. I'm looking for button.since to determine if the button is pressed again.
    That's good, but everytime a poll is done, the button.since attribute is updated, because it is tied to time().

    reactor-mqtt-contrib/shelly_gen1.yaml at 8bf5022f6b8ee80feed3d881befc119a1f58fcdc · dbochicchio/reactor-mqtt-contrib

    reactor-mqtt-contrib/shelly_gen1.yaml at 8bf5022f6b8ee80feed3d881befc119a1f58fcdc · dbochicchio/reactor-mqtt-contrib

    Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

    So, I introduced the use of event_cnt from the payload, comparing the value to the stored one, in order to understand if it has been pushed again, or, in general, the number of times the button is pushed.
    Updated template:

        events:
          "shellies/%topic%/input_event/%channel%":
            - attribute: "value_sensor.value"
              json_payload: true
              expr: "float(payload?.event_cnt)"
            - attribute: "button.since"
              json_payload: true
              expr: >
                entity.attributes?.button?.since == null || 
                float(payload?.event_cnt) != entity.attributes?.value_sensor?.value
                  ? time() : entity.attributes.button.since
            - attribute: "scene_activation.since" # just copy button.since
              expr: "entity?.attributes?.button?.since"
            - attribute: "button.state"
              json_payload: true
              expr: >
                payload?.event == "S" ? "single" :
                payload?.event == "SS" ? "double" :
                payload?.event == "SSS" ? "triple" :
                payload?.event == "L" ? "long" :
                "unknown"
            - attribute: "scene_activation.scene_id"
              json_payload: true
              expr: "payload?.event"
            - attribute: "x_mqtt_device.online"
              expr: true
    

    This should work, but instead I have this value:

    20de8c3f-ad80-4c4a-9f4e-cb404f54553e-image.png

    and that's beyond strange and I can't honestly figure it out. @toggledbits any hint is appreciated. Thanks.

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    @toggledbits I have a couple of routines (previously working OK) that are checking for various things based on the hour we're in.

    The variable code is like this one:

    d = dateparts(),
    (d.hour >= 20 && d.hour <= 23)
    

    I remember we've been told that this would not work in previous builds (but it did), but it's not really working now. It was false at 20 (the rule is triggered every 30 minutes when dark), and after I pressed play it went to true. I changed it with a script action and it's working now. But I'm reporting as an edge case, because I'm not sure it is supposed to work with the new behavior. Nothing else to report ATM. Thanks for the effort!

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    So far, so good. Everything seems to be OK atm. I'll report in case of problems.

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    @toggledbits said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:

    Just a tip, a more efficient way to write this:

    OMG, very old rules, isn't it? Thanks, I fixed it.

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    yep, it seems to be related (in general) to variables not being evaluated at startup. Here's a screenshot from a daily rule that it's setting a couple of things, including a virtual binary sensor for Christmas from a local variable:

    image.png After re-setting the rule, the expression got re-evaluated and the error went away. @toggledbits

    EDIT. a similar one + logs

    This one, instead, every time is evaluated gives the error.

    e1f0057d-0f11-48c6-89a4-0760325798af-image.png

    [latest-25248]2025-09-11T07:19:37.602Z <Rule:ERR> Lights-Christmas-Off (rule-kwv6wdpw in Lights-Outdoor): error evaluating expression specialdays: [Error] Object does not exist [-]
    [latest-25248]2025-09-11T07:19:37.603Z <Rule:ERR> Full expression: t = time(), m = dateparts(t).month, d = dateparts(t).day,
    (m == 12 && d == 24) ||
    (m == 12 && d == 25) ||
    (m == 12 && d == 31) ||
    (m == 1 && d == 1) ||
    (m == 1 && d == 5) ||
    (m == 1 && d == 6)
    [latest-25248]2025-09-11T07:19:37.604Z <Rule:CRIT> Error: Object does not exist [-]
    Error: Object does not exist
        at GlobalExpression.getInstance (/opt/reactor/server/lib/GlobalExpression.js:160:27)
        at _0x1ec9e7._func.<computed> [as _ref] (/opt/reactor/server/lib/Rule.js:848:69)
        at _resolve (/opt/reactor/common/lexp.js:1385:27)
        at _run (/opt/reactor/common/lexp.js:1429:31)
        at /opt/reactor/common/lexp.js:1697:33
        at Array.forEach (<anonymous>)
        at _run (/opt/reactor/common/lexp.js:1696:28)
        at _run (/opt/reactor/common/lexp.js:1604:33)
        at _run (/opt/reactor/common/lexp.js:1438:34)
        at /opt/reactor/common/lexp.js:1425:29
    [latest-25248]2025-09-11T07:19:37.627Z <Rule:INFO> Lights-Christmas-Off (rule-kwv6wdpw in Lights-Outdoor) evaluated; rule state transition from NULL to RESET!
    [latest-25248]2025-09-11T07:19:37.638Z <Rule:INFO> Lights-Christmas-Off (rule-kwv6wdpw in Lights-Outdoor) started
    
    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    Ok, I got a bunch of errors at restart because of failed references in almost all variables - now it seems to be OK and variables are updated. I'm observing a couple of rules I haven't migrate yet - and, at this point, I'll not migrate - where I used to old trick that @gwp1 surfaced (and that I used without making it a rule). always seems to be OK.

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    @toggledbits I've updated my main system. I'll observe and report back. Thanks

    Multi-System Reactor

  • [Reactor] Copy&Paste of Rules
    therealdbT therealdb

    I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.

    While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.

    I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.

    Just an idea 🙂

    Multi-System Reactor

  • [MSR] reactor-mqtt-contrib package for additional MQTT templates
    therealdbT therealdb

    Version 25244: https://github.com/dbochicchio/reactor-mqtt-contrib/releases/tag/25244

    Add new Shelly Gen3 templates for dimmer and energy meter, modify version in manifest.yaml to 25244, enhance sensor expressions for accuracy, and improve event handling and actions. General refactoring and cleanup across YAML files for consistency and quality.

    Multi-System Reactor

  • [Reactor] Help with screne controller cycling logic
    therealdbT therealdb

    So, my solution, based on the logic, is this the following.

    Cycle Logic (pseudo-blocks)

    Trigger: Button press (scene controller state changes)

    Variables:

    • fan1 = getEntity("zwavejs>13-1").attributes.power_switch.state
    • fan2 = getEntity("zwavejs>13-2").attributes.power_switch.state
    • skip (default = false)
    • lastTurnedOff (text)

    Group 1 – Both OFF → Fan1 ON
    Condition: skip == false AND fan1 == OFF AND fan2 == OFF AND lastTurnedOff <> "fan1"
    Action:

    • Turn Fan1 ON
    • Set skip = true

    Group 2 – Fan1 ON → Fan1 OFF
    Condition: skip == false AND fan1 == ON
    Action:

    • Turn Fan1 OFF
    • Set lastTurnedOff = "fan1"
    • Set skip = true

    Group 3 – Fan1 just OFF → Fan2 ON
    Condition: skip == false AND fan2 == OFF AND lastTurnedOff == "fan1"
    Action:

    • Turn Fan2 ON
    • Set skip = true

    Group 4 – Fan2 ON → Fan2 OFF
    Condition: skip == false AND fan2 == ON
    Action:

    • Turn Fan2 OFF
    • Set lastTurnedOff = "fan2"
    • Set skip = true

    Notes

    • The skip variable ensures only one group runs per button press.
    • lastTurnedOff lets Reactor know which fan was just turned off by this rule (so it can toggle the other fan on next).

    I'll make some other tests and see if it's working as expected. I used Chat GPT 5 giving the Reactor Docs as context and deep reasoning and it helped me a lot. I just had to explain my logic, provide a couple of screenshots and ask for logic blocks instead of script action. YMMV.

    Multi-System Reactor

  • [Reactor] Help with screne controller cycling logic
    therealdbT therealdb

    I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.

    That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
    Example: Light 1 ON → OFF, then Light 2 ON → OFF.

    The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.

    Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    therealdbT therealdb

    Yep, I confirm I had to update a couple of rules where I had similar variables as @tunnus
    I used script action because it’s multi line and definitely better in terms of readability.

    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