Announcement

Collapse
No announcement yet.

My Zee S2 lost it's Z-Wave

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

    My Zee S2 lost it's Z-Wave

    Yesterday I did a "Fully Optimize Network" on my Zee S2. Shortly after that I could no longer control any Z-Wave devices. What I got I was getting the dreaded "This network has no active interfaces enabled for it...." message in the Z-Wave Network and Options section. Reboots didn't help at all.

    After much messing around I finally clicked on the error icon, I didn't realize it was a button and not just a status indicator, for the Z-Wave Internal entry and the Z-Wave device popped back up however I still couldn't communicate with any Z-Wave devices.

    After more messing around including several power shutdowns and restarts I was able to briefly able to communicate with a few of devices at least to the point that it saw them.

    I was also able to get a Z-Wave interface and HS3 backup since my last one was about 4 days old and I've added several devices during that time. I'm just hoping that the Z-Wave backup is good.

    I'm coming to the conclusion that the Z-Wave controller in the Zee may have partly failed at least at the radio level but I'm not ruling out a software failure. The reason I think that is I've seem messages come in from battery devices. Here is an example, read from last to first.

    Oct-30 5:33:22 AM Z-Wave Internal: Z-Wave Wake-Up 'No More Info' Notification sent to Node 34(Sensors Furnace Room Aeon Labs Notification Sensor).
    Oct-30 5:33:21 AM Z-Wave Internal: Device (Node 34) woke up and Poll Device for Sensors Furnace Room Access Control Notification was successfully sent.
    Oct-30 5:33:18 AM Z-Wave Internal: Wake-Up Notification Processing for Node 34 (Sensors Furnace Room Aeon Labs Notification Sensor)
    Oct-30 5:33:18 AM Z-Wave Internal: Z-Wave Wake-Up Notification Received for Node 34
    So that seems to point to a partial failure and that at least the Z-Wave receiver is still working.

    I've put in a support ticket to see where we can go from here. At least my Zee is only about 6 months old so it's still under warranty.

    If anyone has any other ideas I'm open while I'm waiting for HS to contact me back.
    Last edited by Timon; October 30, 2017, 08:31 AM.
    HomeSeer Version: HS3 Standard Edition 3.0.0.548
    Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    Number of Devices: 484 | Number of Events: 776

    Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
    3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
    4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
    3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

    Z-Net version: 1.0.23 for Inclusion Nodes
    SmartStick+: 6.04 (ZDK 6.81.3) on Server

    #2
    Originally posted by Timon View Post
    Yesterday I did a "Fully Optimize Network" on my Zee S2. Shortly after that I could no longer control any Z-Wave devices. What I got I was getting the dreaded "This network has no active interfaces enabled for it...." message in the Z-Wave Network and Options section. Reboots didn't help at all.

    After much messing around I finally clicked on the error icon, I didn't realize it was a button and not just a status indicator, for the Z-Wave Internal entry and the Z-Wave device popped back up however I still couldn't communicate with any Z-Wave devices.

    After more messing around including several power shutdowns and restarts I was able to briefly able to communicate with a few of devices at least to the point that it saw them.

    I was also able to get a Z-Wave interface and HS3 backup since my last one was about 4 days old and I've added several devices during that time. I'm just hoping that the Z-Wave backup is good.

    I'm coming to the conclusion that the Z-Wave controller in the Zee may have partly failed at least at the radio level but I'm not ruling out a software failure. The reason I think that is I've seem messages come in from battery devices. Here is an example, read from last to first.



    So that seems to point to a partial failure and that at least the Z-Wave receiver is still working.

    I've put in a support ticket to see where we can go from here. At least my Zee is only about 6 months old so it's still under warranty.

    If anyone has any other ideas I'm open while I'm waiting for HS to contact me back.
    The first thing I would do is to pull a fresh backup off of the controller now, before I did anything else. The fresh backup will give you the ability to get back to where you are now in the event you need to replace the Z-Wave controller. These backups are text files. You can compare the one 4 days ago with the one now and see if things are missing -or- if it is complete including the new nodes. The files will look like this with the HomeID at the top followed by node information.
    Code:
    00BE4093
    1
    1,211,22,0,2,2,1
    2,211,156,1,4,17,1
    3,211,156,1,4,16,1
    4,103,229,232,3,2,4
    5,211,156,0,4,16,1
    6,146,150,0,2,17,0
    7,211,156,1,4,16,1
    8,211,156,0,4,16,1
    9,211,156,1,4,16,1
    10,211,156,1,4,17,1
    11,146,150,0,2,17,0
    12,211,156,1,4,17,1
    13,209,140,0,4,18,1
    14,211,156,1,4,16,1
    15,211,156,1,4,16,1
    16,211,156,0,4,16,1
    17,211,156,1,4,16,1
    18,211,156,1,4,16,1
    20,211,156,1,4,16,1
    21,211,156,1,4,17,1
    22,211,156,0,4,17,4
    23,211,156,1,4,16,1
    24,211,156,1,4,17,1
    25,211,156,1,4,16,1
    26,211,156,0,4,16,1
    28,211,156,1,4,33,1
    If the node information is there for nodes you cannot reach you could suspect the controller does have a radio problem.
    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

    Comment


      #3
      Originally posted by rprade View Post
      The first thing I would do is to pull a fresh backup off of the controller now, before I did anything else. The fresh backup will give you the ability to get back to where you are now in the event you need to replace the Z-Wave controller. These backups are text files. You can compare the one 4 days ago with the one now and see if things are missing -or- if it is complete including the new nodes. The files will look like this with the HomeID at the top followed by node information.
      Code:
      00BE4093
      1
      1,211,22,0,2,2,1
      2,211,156,1,4,17,1
      3,211,156,1,4,16,1
      4,103,229,232,3,2,4
      5,211,156,0,4,16,1
      6,146,150,0,2,17,0
      7,211,156,1,4,16,1
      8,211,156,0,4,16,1
      9,211,156,1,4,16,1
      10,211,156,1,4,17,1
      11,146,150,0,2,17,0
      12,211,156,1,4,17,1
      13,209,140,0,4,18,1
      14,211,156,1,4,16,1
      15,211,156,1,4,16,1
      16,211,156,0,4,16,1
      17,211,156,1,4,16,1
      18,211,156,1,4,16,1
      20,211,156,1,4,16,1
      21,211,156,1,4,17,1
      22,211,156,0,4,17,4
      23,211,156,1,4,16,1
      24,211,156,1,4,17,1
      25,211,156,1,4,16,1
      26,211,156,0,4,16,1
      28,211,156,1,4,33,1
      If the node information is there for nodes you cannot reach you could suspect the controller does have a radio problem.
      I already made the backups once the controller was back under HS control so I'm good to go there.

      Just did a comparison between the 4 day old and the new Z-Wave backup files. They match with the exception of the 6 new devices that were added over the last three days. So it looks like I'm good to go once the problem is solved.

      I'm wondering if HS will just send the Z-Wave card or a whole Zee S2. I've got other processes loaded on the Pi so I'll likely swap the SD card if they send a new Zee.

      I've seen messages coming in from HS dimmers when I manually change them so that's leaning more and more toward a bad Z-Wave transmitter especially since I can't change those same dimmers from HS3.
      HomeSeer Version: HS3 Standard Edition 3.0.0.548
      Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
      Number of Devices: 484 | Number of Events: 776

      Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
      3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
      4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
      3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

      Z-Net version: 1.0.23 for Inclusion Nodes
      SmartStick+: 6.04 (ZDK 6.81.3) on Server

      Comment


        #4
        Originally posted by Timon View Post
        I already made the backups once the controller was back under HS control so I'm good to go there.

        Just did a comparison between the 4 day old and the new Z-Wave backup files. They match with the exception of the 6 new devices that were added over the last three days. So it looks like I'm good to go once the problem is solved.

        I'm wondering if HS will just send the Z-Wave card or a whole Zee S2. I've got other processes loaded on the Pi so I'll likely swap the SD card if they send a new Zee.

        I've seen messages coming in from HS dimmers when I manually change them so that's leaning more and more toward a bad Z-Wave transmitter especially since I can't change those same dimmers from HS3.
        Swapping the SD card will work for everything but the Z-Wave network information (it is stored on the controller), so you will need to restore that from a backup and re-optimize. While the card is out, I would back it up using Win32DiskImager or similar.
        HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

        Comment


          #5
          Originally posted by rprade View Post
          Swapping the SD card will work for everything but the Z-Wave network information (it is stored on the controller), so you will need to restore that from a backup and re-optimize. While the card is out, I would back it up using Win32DiskImager or similar.
          Got it

          I've gotten the Zee basically working but it's far from being as stable as it was. I think something has happened to the internal Z-Wave interface which is making it unstable but not totally dead. I think I can limp along this way until HS figures out what the repair procedure will be.

          BTW, at this time if you reboot it's more likely than not the Z-Wave interface will not go online and you'll have to enable it by hand. Also, it can't access all of the nodes during a Full Optimization. All of this which points to a damaged Z-Wave interface.

          I can say right now that I'd like to see HS3 to do an automatic backup of both the Z-Wave and HS3 then e-mail the resulting zip file and/or send them to a dropbox or some other share service. That would make sure that backups are always getting done. I'd rather not see this as a plugin due to the loss of one when running on a Pi.
          HomeSeer Version: HS3 Standard Edition 3.0.0.548
          Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
          Number of Devices: 484 | Number of Events: 776

          Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
          3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
          4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
          3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

          Z-Net version: 1.0.23 for Inclusion Nodes
          SmartStick+: 6.04 (ZDK 6.81.3) on Server

          Comment


            #6
            Well, things are looking up. Matt has been a big help getting things working. Looks like the Internal Z-Wave interface may be just fine. Did a complete erase and reload, although I think I did something wrong and wiped out all of the connections between devices and nodes so I had to load my HS3 backup, and that cleaned a lot up.

            I was still having some problems so I took out my old Evolve LTM-5W single scene controllers and things really cleaned up. I'm suspecting that they were blocking or interfering with the transmissions. We'll run for a few days before we call everything good.

            Again, many thanks to Matt.

            [rant on]
            Boy, do I hate Evolve Controls. Some of their products just plain sucks. In fact it's worse than sucks. Every one of my LTM-5W has either died or is seriously malfunctioning and Evolve has never been any help.

            I used to get lots of dimmer lockups when I was running VeraLite and Evolve blamed it on the Vera. Now I get periodic lockups, not near as many, with HS3 and I suspect they would blame HS3. Don't ever deal with them. Over the next year I hope to replace all of them with WD-100+ dimmers.
            [/rant off]

            Note toHomeSeer: You really need to take a WD-100+ and turn them into scene devices much like but much better than the LTM-5's. Just take the WA-100 case and add the scene part of the WD-100+ without any of the dimmer controls. You can call it the WS-100+ and then price it between the WS-100+ and the WA-100+. Either that or a 5 button scene controller, similar to the Cooper one, but each button would have multi-tap just like the dimmers. I think you have a real seller with either of these.
            HomeSeer Version: HS3 Standard Edition 3.0.0.548
            Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
            Number of Devices: 484 | Number of Events: 776

            Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
            3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
            4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
            3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

            Z-Net version: 1.0.23 for Inclusion Nodes
            SmartStick+: 6.04 (ZDK 6.81.3) on Server

            Comment

            Working...
            X