@@hendetta I would say that's a good comparison. There's no explicit limitation on throuput, and once in the other side of the "bridge" , the mesh algorithm takes on additional targeted hops as necessary to complete the delivery. I have had to temporarily disable the cloud service in the past few days, as the mesh algorithm has changed substantially, and the cloud capability needs to be tweaked to take full advantage.
Barely started looking i to off grid communication this year and im not tech savvy. So doesnt this kind of defeat the whole purpose of what this was intended for?
There are certain circumstances where cloud is useful. If you have Internet available intermittently or satellite based internet, it just adds another option for messages to go any distance, while still maintaining the privacy and protections. It's totally an optional thing, and cloud/internet is not necessary or required for ChatterBox to work. There are certain distances you're just not going to get using meshing/LoRa alone, and for people who need that as an option, it's there.
There are parts of the world where some days internet/cell is available and some days it's not. If you think that could ever be a possibility, that would be one scenario where this could be useful.
@@mattcalhoun61at an additional monthly cost. How is this more beneficial than MQTT? Already paid $70+ for 3 licenses and. Now cloud is a monthly charge? The level of adoption isn’t there yet. The UI is shiny but it’s a walled garden.
@RandyAllman I wouldn't say it's more beneficial than mqtt, almost the same thing, this just was designed to require zero config for the user. Either way, whoever hosts a service (mqtt or otherwise), someone has to pay for the bandwidth and resources. That's the reason for the monthly fee if someone wants a cloud bridge.
Is this similar to the MQTT on meshtastic? Thanks.
@@hendetta I would say that's a good comparison. There's no explicit limitation on throuput, and once in the other side of the "bridge" , the mesh algorithm takes on additional targeted hops as necessary to complete the delivery.
I have had to temporarily disable the cloud service in the past few days, as the mesh algorithm has changed substantially, and the cloud capability needs to be tweaked to take full advantage.
Barely started looking i to off grid communication this year and im not tech savvy.
So doesnt this kind of defeat the whole purpose of what this was intended for?
There are certain circumstances where cloud is useful. If you have Internet available intermittently or satellite based internet, it just adds another option for messages to go any distance, while still maintaining the privacy and protections.
It's totally an optional thing, and cloud/internet is not necessary or required for ChatterBox to work. There are certain distances you're just not going to get using meshing/LoRa alone, and for people who need that as an option, it's there.
There are parts of the world where some days internet/cell is available and some days it's not. If you think that could ever be a possibility, that would be one scenario where this could be useful.
@@mattcalhoun61at an additional monthly cost. How is this more beneficial than MQTT? Already paid $70+ for 3 licenses and. Now cloud is a monthly charge? The level of adoption isn’t there yet. The UI is shiny but it’s a walled garden.
@RandyAllman I wouldn't say it's more beneficial than mqtt, almost the same thing, this just was designed to require zero config for the user. Either way, whoever hosts a service (mqtt or otherwise), someone has to pay for the bandwidth and resources. That's the reason for the monthly fee if someone wants a cloud bridge.
@RandyAllman some people would actually prefer a walled garden, depending on why they're using a system like this , so cloud is disabled by default