Announcement

Collapse
No announcement yet.

No connection/data transfer with eagle 200 using HS3 Zee S2

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

    No connection/data transfer with eagle 200 using HS3 Zee S2

    Spud, I cannot connect your app to my Rainforest Eagle 200. It sets up the 5 items in my list. But they do not connect and report. Yes I went to config, selected eagle-200, put in my email address for my rainforest cloud login and my password for the same account. I also logged to that cloud account with the same credentials and read the eagle data just fine.
    So I then removed and replaced the plug-in and deleted the 5 lines in between. The plug in again created the 5 lines but still no data.
    What do I need to do next?
    I am currently running HS# ZEE S2 using an aeotec gen 5 z-stick, Rock Pi4 and running on Debian 9.
    It also did not work running on the original raspberry pi running Raspbian.
    Current Date/Time: 2/16/2020 5:55:18 PM
    HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.548
    Linux version: Linux linaro-alip 4.4.154-90-rockchip-ga14f6502e045 #22 SMP Tue Jul 30 10:32:28 UTC 2019 aarch64 GNU/Linux System Uptime: 0 Days 0 Hours 3 Minutes 24 Seconds
    IP Address: 127.0.0.1
    Number of Devices: 156
    Number of Events: 45
    Available Threads: 591
    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

    Enabled Plug-Ins
    3.0.0.31: EnvisaLinkAdemco
    3.0.0.8: RainforestEagle
    3.0.2.234: Z-Wave

    #2
    Please set the log level to debug, and post what you get in the logs when the plugin tries to poll for data (wait at least 5minutes for this to happen)

    Also what is your mono version

    Code:
    sudo mono --version

    Comment


      #3
      My System is now running on a RockPi4A running 4Gb using Debian9.
      I added mono using the Homeseer instructions for installing on a pi.

      linaro@linaro-alip:~$ mono --version
      Mono JIT compiler version 4.6.2 (Debian 4.6.2.7+dfsg-1)
      Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
      TLS: __thread
      SIGSEGV: normal
      Notifications: epoll
      Architecture: arm64
      Disabled: none
      Misc: softdebug
      LLVM: supported, not enabled.
      GC: sgen
      linaro@linaro-alip:~$
      Below is the last entry in RainforestEagle.txt

      Feb-28 20:25:52 ERROR System.Net.WebException: Error: SecureChannelFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: Error while sending TLS Alert (Fatal:InternalError): System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer
      at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult result) [0x00033] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.Net.Sockets.NetworkStream.EndRead (System.IAsyncResult asyncResult) [0x0005f] in <bd46d4d4f7964dfa9beea098499ab597>:0
      --- End of inner exception stack trace ---
      at Mono.Security.Protocol.Tls.RecordProtocol.EndReceiveRecord (System.IAsyncResult asyncResult) [0x00040] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.SslClientStream.SafeEndReceiveRec ord (System.IAsyncResult ar, System.Boolean ignoreEmpty) [0x00000] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.SslClientStream.NegotiateAsyncWor ker (System.IAsyncResult result) [0x00071] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      --- End of inner exception stack trace ---
      at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHands hake (System.IAsyncResult result) [0x0003b] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallb ack (System.IAsyncResult asyncResult) [0x0000c] in <1d0bb82c94e7435eb09324cf5ef20e36>:0 ---> System.IO.IOException: Unable to write data to the transport connection: The socket is not connected. ---> System.Net.Sockets.SocketException: The socket is not connected
      at System.Net.Sockets.Socket.BeginSend (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socket_flags, System.AsyncCallback callback, System.Object state) [0x0002b] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.Net.Sockets.NetworkStream.BeginWrite (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.AsyncCallback callback, System.Object state) [0x000b4] in <bd46d4d4f7964dfa9beea098499ab597>:0
      --- End of inner exception stack trace ---
      at System.Net.Sockets.NetworkStream.BeginWrite (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.AsyncCallback callback, System.Object state) [0x00113] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at Mono.Security.Protocol.Tls.RecordProtocol.BeginSendRecord (Mono.Security.Protocol.Tls.ContentType contentType, System.Byte[] recordData, System.AsyncCallback callback, System.Object state) [0x00026] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.RecordProtocol.SendRecord (Mono.Security.Protocol.Tls.ContentType contentType, System.Byte[] recordData) [0x00000] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.RecordProtocol.SendAlert (Mono.Security.Protocol.Tls.Alert alert) [0x00027] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Security.Protocol.Tls.RecordProtocol.SendAlert (System.Exception& ex) [0x00021] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      --- End of inner exception stack trace ---
      --- End of inner exception stack trace ---
      at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (System.IAsyncResult asyncResult) [0x00057] in <1d0bb82c94e7435eb09324cf5ef20e36>:0
      at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsC lient (System.IAsyncResult asyncResult) [0x00011] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsClie nt (System.String targetHost, System.Security.Cryptography.X509Certificates.X509Certificat eCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000e] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x00044] in <bd46d4d4f7964dfa9beea098499ab597>:0
      --- End of inner exception stack trace ---
      at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at HSPI_RainforestEagle.Eagle200Gateway.SendCommand (System.String path) [0x00084] in <8705cc46dee94a63a3092ceb1211e016>:0

      Comment


        #4
        Rainforest server requires TLS 1.2, and it's only supported in mono version 4.8 or later. So you need to upgrade mono

        Comment


          #5
          That was it. Debian9 was stuck on 4.6.2. I went to the Mono site and cut and pasted their instructions and rebooted twice to get everything working. Thank you.
          Robert

          Comment

          Working...
          X