Skip to content

Latest commit

 

History

History
70 lines (67 loc) · 6.09 KB

Configuration.md

File metadata and controls

70 lines (67 loc) · 6.09 KB

Configuring Robotan

Die deutsche Version befindet sich hier.

To configure Robotan's options, go to
http://192.168.4.1/config
If you are asked for a login, the username is "Robotan" and the password is "Robotan88", unless you chose your own credentials during instalation. If Robotan is already connected to your own WiFi network, you'll have to use the IP address assigned to Robotan or try using the hostname "robotan" instead of the IP number.

Configuring WiFi network

By default, Robotan sets up its own WiFi network called "Robotan" with the password "Robotan88". If you want to access your robot from within your own WiFi network, you can enter the name of your WiFi network at "WiFi SSID" and your WiFi's password at "WiFi Password". Then click on "Set WiFi" and wait a while. If your robot does not automatically connect to your own network, you can turn off the robot and turn it on again after a few seconds.

If Robotan cannot connect to your WiFi network, for example because the password is wrong or because it is too far away to pick up a signal, Robotan will fall back to setting up its own "Robotan" network mentioned above. However, it will try every five minutes to connect again to your WiFi network. This will ensure it will re-connect to your network even if it lost signal in a remote section of your garden.
You also have the option to provide the Robotan module with a fixed IP address along with gateway, subnet and dns addresses in the configuration menu.

Configuring push notifications

Robotan can notify you in case the robot reports an error, for example when it gets stuck. To be able to send the notifications, Robotan must use your own WiFi network (see above). Robotan will call the URL defined at "Notify URL" and add the reason for the notification (i.e. "Lift Error") at the very end, so you can call an URL and pass the reason as a parameter. If you don't want the error to be passed on, then just end your URL with a #. The reason text will still be appended, but the # will basically make the text being ignored in the URL.
As of May 2020, only calls to https sites are supported!

Example for using Prowl (Apple iPhone/iPad)

Prowl is a notification app for iPhone and iPad. After you register, you can create an API key which you can send your notifications to. The URL for Robotan would look like this:
https://api.prowlapp.com/publicapi/add?apikey=INSERT YOUR API KEY HERE&application=Robotan&event=
Take note of the end of the URL: The last parameter is "event=", so Robotan will add the reason for the notification there, so that the final URL might end like "event=Lift Error"

Example for using SimplePush (Android)

SimplePush is a notification app for Android. After you've downloaded the app, you'll get a key which you can send your notifications to. The URL for Robotan would look like this:
https://api.simplepush.io/send/INSERT YOUR KEY HERE/. The error message will then be pushed to your Android device running the SimplePush app. Please take note that the URL must end with a / after the key!

Example for sending an e-mail via a PHP script

You can download and install the sendmail.php script on your own server and configure it to send an e-mail through an e-mail service of your choice. Note: Only `https` addresses are supported! The script expects the parameter "error" to be sent via a GET request like this:
https://this-is-my-server.com/sendmail.php?error=Error-Message
Please make sure that the script runs smoothly before setting it up in Robotan by calling the script from your browser. If you receive an e-mail from the script, you can use the URL in the Robotan configuration like this:
https://this-is-my-server.com/sendmail.php?error=
Then click "Set URL" and Robotan will send out a notification each time an error occurs.

Configuring stuck detection

If you have installed a ADXL335 acceleration sensor, you can activate its use here which will provide a "stuck detection" for older robots who are not able to read the error status of the robot ("Steering only"). If you get false positives when the robot is mowing, play around with the sensitivity value a bit. Higher values lead to a greater tolerance, lesser values to a lower tolerance.

Configuring GPS functions

In the configuration menu, you have the following GPS-based options:
  • Enable GPS logging
  • GPS logs will be saved every 10 seconds into the device's flash memory until the size exceeds 1 MByte after which it will automatically be deleted. You have the option to download the logs in GPX format to be displayed for example on sites like GPS Visualizer.
  • Enable GPS stuck detection
  • This is useful for older robots which do not provide access to the error messages, like when the robot is stuck. This function will evaluate the (not 100% accurate) GPS position of the robot and determine whether the robot is stuck or not. The inaccuracy radius may help to prevent false positives. Alerts will only be sent during start and end time. Please note that these times are based on the UTC timezone (which is in summer two hours behind the rest of central Europe. The position of the base (garage) helps to prevent false positives when the robot is in the garage (and therefore looks as being 'stuck').
  • Enable geo-fencing
  • You may provide coordinates of your garden here. Once the robot leaves these coordinates (e.g. because of theft) a message will be sent out with the current coordinates.

GPIOs direct access

Via the URL /gpio?x=y the GPIO pins of the Wemos can be accessed directly, e.g. to control a relay shield, where x is the intenral number of the GPIO pin, and y is either 0 or 1, depending on whether the pin should be low or high.