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
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
About
Posts
1.1k
Topics
109
Shares
0
Groups
1
Followers
0
Following
0

Posts

Recent Best Controversial

  • New HA instance
    CatmanV2C CatmanV2

    I just wanted to post how impressed I am with both HA and MSR. I really don't see that Ezlo have a chance in hell.

    I noticed that my Virtual HA instance was killing my machine's performance, so decided that my project for the weekend would be a stand alone Raspberry Pi instance. Less than an hour to install, restore and configure both HA and MSR and it all just works. Thanks to everyone that contributes to these fabulous projects. Especially our own @toggledbits for the amazing work that is the new Reactor!

    C

    Home Assistant

  • Arduino to make a weather station
    CatmanV2C CatmanV2

    Sorry, just had to...

    e68fbd78-7e6e-405e-9504-9e01f614dc88-image.png

    C

    General Discussion

  • This is me
    CatmanV2C CatmanV2

    Well, if I see further, it's because I stand of the shoulders of giants. I've got where I got because of the experts here. I started about 15 years ago with some really basic X10 stuff. When we moved in 2011 for some reason it simply would not work in the new house, so z-wave was the thing. Vera lite then Vera Plus.

    I'm a child of the 70s. I want the car on the drive to be KITT and my lounge a cross between the bridge of the enterprise and the Lars farm on Tattoine.

    Not there yet, but with about 250 devices (virtual and real) things are fun (when they work!)

    The absolute killer app for me is Alexa bi directional speech. To the extent that I've walked into hotel rooms and said 'Alexa turn the lights on....'
    I'm within a spit of never buying another control and doing everything via Alexa and Reactor (had to drop that in)

    So that's pretty much me.

    C

    Blogs

  • Smart home with no WIFI
    CatmanV2C CatmanV2

    Perhaps another thing to point out is that WiFi<> Internet and there is absolutely no technical reason you cannot have a WiFi network simply because you have no internet access

    C

    General Discussion

  • My migration from Vera, or what I did on my holidays
    CatmanV2C CatmanV2

    Well here we go. A slow, considered migration from Vera to something (I hope) more reliable.
    Hopefully we'll end up with a decent documented process for people as right now I'm still not quite clear 🙂
    Starting point:
    I have a 'mature' Mios set up running on an extrooted Vera Plus with roughly 100 devices, both physical and virtual
    Integration with Alexa both voice control and TTS
    iPhones for Geolocation
    Volumio devices for music playing around the house.
    I have no user defined scenes, all automation is run from Reactor.

    My impetus is final dissatisfaction with the quality of UI7 software delivery and operational rigour (for full disclosure I am a senior IT Operations leader with circa 20 years experience delivering properly stable systems, so I probably have un-realistic expectations 😄 )

    So initial steps:

    1. Raspberry Pi 3 B+ (I think this is my 5, and 6th Pi in total. I may have a problem)
    2. Raspbian
    3. OpenLuup
    4. Verabridge

    That I think is stage 1

    C

    Blogs

  • OT: Universal Remote
    CatmanV2C CatmanV2

    Just to close this off, I managed to get a Harmony Elite and Hub from ebay. Lightly used at a reasonable price.
    God knows why they are pulling out of the market. First impressions is it's an ace bit of gear. Didn't realise quite what the hub could do and am thinking of getting another to replace my Broadlink in the cinema.

    Thanks, all

    C

    General Discussion

  • My migration from Vera, or what I did on my holidays
    CatmanV2C CatmanV2

    OK so time for an update. This has kind of drifted off the 'Here's how you do it'

    Most of getting Openluup, HA Bridge, AltUI, and getting Z-way up and runningwas pretty trivial (all things considered)

    The migration from Vera to Z-way, was not as simple as I'd have hoped. Pretty much 2 days of fettling.

    Couple of gotchas:

    1. My restore to the UZB dongle took a couple of shots. It took quite a long time as well.
    2. Migration to Z-way per se was pretty simple
    3. However, Z-way requires a totally different way of thinking. Pretty much every service creates an individual device. If you're not ready for this you can get in a hell of a mess trying to name stuff. I still have a few odd devices that I'm not quite sure what they are. I suspect tamper switches!
    4. Some devices are not what you think. Sirens. In fact these are shown as switches. Makes total sense when you think about it, but doesn't look great on the interface.
    5. The rooms were not migrated. So although all my rooms already existed in AltUI / Opeluup (from Vera) new devices all appeared in a ZWay room. In retrospect this could be because I already had rooms named, and they had different UIDs
    6. Reactor is still fantastic
    7. There are a couple of devices that aren't supported in Openluup / AltUI. Meh might be worth checking in advance.

    Finally a huge thankyou to @akbooer @rafale77 @therealdb Partrick (is he here? If not can someone ping him the other place) and the rest of you that have made this work.

    This is so much faster, more sensible, reactive, responsive and everything else. Now I just want to do more

    Respect

    Chris

    Blogs

  • Finally gave up on my Ezlo Plus
    CatmanV2C CatmanV2

    @therealdb well we got this place....

    C

    Blogs

  • Finally gave up on my Ezlo Plus
    CatmanV2C CatmanV2

    @librasun said in Finally gave up on my Ezlo Plus:

    Sound familiar?

    Never heard that! 😉

    C

    Blogs

  • Alexa skill for Open Luup / Zway
    CatmanV2C CatmanV2

    @therealdb I got this running in about 30 minutes tops.....

    C

    General Discussion

  • Up and running
    CatmanV2C CatmanV2

    After much (un-necessary) faffing on Debian 10 I got MSR up and running in about 10 minutes flat this morning, on the same box as AltUI

    As a warning, expect lots of stupid questions. 😉

    C

    Multi-System Reactor

  • Vera firmware 7.32 beta
    CatmanV2C CatmanV2

    @pabla said in Vera firmware 7.32 beta:

    I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!

    Works A1 on Openluup 😉

    C

    Vera

  • Not so much a blog
    CatmanV2C CatmanV2

    If it doesn't work, it certainly won't be the software's fault!

    Can I really buy another pi :D. That'll be 5 in the server cupboard and one under the sofa!

    And I still need Alexa, but yes, crawling progress

    C

    Blogs

  • New Ezlo Web GUI now in "beta"
    CatmanV2C CatmanV2

    @librasun said in New Ezlo Web GUI now in "beta":

    I prefer the term "Vaporware" until a pitched product at least becomes accessible to a portion of its target audience. The silence from ezlo's team -- aside from acknowledging customer complaints and new Jira tickets -- is deafening.

    Plus ca change....

    C

    General Discussion

  • Owntracks Entity does not update as expected
    CatmanV2C CatmanV2

    Fabulous! For once I wasn't being a complete idiot, and now the entity is True (which is sort of what I'd expect) Thanks so much!

    C

    Multi-System Reactor

  • Instant regret after clicking "Configure Node Right Now" on device
    CatmanV2C CatmanV2

    @librasun said in Instant regret after clicking "Configure Node Right Now" on device:

    Many thanks, Gents! Nice believing that I am neither the first nor last to spazz in this manner. 🙂

    Radical thought, but you could move to Openluup 😉

    Then all these problems would vanish...like tears in the rain......

    C

    Vera

  • Disaster recovery and virtualisation
    CatmanV2C CatmanV2

    Well after much trepidation, and some additional work, I think we are complete.

    After the successful virtualisation of my Home Assistant and Music Server hosts, and a successful POC of the main Vera / MQTT / MSR / everything else box I did some testing with a spare UZB stick to make sure I could connect it to the virtual host.

    With a long weekend ahead to solve any issues, this morning I bit the bullet and shut down the hardware device, moved the production UZB stick over to the NAS and spun up the VM.

    It was not entirely smooth as for some reason Z-way-server was saying it wasn't connected and AltUI claimed an authentication issue, but with some judicious restarts and testing, everything that I can think of to test now works!

    Some of the Z-wave commands from remote controls are a little slow, oddly, but I suspect the network needs to sort itself out as it's nearly two months 'old' Direct control from web interfaces / voice commands seems fine so I'm not overly worried.

    So, barring any unforseen failures, I have a fully virtualised system. Better even, when reading about the Synology range, I decided to source an older unit as a backup cluster device so I have some serious resilience 🙂

    Thanks for all the support an input!

    C

    General Discussion

  • Entity sanity check
    CatmanV2C CatmanV2

    Fab so I have an entity. I had to make some changes to the Owntracks config so there was no stored message. Time will tell. Thanks for all the help

    C

    Multi-System Reactor

  • Oh the joy of pairing
    CatmanV2C CatmanV2

    When I remember the old days 🙂

    Just added a new Tuya plug (OK so it's cloud)

    Start to finish, visible in HA and MSR < 30 seconds...

    C

    Vera

  • IR to IR transmitter
    CatmanV2C CatmanV2

    https://www.keene.co.uk/keene-ir-anywhere-ir-over-ip-modules-pair.html

    Keene are great for all this kind of stuff.

    C

    Hardware
  • Login

  • Don't have an account? Register

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