Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

RTH9585WF model thermostat

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

  • shill
    replied
    Glad to hear that!

    Leave a comment:


  • E.S.Buckeye
    replied
    Click image for larger version

Name:	screenshot.jpg
Views:	1
Size:	69.7 KB
ID:	1197077

    Success

    Leave a comment:


  • E.S.Buckeye
    replied
    I'll try a reinstall of Mono and let you know.

    Thanks!

    E.S.

    Leave a comment:


  • shill
    replied
    Originally posted by E.S.Buckeye View Post
    But I'm running Mono 5.4.1
    Oops! You're right - the issue I had this weekend was someone running Mono 4.5.1, so my brain just went a bit dyslexic on me, I guess.

    The additional logging I put in did the trick, though - upon further examination, this is your issue:

    System.IO.FileNotFoundException: Could not load file or assembly 'System.Xml.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.

    Your system is missing the System.Xml.Linq assembly, distributed with mono 5.4 via libmono-system-xml-linq4.0-cil, I think. On my mono 5.X system I ended up just doing mono-complete because I ran into this and several other missing DLLs.

    Leave a comment:


  • E.S.Buckeye
    replied
    But I'm running Mono 5.4.1

    Leave a comment:


  • shill
    replied
    Aha... I was just dealing with a similar issue over email with another user, and found a defect in my logging that's supposed to warn you that you're not running a supported version of Mono.

    6/10/2018 16:32:34.929 Info [------] PluginLogic.InitIO Running on Linux Version 3.16.0.31600 using Mono version 5.4.1

    This should cause the plugin to throw a "FATAL" error and indicate the issue on the plugin status page.

    Because Honeywell requires HTTPS connections using TLS 1.2 for security reasons, and because Mono doesn't support TLS 1.2 until version 4.8, this plugin requires at least that level of mono.

    While I have some instructions in the sticky post above (LINUX/ZEE USERS: MONO 4.8 OR HIGHER IS REQUIRED!!), from my experience this weekend it seems HS has distributed Mono 4.5.1 in an unusual way on the Zee devices, so my advice is to contact them and ask about how you get an updated version on Mono that supports TLS 1.2 installed.

    Leave a comment:


  • E.S.Buckeye
    replied
    HSPI_SKWARE_HW_WIFI_TSTAT-3.txt

    This is the new Trace file. Took me a few days to get to this sorry.

    Leave a comment:


  • shill
    replied
    Originally posted by E.S.Buckeye View Post
    OK one last thing... do you know the correct path for the install. I can probably figure it out but having the path would help.

    E.S.
    Plugins just go in the root directory of hs3.

    Leave a comment:


  • E.S.Buckeye
    replied
    OK one last thing... do you know the correct path for the install. I can probably figure it out but having the path would help.

    E.S.

    Leave a comment:


  • shill
    replied
    That exe is the plugin, the same file that's downloaded a you install it from the updater (minus all the supporting files). HomeSeer on Linux leverages mono to run .NET applications.

    And you don't need to run it, just replace the existing file with this new one.

    Leave a comment:


  • E.S.Buckeye
    replied

    Leave a comment:


  • shill
    replied
    Originally posted by E.S.Buckeye View Post
    I am sure we can figure out a way to transfer a file and I have direct access to the server here ... if I understand your question.
    Ok, I've added some more logging and additional error handling. Let's see what this tells us...
    • Stop the plugin
    • Delete any devices it created
    • Download this file: https://skware1.blob.core.windows.ne..._EXE_1_3_3.zip
    • Unzip the file and put the new EXE in your HS3 directory on the server
    • Start the plugin
    • Set the plugin log file to Trace
    • Add your thermostat and click "Save Settings"
    • Wait 2 minutes
    • Set the plugin log file back to Info and click "Save Settings"
    • Download the log file and send it to me


    Thanks for your patience!

    Leave a comment:


  • E.S.Buckeye
    replied
    I am sure we can figure out a way to transfer a file and I have direct access to the server here ... if I understand your question.

    Leave a comment:


  • shill
    replied
    Thanks! I see now what's going on much more clearly - it's getting to the point where it's supposed to embed the details about the thermostat in the root thermostat device and then nothing happens... no error is thrown, nothing gets written to the log file, it just goes into the "PEDAdd" function and then stops.

    My guess is if you looked at your HomeSeer log for when this happened last (6/1/2018 11:05:54) you'd see an error there that HomeSeer had with the plugin but that didn't show up within the plugin itself. I will add some additional logging to that particular method and provide an updated plugin file testing later tonight.

    Are you able to copy files onto the server? Using FTP, WinSCP, an SSH client like MobaXterm, or using Samba (or any other method)?

    Leave a comment:


  • E.S.Buckeye
    replied
    HSPI_SKWARE_HW_WIFI_TSTAT (3).txt

    There's the log file as .txt

    E.S.

    Leave a comment:

Working...
X