Firewalla AP7 Ceiling Version (Status and Updates)

Pinned

Comments

259 comments

  • Avatar
    Shon

    @Firewalla, thank you. That is great news 

    0
    Comment actions Permalink
  • Avatar
    Ryan Rawson

    Are you still looking for beta testers? If so, what is the process to get on the list for future products? Thanks

    0
    Comment actions Permalink
  • Avatar
    J C

    @Firewalla, some network controllers (like UniFi Network) allow you to "lock a client" to an AP. There are times, especially for IoT devices, when a client may associate with a further away AP either because of load balancing or temporary conditions like an AP that needs to reboot. Even if the situation is temporary, because the RSSI between the client and the AP is above a threshold, the client will not re-associate with the nearby access point and have a less strong connection. I just installed two AP7s yesterday and actually have a few IoT devices that are in this condition (sub-optimally connected to the further away access point).

    This isn't a problem for mobile clients because they will roam between APs.

    Here's what the feature looks like in the UniFi controller web UI:

    5
    Comment actions Permalink
  • Avatar
    rogcisco

    Does this AP support PPSK for each vlan with same SSID?

    0
    Comment actions Permalink
  • Avatar
    rogcisco

    @ J C, I also agree this "Lock to AP" is very important as many legacy IoT device don't stay connected to certain AP.  In my Unifi environment, I had few of them to be locked in order to stay connected.

    5
    Comment actions Permalink
  • Avatar
    Firewalla

    @rogcisco AP support PPSK for the same SSID. 

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @J C, will take a look. Our developers were playing with locking devices, but not all devices behaved nicely. 

    1
    Comment actions Permalink
  • Avatar
    Colin Scattergood

    @firewalla FWIW Device locking would make this an instant buy for me. I have eeros that are *fine* but not great. One thing they really lack is device locking and it’s such a pain. If firewalla ends up adding Device locking that would be enough for me to pull the trigger. Hope it comes someday!

    1
    Comment actions Permalink
  • Avatar
    Troy Dampier

    The way I have gotten around this with other APs was using MAC address filtering but of course the requires you to enter the MAC address of all your clients for the remote AP you don't want the IoT devices to connect to. 

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Our WiFi team is pretty eager to make cool features that's important to you all! So keep them coming! 

    3
    Comment actions Permalink
  • Avatar
    Eibensl

    TP Link Omada also allows for locking devices to specific APs; comes in handy for above stated reasons along with load balancing clients between APs when the client is setting on the coverage edge of multiple APs.

    2
    Comment actions Permalink
  • Avatar
    Eibensl

    @Firewalla...as long as the team is taking a look at allowing for locking clients to a specific AP, would like to toss back out there the ability to manually select the upstream AP that an AP will use when connecting via mesh.  This is a standard feature with TP Link Omada and, I believe Ubiquiti, that has been useful.

    1
    Comment actions Permalink
  • Avatar
    Eibensl

    @Firewalla:  another function request.  Wifi logs showing connection events (success / failure) for clients and APs.

    1
    Comment actions Permalink
  • Avatar
    Steven

    Additionally if we are looking for feature requests @firewalla - take a look at the Homekit request for templates.  This goes beyond just Apple devices and the concept will help with vlan configurations.

    https://help.firewalla.com/hc/en-us/community/posts/37715472458387-HomeKit-not-working-after-install

    And really this is not only to help when using vlans and segregation of devices, this will absolutely help with the constant issues where Firewalla blocks certain communications outbound (wan), requiring to place the device into emergency access (essentially) spending hours to figure how which rules are blocking the device from functioning properly. 

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    I been collecting various requirements for sure. So keep them coming; 

    1
    Comment actions Permalink
  • Avatar
    Ryan Nacker

    Any idea which of those features I mentioned above are already implemented, planned and/or not planned?

    -1
    Comment actions Permalink
  • Avatar
    Firewalla

    Hi Ryan

    Can you please take a look at the product description or getting started guide, https://help.firewalla.com/hc/en-us/articles/37151746345491-Getting-Started-with-Firewalla-Access-Point-7

    Things like changing channels, frequency, creating SSIDs, and local flows are all there. However, not everything can be changed in the 1.64 version, so you will have to wait for things like channel band.

    We never considered including turning off 802.11be or ax ... but if enough people ask, we can put it in.

    Some of the more detailed requirements like Perfered Channel Selection and DFS should be there already. 

    DFS Zero wait, don't have it, it requires another radio.

    If Client Balancing is part of the MLO you are talking about, we are unlikely to turn on MLO until there are more clients supporting it. 

     

     

    1
    Comment actions Permalink
  • Avatar
    Ryan Nacker

    Ability to turn off be/ax is great for 2.4 only/IoT devices.

    1
    Comment actions Permalink
  • Avatar
    Ephraim Fabian

    Hey @Firewalla: will the ceiling version of the AP be less/more expensive, or about the same price as the Desktop AP? Apologies if this has been asked already.

    I appreciate your updates and hard work in developing these APs.
    I'm enjoying my desktop AP at the moment.

    0
    Comment actions Permalink
  • Avatar
    Mo Ali

    @firewalla
    This may not be specific to this device but all devices. Is there a plan to add local management instead of cloud/phone management?

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    The ceiling version is likely the same price (+/-10 to 20 dollars difference) as the Desktop version. The build cost of the ceiling mount AP is a bit higher due to its compact design and ability to regulate heat better. 

    1
    Comment actions Permalink
  • Avatar
    Firewalla

    @Mo Ali, the firewalla AP's are locally managed by a controller running inside your firewalla. So all the roaming controls etc ... are local already. This controller will work, even if your wan is down. Same as the app.

    As of App control, can't change that. MSP interface may be enhanced, that's for the future. 

    1
    Comment actions Permalink
  • Avatar
    Firewalla

    4
    Comment actions Permalink
  • Avatar
    Firewalla

    Here is the drilling template , in case you want to know how big the unit is 

     

    2
    Comment actions Permalink
  • Avatar
    Firewalla

    Just posted the AP7 Ceiling version survey https://forms.gle/w3w3VcBszX6BwJYH7

    Please complete this if you are interested in ordering either the AP7 Desktop or AP7 Ceiling in March 2025

    1
    Comment actions Permalink
  • Avatar
    N Willis

    What is the estimated coverage area for the AP7 Ceiling? For instance, would one device cover a 2300, one-story home if it was centrally located?

    1
    Comment actions Permalink
  • 0
    Comment actions Permalink
  • Avatar
    N Willis

    @Firewall, thank you!

    0
    Comment actions Permalink
  • Avatar
    Eibensl

    @Firewalla, I have been emailing Firewalla Support about the current decision to only allow 6GHz for mesh connectivity between AP7s, was informed that, if enough customers want it, that you could enable the ability for customers to choose between using either the 5GHz or 6GHz for mesh.

    Please allow customers to make this decision, though you could have it default to 6GHz.

    5GHz signal travels a lot better than 6GHz.  For my use case, I will need to connect an AP7 in the garage to another in my office (I already have this with my current APs).  But, I have had to use 5GHz since 6GHz connection between the two locations is poor.  
    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @Eibensl, are you using the AP7 now? or is this a theoretical assumption?  

     

    1
    Comment actions Permalink

Please sign in to leave a comment.