Announcement

Collapse
No announcement yet.

Strange issues with "Last Working Route:"

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

  • Strange issues with "Last Working Route:"

    I really need help on this issue. I keep seeing strange node numbers in the Last Working Route: for several nodes. I have a feeling that it has something to do with my Z-Wave network being slow at times. Here are several examples.

    64->105->55->45

    168->189->79->55

    255->255->227->255

    55->174->233->241

    My highest node number is 64 so I don't see how I can have numbers higher than that. I also have several nodes that have no last route that also can't see node one yet they can communicate with node 1.
    HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
    Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

    Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
    mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

    Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

  • #2
    I would reset the z-wave database. Make sure you have an up-to-date backup. You can reset it by going to Plug-Ins - Manage and then click on the Z-Wave plugin’s hyperlink. There will be a button there.
    HS 3.0.0.548: 1970 Devices 1149 Events
    Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

    Comment


    • #3
      Well, I'm really down now. My Z-NET interface refuses to restore. Everything was basically working until I tried to restore. Here is what I get whenever I try to restore.


      Checking file...
      Starting restore operation.
      Restoring node information from the file /home/pi/Beta/HomeSeerTest/Data/Z-Wave/ZNet_Wxxxxx Family_F9xxxxxx_2018-12-24_13.15.43.ZWave. Please wait...
      Erasing the interface...
      Z-Wave Interface Z-NET-01 (1) has been reset to its defaults.
      Error: Z-NET-01: The command to set the interface to its defaults failed.
      Error sending ERASE CONTROLLER command to the interface.

      I even when back to the system on my RaspberryPi, made a copy of the HomeSeer directory so I don't touch the original then started the copy. I still get the same messages. For some reason I can't restore the Z-NET. I’ve done this before
      I do have the image so I can start from scratch unless something is wrong with the actual controller in the Z-NET.

      Thing is I've done this before and never had an issue like this.

      I can remember his ID but if possiable will the member who knows Z-Wave and Z-NETs like the back of his hand please chime in?
      HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
      Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
      IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

      Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
      mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

      Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

      Comment


      • #4
        Thought I toss in an update. This is from my Ubuntu system where the problem started. It's much the same but a slightly different error to start. Running Bet 478 and Z-Wave 249 (also just tried 252), more info below, both of which have been rock solid.

        This is from the restore command.
        Checking file...
        Starting restore operation.
        Restoring node information from the file /opt/homeseer/Data/Z-Wave/ZNet_Warren Family_F9xxxx15_2018-02-27_05.57.34.ZWave. Please wait...
        Erasing the interface...
        Z-Wave Interface Z-NET-01 (1) has been reset to its defaults.
        Error: Z-NET-01: The command to set the interface to its defaults failed.
        Error sending ERASE CONTROLLER command to the interface.
        Here is from HS3 output when started from the ./go command which is basically the log info plus a bit more. You can see the failure here plus it connection using the wrong network ID because the restore didn't complete.
        06:59:24:7636:[Z-Wave]->Z-NET-01: Restoring node information from the file /opt/homeseer/Data/Z-Wave/ZNet_xxxxxx Family_F9xxxx15_2018-02-27_05.57.34.ZWave. Please wait...3.0.1.249: Z-Wav
        06:59:24:7672:[Z-Wave Warning]->Z-NET-01: Erasing the interface...
        06:59:24:7681:[Z-Wave]->Z-Wave Interface Z-NET-01 (1) has been reset to its defaults.3.0.1.249: Z-Wav
        Error: Z-NET-01: The command to set the interface to its defaults failed.
        06:59:29:7715:[Z-Wave Error]->Z-NET-01: The command to set the interface to its defaults failed.
        06:59:33:7771:[Z-Wave]->Z-NET-01: Exiting Ethernet Communications Thread
        06:59:34:0129:[Z-Wave]->Z-NET-01: ============================================================ ==========
        06:59:34:0136:[Z-Wave]->Z-NET-01: ----------------------------------------------------------------------
        06:59:34:0142:[Z-Wave]->Initializing Z-Wave interface Z-NET-01 (HomeSeer Z-NET Ethernet) at 10.0.2.17, port 2001
        06:59:34:0148:[Z-Wave]->Z-NET-01: ----------------------------------------------------------------------
        06:59:34:0157:[Z-Wave]->Z-NET-01: The Z-Wave Command Execution Thread was Started or Restarted.
        06:59:34:0168:[Z-Wave]->Z-NET-01: Z-Wave Ethernet at IP 10.0.2.17, connected to interface ok.
        06:59:34:2693:[Z-Wave]->Z-NET-01: The Z-Wave API Execution Thread was Started or Restarted.
        06:59:34:2717:[Z-Wave]->Z-NET-01: Getting node information from controller...
        06:59:36:4066:[Z-Wave]->Z-NET-01: Controller Manufacturer: Express Controls, ID=0x2, Type=0x53.0.1.249: Z-Wav
        06:59:36:4082:[Z-Wave]->Z-NET-01: Controller firmware version: 4.32
        06:59:36:4294:[Z-Wave]->Z-NET-01: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.3.0.1.249: Z-Wav
        06:59:36:4310:[Z-Wave]->Z-NET-01: Z-Wave Serial API version: 5
        06:59:36:4325:[Z-Wave]->Z-NET-01: Z-Wave interface node ID: 1, Home ID: C20A5A27
        06:59:36:4344:[Z-Wave]->Z-NET-01: Found 1 Z-Wave nodes in interface node ID 1 (Z-NET-01)
        06:59:36:4716:[Z-Wave]->The interface's security support has been set.
        06:59:36:4996:[Z-Wave]->Z-NET-01 Controller chip type is ZW050x.
        06:59:36:5014:[Z-Wave]->Z-NET-01 Controller is static lib.
        06:59:36:5030:[Z-Wave]->Z-NET-01 is the Primary Controller for this network.
        06:59:36:5046:[Z-Wave]->Z-NET-01 attempting to set as SUC/SIS...
        06:59:36:5700:[Z-Wave]->Z-NET-01 has successfully been made the SIS for this network.
        06:59:36:5748:[Z-Wave]->Z-NET-01: ............................................................ ..........
        06:59:36:5764:[Z-Wave]->Z-NET-01: .............................. FINISHED ..............................
        06:59:36:5780:[Z-Wave]->Z-NET-01: ............................................................ ..........
        Current Date/Time: 1/5/2019 7:20:41 AM
        HomeSeer Version: HS3 Standard Edition 3.0.0.478
        Linux version: Linux auto 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 0 Hours 31 Minutes 18 Seconds
        IP Address: 10.0.2.15
        Number of Devices: 339
        Number of Events: 470
        Available Threads: 399
        HSTouch Enabled: True
        Event Threads: 0
        Event Trigger Eval Queue: 0
        Event Trigger Priority Eval Queue: 0
        Device Exec Queue: 0
        HSTouch Event Queue: 0
        Email Send Queue: 0
        Anti Virus Installed:

        Enabled Plug-Ins
        3.0.0.13: AirplaySpeak
        3.0.0.54: EasyTrigger
        1.3.6927.42284: LiftMaster MyQ
        3.4.17.1: mcsMQTT
        3.0.1.109: PHLocation
        0.0.0.45: Pushover 3P
        3.0.1.252: Z-Wave
        HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
        Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
        IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

        Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
        mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

        Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

        Comment


        • #5
          Does "Erase this interface and create a new network" work?
          HS 3.0.0.548: 1970 Devices 1149 Events
          Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

          Comment


          • #6
            In a word, NO. Last reports when I did the erase. Every time it goes through the cycle it creates another network.

            10:19:50:4519:[Z-Wave]->Z-Wave Interface Z-NET-01 (1) has been reset to its defaults.
            Error: Z-NET-01: The command to set the interface to its defaults failed.
            10:19:55:4578:[Z-Wave Error]->Z-NET-01: The command to set the interface to its defaults failed.
            10:19:55:4623:[Z-Wave Warning]->A Z-Wave interface on the system is being restarted - some Z-Wave signals could be missed.
            10:20:03:3718:[Z-Wave]->Z-NET-01: Exiting Ethernet Communications Thread
            10:20:10:7046:[Z-Wave]->Z-NET-01: ============================================================ ==========
            10:20:10:7051:[Z-Wave]->Z-NET-01: ----------------------------------------------------------------------
            10:20:10:7055:[Z-Wave]->Initializing Z-Wave interface Z-NET-01 (HomeSeer Z-NET Ethernet) at 10.0.2.17, port 2001
            10:20:10:7059:[Z-Wave]->Z-NET-01: ----------------------------------------------------------------------
            10:20:10:7066:[Z-Wave]->Z-NET-01: The Z-Wave Command Execution Thread was Started or Restarted.
            10:20:10:7075:[Z-Wave]->Z-NET-01: Z-Wave Ethernet at IP 10.0.2.17, connected to interface ok.
            10:20:10:9597:[Z-Wave]->Z-NET-01: The Z-Wave API Execution Thread was Started or Restarted.
            10:20:10:9613:[Z-Wave]->Z-NET-01: Getting node information from controller...
            10:20:13:0954:[Z-Wave]->Z-NET-01: Controller Manufacturer: Express Controls, ID=0x2, Type=0x5
            10:20:13:0972:[Z-Wave]->Z-NET-01: Controller firmware version: 4.32
            10:20:13:1193:[Z-Wave]->Z-NET-01: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
            10:20:13:1212:[Z-Wave]->Z-NET-01: Z-Wave Serial API version: 5
            10:20:13:1250:[Z-Wave]->Z-NET-01: Z-Wave interface node ID: 1, Home ID: DAE11AC5
            10:20:13:1267:[Z-Wave]->Z-NET-01: Found 1 Z-Wave nodes in interface node ID 1 (Z-NET-01)
            10:20:13:1732:[Z-Wave]->The interface's security support has been set.
            10:20:13:2011:[Z-Wave]->Z-NET-01 Controller chip type is ZW050x.
            10:20:13:2028:[Z-Wave]->Z-NET-01 Controller is static lib.
            10:20:13:2044:[Z-Wave]->Z-NET-01 is the Primary Controller for this network.
            10:20:13:2057:[Z-Wave]->Z-NET-01 attempting to set as SUC/SIS...
            10:20:13:2727:[Z-Wave]->Z-NET-01 has successfully been made the SIS for this network.
            10:20:13:2773:[Z-Wave]->Z-NET-01: ............................................................ ..........
            10:20:13:2787:[Z-Wave]->Z-NET-01: .............................. FINISHED ..............................
            10:20:13:2804:[Z-Wave]->Z-NET-01: ............................................................ ..........
            10:20:40:7797:[Z-Wave]->Starting Z-Wave Polling for Network DAE11AC5...
            HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
            Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
            IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

            Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
            mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

            Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

            Comment


            • #7
              Post the contents of /etc/ser2net.conf from the Z-Net.

              Comment


              • #8
                Here it is. BTW, about the only thing I have come up with is it got corrupted during a power down restart. If not that I guess the card may have failed but it seems to respond in every way other than what you see. Push comes to shove I can always re-image the card.

                BTW, can ser2net handle more than z-wave? I was thinking ZigBee.

                #
                # This is the configuration file for ser2net. It has the following format:
                # <TCP port>:<state>:<timeout>:<device>:<options>
                # TCP port
                # Name or number of the TCP/IP port to accept con-
                # nections from for this device. A port number may
                # be of the form [host,]port, such as 127.0.0.1,2000
                # or localhost,2000. If this is specified, it will
                # only bind to the IP address specified. Otherwise
                # it will bind to all the ports on the machine.
                #
                # state Either raw or rawlp or telnet or off. off disables
                # the port from accepting connections. It can be
                # turned on later from the control port. raw enables
                # the port and transfers all data as-is between the
                # port and the long. rawlp enables the port and
                # transfers all input data to device, device is open
                # without any termios setting. It allow to use
                # /dev/lpX devices and printers connected to them.
                # telnet enables the port and runs the telnet proto-
                # col on the port to set up telnet parameters. This
                # is most useful for using telnet.
                #
                # timeout
                # The time (in seconds) before the port will be dis-
                # connected if there is no activity on it. A zero
                # value disables this funciton.
                #
                # device The name of the device to connect to. This
                # must be in the form of /dev/<device>.
                #
                # options
                # Sets operational parameters for the serial port.
                # Options 300, 1200, 2400, 4800, 9600, 19200, 38400,
                # 57600, 115200 set the various baud rates. EVEN,
                # ODD, NONE set the parity. 1STOPBIT, 2STOPBITS set
                # the number of stop bits. 7DATABITS, 8DATABITS set
                # the number of data bits. [-]XONXOFF turns on (-
                # off) XON/XOFF support. [-]RTSCTS turns on (- off)
                # hardware flow control, [-]LOCAL turns off (- on)
                # monitoring of the modem lines, and
                # [-]HANGUP_WHEN_DONE turns on (- off) lowering the
                # modem control lines when the connextion is done.
                # NOBREAK disables automatic setting of the break
                # setting of the serial port.
                # The "remctl" option allow remote control (ala RFC
                # 2217) of serial-port configuration. A banner name
                # may also be specified, that banner will be printed
                # for the line. If no banner is given, then no
                # banner is printed.
                #
                # or...

                # BANNER:<banner name>:banner
                # This will create a banner, if the banner name is given in the
                # options of a line, that banner will be printed. This takes the
                # standard "C" \x characters (\r is carraige return, \n is newline,
                # etc.). It also accepts \d, which prints the device name, \p,
                # which prints the TCP port number, and \s which prints the serial
                # parameters (eg 9600N81). Banners can span lines if the last
                # character on a line is '\'. Note that you *must* use \r\n to
                # start a new line.
                #
                # Note that the same device can be listed multiple times under different
                # ports, this allows the same serial port to have both telnet and raw
                # protocols.

                # The original config file shipped with the upstream sources can be
                # found in /usr/share/doc/ser2net/examples

                BANNER:banner:\r\nser2net port \p device \d [\s] (Debian GNU/Linux)\r\n\r\n

                #2000:telnet:600:/dev/ttyS0:9600 8DATABITS NONE 1STOPBIT banner
                2001:raw:0:/dev/ttyAMA0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
                #3000:telnet:600:/dev/ttyS0:19200 8DATABITS NONE 1STOPBIT banner
                #3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner
                HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                Comment


                • #9
                  I haven't tried this yet but I will tomorrow. I'm going back to my Pi and make a backup of the pre-beta system and then run that to see if it can reconnect to the Z-NET. If it can then I suspect there is a bug in the latest Z-Wave plugins when it comes to reloading. If it fails then something has happen to my Z-NET and I'll reimage the SD card and try again. Well maybe not till monday as we were planing to go to Disneyland tomorrow.
                  HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                  Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                  IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                  Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                  mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                  Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                  Comment


                  • #10
                    Low probability the issue is with the Raspberry Pi or associated SD card. All the rpi provides is a transparent communication path between the ZWave plugin and the Zwave controller chip (on the daughtercard). I asked about ser2net.conf because I hoped it was something simple -- too short of a timeout. Unfortunately, you have the original (un-patched) version that has no timeout configured, so that can't be it.

                    The problem you are seeing "The command to set the interface to its defaults failed" seems most likely to be an issue with the controller chip itself, or possibly some mis-configuration or error at the ZWave plugin end. I've nothing to suggest if the issue is with the controller, but on the chance its with the plugin, if you haven't already done so I would suggest a 'Factory Reset' from the /ZWaveConfig page. According to the mouse-over of this button, this "will erase all of your Z-Wave interfaces, delete the Z-Wave database file and delete the Z-Wave INI file".

                    Comment


                    • #11
                      Didn’t see a factory reset option only an Erase. When I use the Erase it gives an error.

                      I also went went directly to the Z-NETs web interface but no Factory Reset there.

                      So I’ll try going back to a copy of HS3 prior to switching to the Beta of HS3 and the Z-NET and try again. After that a full reload. I could also try the latest sent code you upgraded. That would be one last shot but if that doesn’t fix it I guess I’ll have to order a ZNET.
                      HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                      Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                      IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                      Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                      mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                      Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                      Comment


                      • #12
                        Go to /ZWaveConfig

                        Or Plugins->Manage, then click on the 'Z-Wave' link on the title of the plugin.

                        Click image for larger version

Name:	ZWaveConfig.PNG
Views:	17
Size:	220.0 KB
ID:	1272989

                        Comment


                        • #13
                          I was confused and was on the controller page. Went there and did all the resets and nothing has changed other than the database is trashed. Not worried about that as I’ll just restore it.

                          that leaves just the tests with the older drivers to see what happens.
                          HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                          Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                          IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                          Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                          mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                          Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                          Comment


                          • #14
                            I was wondering about doing a manual reset with a simple terminal program on the pi. That way once could see exactly what’s returned. Anyway, just a thought.
                            HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                            Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                            IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                            Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                            mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                            Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                            Comment


                            • #15
                              One other idea, my ZNET is my old ZeeS2. I’m thinking I could put the original, or a copy, SD card back in and use it to try and reset the wave card. If that doesn’t work I figure nothing will.
                              HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                              Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                              IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                              Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                              mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                              Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                              Comment

                              Working...
                              X