<pre>

Enable dallas sensor module on PIN 23

dallas:

• pin: 23
  update_interval: 60s

The sensor itself

sensor:

• platform: dallas

  flash the config fist without the sensor block

  and pick the dallas address from the log

  address: 0xCD012062C7DCFFFF
  resolution: 12
  id: mysensor
  filters:

  generate the median from 5 values to improve the quality

  the sensor will transmit a value to influxdb each 5 minutes

  • median:
    window_size: 5
    send_every: 5
    send_first_at: 5
    on_value:
    then:

    send the data

    • http_request.post:
      url: https://metrics.example.com/write?db=sensordata

      esphome is not able to verify a certificate

      verify_ssl: false
      headers:

      influxdb 1.x uses basic authorization

      In a Linux shell:

      echo -n "username:password" | base64

      Authorization: 'Basic YWxpY2U6cGFzc3dvcmQ='

      a few lines of C code to generate the influxdb request data

      https://docs.influxdata.com/influxdb/v1.8/guides/write_data/#write-data-using-the-influxdb-api

      body: !lambda |-
      char buf[64];
      sprintf(buf, "%0.1f", id(mysensor).state);
      return ((std::string) "temperature,group=outdoor,locationkey=example-sensor,stage=test,platform=esphome,sensor=dallas value="+buf).c_str();
      </pre>

When loading firmware, I get a message like Connecting ....._.....__..... and it eventually times out.

The programming application needs to reboot the ESP32 while gpio.2 is in a low state to put it in bootloader mode. The USB/Serial control pins normally do this on well designed hardware. Some hardware, especially older dev kits, have trouble holding the boot pin in the low state long enough. You might also have circuitry tied to that pin that is holding it in the wrong state.

Most dev kit modules also have a boot button connected to gpio.2. If you hold this down while the ESP32 reboots, then release it it when you see the Connecting .....___. It will usually fix the problem.

Some poorly designed hardware cannot reboot the ESP32. If this is the case you should hold the boot button, click the reset button (often labeled EN) and then release the boot button when you see the Connecting .....___

If the above ideas do not help and you are using a removable module, try programming the module with it removed from the controller.

This is not an issue with our firmware or install scripts. Please don't vent your frustration on us. contact the supplier of your part.