It's not entirely clear in the description, but it sounds like data is sent to 2lemetry and then from 2lemetry it's sent to your server via POST.
It's too bad that you can't just send data directly, but I guess this probably means that 2lemetry will require specific structured data and will limit requests. They say the limit is TBD which is pretty vague and not very inspiring.
2lemetry is running an MQTT broker - MQTT is a standard protocol designed by OASIS for these sorts of low-power, low-bandwidth scenarios. It's a pub/sub system and you'll probably get away with a few messages per minute. I think the 2G hardware might be the limiting factor here.
We are modeling data limits around scenarios where a sensor value is sent to an HTTP endpoint once or twice per minute. Expect final rate limits to be in that range. For specific questions on increased rate usage, please email us at info@2lemetry.com. Higher end plans are available.
Comments
It's not entirely clear in the description, but it sounds like data is sent to 2lemetry and then from 2lemetry it's sent to your server via POST.
It's too bad that you can't just send data directly, but I guess this probably means that 2lemetry will require specific structured data and will limit requests. They say the limit is TBD which is pretty vague and not very inspiring.
2lemetry is running an MQTT broker - MQTT is a standard protocol designed by OASIS for these sorts of low-power, low-bandwidth scenarios. It's a pub/sub system and you'll probably get away with a few messages per minute. I think the 2G hardware might be the limiting factor here.
Thanks, very informative.
From their faq:
Awesome, thanks.