Getting Started » History » Version 1
Hammel, 17 Jan 2016 19:49
| 1 | 1 | Hammel | h2. What does it encompass |
|---|---|---|---|
| 2 | |||
| 3 | h3. voice control interface to infrastructure |
||
| 4 | |||
| 5 | * mobile |
||
| 6 | * Jarvis |
||
| 7 | * home UIs - NEST-like |
||
| 8 | * Follow-Me architecture - voice control follows you around the home. |
||
| 9 | |||
| 10 | h3. futuristic media display system |
||
| 11 | |||
| 12 | * display on glass w/ |
||
| 13 | ** static opaqueness |
||
| 14 | ** variable opaqueness |
||
| 15 | * Heads up |
||
| 16 | * Motion capture |
||
| 17 | |||
| 18 | h3. system control |
||
| 19 | |||
| 20 | * thermostatic and vent |
||
| 21 | * windows/shades/blinds |
||
| 22 | * garden |
||
| 23 | |||
| 24 | h3. robotic assistance |
||
| 25 | |||
| 26 | h3. controlled access: doors, windows, garage |
||
| 27 | |||
| 28 | h3. security cameras |
||
| 29 | |||
| 30 | h3. controllable power: outlets, lights |
||
| 31 | |||
| 32 | h3. resource management: |
||
| 33 | |||
| 34 | * what do you need (toilet paper, eggs) |
||
| 35 | |||
| 36 | h3. Monitoring: utilities |
||
| 37 | |||
| 38 | * location: humans, pets, visitors |
||
| 39 | |||
| 40 | h3. Media devices |
||
| 41 | |||
| 42 | h3. home data center |
||
| 43 | |||
| 44 | h2. Device node |
||
| 45 | |||
| 46 | Concept of a module unit so each new application doesn't need a new device. |
||
| 47 | |||
| 48 | * esp8266 for IoT |
||
| 49 | * CHiP/RPi Zero for subnodes |
||
| 50 | * RPi quad for master |
||
| 51 | * No Intel - ARM or related |
||
| 52 | * Want a reusable minimal component |
||
| 53 | |||
| 54 | h2. Products |
||
| 55 | |||
| 56 | * server box - master @ home, could have multiple, distributed in a single home |
||
| 57 | * subnode - manages a collection of devices, reports to master |
||
| 58 | * nodes - IoT, media servers - any "thing" that is an endpoint |
||
| 59 | |||
| 60 | h2. Problems |
||
| 61 | |||
| 62 | * Margins: 80-100% initially, %30 sustained |
||
| 63 | * Cost: $80 per outlet would not be reasonable |
||
| 64 | * wired network (wireline electrical)? |
||
| 65 | * wifi problems? |
||
| 66 | ** g - interference |
||
| 67 | ** n - faster, still interference? |
||
| 68 | ** ac - best? not in esp8266? |
||
| 69 | ** could we use non-wifi comm? |
||
| 70 | * Comm security |
||
| 71 | * power IoT - must last a long time |
||
| 72 | ** power harvesting |
||
| 73 | ** minimal power for comm - save most for control of device |
||
| 74 | * Mechanical experience |
||
| 75 | * Data band vs Control band |
||
| 76 | ** wifi for data |
||
| 77 | ** bluetooth or other RF for control |
||
| 78 | * No cloud - network comm is private, not to 3rd party |
||
| 79 | ** Add on: we manage a server |
||
| 80 | |||
| 81 | h2. What is the MVP? |
||
| 82 | |||
| 83 | * Proof of Concept: defined by Feb 20th |
||
| 84 | * 1st product: definition by end of April |
||
| 85 | * Danny - Jasper project working code - integrate with Jarvis? |
||
| 86 | * Mike - PiBox, builds and infrastructure, UI maybe |
||
| 87 | |||
| 88 | h2. How do we divvy the work? |
||
| 89 | |||
| 90 | * Electrical: Danny, Mike |
||
| 91 | * Software: Mike, Danny |
||
| 92 | |||
| 93 | h2. What's already out there? |
||
| 94 | |||
| 95 | * what niches are not being filled? |
||
| 96 | * what niches are we competing against? |
||
| 97 | |||
| 98 | h2. Things to look at? |
||
| 99 | |||
| 100 | * Wink - home automation/IoT company |
||
| 101 | ** app-celerator - write Javascript, compile into mobile-specific apps |
||
| 102 | * Blynk - home automation mobile dev tool |