Older Imp001 from 2017 Connects to Wifi, will not connect to server

1

I have an Imp001 from an imp explorer kit purchased in 2017 that I have never used. It will connect to my wifi router and gets an Ip address, but cannot connect to ElectricImp servers.

I have another impExplorer with imp001 purchased at the same time that has worked fine for years and connects fine through the same router.

The only thing I can see on the router for activity for the failed attempts are the following:

Proto NATed Address Destination Address State
tcp 172.16.0.128:11929 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:8117 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:1611 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:34218 54.212.72.238:31314 TIME_WAIT
tcp 172.16.0.128:19521 54.212.72.238:31314 TIME_WAIT
tcp 172.16.0.128:23769 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:38098 54.212.72.238:31314 TIME_WAIT
tcp 172.16.0.128:5768 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:58552 54.212.72.238:31314 TIME_WAIT
tcp 172.16.0.128:23670 54.212.72.238:31314 TIME_WAIT
tcp 172.16.0.128:61297 54.212.72.238:993 TIME_WAIT
tcp 172.16.0.128:11853 54.212.72.238:31314 TIME_WAIT

a few hours ago, it was attempting a different remote IP address

Proto NATed Address Destination Address State
tcp 172.16.0.128:24182 54.189.241.137:31314 ASSURED
tcp 172.16.0.128:12135 54.189.241.137:31314 TIME_WAIT
tcp 172.16.0.128:19803 54.189.241.137:31314 TIME_WAIT
tcp 172.16.0.128:52334 54.189.241.137:993 TIME_WAIT
tcp 172.16.0.128:30192 54.189.241.137:993 TIME_WAIT
tcp 172.16.0.128:10104 54.189.241.137:993 TIME_WAIT
tcp 172.16.0.128:37999 54.189.241.137:993 TIME_WAIT
tcp 172.16.0.128:24186 54.189.241.137:31314 TIME_WAIT
tcp 172.16.0.128:18340 54.189.241.137:31314 TIME_WAIT
tcp 172.16.0.128:54609 54.189.241.137:31314 TIME_WAIT
tcp 172.16.0.128:61052 54.189.241.137:993 TIME_WAIT

(172.16.0.128 is the IP address assigned by my DHCP to the imp001)

Is it using an old server address? expired certificate? Would this be resolved after an initial update (if it could connect), which could explain why the other imp001 is working fine? (i.e. it was updated periodically over the years).

2

I’m having a similar issue with older imp001’s. One I can get to join my WiFi, but I have 3 others that can’t even join the WiFi. I recently purchased some April boards, assuming the imp001’s are still viable. If they’re not viable, then KORE should not be selling the April boards. Any suggestions would be greatly appreciated!
IMG_8531

3

I’m now wondering if anyone from Electric Imp watches this forum…

Support from them used to be spectacular.

4

You may get a faster response if you provide the mac addresses in a copyable format, and a better description of what you have tried and observed.

  • which one is able to connect at least to wifi?
  • what are the LED patterns shown for all four imps?
  • what mobile device and OS version are you using to blinkup?
  • have you confirmed that blinkup is completing successfully?
  • what AP make, model and firmware version are you using?
  • what wifi encryption type and channel are you using?

Business customers can also raise a ZenDesk ticket directly with the support team.

5

The device that connects to WiFi, but then goes dormant is: 0C:2A:69:02:2D:AC
I can see it on my network scanner and ping it for a while, but then it stops responding to pings for several seconds before resuming ping responses. It never shows the green LED I seem to recall seeing. It blinks red and then orange repeatedly.

The other devices blink red once and then just keep blinking orange.

I’m using an iPhone (iOS 17.5.1) with the latest version of the Electric Imp app.

The Blink Up ALWAYS fails on all of the devices.

I’m using a NetGear Orbi mesh network with WPA2 encryption.

The other MAC’s are:
0c2a69047166
0c2a690232c6
0c2a69046af8

Yes, I could have provided those earlier, but thought showing the imp001 cards might be the easiest so you know exactly what I have. I’m using to easily grabbing data from a photo with my Mac and forgot it’s not as easy for everyone.

If this is too much of an ask, I can just return the 3 April boards for a refund and go with another platform.

6

Both my 2.4 and 5 GHz networks have the same SSID (limitation of the Orbi devices). I wonder if that could be causing the issue.

OK. I was able to turn off the 5 GHz network and successfully Blink Up the device with the MAC ending in 7166. The imp001 now seems to have connect to impcentral.

The device 0C:2A:69:02:2D:AC blinked green for a few seconds and now blinks one red followed by 3 shorter reds.

I can’t get 0c2a69046af8 to do anything but blink orange.

8

I can see that 0c2a69047166 has connected and updated to impOS 42.9. I think you must have changed something about your blinkup process to make that work, which you can hopefully replicate for the other devices.

You’re right that imp001s cannot connect to 5GHz networks, although switching that off should not have made a difference to blinkup success/failure. If the imp flashes long red then repeatedly flashes orange, then blinkup hasn’t worked and router settings won’t make a difference.

For those devices, try disabling any settings on your iPhone that dynamically adjust the screen brightness (under Accessibility, possibly), pinching the imp001 card between thumb and finger to block any ambient light passing through the plastic near the light pipe, and conducting blinkup in a place with low ambient light levels. Once devices have connected they will fetch an impOS update and subsequent blinkup should be easier.

0c2a69022dac has not been seen by the servers yet. According to the database it is running impOS 32.12 (circa. 2015). Long red followed by three short red is ‘joining network’ (i.e. associating with the access point). Assuming that the SSID and password are the same as for the connected device, this could be a signal strength issue. Is the device in the same location as the connected one? Do you have any mesh repeaters with the same SSID but weaker RSSI? Otherwise I would try clearing settings back to flashing orange (from the app) and blinking up again.

0c2a690232c6 connected yesterday and has updated to impOS 42.9.

I cannot see any information about 0c2a69046af8 in the database. Does the flashing orange stop while blinkup is happening?

9

This topic was automatically closed after 60 days. New replies are no longer allowed.