Announcement

Collapse
No announcement yet.

Aladdin GenieConnect (Remote Garage Door) Issues

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Aladdin GenieConnect (Remote Garage Door) Issues

    Hi,

    I've had the Aladdin GenieConnect Garage Door Opener for almost 1.5 years and it worked great with Untangle. About 2-3 months ago, I've lost the ability to open/close the door from the Application on my iPhone (both Cellular and Wifi). I still get Notifications on my mobile devices of when the Door is Opened/Closed from the actual garage door opener itself.

    Tonight I decided to troubleshoot the issue. The GenieConnect is connected to my wifi (IP 10.0.0.62). I reviewed all the Applications running on Untangle 14.0.1 and see no "Blocked" of anything. Reviewed the Packet Test and don't see anything being blocked either (see attachment). I decided to one by one turn off individual applications and found the issue is with Virus Blocker Lite. Once it was turned off, I could control my Garage Door from my mobile device both on Cellular and Wifi.

    Reviewing the Untangle forms, I've tried the following to get it to work with Virus Blocker Lite turned on but still failing to get it to work:

    -> Created a bypass rule Bypass Rule with Condition of Destination IP of 10.0.0.62, to Bypass. Then moved it to the top.
    -> Turned off HTTP Scanning in Virus Blocker Lite as a test.
    -> Added Server names (vendor.m2.exosite.com and genie.m2.exosite.com) and IP (52.8.95.118) as "Passed Sites"

    Any help would be greatly appreciated as I'd like to leave Virus Blocker Lite on and have the Aladdin GenieConnect still work from any mobile device controlling the Garage Door.

    Thanks,
    Brian
    Attached Files

  • #2
    You need two bypass rules, one destined to 10.0.0.62, the other sourced from 10.0.0.62, that'll make sure no rack application ever touches that thing ever.
    Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: [email protected]

    Comment


    • #3
      You probably want to use DHCP reservation for the device as well so it always has the .62 address.

      Comment


      • #4
        Originally posted by sky-knight View Post
        You need two bypass rules, one destined to 10.0.0.62, the other sourced from 10.0.0.62, that'll make sure no rack application ever touches that thing ever.
        Rob,

        Thank you. That worked with having a Destination of 10.0.0.62 and Source of 10.0.0.62.

        Comment


        • #5
          Originally posted by Kyawa View Post
          You probably want to use DHCP reservation for the device as well so it always has the .62 address.
          Yep. All my Home Automation Devices have DHCP Reservations so I don't have to remember them

          Comment


          • #6
            Originally posted by WizBomb View Post
            Yep. All my Home Automation Devices have DHCP Reservations so I don't have to remember them
            In this case it's critical because a power failure that keeps Untangle offline for the lease duration will result in devices changing addresses. Obviously if you have rules based on those addresses, changes mean problems!
            Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
            NexgenAppliances.com
            Phone: 866-794-8879 x201
            Email: [email protected]

            Comment

            Working...
            X
            😀
            🥰
            🤢
            😎
            😡
            👍
            👎