Cannot blinkup device in organisation

Hi All,

I work in an organisation which is having 802.1x Wi-Fi authentication so they provided me other wifi endpoint where 802.1x is disabled but still I am not able to blinkup the device.

Could you please suggest next course of actions.

Thanks
Dheeraj

If someone tell me what exactly blinkup process does, then I will come to know what I need to do.

Blinkup just sends the wifi credentials and an enrollment token to the imp.

Sounds like the alternate network they have provided has some other issues. Have you tried connecting with a phone? Does it have a landing page or similar? Wifi devices generally can’t get through those as doing so would usually require the device to comply with a legal agreement which isn’t really within the remit of a thing :slight_smile:

What does the LED code indicate? That will let you know what stage of connection is failing.

I believe wifi credentials username and password based connection string.

What is enrolment token? If you have any link for online documentation that will help me.

Enrollment token is a token sent to the imp servers once the device has made the connection, which uniquely identifies the connection attempt.

The token is immaterial if you’re not getting connected. As I said, what is the LED blinking?

See https://electricimp.com/docs/troubleshooting/blinkup/

The other question would be what phone are you using, and has the imp ever connected to any network? Old developer imps are over 3 years old now and the android support improved hugely over that time.

Also https://electricimp.com/docs/troubleshooting/networks/

Hi Hugo,

I am now able to blink-up my IMP successfully.
If I move from one wifi network to other then I have to blinkup my device again. In that case enrollment-token will be created again or earlier token which is in server will get used.

Hi Amittytone,
I used link “https://electricimp.com/docs/troubleshooting/networks/” suggested by you to work with IT guys.

Thanks
Dheeraj

In that case enrollment-token will be created again or earlier token which is in server will get used.

That’s an implementation detail, and subject to change.