Announcement

Collapse
No announcement yet.

ISY Insteon 1.0.2.6 and 1.0.2.14

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

    ISY Insteon 1.0.2.6 and 1.0.2.14

    This is a version 1.0.2.14 of the ISY Insteon Plug-in.

    This is being released as an installation package that will update an existing installation of the plug-in to this version. It will re-use the your existing license key.

    Version 1.0.2.10 and later change how commands to the ISY are processed. Commands to the ISY (device/scene/program commands) are queued and then sent to the ISY in sequence from the queue. This allows the plug-in to return control back to HomeSeer immediately. The code at the communication level is the same, it is just the queuing mechanism that is new. I believe this provides a more reliable mechanism and also makes it possible to monitor the command backlog. The status page has been enhanced to show the current number of commands waiting to processes and the current number of incoming messages from the ISY that are waiting to be processed.

    Version 1.0.2.14 has been tested to work with ISY Firmware up to and including 2.8.10.


    Installation
    1. Download the ISYInsteion-1.0.2.14.zip file
    2. Unzip the contents
    3. shutdown HomeSeer
    4. Run HomeSeerPluginISYInsteon_1_0_0.msi
    5. Restart HomeSeer

    Updates since 1.0.2.5
    - Changes to the network communication layer to provide better error reporting.
    - Fixed a bug in the program conditions. They would only detect if a program was in the state true or false and ignore programs in the states "running true" or "running false". Now "running true" and "true" are considered true. "running false" and "false" are considered false.
    - The Thermostat API now only reports the main thermostat device. The secondary (heat/cool/fan) thermostat devices are ignored by the API functions.
    - When creating the HomeSeer records for a thermostat, the secondary devices are now treated as generic on/off sensors instead of thermostats. This doesn't effect existing installed thermostat devices.
    - A log message that reported execution of program command was changed to output the full program name instead of the program ID.

    Updates since 1.0.2.6
    - Command queuing mechanism described above
    - Enhanced the device trigger drop down selection boxes to display the full device name (name + path/folder info).
    - Added a configuration option to set the HomeSeer device location and/or location 2 fields to a user defined text string. This string is applied to all device records owned by the ISYInsteon plug-in.

    Updates since 1.0.2.7
    - Changed the custom device types, defined by the plug-in, to all be prefixed with "ISY " so they won't conflict with other standard or custom device types. To update your current ISYInsteon defined device types, use the "Update Device Types" button on the configuration screen.
    - Added some debugging messages around group (scene) import from ISY.

    Updates since 1.0.2.8
    - Fixed bug where newly created scenes are not imported into the plug-in. This likely effects any scenes created using ISY firmware 2.8.0 or later.

    Updates since 1.0.2.9
    - Fixed a bug where scenes created by the latest ISY firmware cannot be controlled.

    Updates since 1.0.2.10
    - Fixed a bug that would cause the plug-in to go into an infinite loop if communication with the ISY is lost.

    Updates since 1.0.2.11
    - Added conditional trigger support for scenes.
    - Added basic support for iMeterSolo energy monitoring devices from SmartHome.
    - Changed all device types generated by the ISYInsteon plug-in to be prefixed with "ISY" so that they don't conflict with generic device types or device types created by other plug-ins.

    Updates since 1.0.2.12
    - Fixed a bug in the command queue, if communication with the ISY was disrupted and a program command was sent, the plug-in would crash.
    - Changed device drop downs in conditional triggers to include the device location along with the device name.
    - Added a new log level called "Status". This is slotted in between Warnings and Notices. It logs device status changes along with Errors and Warnings. Note: if you were using log levels Notice or above, you'll have manually reset your log level.

    Updates since 1.0.2.13
    - Updated to work with ISY firmware 2.8.10.
    - Added additional support for iMeter-Solo devices. This is still a work in progress.
    Attached Files
    Last edited by bpwwer; December 27, 2010, 06:27 PM.
    --
    Bob Paauwe
    ISYInsteon Plug-in
    http://www.bobsplace.com/ISYInsteon/

    #2
    Thanks Bob! I tried 26 last night and then updated to 27 this morning. . . neither one shows any problems in the log, and there are no SEND LOCK errors in my log. Let me know what to watch for in the logs and if I have any problems, I'll send the logs your way. If you want my logs anyway, even without errors, PM me and let me know.

    Thanks,

    Tim

    Comment


      #3
      Originally posted by timlacey View Post
      Thanks Bob! I tried 26 last night and then updated to 27 this morning. . . neither one shows any problems in the log, and there are no SEND LOCK errors in my log. Let me know what to watch for in the logs and if I have any problems, I'll send the logs your way. If you want my logs anyway, even without errors, PM me and let me know.

      Thanks,

      Tim
      Tim,

      With 2.7 the locking was removed so you can't get "send lock" errors anymore. All the other "network communication failures" errors are still applicable so if you see any of those, something still might be wrong.

      Check the plug-in status page when one of your large whole house programs are running and see what the message queue and command queue look like, I'm curious about that.
      --
      Bob Paauwe
      ISYInsteon Plug-in
      http://www.bobsplace.com/ISYInsteon/

      Comment


        #4
        No matter what I do, I can't get any errors to occur. My events that trigger on Running True are working great.

        I have searched my logs and not found one instance of the word "network".

        I have watched the plug-in status page and refreshed it during a massive clearing of my house over and over again. . . no problems, both backlog numbers show as zero. They might be more useful if they reflected the MAXIMUM value in the past 30 seconds or something, but there seems to be no problem with my machine keeping up.

        So I am giving the plug-in a clean bill of health and letting you know - I can't find anything wrong with it anywhere! Thanks!

        Tim

        Comment


          #5
          Hi Tim,

          Great news. I guess the combination of your clean up and my code changes solved it.

          I'm not sure if the message backlog number is working since I have not seen it change from 0. I did get the command backlog up to 74 in testing by running a script with 4 device and 4 program commands in a loop so I think I sent 80 commands all at once.

          I'll add the maximum values too. That might be interesting to see.

          Originally posted by timlacey View Post
          No matter what I do, I can't get any errors to occur. My events that trigger on Running True are working great.

          I have searched my logs and not found one instance of the word "network".

          I have watched the plug-in status page and refreshed it during a massive clearing of my house over and over again. . . no problems, both backlog numbers show as zero. They might be more useful if they reflected the MAXIMUM value in the past 30 seconds or something, but there seems to be no problem with my machine keeping up.

          So I am giving the plug-in a clean bill of health and letting you know - I can't find anything wrong with it anywhere! Thanks!

          Tim
          --
          Bob Paauwe
          ISYInsteon Plug-in
          http://www.bobsplace.com/ISYInsteon/

          Comment


            #6
            Bob,

            I'm running1.0.2.10 and 2.8.2 ISY Firmware and I'm getting the following errors. I was running ISY Firmware 2.8.4 but backed off thinking it was the culprit, to no avail.
            Attached Files
            -Todd

            ____________________________________________________________ ________________
            HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

            Comment


              #7
              Originally posted by tmcgowan View Post
              Bob,

              I'm running1.0.2.10 and 2.8.2 ISY Firmware and I'm getting the following errors. I was running ISY Firmware 2.8.4 but backed off thinking it was the culprit, to no avail.
              Hi Todd,

              First, you should update to 1.0.2.11. The communication error could have caused the plug-in's send thread to go into an infinite loop with 1.0.2.10.

              Is the network connection fail happening frequently? There's not really anything the plug-in can do about the network link. If it is happening frequently (like more than once a month), it indicates that you may have a network problem. That could be anything from the network interface on the ISY, on the HomeSeer PC, wiring, hub/switch, etc. Or possibly something that periodically hogs all your network bandwidth and blocks the ISY and plug-in from communicating.

              Are the other errors caused by the plug-in reporting bad WeatherBug data?

              If these are happening often enough, bump up the log level of the plug-in to verbose debug and capture send the relevant section of the log.

              You can also drop back down to plug-in 1.0.2.6 if the problems seemed to coincide with updating the plug-in.
              --
              Bob Paauwe
              ISYInsteon Plug-in
              http://www.bobsplace.com/ISYInsteon/

              Comment


                #8
                Hello Bob,

                1.0.2.11 did the trick! 18 hours up and running and no ISY related error messages.

                Thanks,

                Todd
                -Todd

                ____________________________________________________________ ________________
                HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

                Comment


                  #9
                  Well, that was short lived. Here's the error message I found on the HS server when I remote logged in:

                  10/26/2010 11:46:32 AM
                  Unable to connect to the remote server
                  HomeSeer version: 2.4.0.72
                  Source: System
                  Target: System.IO.Stream GetRequestStream(System.Net.TransportContext ByRef)
                  Stack trace:
                  at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
                  at System.Net.HttpWebRequest.GetRequestStream()
                  at HSPI_ISYINSTEON.isy.SOAPRequest(String service, String args)
                  at HSPI_ISYINSTEON.isy.ProcessCommand(Object sender, isyCmdArgs cmd)
                  at HSPI_ISYINSTEON.CommandQueue.QueueLoop()
                  at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
                  at System.Threading.ExecutionContext.runTryCode(Object userData)
                  at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWi thGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
                  at System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state)
                  at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
                  at System.Threading.ThreadHelper.ThreadStart()

                  Please specify what you were doing at the time of this error:
                  --------------------------

                  Any ideas as to what went wrong?
                  -Todd

                  ____________________________________________________________ ________________
                  HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

                  Comment


                    #10
                    All is working well for me. no mention of "network" in my log. . . .hopefully this reply won't jinx it.

                    Comment


                      #11
                      I think there might by a network bandwidth problem. I have my security camera server ftping images set to 1 second intervals and that's creating a bottleneck even through a 1ghz Linksys switch.

                      I've backed the ftp rate down and that seems to have significantly freed-up the pipe.

                      I hope so, anyway!
                      -Todd

                      ____________________________________________________________ ________________
                      HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

                      Comment


                        #12
                        Originally posted by tmcgowan View Post
                        I think there might by a network bandwidth problem. I have my security camera server ftping images set to 1 second intervals and that's creating a bottleneck even through a 1ghz Linksys switch.

                        I've backed the ftp rate down and that seems to have significantly freed-up the pipe.

                        I hope so, anyway!
                        The exception you posted before is still a bug in the plug-in. It should trap that and possibly re-try the send. I've added it to the bug list.
                        --
                        Bob Paauwe
                        ISYInsteon Plug-in
                        http://www.bobsplace.com/ISYInsteon/

                        Comment


                          #13
                          Hello Bob,

                          I'm running version 1.0.2.11 and firmware version 2.8.5, but I'm getting the following errors showing up in my log. Any suggestions?
                          Attached Files
                          -Todd

                          ____________________________________________________________ ________________
                          HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

                          Comment


                            #14
                            Originally posted by tmcgowan View Post
                            Hello Bob,

                            I'm running version 1.0.2.11 and firmware version 2.8.5, but I'm getting the following errors showing up in my log. Any suggestions?
                            Todd,

                            I can go through what I think is happening, but without more information, I don't know why.

                            It looks like HomeSeer is calling the plug-in to turn on device '87 because it thinks the plug-in owns that device.

                            The plug-in looks up the ISY device address from a private data structure and gets 6187 back. That looks like a scene device address.

                            The plug-in then looks up the address (6187) in the list of devices that was retrieved from the ISY when the plug-in started. In your, log this fails, not enough info to know why.

                            The plug-in tries to send the command anyway by sending a command to the ISY to turn on device 6187, but the ISY responds with an error.


                            Questions:

                            Does the ISY have a scene with address 6187 that corresponds to the HomeSeer device?

                            Does the address show up in the list of devices on the Plug-in's configuration screen?

                            What type of device is '87 suppose to be?
                            --
                            Bob Paauwe
                            ISYInsteon Plug-in
                            http://www.bobsplace.com/ISYInsteon/

                            Comment


                              #15
                              Hello Bob, here are my responses to your questions:

                              Does the ISY have a scene with address 6187 that corresponds to the HomeSeer device?

                              Response: Not that I can see. I looked in the ISY Scenes tab as well as the ISY Programs tab and the only thing that seems applicable is my ISY Program to Query All modules every 15 minutes. I cannot find a reference number anywhere in the ISY99i screens. Is there some other place I can find it?

                              Does the address show up in the list of devices on the Plug-in's configuration screen?

                              Response: Yes. The exact module name shows up in my HS Device List, ISY Plug-in Configuration Screen and within the ISY99i Device listing. I have no problem turning the module on or off directly from the ISY99i Device (or Admin) screens. However, it's spotty when I try to control it from the HS Device Screen.

                              One thing I should mention is that about a month ago I did rename the module (from within HS) to the name that shows up in my previous post. Since the name also appears the same from within the ISY99i Device Screen, I assume that the two synched by properly. I haven't had time to try to delete the device from the ISY99i screen and re-add it, but I may try that this evening when I get home.

                              What type of device is '87 suppose to be?
                              Response: The module is a 2456S3E Outdoor (Relay) Plugin Module. It shows up in the ISY Plug-in as an "ISY Relay". The device has been functioning fine with no problems activating it either locally (using the little square button next to the controlled plug outlet) and using the ISY99i Device/Admin Screens.
                              -Todd

                              ____________________________________________________________ ________________
                              HS2Pro: 2.5.0.81 :: HS3Pro (beta) || Plugins:| SmartHome PowerLinc USB, Global Cache, BLBackup, DooCPU Monitor, DooMotion, BLOutlook, BLIcon, BLOutgoingCalls, OutgoingCalls, ROC-Rnd, HSTouch iPhone, UPS Monitor, DooMenuBar, BLSpeech, HSTouch Server, WAF AB8SS, mcsTemperature, VWS, BLChart, RFXCOM, ISY Insteon, iAutomate RFID, iTunes, NetCAM, DSC Security, Nest

                              Comment

                              Working...
                              X