Our walls need APs, right?

So I wanted to do a quick little physical comparison between two wall-plate style Access Points. I think this market is pretty open, maybe not so much for greenfield projects, but this fits in a nice place for the brownfield folks.  Lots and lots of hotels need wireless access. And I think cost is a huge factor. If you have people paying $50 to $600 a night for a room you want excellent wireless connectivity. That might be hard for the hotels/motels that have been around for 30+ years. Hence why I think wall-plate APs are a very good fit. And, it goes well with “don’t put the APs in the hallways” chant.

So I have an AP from two different folks, one from UBNT: AC IN-WALL and the Cisco Meraki MR30H. (I think the MR30H sounds like MR38, should be renamed to MRH30)

Now this is just a physical comparison, nothing about performance, setup etc… or any other metrics have been done yet. I just wanted to show what they look like and because I think these units fit two different needs, and I’ll explain that thought a little down the road.

Alright, picture time. (UBNT is the smaller of the two)

They are roughly about the same size, however the MR30H is much heavier. If you tossed it in your backpack–you’d know.

For thickness they are roughly the same. One thing that is interesting about the UBNT is how it mounts. The AP is actually inside a plastic mounting “case”. You can see the little plastic push part at the top that you press to remove the top half cover. The back half is then mounted to your wall or junction box, or whatever. The AP has a couple screws to secure it to the back cover, then the front cover snaps on. It’s actually pretty difficult to pop off, a few times I thought it was going to break by the amount of force I was using on it. I would say it’s pretty secure–but if you are determined to get into it, well whatever, you’ll get into it.

The MR30H has a metal bracket that is mounted, then the AP connects to that, you have to use a special tool to release a little bracket, then the AP tilts off the bracket. I think this is a little harder to remove, because you need a specialized tool.  But you’ll need a screwdriver to remove the UBNT unit from the back cover too.  So bottom line is—for maintenance, a tool is needed. Not really a big deal.

And here is the UBNT unit…

And as for what comes in the box, MR30H has more, typical foam/sponge(Meraki does this with other products) that holds all the little screws etc, normal docs and mounting plate.

The UBNT is very minimal also, tiny little bag of a few screws and a little folded install, setup guide.

I mentioned early, I think these fit two different areas. On one hand, you could install a couple UBNT vs. one MR30H. What does that mean? Well, it’s the price. List price on UBNT is just under 100 US Dollars and the other is around 400.  Now, the MR30H does have four network ports. Personally I can’t remember the last time in five years I plugged into a hotel network port. But then again, my hotel stays have been in large metro areas. Good thing they do have networks ports though, as I always see some type of IP phone in the hotel room. Lets say one CAT cable is ran, you then have an AP and IP telephony. Cool.

Also, one requires a “cloud license” and the other a “controller” of some type.  If you’re reading this blog, then you know how one operates. But, the other can do local, cloud, or a hybrid controller. I think UBNT is fitting the perfect need of the smaller hotel/motel. As you know you need wireless access, but how? And, budget is a huge deal. Maybe you only have 75 or less rooms? If your facility is older, you probably have cinder block walls which equals nice attenuation. So you do one AP per room, drop the power or do whatever(but seriously though, do a predictive model–if you can).

So basically this is it, you just became a little more familiar on some wall-plate Access Points.

He Who Dares, Wins!

“He Who Dares, Wins”   I like that…. I find it interesting.  For the last few months I have a support ticket open for what is called a “cosmetic issue” or so I’m told.  And, that issue is, all of my Cisco Meraki MS220-8P switches are showing the  incorrect LED status, for any ports and even the main switch status light.

Here’s a somewhat bad photo that shows what I’m talking about:


The main status light on the far left is Amber, that should be Green.  However, if Port One is unplugged, which currently is showing Amber, the switch status light turns off. And, instead of showing Amber on the ports, it should show Green.  Hmm.

Cosmetic Issue …. Yeah … the switch itself appears to function fine, I have not noticed any issues with devices being able to pass traffic or any related performance metrics that are not meeting a goal. So Okay, then what are we winning?  Well, let me explain what I’m thinking….

Could Cisco Meraki be doing a client test or collecting information to see who actually looks at port lights? If we are moving to a complete cloud based system do we really need lights? Sure, I would think, maybe a power light, to say “hey, I have power, or I’m not doing well”.  BUT, how often do you *really* look at your switches or even look at each switch port status? From the (wireless) access point side of things, people want the status LED turned off.  Some people just do not like it.  Maybe that approach is making a road towards switches and other devices, turn all the lights off.

………… or maybe someone messed up and just hasn’t fixed it???


The ball and the three cups.

The greatest trick Meraki ever pulled was convincing the world to run Beta code.

Yeah, I changed it .. and that’s what I’m thinking now. Let me explain…

After reading this post on the Meraki blog about the new phone features—which really should have been around from day one.  I was impressed, but then that wore off really quick. I found one of the features was available right now—the easier porting of an existing phone number into the Meraki system. Nice.

But wait … where are the other two?

Well, they’re stuck in “Beta” code. ……. FUCK! Really!?!?

When it comes to things with the word Beta attached, I stay away. But why? Gmail was Beta for years.  Good point. But that’s email, not a phone call.  A phone call could be important and it could be nothing.  The important part being–the need to call emergency services. Do you want your phone to reboot, lockup, or just not work? Nah, I didn’t think so either.

