Controllerless Networks

I have a WEMO Belkin Light switch when I goto connect it to the AP it is coming up in the IDS as rogue and the device cannot connect to it, the security levels are set to the lowest point, any ideas?

If you are not enforcing rogues, then the issue lies between your device and the light switch as it uses a softAP connection model. 



Thanks, 
Tim

I have a similar problem, in that WeMo won't work with Aruba (275/225 in my case). I created a 2.4-only SSID and ran through the configuration with that. I see it appear on Airwave as authenticated, but the unit itself blinks red on its wifi light and I cannot connect the client to it. I've tried factory reset any number of times.

 

I'll take it home (where I have another one working) and see if maybe getting a firmware update will help here.

 

Frustrating - I am in a zoo (literally) and have some IP cameras in an animal enclosure that need fairly frequent power cycling. WEMO would be perfect for this, as it can be a hassle to schedule access.

Do you see them in the AirGroup servers list?

Is that in AirWave? I'm not sure where to look for an Airgroup server list.

On the controller: show airgroup servers

Thanks. No, the Wemo is not in that list. I only have 3 listed, and they're all airprint services

Did you add a custom service for Wemo?

No custom service (I wouldn't even know how to do that).

 

My first WEMO was at home, where I have a Cisco router that puts out separate 5 and 2.4 SSIDs. It was quite straightforward and was operational in 5 minutes.

 

Trying at work, no joy. I had a few SSIDs which were all multiband. So I created a 2.4 only, just to see.

 

That SSID is ZooStaff2.4 and something I read will have me try all lower case and no period (zoostaff24) and see if that works.

Wemo uses custom services that are not built-in to AirGroup. You need to
create a custom AirGroup service with the appropriate service IDs.



You can see the service IDs by running show airgroup blocked-service-id

First, thanks very much for working with me on this!

 

Even though this doesn't match the IP that I am seeing in AirWave for the WEMO, here's the results that look likely on the blocked services command:

 

10.170.138.149  urn:Belkin:device:controllee:1                  88
10.170.138.149  urn:Belkin:service:WiFiSetup:1                  89
10.170.138.149  urn:Belkin:service:timesync:1                   87
10.170.138.149  urn:Belkin:service:basicevent:1                 87
10.170.138.149  urn:Belkin:service:firmwareupdate:1             89
10.170.138.149  urn:Belkin:service:rules:1                      89
10.170.138.149  urn:Belkin:service:metainfo:1                   89
10.170.138.149  urn:Belkin:service:remoteaccess:1               89

 

Can you tell me how I might go about ublocking these services?

Thanks!!

hmm, and now maybe I have an explanation for why I couldn't get a Foscam IP Camera to work on my outdoor AP's

Take a look at defining an AirGroup service:



http://www.arubanetworks.com/techdocs/ArubaOS_64x_WebHelp/Web_Help_Index.htm
#ArubaFrameStyles/AirGroup/Integrated_Deployment_Model.htm

Many thanks for the help.

 

I needed to do a combination of things:

• Belking services enabled in an Airgroup
• simplify the SSID to lower case, no special characters
• simplify the password on the SSID to lowercase, no special characters
• Put the SSID on a 2.4 Ghz only radio
• and the weirdest, use an older device (in my case an iPod) that doesn't have an AC radio

Funny, the WEMO wifi light is still amber. But I can see it on my iPod and turn it off an on, which is all I wanted to do.

Very late response here but just be sure your WeMo light switch can ping the gateway address. If it cannot ping the gateway the amber light will flash and it will continue to broadcast a hidden open SSID, even though it may connect successfully to your network and work as expected.

This solved my problem

2.4Ghz only

Lower case letters only for BOTH SSID and Password.

 

Thank you!

Hi!

I had a problem with Wemo switches today and was able to get them to connect by disabling 802.11k.