NeatoScheduler is a php framework, wrapped with a bootstrap interface. The framework provides a webservice that can be used to control your ESP8266 controlled neatobotvac.
Required:
- Apache 2.4.X +
- Php 5.4.16 +
To install, simply clone this repository into the folder of your choice, and run install.sh with bash. This should create the credentials (admin/password) and systems folders for you, and set the appropriate permissions. For simplicity sake, the web application creates files on disk rather than in a database.
To make the deployment of neatoscheduler simple and site configurable, we've included a config.php file that allows you to set default values for fields, as well as define additional facts that you want to add to your site. This file also includes folder paths that you can change based on your requirements. Detailed discussion of this file won't be done here, as the configuration file is marked up for ease of use. The only important field to change initially, is your current timezone as this will be used for scheduling. A list of accepted PHP timezones can be found here: http://php.net/manual/en/timezones.php
To ensure scheduled actions run when they should, you need to add a cronjob that points to the neatoCronActions.php file, that runs every minute. You can place this file anywhere on your filesystem, but be sure to update the file to point to the correct location of your webservice install path. In our example, we're using /var/www/neato/neato/.
Upon opening the webservice for the first time, you will need to login with the username "admin" and password "password". Please be sure to change this password!
- PHP permissions must be set as such, that you're able to create local files.
- Currently only works under linux. (Now that python requirements have been removed, this may no longer be the case)
- This interface only works with neato-bot ESP8266 image >= 2.0
- The api folder needs to be accessable via http and not https. This is because the 8266 has no ability to use https for accessing the api. I've included an .htaccess that prevents that redirection.