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. zwaveJS controller question/s
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor

zwaveJS controller question/s

Scheduled Pinned Locked Moved Multi-System Reactor
23 Posts 3 Posters 7.7k Views 3 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.
  • toggledbitsT toggledbits

    @gwp1 Open its Web UI and make sure the WebSocket (WS) server is enabled... looks like it may not be...

    26df1b39-e026-42c1-ae4f-3c783a9a6906-image.png

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

    @toggledbits It is.

    63e70a11-68cc-4b64-8604-5b06fe4f8ee7-image.png

    EDIT: I even cleared the 0.0.0.0 from the Server Host field just in case it was causing something wonky.

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

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

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

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #12

      0.0.0.0 is another way of saying "any address", so that's OK. Looks like HassOS, then?

      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
      0
      • toggledbitsT toggledbits

        0.0.0.0 is another way of saying "any address", so that's OK. Looks like HassOS, then?

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

        @toggledbits Yessir on both points.

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

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

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

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #14

          It's the devil.

          Try this: https://github.com/home-assistant/core/issues/63670#issuecomment-1008624418

          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
          0
          • toggledbitsT toggledbits

            It's the devil.

            Try this: https://github.com/home-assistant/core/issues/63670#issuecomment-1008624418

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

            @toggledbits So this is interesting (to me)...

            aa3feac8-d203-451d-9436-754dcc9e3313-image.png

            This isn't running. Should it be? In my initial install of Z-Wave JS UI it seemed to point toward that NOT running, it was handling everything and that just needed to be installed (which it prompted for IIRC.) I do have three devices on and running.

            EDIT: started Z-Wave JS, third tab Configuration and added this:

            0ad4bfb0-4e4b-45e8-ae47-02ce6ae6c014-image.png

            Z-Wave JS keeps stopping after I access Z-Wave JS UI which further supports my recollection that they don't both RUN, but both need to COEXIST.

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

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

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

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #16

              I have no idea... you can try it. HassOS is, to me, the devil incarnate, and I don't use it. Others here do, I suspect, and maybe they have some experience to offer. I would take the auto-updates, at least, because HA itself often requires new/latest versions of Z-Wave JS, and everything goes away on that integration when it doesn't get it.

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

              1 Reply Last reply
              1
              • PablaP Offline
                PablaP Offline
                Pabla
                wrote on last edited by
                #17

                You can only run one or the other. Uninstall whichever add on you don't need and try again, I ran into the same issue.

                G 1 Reply Last reply
                0
                • PablaP Pabla

                  You can only run one or the other. Uninstall whichever add on you don't need and try again, I ran into the same issue.

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

                  @pabla That did it! Uninstalled one, rebooted the other and applied the tweak that @toggledbits noted previously. Works like a champ - thank you both!

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

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

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

                  1 Reply Last reply
                  2
                  • G Offline
                    G Offline
                    gwp1
                    wrote on last edited by
                    #19

                    Quick question @toggledbits : in looking at my iblinds, I see the ability to call for recalibration. The Hubitat community driver has surfaced this. HASS has not (not a surprise, they're quite conservative in what they surface), MSR's zwaveJS controller does not. Is there a way to do so manually (editing a config, for instance)? These blinds wander over time and a scheduled recalibration is very helpful.

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

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

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

                    1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #20

                      I would have to look at the device data for the iBlinds devices you have, but I believe that you can access any feature of any device via ZWaveJSController, it just may not be a declared action on a native Reactor capability (in the same way you can call any service in HassController, even if it's not a declared service on the Reactor entity). We just need to figure out what that mechanism is for the iBlinds devices, and either use it as offered, or decide to bring it forward as a simplified action.

                      Can you point me to online docs for iBlinds that describe how to start (via Z-Wave) the calibration process?

                      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
                      0
                      • toggledbitsT toggledbits

                        I would have to look at the device data for the iBlinds devices you have, but I believe that you can access any feature of any device via ZWaveJSController, it just may not be a declared action on a native Reactor capability (in the same way you can call any service in HassController, even if it's not a declared service on the Reactor entity). We just need to figure out what that mechanism is for the iBlinds devices, and either use it as offered, or decide to bring it forward as a simplified action.

                        Can you point me to online docs for iBlinds that describe how to start (via Z-Wave) the calibration process?

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

                        @toggledbits Here's the link to the community driver that surfaced this:

                        https://raw.githubusercontent.com/RMoRobert/Hubitat/master/drivers/iBlinds-v3.groovy

                        I'll need to dig/contact iblinds Support for any official docs they might have.

                        EDIT: don't know if this is helpful or not but here's how the blinds show up in MSR:

                        e9363aad-2048-49de-a754-b46f98c00a1d-image.png 41426613-0aa1-4bd8-aacd-35ceef44f506-image.png a47c1497-bbc3-40d0-9645-73e89d899d4f-image.png e9775e26-efb5-40fc-9631-31c479c129a8-image.png 0761fad6-58ae-4d65-9c30-d6b6e6f2eb0f-image.png 570f6d19-8ae1-4c4d-99bb-613de072d177-image.png

                        This caught my eye, hence the ask:

                        x_zwave_values.Configuration_Remote_Calibration=1
                        

                        Again, don't know if any of this helps at all.

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

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

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

                        1 Reply Last reply
                        0
                        • toggledbitsT Offline
                          toggledbitsT Offline
                          toggledbits
                          wrote on last edited by
                          #22

                          OK. So it's driven by setting a config value, and that's not usual. You would use zwave_device.set_config action on that entity. That's parameter 7, it's a 1-byte length value, the value would be 1 and the bitmask you can just leave at 0.

                          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

                            OK. So it's driven by setting a config value, and that's not usual. You would use zwave_device.set_config action on that entity. That's parameter 7, it's a 1-byte length value, the value would be 1 and the bitmask you can just leave at 0.

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

                            @toggledbits PERFECT! Works exactly as the Community driver did in Hubitat. This is huge for my setup, thank you.

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

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

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

                            1 Reply Last reply
                            1
                            • G gwp1 referenced this topic on
                            • T tamorgen referenced this topic on
                            • toggledbitsT toggledbits locked this topic on
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            Recent Topics

                            • Arming Envisalink panel from MSR
                              T
                              tamorgen
                              0
                              7
                              182

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

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

                            • DynamicGroupController and attributes
                              therealdbT
                              therealdb
                              1
                              5
                              125

                            • Upgrade Issues
                              T
                              tbully
                              0
                              9
                              244

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

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

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

                            • Logon screen timeout
                              G
                              gwp1
                              0
                              5
                              199

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

                            • Upgrade advice - upgrade from aarch64 to ARM64 image
                              toggledbitsT
                              toggledbits
                              0
                              4
                              222
                            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