Announcement

Collapse
No announcement yet.

ISYInsteon 3.0.1.4 has expired

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

    #16
    Just to clarify - is it safe to upgrade to 3.0.1.4? The upgrader is saying it's available but I'm waiting until the "hourly expiration" problem is solved.

    Thanks.

    Comment


      #17
      Originally posted by jwshome2 View Post
      Just to clarify - is it safe to upgrade to 3.0.1.4? The upgrader is saying it's available but I'm waiting until the "hourly expiration" problem is solved.

      Thanks.
      Yes, this is the non-expiring version. I double and triple checked to make sure it was right. I still don't know how I ended up getting that version with the expiration turned on, I was trying to be very careful about turning on the expire code for only the beta versions.

      At this point, there won't be any more beta versions that expire, going forward any beta releases will be used to roll out new features and will require a license.
      --
      Bob Paauwe
      ISYInsteon Plug-in
      http://www.bobsplace.com/ISYInsteon/

      Comment


        #18
        Well it did not appear to change anything but it just did not connect.

        Sooo I noticed there is now 3.0.1.5 available so I loaded that.

        The status indicates it is not connecting to the ISY.

        The configuration display shows all the ISY settings are correct.

        The following are representative log entries...

        Jun-07 9:05:55 PM

        ISYInsteon
        Restart : ->
        Jun-07 9:05:55 PM

        ISYInsteon
        Restart : Last message received before restart
        Jun-07 9:05:55 PM

        ISYInsteon
        Bottom of subscription thread loop
        Jun-07 9:05:55 PM

        ISYInsteon
        Attemp to close TcpClient
        Jun-07 9:05:55 PM

        ISYInsteon
        Read exited with False
        Jun-07 9:05:55 PM

        ISYInsteon
        read : The subscription connection to ISY has failed.
        Jun-07 9:05:13 PM

        Comment


          #19
          Originally posted by Jim Kosloskey View Post
          Well it did not appear to change anything but it just did not connect.

          The status indicates it is not connecting to the ISY.

          The configuration display shows all the ISY settings are correct.

          The following are representative log entries...

          Jun-07 9:05:55 PM

          ISYInsteon
          Restart : ->
          Jun-07 9:05:55 PM

          ISYInsteon
          Restart : Last message received before restart
          Jun-07 9:05:55 PM

          ISYInsteon
          Bottom of subscription thread loop
          Jun-07 9:05:55 PM

          ISYInsteon
          Attemp to close TcpClient
          Jun-07 9:05:55 PM
          Typically, by the time it reports a problem with the subscription, most of the initialization with the ISY has already taken place.

          The subscription thread makes a connection to the ISY to receive status and other messages from the ISY. The ISY continually sends out message. This is roughly the same message you'll see in the ADMIN console's Event viewer when you set it to it's most verbose setting. If the plug-in doesn't see anything from the ISY, it closes the connection and then reopens it. There's nothing the plug-in can do to force the ISY to send the information.

          Can you set the plug-in's log level to "Notice", restart the plug-in and capture the log from the point where it was restarted to when you start getting these failures? It seems like if this is failing, much of the other initialization should be failing too. You can either attach the log here or send it to bpaauwe at yahoo dot com.
          --
          Bob Paauwe
          ISYInsteon Plug-in
          http://www.bobsplace.com/ISYInsteon/

          Comment

          Working...
          X