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