search

octoblu / meshblu

Meshblu is a cross-protocol IoT machine-to-machine messaging system.
https://meshblu.readme.io/
MIT License
816 stars 181 forks source link

Parent connections only work one way? #66

Closed kawaja closed 9 years ago

kawaja commented 10 years ago

I'm trying to set up a local meshblu (child) and be able to exchange messages with meshblu.octoblu.com (parent).

I can send messages from meshblu.octoblu.com to the local meshblu (parent to child), but there doesn't seem to be a mechanism to send messages the other way (child to parent).

Looking through the code, it looks like commit 4565fe8 by @monteslu added the mechanism to forward messages sent to unknown device UUIDs to the parent.

A few weeks later, commit 4caea0d removed the forwarding mechanism, as part of the mongodb scaling changes.

Was this deliberate?

chrismatthieu commented 10 years ago

The MongoDB update was to streamline NEDB support for deployments without MongoDB allowing us to deploy Meshblu to low capacity environments such as Raspberry Pis.

You should be able to still send messages to/from parent or child networks.

This may be a bug. Researching...

monteslu commented 10 years ago

This was deliberate as part of the last major refactoring. Now that sendMessage has been fully abstracted across protocols we just need to maintain separate parent client connection per node process. Will fix soon.

kawaja commented 10 years ago

cool, thanks - I'll watch out for updates

chrismatthieu commented 9 years ago

This issue has been fixed.