Announcement

Collapse
No announcement yet.

Cannot get a SmartStick+ to restore when connected to a Z-NET

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

  • Cannot get a SmartStick+ to restore when connected to a Z-NET

    I have a thread here about this but it's not getting much traffic likely due to it's in the wrong place. Maybe the moderators can combine it with this thread.

    I have a ZeeS2 that I retired when I got HS3 Standard and installed it on a Intel NUC. So I took the ZeeS2 and installed the Z-NET v1.0.23 software on it and ran it for many months with it's built in EZZee card. Well, that card failed so I borrowed a UZB and it ran great. I needed to remove the UZB so I figured I just get a SmartStick+ and run it just like I had with the UZB. BTW, I would have just replaced the borrowed UZB with another UZB however the latest firmware shipping in the current UZB, according to HS, won't restore as the earlier firmware did.

    Well, there is where I started having problems as the Z-Net doesn't seem to be able to restore to a SmartStick+ on a Z-Net. I can put the SmartStick+ on my NUC and it restores. I can then put it on the Z-Net and everything works except the restore function. That seems strange why this is the case being a HS product.

    Any ideas
    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
    Could someone at HS please answer this question. I've read that a SmartStick+ should function fine when used on a Z-NET. Is this the case or not? Is there any thing special to get it to work?
    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


    • #3
      Are you trying to plug a Z-Stick into a Z-Net? If so this will not work. The Z-Net is the "Z-Wave" interface as far as HS3 is concerned.
      -Rupp
      sigpic

      Comment


      • #4
        I’ve got to find it again but I thought there were documents that it should. The only thing that doesn’t work is the restore.
        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
          Originally posted by Rupp View Post
          Are you trying to plug a Z-Stick into a Z-Net? If so this will not work. The Z-Net is the "Z-Wave" interface as far as HS3 is concerned.
          Why do you think this wouldn't work? The SmartStick is functionally identical to the UZB, which is what is delivered on the International Z-Net models. Plus, as he said, everything is working except for restore.

          Comment


          • #6
            I'm referring to the non European version of the Z-Net as these come shipped without an external radio. The EU version this may work.
            -Rupp
            sigpic

            Comment


            • #7
              It should make any difference. Ser2net is basically a transport system. There is no Z-Wave code at all to my understanding. In face my understanding is that any serial USB device such ZigBee could use the transport.

              Dave, 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


              • #8
                Yes, the most recent release Z-Net V2 1.0.23 from late 2016 added support for the /dev/ttyACM0 serial device. This supports both the UZB device delivered with the international Z-Net's and the SmartStick+.

                From your other thread, your problem seems to initiate at the point where the plugin is attempting to reconnect to the controller after the erase operation has completed. Pure speculation, perhaps there is a software timing issue. What type/how fast is the system you are running HS3 on?

                Comment


                • #9
                  Below is the computer specification It's Ethernet connected. It has 8GB of ram and a 120GB SSD.

                  The RPi is a 3B v2 which is what HS uses for the ZEE S2 which is what it was originally. The RPi is WiFi connected but the AP and the RPi are only about 4 feet apart so it has a very strong signal.

                  Did another connection to the Z-NET to confirm the version. (Z-NET V2 Configuration- Version 1.0.23)

                  Note, I did a restart interface from the Z-Wave menu and I did get an error. I don't remember seeing this during a full HS3 startup.
                  Code:
                    
                  Jul-23 5:53:22 PM
                  Z-Wave Error
                  HS-SS+ZNet-1: The HS-SS+ZNet-1 interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (5).
                  Jul-23 5:53:22 PM
                  Z-Wave Error
                  HS-SS+ZNet-1: The HS-SS+ZNet-1 interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (5).
                  Jul-23 5:53:18 PM
                  Z-Wave Warning
                  A Z-Wave interface on the system is being restarted - some Z-Wave signals could be missed.
                  I did have to readd a FC100+ which was screwed up. I've had to play with it to get it working. There may be something amiss with the configuration. I have a 25' Ethernet cable so I could direct connect to Ethernet, assuming I can free up a port, and do some testing to see if that helps.

                  The only reason I've been sticking with HS version Ser2net was for the find.homeseer.com but since I assign it's fixed IP address using DHCP reservations I really don't have to.

                  Code:
                  • Intel Core i3-8109U CPU (Coffee Lake), dual-core with hyperthreading, up to 3.60 GHz, 28W TDP
                  • Integrated Intel Iris Plus Graphics 655 GPU, up to 1.05 GHz, 128 MB eDRAM
                  • RAM: 2x DDR4-2400 SO-DIMM, 1.2 volt, 32 GB max.
                  • SSD: 1x 22×80 (22×42 also supported) M.2 SSD slots for SATA or NVMe SSD
                  • HDMI 2.0a port, 4k support with HDR
                  • USB Type-C port that provides USB 3.1 Gen2 (10 Gbps), Thunderbolt 3 and DisplayPort 1.2 capabilities
                  • 4 USB 3.1 Type-A (the normal one) ports (2 front, 2 rear)
                  • Intel gigabit Ethernet Adapter
                  • Intel Wireless-AC 9560 WiFi adapter with Bluetooth 5.0
                  • 3.5 mm front audio jack for stereo + microphone
                  • Consumer infrared receiver
                  • Dual microphone array
                  • SDXC card reader
                  • Dimensions: 117 mm x 112 mm x 51 mm (4.6″ x 4.4″ x 2.0″)
                  • 90W power adapter
                  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
                    Do you have another power supply you can try on the RPi? Just in case the 5 volts is sagging and the SmartStick is resetting.

                    Comment


                    • #11
                      All I have currently are 2.1A Apple 12W chargers. I also have the 2.1A original supply that came with the ZeeS2 which I haven't tried it yet.

                      The supply the Z-NET is currently connected to is a AC receptacle with built in USB which I think was 4.8A although that could be two 2.4A outputs.

                      Push comes to shove I can run over to MicroCenter and get a 3A supply.

                      Darn, I sure wish I still had access to a Spectrum Analyzer, scope and other test equipment so I could really see what's going on.

                      Can you sent me your latest ser2net build and I build up another RPi and try it. You have my e-mail address.
                      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
                        My last communication from support was that they haven't actually tested the SS+ on a Z-NET so they don't know if it works or not. I must admin I was totally surprised by that answer.

                        I don't feel I have a power issue as I've tried multiple supplied from 2.1 to 4.8A.

                        I tend to agree that it's a timing issue but how do we prove that and is there anything we can do to compensate for it if it is?

                        BTW, isn't there some other commands that cause a disconnect/reconnect? Thinking back I believe I'm seen another function that has caused the SS+ to drop out and a simple enable/disable brought it back.
                        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


                        • #13
                          If its not too late, consider exchanging the SmartStick for another, to rule out a bad unit.

                          If you can setup HS3 on a slower CPU, such as a Raspberry Pi, you could rule out if your main system is responding too fast, indicating a timing issue. Though getting HomeSeer to do anything about it could be a challenge.

                          Comment


                          • #14
                            Setting up another Pi would have to be from the ground up since my current configuration is too large and for swamp a Pi. Since I now have some old Evolve I could use I could make a board that would be something like that HS has used in their videos. However I think I'm short one Pi to do this but heck with the Pi 4 out Pi3B are a bit cheeper at some places.

                            I've not done any testing in the last couple weeks as I'm in the process of installing the 15 WD200 I received. I've got 4 more to install plus a outdoor motion detector and one more internal one. We also have all new front yard landscaping being put in and a few other things that I have to keep track of. I'm also deciding if I'm going to connect the Irrigation system to HS3 and what to use if I do. Hoping to get back to another big test with your version of ser2net in a couple weeks. As long as I can restore directly from the NUC I can always get back up. I will say I do like the NUC. Being only 4x4x3 it's quite small although the power brick kinda negates that a bit. Still if your running headless you can hide it almost anyplace you can put a Pi in one of the VESA cases.

                            Sometime I need to set down and see just how ser2net works. What might be interesting is to fire up WireShark and watch the traffic between HS3 and the Z-NET. It requires a bet of network setup so my switched forward traffic from the NUC or the Z-NET to the port my computer is on but that's not too hard. Since everything tracked is timestamped hopefully the problem might be found if it's timing. Still don't know just what we could do other than report to HS.

                            All that said, it seems to me that HS is going to be forced to test this due to the new UZBs no longer restoring under HS3 because of firmware changes. I see HS having two choices.
                            • Updating HS3 to be able to work with the upgraded UZB.
                            • Releasing a EU version of the SS+, so they would have to get all SS+'s working, which allows them to sell it instead of the UZB.
                            I suspect they would rather do the latter so they don't have to stock and sell UZBs and could sell SS+ instead.

                            None of this would have been an issue if HS would just sell a customer a EZZee board when the customers breaks. Matt is asking again if they will and will let me know. Heck I'll even buy another Z-NET since I'm going to need one toward the back of the house and one near the front so I can better cover the house, stuff up front that is basically outdoors and stuff in the back which is also basically outdoors.

                            The one part of HS3 that I wish that HS would open source are the protocol plugins like Z-Wave. That way the Z-Wave plugin would get updates for new devices more quickly than they do now which unloads HS to work on new features. Also when issues like this crop up they could be fixed much more quickly as HS doesn't have to redirect resources to it other than QCing the update.
                            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