So when you’re still in the initial flashing stage, you only need to have an USB connection to the device. Pinging the ESP won’t help because it’s probably not even connected to WiFi. Are you still in the “first flashing” stage? Then it’s probably due to the FTDI adapter not being recognized, and I don’t know too much how to help with that.
@e_jp Somehow your computer still has esphomeyaml 1.6.2 installed somewhere. I would suggest just trying to remove esphomeyaml (with
pip2 uninstall esphomeyaml and
sudo pip2 uninstall esphomeyaml) until
esphomeyaml ... run returns a
command not found. Then you can try re-installing esphomeyaml again and I hope it should work.
@pcl I’m not sure what error you’re referring to But here are a few steps that should help with all kinds of upload problems:
- Make sure the initial flashing works - So check that the first “upload” happens via USB.
- Look at the serial monitor logs (“logs” with the USB device selected in the header bar in the dashboard). Do any errors appear there? The esphomelib logs are a great place to debug these issues
- When the first upload worked and you’re now trying an OTA update, try flashing with a static IP in the
wifi:section (if the static IP points to a new host, you’ll have to reflash with USB again; unless you’re using the command line version, then you can use
- Look at the logs again, does anything show up there?