Announcement

Collapse
No announcement yet.

Jon00 Homeseer 2 - Homeseer 3 - Homeseer 4 Connector

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

    Thanks very much Steve. I'm pleased you got your firewall & AV issues sorted.
    Jon

    Comment


      Jon00 Homeseer 2 - Homeseer 3 Connector

      Jon, when using hs.SaveVar("Jon00GW".............) in a manual HS3 event to trigger an HS2 event (per your example in the PDF), it works fine when manually triggered from the local HS3 computer keyboard. But it will not work for me when I trigger the HS3 manual event from another computer on my local network via the web browser. I am running HS3 on a Netbook (IP xxx.xxx.xx.5) but I use my desktop (IP xxx.xxx.xx.7) as a console to enter info and control HS3. Can you confirm this works for you. Perhaps it is another firewall issue for me.

      Steve Q


      Sent from my iPad using Tapatalk HD
      HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
      2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

      Comment


        I can try it later on when I return from work, however I would of thought any event triggered this way would exhibit the same issue?
        Jon

        Comment


          Jon00 Homeseer 2 - Homeseer 3 Connector

          I don't have a large number of HS3 events setup yet, but the events that I have tested can all be triggered from my iPad and my other LAN computers. There must be something about hs.SaveVar that makes it behave differently.

          Steve Q


          Sent from my iPad using Tapatalk HD
          HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
          2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

          Comment


            Steve,

            Sorry but have not had time to test today. Will do so tomorrow.
            Jon

            Comment


              Jon00 Homeseer 2 - Homeseer 3 Connector

              No problem Jon. I did a little more testing and found that even when I use the keyboard on the HS3 computer to trigger the event manually, it does not fire most of the time. There is always an HS3 log entry but there is only an HS2 log entry when the event works as it should. Something seems to be interfering with the HS3 client sending the message.

              Steve Q


              Sent from my iPad using Tapatalk HD
              HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
              2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

              Comment


                Steve,

                The HS3 to HS2 connection uses a different port to the HS2 to HS3 so that may be an issue. Try and mirror a HS3 device in HS2. If it fails then you still have firewall issues.
                Jon

                Comment


                  Jon00 Homeseer 2 - Homeseer 3 Connector

                  Turning off the firewalls on both computers did not help. The event can usually be triggered the first time I try it after making a change to the event. But then stops working. No idea what is going on?

                  Steve Q


                  Sent from my iPad using Tapatalk HD
                  HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                  2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                  Comment


                    Steve,

                    I don't really know. I've done extensive testing from an iPad, several other PC's and the HS2 event always fires.

                    How do you have the event set up?
                    Jon

                    Comment


                      Nothing unusual about the setup. See Attachment.

                      It might just be my HS2 setup. I have had other times when it would not respond to network info. I have another HS2 computer that I can try.

                      Steve Q
                      Attached Files
                      HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                      2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                      Comment


                        Here is another issue. I am measuring the temperature via xAP on HS2 (Device R2).
                        I have successfully mirrored this to HS3 with your connector. (See attachment 1. I assigned device address R102 to it. The correct temperature value shows in the device management page. However, when I create an event to write the temperature to the HS3 log (see attachment 2) it appears in the log as " -1 ". (attachment 3). Any ideas?

                        Steve Q
                        Attached Files
                        HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                        2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                        Comment


                          Steve,

                          Even though you see the correct value on the device string, you need to go back to HS2 and check to see if the device value for R2 has been set.
                          Jon

                          Comment


                            Jon00 Homeseer 2 - Homeseer 3 Connector

                            Jon, I checked the value of R2 in HS2, it is correctly set to 60 which is the the value shown on the HS3 device management page.

                            Steve Q


                            Sent from my iPad using Tapatalk HD
                            HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                            2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                            Comment


                              Steve,

                              Click on the R102 name link on the device management page, then click on the advanced tab. What does the value show?

                              Go back to hs2 and check the device value of R2 i.e. hs.devicevalue("R2")
                              Jon

                              Comment


                                Jon00 Homeseer 2 - Homeseer 3 Connector

                                I had already checked the advanced tab in HS3 and Again checked HS2 via the script function hs.devicevalue. They both show the same temperature.

                                I'm using HS3 pro ver 3.0.0.54. Do you have a way to look into the HS3 SQLite database?

                                Steve Q


                                Sent from my iPad using Tapatalk HD
                                HomeSeer Version: HS3 Pro Edition 3.0.0.368, Operating System: Microsoft Windows 10 - Home, Number of Devices: 373, Number of Events: 666, Enabled Plug-Ins
                                2.0.83.0: BLRF, 2.0.10.0: BLUSBUIRT, 3.0.0.75: HSTouch Server, 3.0.0.58: mcsXap, 3.0.0.11: NetCAM, 3.0.0.36: X10, 3.0.1.25: Z-Wave,Alexa,HomeKit

                                Comment

                                Working...
                                X