<div dir="ltr">It looks like Twilio announced today that they are going to be providing access to T-mobile cellular data for IoT devices. I like the idea of pooling data cost and usage over multiple devices. <div><br></div><div><a href="http://techcrunch.com/2016/05/24/twilio-ramps-up-mobile-play-with-programmable-sims-for-iot-and-handsets-with-t-mobile/">http://techcrunch.com/2016/05/24/twilio-ramps-up-mobile-play-with-programmable-sims-for-iot-and-handsets-with-t-mobile/</a><br></div><div><br></div><div>Shane</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, May 24, 2016 at 6:46 PM Jon Wolfe via TriEmbed <<a href="mailto:triembed@triembed.org">triembed@triembed.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Don't put too much weight on what you might find in opencellID. I have<br>
firsthand experience that their dataset stinks. I have literally driven<br>
around town collecting ID's on Tmobile's network, and 90% of the ID's I<br>
saw were not in their db. I applaud the concept, I just don't think they<br>
have enough critical mass to get a reliable DB. Those same ID's were all<br>
visible in Google's commercial cell tower ID DB.<br>
<br>
<br>
<br>
<br>
On 2016-05-24 14:53, Chip McClelland via TriEmbed wrote:<br>
> Michael,<br>
><br>
> I have some experience with this - using the Adafruit FONA GPRS (2G)<br>
> modem. I will soon start playing with 3G so this might change then.<br>
><br>
> In my experience, AT&T has the better 2G network but they have<br>
> announced plans to close this offering in 2017. You should test the<br>
> T-Mobile 2G coverage at your house as it may be better. If you like,<br>
> you can look at what towers are near you with OpenCellID [1]. This is<br>
> also where the GSMLoc information comes from.<br>
><br>
> I purchase my SIM cards from <a href="http://embeddedworks.net" rel="noreferrer" target="_blank">embeddedworks.net</a> [2] a 2G plan with 5Mb<br>
> of monthly data branded as Vodafone but running on AT&T costs about<br>
> $30.<br>
><br>
> I have a number of plans for this area and I can let you or others<br>
> know if interested:<br>
> - Rewriting the software to eliminate any use of the evil Strings<br>
> data type<br>
> - Playing with different antennas - particularly directional<br>
> - Moving to 3G with either the Spark or FONA platforms<br>
> - Splitting the processing tasks on the board between the Arduino to<br>
> run the sensor and the Simblee to manage communications<br>
><br>
> I hope that helps.<br>
><br>
> Thanks,<br>
><br>
> Chip<br>
><br>
> I have tried both AT&T and T-Mobile<br>
><br>
>> On May 24, 2016, at 1:00 PM, <a href="mailto:triembed-request@triembed.org" target="_blank">triembed-request@triembed.org</a> wrote:<br>
>><br>
>> Send TriEmbed mailing list submissions to<br>
>> <a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a><br>
>><br>
>> To subscribe or unsubscribe via the World Wide Web, visit<br>
>> <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
>> or, via email, send a message with subject or body 'help' to<br>
>> <a href="mailto:triembed-request@triembed.org" target="_blank">triembed-request@triembed.org</a><br>
>><br>
>> You can reach the person managing the list at<br>
>> <a href="mailto:triembed-owner@triembed.org" target="_blank">triembed-owner@triembed.org</a><br>
>><br>
>> When replying, please edit your Subject line so it is more specific<br>
>> than "Re: Contents of TriEmbed digest..."<br>
>><br>
>> Today's Topics:<br>
>><br>
>> 1. Scott has been off the air for 1.5 weeks (Scott Hall)<br>
>> 2. Looking for advice on IoT/M2M data plans (Michael Clayton)<br>
>> 3. Re: Looking for advice on IoT/M2M data plans (Brian)<br>
>><br>
>><br>
> ----------------------------------------------------------------------<br>
>><br>
>> Message: 1<br>
>> Date: Mon, 23 May 2016 13:50:30 -0400<br>
>> From: Scott Hall <<a href="mailto:scottghall1@gmail.com" target="_blank">scottghall1@gmail.com</a>><br>
>> To: SplatSpace <<a href="mailto:durham-makerspace@googlegroups.com" target="_blank">durham-makerspace@googlegroups.com</a>>, Triangle<br>
>> Embedded Computing Interest Group <<a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a>>, Splat<br>
>> Space Board of DIrectors <<a href="mailto:board@splatspace.org" target="_blank">board@splatspace.org</a>><br>
>> Subject: [TriEmbed] Scott has been off the air for 1.5 weeks<br>
>> Message-ID:<br>
>> <CALOtY4MRMCbhVFR3faBG9i-RJi=Au32pPEW=<a href="mailto:egCjWtzaE7%2Bs3Q@mail.gmail.com" target="_blank">egCjWtzaE7+s3Q@mail.gmail.com</a>><br>
>> Content-Type: text/plain; charset="utf-8"<br>
>><br>
>> If anyone has been trying to get a hold of me, I have been without<br>
>> Internet<br>
>> service since the storms hit on the 12th, and without phone service<br>
>> since<br>
>> last Fri. as they have worked on the problem.<br>
>><br>
>> I just got back on the air.<br>
>><br>
>> --<br>
>> Scott G. Hall<br>
>> Raleigh, NC, USA<br>
>> <a href="mailto:scottghall1@gmail.com" target="_blank">scottghall1@gmail.com</a><br>
>> -------------- next part --------------<br>
>> An HTML attachment was scrubbed...<br>
>> URL:<br>
>><br>
> <<a href="http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20160523/4849106c/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20160523/4849106c/attachment-0001.html</a>><br>
>><br>
>> ------------------------------<br>
>><br>
>> Message: 2<br>
>> Date: Mon, 23 May 2016 16:01:02 -0400<br>
>> From: Michael Clayton <<a href="mailto:mwc@clayto.com" target="_blank">mwc@clayto.com</a>><br>
>> To: TriEmbed Discussion <<a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a>><br>
>> Subject: [TriEmbed] Looking for advice on IoT/M2M data plans<br>
>> Message-ID:<br>
>> <<a href="mailto:CANeRK0yvUVTXoPHKkuKYCW6p-9-BMtmUou-O1cqcQ5xJ1NX7zw@mail.gmail.com" target="_blank">CANeRK0yvUVTXoPHKkuKYCW6p-9-BMtmUou-O1cqcQ5xJ1NX7zw@mail.gmail.com</a>><br>
>> Content-Type: text/plain; charset="utf-8"<br>
>><br>
>> Hi all,<br>
>><br>
>> I'm setting up node-red ( <a href="http://nodered.org/" rel="noreferrer" target="_blank">http://nodered.org/</a> ) on a Raspberry Pi,<br>
>> to<br>
>> handle home automation/IoT stuff. Since I want it to ping me if my<br>
>> house<br>
>> is on fire, I'm looking around for device-oriented data plans, in<br>
>> case home<br>
>> Internet goes out.<br>
>><br>
>> Can anyone share their experiences with IoT/M2M data plans in the<br>
>> Triangle<br>
>> area?<br>
>><br>
>> Thanks!<br>
>><br>
>> --<br>
>> Michael Clayton<br>
>> -------------- next part --------------<br>
>> An HTML attachment was scrubbed...<br>
>> URL:<br>
>><br>
> <<a href="http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20160523/285fd083/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20160523/285fd083/attachment-0001.html</a>><br>
>><br>
>> ------------------------------<br>
>><br>
>> Message: 3<br>
>> Date: Mon, 23 May 2016 16:11:31 -0400<br>
>> From: Brian <<a href="mailto:triembed@undecidedgames.net" target="_blank">triembed@undecidedgames.net</a>><br>
>> To: <a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a><br>
>> Subject: Re: [TriEmbed] Looking for advice on IoT/M2M data plans<br>
>> Message-ID: <<a href="mailto:574363F3.6020905@undecidedgames.net" target="_blank">574363F3.6020905@undecidedgames.net</a>><br>
>> Content-Type: text/plain; charset=windows-1252; format=flowed<br>
>><br>
>> On 05/23/2016 04:01 PM, Michael Clayton via TriEmbed wrote:<br>
>><br>
>>> Can anyone share their experiences with IoT/M2M data plans in the<br>
>>> Triangle area?<br>
>><br>
>> No personal experience yet, but SparkFun recommends/resells T-Mobile<br>
>> for<br>
>> their cellular modem products. There are T-Mobile brick-and-mortars<br>
>> in<br>
>> the area, so there must be some amount of coverage...<br>
>><br>
>> -B<br>
>><br>
>> ------------------------------<br>
>><br>
>> Subject: Digest Footer<br>
>><br>
>> _______________________________________________<br>
>> TriEmbed mailing list<br>
>> <a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a><br>
>> <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
>><br>
>> ------------------------------<br>
>><br>
>> End of TriEmbed Digest, Vol 36, Issue 18<br>
>> ****************************************<br>
><br>
><br>
><br>
> Links:<br>
> ------<br>
> [1]<br>
> <a href="http://opencellid.org/#action=filters.recentlyUploadedBaseStationMeasurements&time=24" rel="noreferrer" target="_blank">http://opencellid.org/#action=filters.recentlyUploadedBaseStationMeasurements&time=24</a><br>
> [2] <a href="http://www.embeddedworks.net/m2m-data.html" rel="noreferrer" target="_blank">http://www.embeddedworks.net/m2m-data.html</a><br>
><br>
> _______________________________________________<br>
> Triangle, NC Embedded Computing mailing list<br>
> <a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a><br>
> <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
> TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a><br>
<br>
<br>
_______________________________________________<br>
Triangle, NC Embedded Computing mailing list<br>
<a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a><br>
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a><br>
</blockquote></div>