Adjust default reboot timeouts

esphomeyaml/changelog/index.rst

@@ -50,7 +50,10 @@ New Features
   flashing on Windows/MacOS machines **without having to install esphomeyaml**. So if esphomeyaml for some reason
   can't find your USB port, you now can use the esphomeflasher app. See :ref:`esphomeflasher`.
 
-- ESP8266s now save the states of lights/switches/... internally and restores them on boot. (:libpr:`258`)
+- ESP8266s now save the states of lights/switches/... internally and restores them on boot.
+  Additionally, esphomelib can now operate in fully offline mode if your WiFi network goes down
+  or the MQTT broker is unreachable, see :ref:`automation-networkless`
+  (:libpr:`258`, :libpr:`267`, :yamlpr:`229`)
 
 - The :doc:`Over-the-Air Update </esphomeyaml/components/ota>` process was quite buggy sometimes and the Arduino-library
   esphomelib used was doing some weird stuff. The OTA-process has now been completely re-written to be more stable

esphomeyaml/components/mqtt.rst

@@ -49,7 +49,7 @@ Configuration variables:
   for verifying SSL connections. See :ref:`mqtt-ssl_fingerprints`
   for more information.
 - **reboot_timeout** (*Optional*, :ref:`time <config-time>`): The amount of time to wait before rebooting when no
-  MQTT connection exists. Can be disabled by setting this to ``0s``. Defaults to ``60s``.
+  MQTT connection exists. Can be disabled by setting this to ``0s``. Defaults to ``5min``.
 - **keepalive** (*Optional*, :ref:`config-time`): The time
   to keep the MQTT socket alive, decreasing this can help with overall stability due to more
   WiFi traffic with more pings. Defaults to 15 seconds.

esphomeyaml/components/wifi.rst

@@ -55,7 +55,7 @@ Configuration variables:
   Defaults to ``.local``.
 - **reboot_timeout** (*Optional*, :ref:`time <config-time>`): The amount of time to wait before rebooting when no
   WiFi connection exists. Can be disabled by setting this to ``0s``, but note that the low level IP stack currently
-  seems to have issues with WiFi where a full reboot is required to get the interface back working. Defaults to ``60s``.
+  seems to have issues with WiFi where a full reboot is required to get the interface back working. Defaults to ``5min``.
 - **power_save_mode** (*Optional*, string): The power save mode for the WiFi interface. Defaults to no power saving.
   See :ref:`wifi-power_save_mode`
 - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.

esphomeyaml/guides/automations.rst

@@ -292,6 +292,19 @@ Configuration options:
   can not be restored or if state restoration is not enabled. This needs to be wrapped in quotes! Defaults to
   the C++ default value for this type (for example ``0`` for integers).
 
+.. _automation-networkless:
+
+Do Automations Work Without a Network Connection
+************************************************
+
+YES! All automations you define in esphomelib are execute on the ESP itself and will continue to
+work even if the WiFi network is down or the MQTT server is not reachable.
+
+There is one caveat though: esphomelib automatically reboots if no connection to the MQTT broker can be
+made. This is because the ESPs typically have issues in their network stacks that require a reboot to fix.
+You can adjust this behavior (or even disable automatic rebooting) using the ``reboot_timeout`` option
+in the :doc:`wifi component </esphomeyaml/components/wifi>` and :doc:`mqtt component </esphomeyaml/components/mqtt>`.
+
 All Triggers
 ------------