Found unsatisfactory workaround for the network issues. I have an android phone. I disconnected it from the my home WiFi and started a wifi hot spot through the phone. I was able to select that network during the setup of the Argon and it successfully established an cloud connection. I can’t leave my phone in the field so this will not work in real life. My home WiFi is IPv6 comparability problem. I would really like to go through my LinkSys router.
Hi, I had the same issue until I found this post:
I deactivated IPv6 on my router and voila! all my problems went away
PS: oh, I see it’s been mentioned here above already:
I just tried disabling IPv6 on my router but still could not get connected. perhaps there was some element of IP6v on my router. I am back on my phone wifi hotspot and hope the patch can push out to my argon soon.
I just wanted to give an update to my situation, as it relates to this topic.
My Argon will not connect to my home wifi using the ios app - it always results in rapid green blinking. It will connect to my iPhone’s Personal Hotspot wifi, resulting in breathing cyan, and I can publish events et. al. only when it is connected to my phone acting as a hotspot.
My home wifi is a TP-Link Deco M5 mesh network. It has both 5GHz and 2.4GHz networks both using the same SSID and credentials. IPv6 is disabled. The password is “Abcdefghi1”. When trying to connect to this network as is, after selecting my network from the ios app, the Argon switches to rapid green blinking, the ios app tells me the bluetooth connection was lost, and I need to do a factory reset on the Argon to get it back to blue blinking listening mode.
I added a guest network on my home wifi and turned off the 5GHz, so it is 2.4GHz only. It has a different SSID then my regular network, and the password is (was) “abcdefgh”. IPv6 is still disabled, and the Argon is unable to connect to this network either. Same results as before.
So I am unable to connect to my home wifi using the ios app.
Just recently @avtolstoy has pinpointed an issue I had from the beginning which finally has boiled down to my router providing more than two possible DNS servers.
If yours does too, rc.26 should have a fix for that.
I was just going to delete the third DNS that was stored in my router to check whether that’s a workaround till rc.26 gets released.
After removing the third DNS entry from my router my Argon connects to my WiFi.
Evidence in my network supports this issue with >2 dns servers.
Not all other things are equal, but I was able to set up a less complex (and consequently less protected) testing network. One difference is a single dns server compared to more than 2 on my production network.
All mesh devices connect happily to the network with a single dns server while failing to connect to the network with more than 2 dns servers.
I confirm, can’t able to connect Argon to local WiFi network when the password of SSID use special caracter. I try to another SSID with only letter caracters and worked.
I have the same issue I can’t connet any of my argon (2) on my wifi 2.4, password contain only letters and numbers, IPV6 is off. I had 3 DNS I removed one and still can’t connect. I tried with my iphone 8 and galaxy s9.
I ran out of thing to try…
On my s9 on the first boot I selected xenon instead of the argon and the app pushed the firmware update…can this be the source of the problem?
In other words, is the first firmware update is the same for argon/xeno/ argon ?
It’s the same updating process for all mesh devices, but the binaries are different. I think that the updater checks to make sure the .bin file is the correct one for the target device, but I’m not positive.
particle flash --usb system-part1-0.8.0-rc.25-argon.bin
Then, try going through the setup process again using your mobile device.
@particleD Thanks for the suggestion.
I flashed the system-part1-0.8.0-rc.25-argon.bin and still can’t connect wifi
I also tried to flash
particle flash --usb argon-ncp-firmware-0.0.5-factory.bin --force
And I get
dfu-util: Last page at 0x0019e6ff is not writeable
I think the NCP update wants to be applied via
particle flash --serial and you should use this binary
However, rc.25 has still got issues that may prevent you from connecting to WiFi for various reasons. rc.26 has solved a lot of these.
I would try rc.26 it’s not release yet, is there a way to get it now?
Have to wait a little bit longer. Shouldn’t be too long anymore though.
I just tried to connect my argon on my s9 wifi hotspot and it worked flawlessly. My home wifi still refuse to let the argon connect
Hey folks! Wanted to make sure that everyone is aware that we’ve released a new version of device firmware (rc.26) that aims to address some of the first order issues affecting Android Bluetooth connectivity issues (failure to connect to device, failure to update Device OS).
After updating your devices, please restart your Particle app to ensure that the Bluetooth configuration settings are refreshed.
Instructions for updating are available here:
@will Thanks for letting us know
I just upgraded to rc26.
rc25 = fast blinking green
rc26 = fast blinking green then turquoise (like it’s trying to connect to wifi) but never does
Tried on both ios and android.
I connected the argon rc25 on my s9 hotspot in seconds. For sure there is something on my wifi network that the argon does not like. I have 9 photon connected and working flawlessly. But this argon is very stubborn.
I tried the same process with my other argon and boom! connected.
Turquoise or, “cyan”, means that the device has successfully connected to the Wi-Fi network and is attempting to connect to the Cloud. That means that the
rc.26 fix likely worked around the network issues that you were seeing.
To add to Will’s statement, you are making it to wi-fi! Hooray!
So if you are fast blinking cyan on your wifi network but are able to get online just fine with your S9, I would have to guess it’s something to do with your router or network configuration.
Particle uses port 5683 for it’s CoAP protocol to communicate out. For Photon and earlier devices, this is under TCP. It is changed for Electron + all Mesh.
See if there’s anything on your router settings that may be prohibiting this as a first step.
Well it’s December 29 2019 almost 2020 and this is still an issue. I cannot get this Argon working at all. Wouldn’t connect to the internet, it kept telling me some BS that my password is incorrect when it is correct. I jump through a bunch of hoops to get it connected, DNS IPV6… Finally got it connected and I went to flash some code to it using the web IDE and now it’s in a dead loop. blue and red light like it’s being flashed then dead with no lights and then back to the blue and red light. It’s caught in this loop. Where is quality control? Particle is slipping up. Putting out frustrating flawed products. Please fix this. Even the error that my password is wrong is stupid. Have an error that says what the issue is. Now I have to return 80 of these. argggggggghhhh…
Could it be that your device is in safe mode, trying to update from an outdated deviceOS? Give it several minutes to see if it comes out of the red/blue (magenta).
Alternatively, place it in DFU mode, and while connected over USB issue ‘particle update’ from an up to date CLI. See if that helps?