Announcement

Collapse
No announcement yet.

Upgraded to 435 nox HSTouch clients not connecting - Suggestions?

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

    Upgraded to 435 nox HSTouch clients not connecting - Suggestions?

    Hi,

    Took the option to upgrade to v435 from 381 this morning. Now android HSTouch clients cannot connect. It took several reboots for HSTouch designer to connect, but now that works fine. Clients are connecting through MyHS.

    Current Date/Time: 5/16/2018 1:20:37 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.435
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 0 Days 0 Hours 7 Minutes 21 Seconds
    IP Address: 192.168.1.122
    Number of Devices: 242
    Number of Events: 121
    Available Threads: 400
    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: Windows Defender

    Enabled Plug-Ins
    2.0.54.0: BLBackup
    2.0.26.0: BLRing
    3.0.6.34: Insteon
    3.0.2.215: Z-Wave

    Initially thought it may be due to the Z-Wave plug-in update, rolled backe to 206 from 215 and no difference.

    I have recreated the user account on the server, re-entered login info on clients, uninstalled and re-installed android clients, all to no avail.

    Did a setting change with 435 that I have missed configuring?

    Many thanks,

    Steve

    #2
    Did the credentials in your android device change. Make sure they are set exactly as your server allows. If that doesn't work just uninstall and reinstall your android HSTouch

    Comment


      #3
      Resolved

      Not really sure what the core issue was. I connected from each client via the MyHS service on homeseer.com, thus proving no port issues. Deleted all the clients and the user account in HSTouch and started from scratch.

      All working now.

      Most frustrating that it broke in the first place.

      Thanks for all of the suggestioins and those I gleanded from many other threads.

      Steve

      Comment


        #4
        Sounds like your sign on credentials in your server reverted to default after your upgrade. Does happen sometimes. It's resolved now so that's a result.

        Comment

        Working...
        X