Announcement

Collapse
No announcement yet.

ISY Insteon 1.0.4.26

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

    #31
    JB, Ed,

    Thanks for reporting that. My local copy of the zip file was corrupt so it wasn't anything with this forum. I recreated the zip file, uploaded it, downloaded it and checked it. Seems good now.
    --
    Bob Paauwe
    ISYInsteon Plug-in
    http://www.bobsplace.com/ISYInsteon/

    Comment


      #32
      Warnings from Brultech

      Hello,
      I thought I'd give the plug in another try.

      I have a 994 IR Pro with Zigbee for Brultech, and run two ECM 1240 Brultech modules.

      When I activate the plugin, I get a ton of warnings that don't seem to go away.

      I really don't care about importing Brultech data into HomeSeer; I just want HS to talk to the ISY for status and control.

      I get a TON of these....

      9/6/2013 11:38:43 AM - ISY Insteon - *WARNING* Trying to get device (ECM 0013A200 - Main 1) status with an invalid capability (1.


      Thanks!!!

      Travis

      Comment


        #33
        Hi Travis,

        Thanks for trying it again! I'm sorry it's not behaving well.

        Originally posted by thedishking View Post
        Hello,
        I thought I'd give the plug in another try.

        I have a 994 IR Pro with Zigbee for Brultech, and run two ECM 1240 Brultech modules.

        When I activate the plugin, I get a ton of warnings that don't seem to go away.

        I really don't care about importing Brultech data into HomeSeer; I just want HS to talk to the ISY for status and control.

        I get a TON of these....

        9/6/2013 11:38:43 AM - ISY Insteon - *WARNING* Trying to get device (ECM 0013A200 - Main 1) status with an invalid capability (1.
        That indicates I have an internal inconsistency in the plug-in so I'd like to track it down. I've looked through the code a bit and it looks like the ISY might be sending out different messages now for the Brultech module. I suspect that you are getting a warning every time the ISY reports data from the Brultechs and if so, yeah, that would be a ton of messages.

        It looks like the Brultech module device is getting treated like it was an iSolo energy device. I'd like to get some more information about your set up so I can track down what's happening and fix it.

        What is the plug-in reporting as the device type for ECM 0013A200 - Main 1?

        Are there other device nodes created for each ECM, for example is there an ECM 0013A200 - something else?

        Are you getting any status messages logged at the same time as the warnings?

        If you don't mind, could you increase the log level of plug-in to debug and post a section of the log surrounding one of the warnings?
        --
        Bob Paauwe
        ISYInsteon Plug-in
        http://www.bobsplace.com/ISYInsteon/

        Comment


          #34
          Hi Bob,

          Thanks for helping me fix this. I'd really like to get it functional.

          Here is a grab in debug mode:

          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:21 PM ISY Insteon EVNT: ECM 0013A200 - CH5 now set to 95800
          9/6/2013 1:11:21 PM ISY Insteon EVNT: SceneTracking Enabled: 0013A20040331C9C 5
          9/6/2013 1:11:21 PM ISY Insteon MAIN: Chk Trigger: ISY InsteonISY Device Update Trigger0013A20040331C9C 5Status
          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:21 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 5
          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:21 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:22 PM ISY Insteon COMM: Sending command []
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 2
          9/6/2013 1:11:26 PM ISY Insteon COMM: Parse failure: CV122300013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: ISY Heartbeat message.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: <<< meter type = 3 >>>
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: Parse fail: CV122300013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon COMM: Parse failure: CC36450013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: Parse fail: CC36450013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: ECM 0013A200 - Main 1 now set to 452400
          9/6/2013 1:11:26 PM ISY Insteon EVNT: SceneTracking Enabled: 0013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon MAIN: Chk Trigger: ISY InsteonISY Device Update Trigger0013A20040331C9C 1Status
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: ECM 0013A200 - CH5 now set to 95767
          9/6/2013 1:11:26 PM ISY Insteon EVNT: SceneTracking Enabled: 0013A20040331C9C 5
          9/6/2013 1:11:26 PM ISY Insteon MAIN: Chk Trigger: ISY InsteonISY Device Update Trigger0013A20040331C9C 5Status
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 5
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon *WARNING* Trying to get device (ECM 0013A200 - CH5) status with an invalid capability (1.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon EVNT: ECM 0013A200 - CH5 Total Power now at 32308
          9/6/2013 1:11:26 PM ISY Insteon *WARNING* Trying to use capability 1 to get ID for device ECM 0013A200 - CH5
          9/6/2013 1:11:26 PM ISY Insteon MAIN: Chk Trigger: ISY InsteonISY Energy Use Trigger0013A20040331C9C 5TPW**
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=0013A20040331C9C 5
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event added to queue. Queue size = 1
          9/6/2013 1:11:26 PM ISY Insteon COMM: NOT HANDLED: <<< meter type = 3 >>>
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event removed from queue. Queue size = 0
          9/6/2013 1:11:26 PM ISY Insteon EVNT: Event Queue is now empty.
          9/6/2013 1:11:26 PM ISY Insteon COMM: Parse failure: CV122000013A20040331BE2 1


          Thanks for your help, and I am willing to try whatever you recommend.

          Travis

          Comment


            #35
            Travis,

            Thanks for the log data, that helps a lot.

            It does look like the Brultech module is now reporting data differently than it did in the past.

            Previously, the ISY would report that the module was installed and then send messages from that module with the various power data.

            Now, it looks like the ISY is actually advertising each channel of each ECM device as an individual device node and sending power status. This is very similar to the iMeterSolo devices.

            The plug-in doesn't recognize this new device type from the ISY so it treats it as a generic device, but generic devices don't have power status so that's what's causing all the warnings.

            My assumption is that you have a number of devices listed in HomeSeer that have names something like:

            ECM 0013A200 - Main 1
            ECM 0013A200 - CH1
            ECM 0013A200 - CH2

            Is this right? And if so, if you go to the ISYInsteon plug-in configuration page, what does it show for the type and id of these devices?

            Once I figure out what the ISY is sending as a device type for these I can update the plug-in to recognize them and deal with the data being sent correctly.
            --
            Bob Paauwe
            ISYInsteon Plug-in
            http://www.bobsplace.com/ISYInsteon/

            Comment


              #36
              Hi Bob,

              Thanks for helping to get this ironed out.

              You are right on the money on how the ISY displays them.

              I have two Brultech ECM 1240 modules, each with 8 channels.

              Here is the data from HomeSeer:

              CH40013A20040331BE2 is the ID

              ISY Unknown is the Type.

              Name ID Type
              ECM 0013A200 - CH40013A20040331BE2 4ISY Unknown


              ECM 0013A200 - CH50013A20040331BE2 5ISY Unknown


              ECM 0013A200 - CH60013A20040331BE2 6ISY Unknown


              ECM 0013A200 - Main 20013A20040331BE2 1ISY Unknown


              ECM 0013A200 - CH20013A20040331BE2 2ISY Unknown


              ECM 0013A200 - CH30013A20040331BE2 3ISY Unknown


              ECM 0013A200 - CH70013A20040331BE2 7ISY Unknown


              ECM 0013A200 - CH40013A20040331C9C 4ISY Unknown


              ECM 0013A200 - CH50013A20040331C9C 5ISY Unknown


              ECM 0013A200 - CH60013A20040331C9C 6ISY Unknown


              ECM 0013A200 - Main 10013A20040331C9C 1ISY Unknown


              ECM 0013A200 - CH20013A20040331C9C 2ISY Unknown


              ECM 0013A200 - CH30013A20040331C9C 3ISY Unknown


              Thanks!!!

              Travis

              Comment


                #37
                Hi Travis,

                Although I have the Brultech module and a ECM 1240 in my test setup, I don't have it connected via zigbee since my ISY has the zwave radio instead. My setup isn't creating any new devices for the ECM.

                I've made some changes that I think will make the plug-in support the zigbee setup and I've attached a new version here. Let me know what this does. It should make the devices show up as Brultech Energy Monitor devices instead of Unknown. The warning messages should be gone too.
                Attached Files
                --
                Bob Paauwe
                ISYInsteon Plug-in
                http://www.bobsplace.com/ISYInsteon/

                Comment


                  #38
                  Thanks Bob!

                  It now works!

                  Since there were a lot of messages coming from ISY with regard to Brultech, I changed logging to "errors" and it now does not show all of the traffic I really don't care about.

                  I will keep it running and keep you posted with any issues.

                  Travis

                  Comment


                    #39
                    Version 1.0.4.12 uploaded. See first post in thread for details on changes.
                    --
                    Bob Paauwe
                    ISYInsteon Plug-in
                    http://www.bobsplace.com/ISYInsteon/

                    Comment


                      #40
                      Version 1.0.4.13 uploaded. See first post in thread for details on changes.
                      --
                      Bob Paauwe
                      ISYInsteon Plug-in
                      http://www.bobsplace.com/ISYInsteon/

                      Comment


                        #41
                        Cannot control scenes

                        Originally posted by bpwwer View Post
                        Uploaded version 1.0.4.9. This fixes a long standing bug in the code that determines scene status.
                        Bob - I am unable to control scenes from the HS Status page. Once in a while you can either turn it on, or off, but once it changes state, you cannot change it back (If you turn it off, you cannot turn it back on again, for instance). Sometimes I cannot do either (I turn it off via the remote, and HS can't turn it back on, I turn it on via the remote and HS cannot turn it off.) And the status is always "OFF" on the status page, no matter what (even after a page refresh).

                        I can control them just fine from the ISY Admin Console & via the scene's controller (RemoteLinc), it's only via HS & HSTouch that it doesn't work.

                        ISY Insteon: 1.0.4.13 Gold ISY: ISY 994i 1024 IR ISY Firmware: 4.1.0

                        Comment


                          #42
                          Originally posted by CJVann View Post
                          Bob - I am unable to control scenes from the HS Status page. Once in a while you can either turn it on, or off, but once it changes state, you cannot change it back (If you turn it off, you cannot turn it back on again, for instance). Sometimes I cannot do either (I turn it off via the remote, and HS can't turn it back on, I turn it on via the remote and HS cannot turn it off.) And the status is always "OFF" on the status page, no matter what (even after a page refresh).

                          I can control them just fine from the ISY Admin Console & via the scene's controller (RemoteLinc), it's only via HS & HSTouch that it doesn't work.

                          ISY Insteon: 1.0.4.13 Gold ISY: ISY 994i 1024 IR ISY Firmware: 4.1.0
                          I'm not able to reproduce this. The scenes that I've been trying all turn on/off correctly every time from the HS Status page.

                          Turning the debug level up and capturing a log may help determine what's going on.
                          --
                          Bob Paauwe
                          ISYInsteon Plug-in
                          http://www.bobsplace.com/ISYInsteon/

                          Comment


                            #43
                            Well Bob, some black magic happened somewhere along the line and now it's working normally! Thank you for following up.

                            Comment


                              #44
                              Hello Bob,

                              I've recently purchased a few of the Insteon Leak Sensors (Model 2852-222) and added them to my ISY99i interface. The devices show up in HS/2 okay, but when the status changes (simulated moisture on the sensors) they don't seem to register in HS even though the ISY sees them.

                              Have you had any other reports of this type of problem?

                              Thanks,
                              -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


                                #45
                                Originally posted by tmcgowan View Post
                                Hello Bob,

                                I've recently purchased a few of the Insteon Leak Sensors (Model 2852-222) and added them to my ISY99i interface. The devices show up in HS/2 okay, but when the status changes (simulated moisture on the sensors) they don't seem to register in HS even though the ISY sees them.

                                Have you had any other reports of this type of problem?
                                Hi Todd,

                                No, I haven't had any reports of problems with leak sensors. I do have one and I see some issues with status changes but HS is running so slow right now that I can't really debug it. I'm also seeing that the ISY is sending messages about the leak sensor that I haven't seen before so I need to see what UDI has added there.

                                Thanks for reporting this.

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

                                Comment

                                Working...
                                X