Getting Started

Version 1 (Hammel, 17 Jan 2016 19:49)

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