Announcement

Collapse
No announcement yet.

Checking before I purchase EnvisaLink System/Plugin

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

  • Checking before I purchase EnvisaLink System/Plugin

    Hi,

    I'm wanting to add my security system to HomeSeer but first I want to be sure that I got it all straight first to be sure I get the correct hardware & software for my alarm/HS3 system.

    The alarm system currently installed in the house is:
    • DSC PC1832 Version 4.23NA
    • Two keypads: both DSC PK5500ENG


    HomeSeer:
    • HS3 running on Windows 7


    What I think I need is:
    • EnvisaLink 3 Ethernet Interface Board
    • EnvisaLink DSC Plugin 3.0.0.24 for HS3


    Am I missing anything?

    Assuming I got all this correct and purchase it, are there any:
    • known issues,
    • tips,
    • tricks,
    • etc...

    that I need to know during the install/config that are not covered in the docs?

    Thanks in advance!

  • #2
    you are correct

    the installation and configuration of both the board and the plugin are pretty straightforward.

    once you have the board installed you can log into the local web page to enable or disable the connection to the Envisalert service. Both the HS plugin and Envisalert can work at the same time, but if you don't want any information to be sent to their server just leave it disabled like in the screenshot below.

    Click image for larger version

Name:	envisalert.jpg
Views:	2
Size:	61.5 KB
ID:	1178308

    let me know if you have any problem

    Comment


    • #3
      Thanks spud!

      I appreciate the prompt response. I'll get the board ordered!

      Comment


      • #4
        How do I log into local webpage? I can't find anywhere to make it static. Under plug in config, there is an ip address within homeseer.
        But, there is no "eyes on" section on web to make static.

        Originally posted by spud View Post
        you are correct

        the installation and configuration of both the board and the plugin are pretty straightforward.

        once you have the board installed you can log into the local web page to enable or disable the connection to the Envisalert service. Both the HS plugin and Envisalert can work at the same time, but if you don't want any information to be sent to their server just leave it disabled like in the screenshot below.

        [ATTACH]45693[/ATTACH]

        let me know if you have any problem
        Jim
        ----
        Plugins:Z Wave 3.0.1.55, HS3 Pro 3.0.0.208, HS3Touch, HS3Touch IOS, Z-Net, SceneMaster, XBMC, Sonos, Media Controller, Envisalink (52 Virtual nodes), JowiHue, EasyTrigger, Liftmaster MyQ, BLBackup, BLLAN, BLRadar, Pushover

        Devices:Cooper RF9540, Cooper Scene, Yale Locks, Sonos, Phillips Hue and Lux, DSC, Somfy Blinds

        Comment


        • #5
          Originally posted by 519zwave View Post
          How do I log into local webpage? I can't find anywhere to make it static. Under plug in config, there is an ip address within homeseer.
          But, there is no "eyes on" section on web to make static.
          in a browser on your local network go to http://envisalink/
          the default username/password is: user/user

          Comment


          • #6
            Thanks, Says static now, but is this an issue?
            DHCP Status DISABLED
            Yours says Bound
            Jim
            ----
            Plugins:Z Wave 3.0.1.55, HS3 Pro 3.0.0.208, HS3Touch, HS3Touch IOS, Z-Net, SceneMaster, XBMC, Sonos, Media Controller, Envisalink (52 Virtual nodes), JowiHue, EasyTrigger, Liftmaster MyQ, BLBackup, BLLAN, BLRadar, Pushover

            Devices:Cooper RF9540, Cooper Scene, Yale Locks, Sonos, Phillips Hue and Lux, DSC, Somfy Blinds

            Comment


            • #7
              Originally posted by 519zwave View Post
              Thanks, Says static now, but is this an issue?
              DHCP Status DISABLED
              Yours says Bound
              this is not an issue, the screenshot had been taken before I made the IP static so it was still using DHCP.

              Comment

              Working...
              X