We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

omega2+ does not connect to Onion Cloud



  • device-client showing connect lost errors. If I enter the URL being used in a browser, I get:

    TypeError: mq.channel.publish is not a function
    at Object.mq.register.sendToQueue.sendToExchange (/var/app/current/system/mq.js:21:14)
    at /var/app/current/system/device_server_http.js:157:10
    at Array.forEach (native)
    at initConnection (/var/app/current/system/device_server_http.js:145:27)
    at /var/app/current/system/device_server_http.js:193:3
    at Layer.handle [as handle_request] (/var/app/current/node_modules/express/lib/router/layer.js:95:5)
    at next (/var/app/current/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/var/app/current/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/var/app/current/node_modules/express/lib/router/layer.js:95:5)
    at /var/app/current/node_modules/express/lib/router/index.js:281:22
    at param (/var/app/current/node_modules/express/lib/router/index.js:354:14)
    at param (/var/app/current/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/var/app/current/node_modules/express/lib/router/index.js:410:3)
    at next (/var/app/current/node_modules/express/lib/router/index.js:275:10)
    at /var/app/current/system/device_server_http.js:65:7
    at null.<anonymous> (/var/app/current/system/device_server_http.js:38:9)



  • I've just purchased 2 Omega2 units - and both of them are having this issue (not surprising given it's a server error).
    Not a good start.

    Any response from the Onion guys?

    Thanks,



  • Same issue here.

    I'm in contact with onion team on Twitter.



  • My Omega1, Omega2 and Omega2+ can not connect to Onion Cloud since August.
    onion-cloud setup command does not work.



  • I've had the same problem and some correspondence with the onion team who have been really quick and helpful in their responses.

    Speaking with the team they've explained that the Onion Cloud was originally developed as a free sandbox resource for hobbyist developers to create web-based projects for light usage. This was always an add-on from the initial offering of onion and the main development process for these boards is using the built in systems locally (http://Omega-XXXX.local/), now OnionOS (More details at https://onion.io/2bt-onion-os/ ).

    Their technical team are aware of the problem with the onion cloud and are working on it so we should see some guidance or statement on this in due course. It's worth noting however that as this was never part of the original promise of onion this doesn't necessarily represent a priority - these are my words however not theirs!

    There are many 3rd party platforms which allow you to integrate an Onion device with them and they may be more robust where management of multiple devices remotely is required - details on these services and how to get started using them can be found here - https://docs.onion.io/omega2-docs/connecting-to-cloud-platforms.html

    I know the initial part of setting up one of these devices can be frustrating, especially if some of the above is not made clear, but none of this detracts from the large amount of amazing things which are possible with these devices.



  • @Hugh-Tonking Thanks for the information. I was not really complaining; I can do what I need to do without the cloud. It is just that the device keeps trying to register with the cloud and the existing docs all talk about the Onion cloud and not the new OnionOS. Seems like this is just a transition period with some documentation in need of updating.



  • @Michael-Van-Norman No worries, didn't think you were at all šŸ™‚ I'd been going through a frustrating cycle of trying to get cloud off the ground - I think I've got about 8 copies of my board 'in the cloud' now!

    I'd seen a few posts from people in the same place as me so thought I'd share what I'd been able to find.

    I really hope that the cloud might become more permanent though. I've worked a bit with the particle.io devices and the cloud approach works really well for these, most likely due to their being far simpler devices though.



  • Ugh. Why do they send docs and have information on the web that implies otherwise? I just wasted time before looking here. I am irritated now whereas if I was told to just ignore the onion cloud bits I would have moved on and configured it by hand to use another service.



  • Am I to understand that the Onion Cloud is now defunct? I've been trying for two days to get my Omega2+ connected by following the instructions on their site with no luck. It fails to connect to my wifi, then fails to register with the cloud and finally, after re-running it for a third time, it seemed to work. Unfortunately it shows on the cloud page as offline despite the device ID being shown.
    I've had the device since the Kickstarter campaign and did have it working, but I changed my wifi system and since then I've never got it going again, does anyone have any suggestions? I'm using the current stable firmware 0.1.10 b160.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.