Announcement

Collapse
No announcement yet.

Z-NET crashes during Optimize

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

    Z-NET crashes during Optimize

    Greetings, HomeSeer Enthusiasts.

    I have two Z-NET controllers (primary/secondary) covering a 50+ node network. During basic optimization (no route changes), the second Z-NET crashes (i.e., HS3 loses contact) consistently in the process at one node (a normally functioning Leviton dimmer). I have tried restarting HS3 and the Z-NETs, to no avail. This is on HS3 3.0.0.368 (Linux) with Z-Wave 3.0.1.152, Z-NETs are 1.0.23.

    Take a look at the abridged log output:

    11:13:50:2024:Starting Z-Wave node neighbor update for all Z-Wave devices...
    11:13:50:4451evice Basement IT Room Z-NET-MainHouse1 (1) will not be optimized because it is a HomeSeer controller.
    11:13:50:4483evice Second Floor Family Room Z-NET-MainHouse2 (33) will not be optimized because it is a HomeSeer controller.
    11:13:50:4504evice First Floor Dining Room Motion (62) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
    11:13:50:5835:Optimize complete wait time is 2:59
    11:13:50:5842:There are approximately 51 nodes to optimize.
    11:13:50:5851:Optimizing node 2 (Basement Gym Ceiling1)...
    11:14:17:6481one.
    11:14:17:6632:------------------------------------------------------
    ...
    11:22:53:6719:Optimizing node 18 (Second Floor Family Room Ceiling)...
    11:23:01:6738one. The optimization was not executed as the node cannot be reached.
    11:23:01:6745:------------------------------------------------------
    11:23:01:6755:Z-NET-MainHouse2: Exception transmitting to IP 10.0.3.107: Unable to write data to the transport connection: The socket has been shut down.
    11:23:01:6762:Optimizing node 19 (Second Floor Bathroom2 Ceiling)...
    11:23:01:6778:Z-NET-MainHouse2: Z-Wave Ethernet at IP 10.0.3.107, connected to interface ok.
    11:23:01:9283:Z-NET-MainHouse2: Getting node information from controller...
    11:23:06:7922:Z-NET-MainHouse2: Controller Manufacturer: Express Controls, ID=0x2, Type=0x5
    11:23:06:7929:Z-NET-MainHouse2: Controller firmware version: 4.32
    11:23:07:3145:Z-NET-MainHouse2: Z-Wave Serial API version: 5
    11:23:07:3152:Z-NET-MainHouse2: Z-Wave interface node ID: 33, Home ID: CD3B26D6
    11:23:07:3166:Z-NET-MainHouse2: Found 54 Z-Wave nodes in interface node ID 33 (Z-NET-MainHouse2)
    11:25:09:4571one.
    11:25:09:4575:------------------------------------------------------
    11:25:09:4578:Z-Wave Optimization of the entire network was aborted early.


    I'd like to understand what's going on with the Z-NET when this happens. Are there log files I can tail there?

    Thanks, JD

    #2
    P.S: As recommended elsewhere, I updated the timeout for port 2001 in /etc/ser2net.conf (from 60 to 120 seconds), but this had no apparent benefit.

    Comment


      #3
      Unfortunately there are no log files.

      The "socket has been shut down" message sort of smells like a timeout though. You might try temporarily disabling the timeout by changing that timeout field to 0. Make sure you reboot the znet after modifying the file.

      Comment

      Working...
      X