Announcement

Collapse
No announcement yet.

Z-wave error message: "Optimization was not executed as the node cannot be reached"

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

  • Z-wave error message: "Optimization was not executed as the node cannot be reached"

    While trying a Z-wave network optimization, I received several of these messages.
    "Optimization was not executed as the node cannot be reached"

    It's puzzling since not only is the device actually reachable from my web Devices control page, but also just fine via Google Home.
    Does anyone know what this message actually means, and is it a concern?


    Thanks
    Steve

    Current Date/Time: 1/22/2019 10:30:18 AM
    HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.475
    Linux version: Linux HomeTrollerZeeS2V5 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux System Uptime: 3 Days 16 Hours 13 Minutes 57 Seconds
    IP Address: 192.168.15.10
    Number of Devices: 218
    Number of Events: 196
    Available Threads: 398
    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.5: CM15A
    3.0.0.54: EasyTrigger
    3.0.0.18: EnvCan
    3.0.1.249: Z-Wave

  • #2
    How did you resolve this? I have the same issue.
    Mark

    Hometroller S6 w/ HS3Pro, Way2Call
    BLAB8SS, BL Backup, Easy Trigger, HSTouch, Open Sprinkler, SONOS, Ultra1Wire3, UltraM1G, WeatherXML, Z-Wave

    Comment


    • #3
      Originally posted by Mark S. View Post
      How did you resolve this? I have the same issue.
      While doing a full network optimization, Homeseer will try to communicate with every Z-Wave device, including the battery powered devices. Battery powered devices have to be manually woken up in order to optimize them. When you first add the battery device is the best time to optimize. Once added, you shouldn’t need to optimize again, unless you’ve added more powered z-wave devices since. In that case, you would need to manually wake each battery powered device and optimize individually.


      Sent from my iPad using Tapatalk
      HS3 3.0.0.500 &HSTouch Designer 3.0.71 with 782 Devices, 479 Events
      Plugin's:
      BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee,
      EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
      weatherXML, Jon00 Alexa Helper, Network Monitor, Z-Wave 3.0.1.252

      Comment


      • #4
        It turns out that my issue was fixed by reinstalling the Z-Stick+ driver and changing the COM port. I'm assuming something got corrupted - file corruption has been all too common in my experience with HS.
        Mark

        Hometroller S6 w/ HS3Pro, Way2Call
        BLAB8SS, BL Backup, Easy Trigger, HSTouch, Open Sprinkler, SONOS, Ultra1Wire3, UltraM1G, WeatherXML, Z-Wave

        Comment

        Working...
        X