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

Edwin1972

@Edwin1972
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
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
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
There is an alternative to homebridge-mqttthing
CrilleC
Just throwing out a general hint to the people running Homebridge and MQTT. Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge. I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function. It took a while to migrate everything but I'm pleased and can recommend.
Software
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
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
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
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
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
About
Posts
71
Topics
15
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • When turning off the dimmer, set the LoadLevelLast to 100%
    E Edwin1972

    I have the following issue: In my Vera, I have created a dimmer using the Switchboard plugin. I want this light always turn on at 100% brightness when turn the light on. By default, the dimmer remembers its last used setting. I have created the following scene: when the light is turned off, the LoadLevelLast should be 100.

    9937e326-2453-43bd-bd32-917803b38e90-image.png

    Manually, this works through the test Luup code (Lua), but not through the scene's action by execute the following Luup code.

    I also tried in MSR, but no result

    Does anyone know the solution to this?

    Vera/openLuup plugins

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    I updated my pi4 with commande sudo apt upgrade and then updated MSR to 23010 and everything works fine.
    Thanks you all for your response.

    Multi-System Reactor

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    Thanks for quick response. I'm not handy with log files yet. I'll try in the weekend. first I will upgrade to the latest version.

    Multi-System Reactor

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    Suddenly my MSR actions aren't running anymore. I've had this before, but with an update to a new version it was fixed. see also

    https://smarthome.community/topic/987/msr-actions-aren-t-running-anymore-can-t-find-what-s-broken/3?_=1674661492589

    But an update from version 22240 to 22256 gave this time no result.

    The reactions aren't running correctly. Most of my MSR automations are use turn lights on/off, and time based automations nothing worked where MSR does his magic.

    I've also tested a bunch of things to see what's broken, here's what I've observed:
    -I can successfully flip lights on/off manually within Vera
    -I can successfully flip lights on/off manually within MSR's Entities section
    -the sensors are correctly reporting to Vera and MSR (I can see when they're switch on/off)
    -the rules within MSR are working correctly, I can see when they flip to 'true' of 'false' '
    '
    But I cannot successfully run the "Set Reaction" and "Reset Reaction" within MSR (by hitting the 'play' button)
    But the play buttons on the entitiy action in the "Set Reaction" and in "Reset Reaction" they work well.

    Can someone help me to get MSR working again

    MSR is running bare metal on Rpi4

    Multi-System Reactor

  • use an expression for “condition must sustained for”
    E Edwin1972

    Reactor 22240-3b3254d6; Raspian bare-metal (RPi4)

    Is it possible to use an expression for “condition must sustained for”? I tried and no error but no result either. When collapsing condition options, the button remains yellow, but the content is no longer displayed when expanded.
    Is this a bug or not possible to use an expression for this?

    9fceec61-d200-4319-a28b-5e409a74883a-image.png

    Multi-System Reactor

  • Reactor 3.9develop-21009.1600 ALTUI Error
    E Edwin1972

    After upgrade everything works fine. @toggledbits Thanks again for the quick response.
    @amg0 When there is a new version of altui I always get an automatic notification. Can't I turn that off?

    Vera/openLuup plugins

  • Reactor 3.9develop-21009.1600 ALTUI Error
    E Edwin1972

    To day I also have the same problem. I've read the post, but can't trace the solution. I am using reactor (version 3.9develop-21009.1600) in openluup and AltUI v2.54.2553. Maybe someone can help me which steps I need to take to use reactor in openluup again.

    Vera/openLuup plugins

  • MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    I had the same problem. After upgrade to new version the problem is solved

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    I haven't found the time yet to fix MSR. I think there is something wrong with NPM. Node Red can't update some plugins either.

    Is it also possible to use the function in a reactor (openluup)?

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    @toggledbits I have updated MSR to latest-21258-6fb388e but still get the same error

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    Thanks for the quick response. I'm playing with it but I get an error when input expression.
    @toggledbits Is this due to the prerelease MSR? I am using version (pre-release) 0.1-21096. I haven't upgraded to new version yet

    61b5ee2b-bdb4-41a2-affb-c5048c3bc0cb-image.png

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    I have a Hikvision camera for a month and have been playing with it. Now I read a post of cw-kid (post : System integration roadmap) that you can control the camera by HTTP API request. That's cool if that also will work for me. Can someone explain what to enter in MSR for HTTPS request command to do so. (Marked red arrows)

    93ca9c9a-9ab1-443c-9201-5efcff3a45e2-image.png

    I want to turn the smart supplement light on and off at a specific time. Now I do that with scheduled switch, but it is better to control that with sunrise and sunset function with MSR. I'm curious how it works.

    Multi-System Reactor

  • MSR http PUT error
    E Edwin1972

    @whyfseeguy I also have a Hikvision camera since a month and I'm playing with it. Now I read your post that you can set a variable remotely through ISAPI. That would be cool. Could you explain how you can do that with MSR. I want to turn the smart supplement light on and off at a certain hour. Now I do that with scheduled switch but it's better with sun rise and sun set with logic MSR

    Multi-System Reactor

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    @rafale77
    I overwritten the L_ZWay2.lua file. De Z-way bridge does its job. The devices gives reaction (ON/OFF) but bridge gives no update of Remote_2-0-0-14-S, Remote_2-0-0-24-S or Remote_2-0-0-25-S

    Z-Wave.me

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    @rafale77
    I overwritten the L_ZWay2.lua file (keep the old one) on my PI4. The z-way bridge does not give an error, but the switches no longer respond in openluup. After the old file has been restored, they will work again.

    Z-Wave.me

  • calculate with MSR variables in LuaXP
    E Edwin1972

    @toggledbits
    Yes, it works! Excellent.
    Thank you for your time! Now I can continue my project. The new variable is also useful.

    Multi-System Reactor

  • calculate with MSR variables in LuaXP
    E Edwin1972

    Thanks! I have installed version 21098 on my vera and I entered 2.5 but it returns the same as 2. With stopwatch about 50 sec.

    Multi-System Reactor

  • calculate with MSR variables in LuaXP
    E Edwin1972

    @toggledbits My explanation of my project

    I use somfy motors (rfx) to open and close my roman blinds electrically. I can control this via RFXtrx433E USB Transceiver connect to my Vera. RFX gives no feedback so I can only open and close them and not moving them to a position based on the percentage of the slider. The RFX plugin (Tinmann) works with a slider related on MaxMoveTime (time to go from completely open to completely close)., but it doesn’t work with somfy. So I started my own project.

    I have installed the switchboard plugin on my Vera. I have created a virtual switch (virtual window coverings) and use it in MSR to close my blinds with the slider based on MaxMoveTime (time to go from completely open to completely close). It works with Vera and also with voice control by google home.

    MRS setting:
    Expression : LoadLevel_Last_Oost, MaxMoveTime_Oost

    c54f6eef-6c95-4e79-b5af-ade45904c297-image.png

    What I haven't solved yet is the following:
    I can operate Romand blinds by MSR with time schedule but would like to operate Roman blinds manually with the fibaro roller shutter 2, double click down / up and triple click stop function. For example, with a double click function I can start the following action:

    a6473fa6-4705-4fe0-b364-8bfd00f567bf-image.png

    I am using the virtual window covering (Switchboard) and switching up (double click Up), down (double click down) and stop (Triple click down). Switchboard can simulate motor movement of the covering by ramping LoadLevelStatus at a rate of XX% per second to the target value. This is the problem.
    MaxMoveTime (time to go from completely open to completely close) = 40 sec. Switchboard simulate motor movement = 34 sec (RampRatePerSecond =2).

    To set simulate motor movement =40 seconds, RamRatePerSeconde should be = 2.35. This does not work because they must be integer number. Is there a possibility to set the MaxMoveTime to simulate motor movement instead of movement % per sec?

    Multi-System Reactor

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    Check, Implementation file in the plugin device is I_ZWay2.xml.

    95f94047-2516-477e-9b30-76ab971efbad-image.png

    Z-Wave.me
  • Login

  • Don't have an account? Register

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