mbainrot / home_automation Goto Github PK

Can't remember if i fixed this bug

i.e. handle "input" messages against the directory tree

Depends on #7

Basically a message queue triggered timer

E.g
sys -> !(re)start_timer|timer_name|timeout in seconds|topic|message
sys -> !stop_timer|timer_name

PIR Controlled Sensor Light:
lifx -> !turn_on|gnffj36743
sys -> !restart_timer|kitchen_auto_off|900|lifx|!turn_off|gnffj36743

Must have the ability for the user to specify what a weekend/weekday is in the config.py

Basically think mqtt files crossed with scripting

Main feature is basic conditions, thus allowing the ability to make deviations in event chains based on say time or variables

with a given file structure such as this

/home_automation/events/custom
└── lights
    ├── all_off
    │   └── all_off.mqtt
    └── all_on
        └── all_on.mqtt

And then when you feed it the following

mosquitto_pub -t custom -m 'lights/all_on'

It works, all_on/ gets traversed and all_on.mqtt gets evaulated but this might be undesirable as in theory one can traverse up and down the tree structure

As we really should separate the LIFX api from the core :\

isc-dhcp-server dhcpd.conf example

option homeautomation-server code 200 = text;
option homeautomation-server "your ip address";

This would tell clients where your automation server is, reducing the amount of configuration required /provided/ node-mcu's firmware has a way of getting the custom dhcp options and that we can find a code that won't break anything

so people actually can use this contraption.....

Child of issue #1

Otherwise it hangs the test forever

To do...
Update .Travis.yml to copy lifx_config.example.py to lifx_config.py

Should be something liek

msg.payload.decode(encoding='ascii')

Basically scripted set of mosquito messaging queue messages

Introduced in #4535fe4

Need to test:

1. Whether server responds to sys,!register on sys_ack channel
2. It subscribes to sys_%device_mac%
3. It creates a tracking file
4. It messages the client on sys_%device_mac% with "!registered"
5. It messages the client on sys_%device_mac% with "!ping|1234"

Appears I forgot to make it return a non zero number

Check if it creates all of the folders it needs for both crontab, event triggering and finally device registration