Now we have a working central database, and can access it from our controller python code and our website php code, it is time to look at the major modules of the home hub. The table below sets out a plan of attack. As we will be switching back and forth from controller features to website features, \u00a0python to php, the plan should help with orientation. It will also help if you need to source hardware for your project.<\/p>\n\n
| Controller Task<\/th> | Electronics<\/th> | Website Task<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|
| <\/td> | <\/td> | Home page, authentication and sensor values<\/td>\n<\/tr>\n |
| Main scheduler<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| Read sensors\/Sensor helpers<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | Add real sensor<\/td> | <\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Organisation<\/td>\n<\/tr>\n |
| Alerts<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Floor plan\/Current Values<\/td>\n<\/tr>\n |
| Sampling<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Comparison Graphs<\/td>\n<\/tr>\n |
| <\/td> | Add actuator<\/td> | <\/td>\n<\/tr>\n |
| Actuators<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Actuator controls<\/td>\n<\/tr>\n |
| Conditions Rules & Actions<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Conditions<\/td>\n<\/tr>\n |
| <\/td> | <\/td> | Condition Graphs<\/td>\n<\/tr>\n |
| Rules and Actions<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| Impulses<\/td> | <\/td> | <\/td>\n<\/tr>\n |
| <\/td> | Add impulse button<\/td> | <\/td>\n<\/tr>\n |
| Long-term statistics<\/td> | <\/td> | <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n","protected":false},"excerpt":{"rendered":" Now we have a working central database, and can access it from our controller python code and our website php code, it is time to look at the major modules of the home hub. The table below sets out a plan of attack. As we will be switching back and forth from controller features to … <\/p>\n |