Announcement

Collapse
No announcement yet.

Z-Net not reconnecting after disconnect - Solved!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by rjh View Post
    The posted solution is no good in that it only handles a link going down, and it does not handle other network issues like loss of Internet, or loss of WIFI.

    With the version .20, can you unplug the cable then wait and see if the LED goes RED in about 60 seconds, then re-connect the cable and see if it reconnects.

    With all my testing here is always re-connects, I don't understand why this fix will not work, I would need to see more logs.

    Make sure you are running the latest Z-Wave plugin as there are some re-connect fixes there also.
    I have tried that, and it does reconnect. But I am still having issues. I use Jon00's log monitor, and after 3 z-wave errors it sends a reboot request to my Z-net, and I get a pushover notification that I had a z-wave error. I get about 4 a day now. I just checked my log but as I restarted after testing with unplugging the cable there is nothing I can send, but I posted the errors on here in this thread before, they are always the same. Since going to .20 its worse for me
    I did a filter in teh log for z-wave error, and I have a few theer which I will attach here. The ones Aug-20 around 11.04 are when I was testing with unplugging the cable. The others are the 'normal' errors I get, and that is yesterday and today until lunchtime...

    I am using zwave plugin 3.0.1.87
    Attached Files
    Last edited by mikee123; August 20, 2016, 10:07 AM.

    Comment


      Originally posted by rjh View Post
      The posted solution is no good in that it only handles a link going down, and it does not handle other network issues like loss of Internet, or loss of WIFI.

      With the version .20, can you unplug the cable then wait and see if the LED goes RED in about 60 seconds, then re-connect the cable and see if it reconnects.

      With all my testing here is always re-connects, I don't understand why this fix will not work, I would need to see more logs.

      Make sure you are running the latest Z-Wave plugin as there are some re-connect fixes there also.
      Mine seem to be staying connected and seem to reconnect reliably.

      I am running 3.0.1.90 and 3 Z-Nets. They are all running 1.0.20 unmodified firmware. after experimenting with zwolfpacks hack, I burned 3 SD cards with fresh factory 1.0.17 versions, then updated all three to 1.0.20 through the web interface.

      I have always and still run them on static IP addresses with Ethernet Connections.

      Since all of these changes, two or all three of my Z-Nets will throw an error several times when HomeSeer is started:

      Aug-20 8:39:15 AM Z-Wave Error Z-Net-Shed: The Z-Net-Shed interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
      Aug-20 8:39:12 AM Z-Wave Error Z-Net-Shed: The Z-Net-Shed interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
      Aug-20 8:39:09 AM Z-Wave Error Z-Net-Shed: The Z-Net-Shed interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
      Aug-20 8:39:08 AM Z-Wave Error Z-Net-Primary: The Z-Net-Primary interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
      Aug-20 8:39:05 AM Z-Wave Error Z-Net-Primary: The Z-Net-Primary interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
      Aug-20 8:39:02 AM Z-Wave Error Z-Net-Primary: The Z-Net-Primary interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).


      These errors have occurred every time I have started HomeSeer since moving from 1.0.17 to 1.0.20 and Z-Wave 3.0.1.89. They only and always show up on HomeSeer startup.

      Everything is working fine after they connect and they will connect after about three of those errors.
      HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

      Comment


        I am updating to 3.0.1.90 now, see if it makes a difference

        Comment


          Even with 3.0.1.90 I am still getting errors. Not sure if they are as frequent, this is the first since the upgrade yesterday. In the log its triggering the Z-wave error event, which normally reboots my Z-net. For the purpose of testing and to be able to document what exactly happens I have disabled the event, so its triggering but its not sending the reboot command.

          This is the log:

          Aug-21 15:04:33 Z-Wave New Interface is the SIS for the network.
          Aug-21 15:04:33 Z-Wave New Interface There is a SUC/SIS in the network.
          Aug-21 15:04:33 Z-Wave New Interface Controller is static lib.
          Aug-21 15:04:33 Z-Wave New Interface Controller chip type is ZW050x.
          Aug-21 15:04:33 Z-Wave The interface's security support has been set.
          Aug-21 15:04:33 Z-Wave New Interface: Z-Wave PC Controller is Type: Static Controller
          Aug-21 15:04:33 Z-Wave New Interface: Z-Wave PC Controller Library Version: Z-Wave 4.05 (ZDK 6.51.6)
          Aug-21 15:04:33 Z-Wave New Interface: Found 48 Z-Wave nodes in interface node ID 1 (New Interface)
          Aug-21 15:04:33 Z-Wave New Interface: Z-Wave interface node ID: 1, Home ID: E075A8D5
          Aug-21 15:04:33 Z-Wave New Interface: Z-Wave Serial API version: 5
          Aug-21 15:04:31 Z-Wave New Interface: Controller firmware version: 4.32
          Aug-21 15:04:31 Z-Wave New Interface: Controller Manufacturer: Express Controls, ID=0x2, Type=0x5
          Aug-21 15:04:31 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:04:29 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:04:29 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.13...
          Aug-21 15:04:28 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:04:28 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:04:28 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:04:26 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:04:26 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.13...
          Aug-21 15:04:25 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:04:25 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:04:25 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:04:24 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:04:24 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:04:22 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:04:20 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:18 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multitemp2.vb
          Aug-21 15:04:18 Event Event Trigger "System Multi temperature virtual device"
          Aug-21 15:04:17 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:14 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:13 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:04:13 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:04:11 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:08 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:05 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:04:02 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:04:02 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:04:01 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:04:01 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:04:01 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:53 Z-Wave Warning New Interface: The Ethernet interface at (192.168.0.13 port: 2001) was not successfully connected. Will keep attempting to connect...
          Aug-21 15:03:53 Z-Wave Warning New Interface: Cannot connect to Z-Wave Ethernet at IP 192.168.0.13 port: 2001, Ex=No connection could be made because the target machine actively refused it 192.168.0.13:2001
          Aug-21 15:03:52 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.13...
          Aug-21 15:03:51 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:50 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:50 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:49 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:49 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:46 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:03:46 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:03:44 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/zwave error.vb
          Aug-21 15:03:44 Pushover 3P Pushover Notification Sent - Message Title: Zwave error
          Aug-21 15:03:44 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:03:44 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.13...
          Aug-21 15:03:43 Jon00_HSLogMon Zwave error event triggered
          Aug-21 15:03:43 Device Control Device: System System Zwave error to On (100)
          Aug-21 15:03:43 Event Event Trigger "System Zwave error"
          Aug-21 15:03:43 Jon00_HSLogMon [Trigger1] Successful trigger parameters
          Aug-21 15:03:43 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:03:43 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:03:43 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:41 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:03:41 Z-Wave Error New Interface: Exception transmitting to IP 192.168.0.13: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
          Aug-21 15:03:41 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:38 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:38 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:37 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:37 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:26 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:26 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:26 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:03:26 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:03:25 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multitemp2.vb
          Aug-21 15:03:25 Event Event Trigger "System Multi temperature virtual device"
          Aug-21 15:03:25 Jon00_HSLogMon [Trigger1] Successful trigger parameters
          Aug-21 15:03:25 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:25 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:24 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:03:24 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.13...
          Aug-21 15:03:23 Jon00_HSLogMon [Trigger1] Successful trigger parameters
          Aug-21 15:03:23 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:23 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:03:23 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:03:21 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:03:21 Z-Wave Error New Interface: Exception transmitting to IP 192.168.0.13: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
          Aug-21 15:03:21 Z-Wave Error New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
          Aug-21 15:03:14 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:14 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:13 Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/multi energy.vb
          Aug-21 15:03:13 Event Event Trigger "System Multi energy virtual device"
          Aug-21 15:03:03 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:03:03 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:03:00 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:03:00 Z-Wave Error New Interface: Exception transmitting to IP 192.168.0.13: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
          Aug-21 15:02:49 Z-Wave New Interface: Getting node information from controller...
          Aug-21 15:02:49 Z-Wave New Interface: Processing data buffered by the interface while it was disconnected.
          Aug-21 15:02:47 Z-Wave New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
          Aug-21 15:02:47 Z-Wave Error New Interface: Exception transmitting to IP 192.168.0.13: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.

          Comment


            Can you disable your reboot request and see if eventually reconnects with .20, it should now.


            Originally posted by mikee123 View Post
            I have tried that, and it does reconnect. But I am still having issues. I use Jon00's log monitor, and after 3 z-wave errors it sends a reboot request to my Z-net, and I get a pushover notification that I had a z-wave error. I get about 4 a day now. I just checked my log but as I restarted after testing with unplugging the cable there is nothing I can send, but I posted the errors on here in this thread before, they are always the same. Since going to .20 its worse for me
            I did a filter in teh log for z-wave error, and I have a few theer which I will attach here. The ones Aug-20 around 11.04 are when I was testing with unplugging the cable. The others are the 'normal' errors I get, and that is yesterday and today until lunchtime...

            I am using zwave plugin 3.0.1.87
            💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

            Comment


              I had the event which is called from the log monitor disabled, but I think it was still running. I have disabled the reboot command, and will post the log here if there is another event

              Comment


                mikee
                Do you know why your having so many disconnects?
                Here I'm working with 7 znets which are spread all over two school campuses. We had some bad connections that were causing our disconnects. I was wondering what's causing you to have the problems you're experiencing.
                Blair

                HomeSeer: HS3 Pro | Blue-Iris 4 on Windows10Pro
                | Devices: 832 | Events: 211 |
                Plug-Ins: Z-Wave | RFXCOM | UltraRachio3 | Sonos
                BLLAN | BLLOCK | NetCAM | Global Cache Pro | Blue-Iris4

                Comment


                  Originally posted by BlairG View Post
                  mikee
                  Do you know why your having so many disconnects?
                  Here I'm working with 7 znets which are spread all over two school campuses. We had some bad connections that were causing our disconnects. I was wondering what's causing you to have the problems you're experiencing.
                  I really don't know. Maybe, my Z-net is connected to the internet via a powerline module. Maybe that drops connection, which then causes the errors. I was thinking of trying to connect via wifi, but that has the same problems at the end of the day.

                  Comment


                    Rich, I have disabled the reboot command for the Z-net. But last night I run my good night event, nothing turned off... I checked and my Z-net was down with the usual error. I did let it try and reconnect for quite a while, but it didn't. Then I manually triggered the Z-net reboot as I wanted to go to bed... I still have about 10 minutes of log file before and including the reboot, so there should be enough. I will attach it as a .txt file as its quite long

                    And I am on .20 firmware, zwave version 3.0.1.90
                    Attached Files

                    Comment


                      I really don't know. Maybe, my Z-net is connected to the internet via a powerline module. Maybe that drops connection, which then causes the errors. I was thinking of trying to connect via wifi, but that has the same problems at the end of the day.
                      Just FYI, I have used the powerline modules and discovered that normal household appliances will cause temporary loss of connection. In fact just about everything with a motor such as a vacuum cleaner or mixer will disrupt the powerline module.

                      I know that my re-occurring disconnects are caused by microwave links dropping, not by HS3. My only issue with HS3 was an orderly recovery after the disconnect.

                      Bob

                      Comment


                        I might give wifi a try to connect my Z-net. Can I use any USB wifi stick ?

                        Comment


                          I might give wifi a try to connect my Z-net. Can I use any USB wifi stick ?
                          I do not know which version ZNet that you have but I remember in the early days of the ZEE, only certain USB WiFi adapters would work. I have always been connected by Cat5e so I cannot answer that question.

                          Bob

                          Comment


                            Originally posted by mikee123 View Post
                            I might give wifi a try to connect my Z-net. Can I use any USB wifi stick ?
                            I used the one offered by HomeSeer and it works well.
                            HS4Pro on a Raspberry Pi4
                            54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                            Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                            HSTouch Clients: 1 Android

                            Comment


                              You can maybe too make adjustments to the network buffer size. Googling found these changes to the RPi OS. Not really sure this will help though.

                              As Rich mentions above an internet link (router connection) or wireless will not make it any better. Easiest to test by just disconnecting the network cable and plugging it back in.

                              add this line to /etc/sysctl.conf

                              Code:
                              # increase TCP max buffer size setable using setsockopt()
                                  #net.core.rmem_max = 16777216
                                  #net.core.wmem_max = 16777216
                                  # increase Linux autotuning TCP buffer limits
                                  # min, default, and max number of bytes to use
                                  # set max to at least 4MB, or higher if you use very high BDP paths
                                  #net.ipv4.tcp_rmem = 4096 87380 16777216
                                  #net.ipv4.tcp_wmem = 4096 65536 16777216
                                  # don't cache ssthresh from previous connection
                                  net.ipv4.tcp_no_metrics_save = 1
                                  net.ipv4.tcp_moderate_rcvbuf = 1
                                  # recommended to increase this for 1000 BT or higher
                                  #net.core.netdev_max_backlog = 2500
                                  # for 10 GigE, use this, uncomment below
                                  # net.core.netdev_max_backlog = 30000
                                  # Turn off timestamps if you're on a gigabit or very busy network
                                  # Having it off is one less thing the IP stack needs to work on
                                  net.ipv4.tcp_timestamps = 0
                                  # disable tcp selective acknowledgements.
                                  net.ipv4.tcp_sack = 0
                                  #enable window scaling
                                  net.ipv4.tcp_window_scaling = 1
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                              HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                              HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                              HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                              Comment


                                Originally posted by mikee123 View Post
                                I will attach it as a .txt file as its quite long
                                This looks like the situation I reported in post #47.
                                Particularly this repeating sequence:

                                Aug-21 22:25:27

                                Z-Wave
                                New Interface: Getting node information from controller...
                                Aug-21 22:25:27

                                Z-Wave
                                New Interface: Processing data buffered by the interface while it was disconnected.
                                Aug-21 22:25:25

                                Z-Wave
                                New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
                                Aug-21 22:25:25

                                Z-Wave Warning
                                Trying to re-connect to Ethernet interface at IP 192.168.0.13...
                                Aug-21 22:25:24

                                Z-Wave
                                New Interface: Getting node information from controller...
                                Aug-21 22:25:24

                                Z-Wave Error
                                New Interface: The New Interface interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
                                Aug-21 22:25:24

                                Z-Wave
                                New Interface: Processing data buffered by the interface while it was disconnected.
                                Aug-21 22:25:22

                                Z-Wave
                                New Interface: Z-Wave Ethernet at IP 192.168.0.13, connected to interface ok.
                                Aug-21 22:25:22

                                Z-Wave Warning
                                Trying to re-connect to Ethernet interface at IP 192.168.0.13...
                                With the 1.20 fix, in the case of a network interruption the Z-NET takes 60 seconds to timeout and drop the connection on port 2001. However for a shorter interruption like is likely happening here, the network connection is reestablished sooner that this and the plugin's reconnect attempts get queued up at the Z-NET. When these finally go thru, the delayed responses appear to confuse the plugin, and mayhem ensues.
                                Despite what Rich says, I think the patch that I posted is a better solution in this particular case.

                                PS. Your best chance at a long-term solution is to fix your link; I would recommend continuing your focus on that.
                                Last edited by zwolfpack; August 22, 2016, 12:08 PM. Reason: add PS

                                Comment

                                Working...
                                X