Maybe Meraki could have two thoughts about code, maybe you still have your traditional “beta” code, that only runs with and on devices that you know are going to be watched and reported on for issues. Then you have almost production code, meaning we’re not sure if something exists, but this code train has passed our internal QA process, which Meraki talked about here. So after passing our check box items, we allow outside folks to run it, with them knowing that is *has* passed xyz of checks, but something could be around. Then after that is done, it becomes the “upgrade available” option in your Meraki Dashboard.

With that little warm feeling available, maybe it would be OK to run Beta code in production environments.  Maybe we’ll call this idea… the the condition of being transparent. Or we could just chase the ball under the the three cups. 🙂


The new eye in the sky? …. maybe

Of course with all new products there is that nice and new feeling you get, the taking off the wrapper of the goodies under the tree.  Well, keep that in mind, they did get the box right, Cisco Meraki makes this an “Apple” like party.  No need to have lots of paperwork that is tossed away, of course all the little screws and misc parts are in a nice little foam sponge like thing–very handy when doing an install(they do the same with the phone and access points). Here are some box pics. Uhm. Yeah.

So on to the camera,  this thing is huge, not sure I like that, I’m comparing this to an existing Axis P3344 camera.  A little bit about that, I love Axis products, not the cheapest by any means, but damn rock solid for the last 10+ years I’ve been using them. Never had any issues and it always did exactly what I wanted it to do. Of course your mileage may very.  And here are some pics of our Axis camera.

So not too bad, the Axis is much smaller, not as deep as the Meraki camera, can I live with that? Maybe.  On to the installation… Okay .. this part was odd .. We use Belkin CAT 6 molded cables.  It was a little tough getting the cable in.  See the pics…

After cramming the cable in, not the best placement–compared to how the Axis is plugged in(see the pics). But then again, this is not something you constantly plug and unplug.  Moving on …  Now Meraki is good for doing the cloud configuration and latest firmware updates, just plug the stuff in … wait 1o or so minutes for the updates, get some coffee or RedBull, watch the green blinking light(no color rainbow like the APs??) then configure. Simple. However, this is a camera you really need to touch it more after the physical installation is done. I figure that’s expected.

So what’s odd?… the clear dome that covers the camera portion, just turn that a little, like very little and it pops right off and then you can move the camera around.  Hmmm. So it could be pointed up, up and into the sky. Well, okay. This is the Internet, use your imagination on this. 🙂

But wait a minute, how would you secure the dome?  This is what Axis did….yeah see the pics.

They have it screwed down internally and included two dome options, clear and frosted. What is shown is frosted. Which also includes a black plastic part that covers more of the camera parts. Wait, you said it’s screwed down? I have a screw driver! But is it a Torx one? All the screws are Torx heads. Hmm ok. Meraki does that too. Cool.  And, just like the Access Points and now Camera, one security screw is all you need.

Well I finally get it mounted, which that was odd–and I didn’t take any pictures– was how it mounted to the wall plate.  It includes a wall plate that you put wherever and then the camera slides onto that. Actually pretty nice. BUT the placement of the network cable and how it lines up with the part that the security screw goes into made it like I had to twist the camera and push down onto the mount plate in an odd way all at the same time. Maybe this is by design to slow people down–you know from taking the camera–which has the security videos.

The hard stuff is done, now onto the Meraki Magic, you know the part where you Merakify everything.  Yeah, I hear that’s a thing now, Merakify.  Listen, just go with it.

Everything on the dashboard is pretty much just like any other Meraki product, you claim the order/license/whatever number and add it to a Network(you create a new Camera Nework) then combine the Camera Network to an existing Network and you’re done. Simple.

Now, finally to the part that I think could just be a software update. Having finer rotation settings, you either have 180 or 0 degrees. So that’s that mattress man.


But hey you can move the camera lens around after you just pop the clear dome off, and yes– you –can.  But let me show you the issue I have—-yeah–more pics. 🙂


Hmm, that looks like shit, well yeah it does. Our camera is mounted on a concrete column by our front elevator.  You can see people moving around, ok that’s fine, However this is what the other camera could do. ugh more pics… See how rotation comes into play.


The other camera you could digitally rotate the picture for a better view. NICE!

And, the full screen option is pretty bad on the Meraki side, here’s why… I had to add a camera to a “video wall” and then that “wall layout” becomes full screen, notice the gray side and black bottom bars on the other picture?  That’s because the Video Wall only allows a camera to take up so much area of the wall, then the entire wall becomes full screen, you get it?!  If I had more cameras I don’t think this would be so bad. Hmm.  I would think I should be able to full screen that camera, from the dashboard list of attached cameras?

Nope… I don’t see the button, do you?


So far in this post  we have lots of “you can do this with something else or this with that blah blah and this sucks”.  I know. I know. Why not just put the other camera back in. etc… etc…

Well, everybody wants to believe in something, right, maybe the next software update will be: “You and me, Max… …we’re gonna give them back their heroes.”

Or maybe not…

I’ll leave you with this, you can Merakify however you like, every product launch has good and bad. Do we know all the details as to why? Nope, Should we?  Ok that’s fine.  BUT you have to have goals and those goals have to be precise.

I kinda like this quote:

You come at me, you better know I move quick...
...and when I do, I slice like a goddamn hammer.
So you're not gonna make Reuben whole?