Re: OIC support

me and Paul brought in constrained iotivity stack few months back to Mynewt, and I probably should send an update what’s going on. I’ve been working on getting it more fully integrated. My first goal is to get the code size/RAM usage down. Just as a FYI for anyone else interested in

Re: OIC support

That is a good point. There are data models for different type of sensors/controls over there. I’m see these are at http://oneiota.org . Acceleration, humidity, temperature etc. This is very useful, and it should be easy to add another layer on top of the base driver to

Re: Mynewt iOS App

I didn't want to self promote here, but I am anyways :) We developed a Plug and Play modular sensor Architecture. you can check out the kickstarter for it here https://www.kickstarter.com/projects/pureengineering/puremodules-for-dreamers-tinkerers-hackers-and-des also more info here:

Re: Mynewt iOS App

Ah ok, I thought you were going for some kind of self contained 'Mynewt Sensor Service' which would be pretty cool in its own right but for demo purposes what you have is all you need. Brian On Thu, Dec 1, 2016 at 2:12 PM, David G. Simmons wrote: > > > On Dec 1, 2016, at 4:00

Re: NRF52dk ADC

Hi David, I have partial answers: > On Nov 29, 2016, at 8:37 AM, David G. Simmons wrote: > > > Moving on from the BLE -- which now works perfectly -- and I understand how > 'subscribed' values work in nimBLE, thanks to all who responded! > > Next up is implementing an

Re: Mynewt iOS App

> On Dec 1, 2016, at 4:00 PM, Kevin Townsend wrote: > > On 01/12/16 21:35, David G. Simmons wrote: > >> >> Rather than go through every Bluetooth device within range, connect to it, >> and see if it's offering the right service, I simply check the name of the >> device

Re: OIC support

> On Dec 1, 2016, at 12:57 PM, Kevin Townsend wrote: > >> >> Hi, >> >> me and Paul brought in constrained iotivity stack few months back >> to Mynewt, and I probably should send an update what’s going on. >> >> I’ve been working on getting it more fully integrated. My

Re: Mynewt iOS App

On 01/12/16 21:35, David G. Simmons wrote: Rather than go through every Bluetooth device within range, connect to it, and see if it's offering the right service, I simply check the name of the device and, if it's not a mynewt device, move on. This is faster than connecting to each device.

Re: OIC support

Hi, me and Paul brought in constrained iotivity stack few months back to Mynewt, and I probably should send an update what’s going on. I’ve been working on getting it more fully integrated. My first goal is to get the code size/RAM usage down. To cut down code size I’m converting it to use

Re: Mynewt iOS App

Thanks Brian, Let me try to clarify ... > On Dec 1, 2016, at 3:02 PM, Brian Giori > wrote: > > Hey, this sounds like a really cool project so just wanted to chime in. As > a preface, I'm not sure if I completely understand what you're going

OIC support

Hi, me and Paul brought in constrained iotivity stack few months back to Mynewt, and I probably should send an update what’s going on. I’ve been working on getting it more fully integrated. My first goal is to get the code size/RAM usage down. To cut down code size I’m converting it to use

Re: Mynewt iOS App

Hey, this sounds like a really cool project so just wanted to chime in. As a preface, I'm not sure if I completely understand what you're going for with this app so correct me if I'm wrong (I'm also a bit rusty). Here are my suggestions: Any MyNewt device that has "nimble" in its name will be

If using develop, upgrade newt and core at the same time

Hello all, TL;DR: If you pull core develop, be sure to pull newt develop at the same time. Otherwise, your builds will fail. I just pushed a fix to the develop branch for this issue: https://issues.apache.org/jira/browse/MYNEWT-365 Unfortunately, this fix introduces an incompatibility with the

Re: Subscription Request and Question.

Your link confounds different Bluetooth versions and different attacks. The TL;DR: LE Legacy Pairing is broken and has been known to be broken since its inception. I wrote on it in 2013[1] and released crackle[2] to demonstrate it. LE Secure Connections address all the weaknesses of legacy

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

+1 > On Nov 30, 2016, at 12:35 PM, Peter Snyder wrote: > > +1 > >> On Nov 30, 2016, at 8:31 AM, Vipul Rahane wrote: >> >> +1 (binding) >> >>> On Nov 30, 2016, at 7:09 PM, David G. Simmons wrote: >>> >>> +1 >>> On Nov 29, 2016,

Re: Mynewt iOS App

Doh!! Ok, so since actually complying with BLE standards is sort of important :-) the UUID to use is E761D2AF-1C15-4FA7-AF80-B5729020B340 which is unique, and is 128-bits. That being said, it is also noted that defined characteristics are all (save one) in the 0x2Axx range. So my choice

Re: Subscription Request and Question.

See https://pomcor.com/2015/06/03/has-bluetooth-become-secure/ Basically its a mess. As far as I can tell, the actual encryption (AES-128 CCM) is fine, but the key exchange (pairing) methods are all broken in various ways. Just Works is vulnerable to MitM by design (a reasonable trade-off for the