Can't register device on cloud [resolved]
-
Hi, i'm having this problem also. Has anyone found a workaround for this problem?
-
Upgraded my Omega2+ by 'omega2p-v0.1.8-b147.bin' and now a request of "device-client" looks like:
'ds.onion.iop/05e78737-5c64-4796-8363-a13baed034e5/listen?key=ynGNSrhqOeK9RkCxDIxoWwnInpPMmEhdGLiNCq9zCt8TqoDugapoionNa3ohCg0Sinfo'When I corrected this request (deleting parts: 'p' and 'info') and sent him by browser, than I get from OnionCloud it: {"cmd":"init"}{"cmd":"heartbeat"}
-
Updated to v0.1.8-b148.bin. Issue still not resolved
-
Until Onion sort out their cloud problems you might want to consider hooking up your Omega to the Blynk cloud. See https://wiki.onion.io/Tutorials/blynk-library and http://www.blynk.cc/getting-started/
-
I think I found where the config info is kept. /etc/config/onion Unfortunately (or fortunately depending on how you want to look at it) the info in the file is correct. Which means that whatever is reading the data is distorting the results. I believe someone mentioned libcurl may be the culprit.
-
I think someone from Onion needs to look in this damn thread and give us a manual way to get the devices on the cloud. OR fix the problem. Been a week since the last message from them...
-
Good afternoon guys.
I started using my omega2 yesterday and had a problem registering it in the cloud.
I checked the post on the curl problem. Today I performed the firmware update and now when running the device-manager, the error that appears is from the url: ds.onion.iop/ not foundMy firmware.
Codename: Ando
Model: Onion Omega2+
Revision: R1
Firmware: 0.1.8 (b148)
Latest Firmware: 0.1.7 (b139)
-
@Joarli-Leandro said in Can't register device on cloud:
Good afternoon guys.
I started using my omega2 yesterday and had a problem registering it in the cloud.
I checked the post on the curl problem. Today I performed the firmware update and now when running the device-manager, the error that appears is from the url: ds.onion.iop/ not foundMy firmware.
Codename: Ando
Model: Onion Omega2+
Revision: R1
Firmware: 0.1.8 (b148)
Latest Firmware: 0.1.7 (b139)PS. At night I update my firmware to 0.1.9 and now my cloud work. Regards
-
The Cloud connectivity issue is now fixed in v0.1.9 b149
Also, the reset button now actually triggers a reboot when pressed!
Run
oupgradeto get the latest firmware on your Omega!See our blog post for more details: https://onion.io/2017/01/more-firmware-fixes-now-with-extra-cloud/
Thank you for your patience and support! We're working hard to make the Omega the very best it can be!
Onion
-
@Lazar-Demin
Have the v0.1.9 b149 with oupgrade imported and am with the Omega2 in the onion cloud again online. Thank you Demin
-
Both of my devices are now working after the update. Now, time to work on Node-Red and getting it to work.
-
Wow. Just got back from my vacation.
Didn't expect this to explode the way it did!Glad it got fixed, thanks guys! :]
-
I'v bought three Omega2+'s, one registered and two can't, and from googling it seems to be this same issue again
Is there a workaround or fix scheduled?
Firmware versions tried so far: omega2p-v0.1.9-b158.bin and omega2p-v0.1.9-b159.bin
-
@Niels-Christensen said in Can't register device on cloud [resolved]:
I'v bought three Omega2+'s, one registered and two can't, and from googling it seems to be this same issue again
Is there a workaround or fix scheduled?
Firmware versions tried so far: omega2p-v0.1.9-b158.bin and omega2p-v0.1.9-b159.bin
Have also tried the latest firmware again: omega2p-v0.1.10-b160.bin
Still no cloud, just a popup advertising "transfer.sh", is this an issue with the registration site url being hogged by a popup?
-
@Niels-Christensen did you get working cloud already? I tried today with my Omega2 and it seems it cannot authenticate to the cloud.
-
@Tomasz-Rybicki
I didn't sadly, this issue is still outstanding for me.I've opened a new thread for my issue as it may be a new bug unrelated to this thread.
New thread found here: https://community.onion.io/topic/2204/can-t-register-device-on-cloud
-
@Niels-Christensen this is fixed now
I tweeted onion and they replied and fixed it straight away
