Can't connect to WiFi network about esphome-core HOT 19 CLOSED

Tried again after your latest updates, and things seems a bit better now. But something I observed along the way. I have issues connecting to Wifi when using an SSID where the PSK contains non-alphanumeric character. The first SSID has a PSK with the %-symbol, not allowing me to connect. I tried another network with a plain alphanumeric PSK, and it connected. It could not reach the mqtt-server, which is on another subnet. Tried creating a new SSID in the same subnet with the MQTT-server, and it connects to MQTT.

It seems there are routing/gateway issues in esphomelib, and of course non-alphanumeric PSK.

from esphome-core.

I also found out the SSID is case sensitive :)

from esphome-core.

I have experienced issues before with non-alpha characters in SSID, but in most projects I have tested this isn't an issue.

Subnets are not necessarily there to restrict access, but they will be if there is no route between them. In my case I have a different wlan ssid for iot-devices placed in one subnet. I'm not that into the workings of arduino libraries yet. But dhcp offers a default gateway (router) which knows the routes to the subnets.

from esphome-core.

Omg, no idea why everything suddenly works, but now i can also connect to mqtt from the ssid in the other subnet. Not sure what has been going on here, I can just assume a bad day where everything I touched went wrong 😕
Again, sorry to waster your time with something that wasn't an issue.

Logging looks great 😄

from esphome-core.

Great to see more people using this project 👍

First, you don't need to worry about the compile errors. They're just compiler warnings and don't really affect anything. Now to the not connecting part: Yes, I've also noticed it and have almost solved it.

The master github branch is not really meant to be used for setups and the latest commit has an issue that I've been trying to debug for the last ~9 hours now (debugging with the ESP8266 is a mess). Simply put, we're running out of RAM. I have a fix almost ready and will put it in the master branch in some time :)

For the time being, I would suggest you take the version from platformio like described in the Installation Instructions (working on cleaning that up... but writing docs is so cumbersome...). Create a new folder and run pio init in the created folder, next put something like this in the platformio.ini

[env:test]
platform = espressif8266
board = nodemcuv2
framework = arduino
lib_deps = esphomelib
build_flags =
    -DMQTT_MAX_PACKET_SIZE=512
    -DARDUINOJSON_ENABLE_STD_STRING

from esphome-core.

Thanks for your quick reply. I'll try using DHT with the PIO-version to verify. I only use bme/bmp280 and htu21d in my projects, that's why I wanted to use the current master version :-) But great project, I think for my kind of sensors this is way quicker than espeasy.

from esphome-core.

Hmmm, the issue about non-alphanumeric PSKs is weird; I'll look into it, but I think it would rather be a bug in the arduino core, not esphomelib... Thanks for reporting it 👍

About the subnets: I'm not a networking guy, but isn't the whole reason for subnets that they restrict access to devices within them 👀?

from esphome-core.

Would it be possible to add some println that shows information received/applied for networking, ip, mask, dns, gateway etc?

from esphome-core.

Yes, that's exactly what I just did 5 minutes ago in my testing :) 😂

Another question: on what board was this? ESP8266/ESP32? I just tried SSID: abc, Password: 123%42abc on my NodeMCU (ESP8266) and it seemed to work, I'll try with the ESP32 and some other PSKs next.

from esphome-core.

Hmm, I must have had a typo or something earlier. It failed on two Wemos D1 and one NodeMCU. Just tested again on a Wemos and ESP32 and both works with %-character now. Oops, sorry 😳

from esphome-core.

Great to hear 👍
I've now pushed a patch that improves WiFi&MQTT logging 😀

from esphome-core.

No problem :) It's always nice seeing other people see this framework. And esphomelib probably still has a ton of bugs that I need to fix. But in the end, fixing all those bugs is also very important to move the project forward 👍

from esphome-core.

Check your subnets and routes on the router as well to see if routing is allowed.

from esphome-core.

Closing this issue as the error is fixed from what I can tell from the comments

from esphome-core.

I'm currently running into problems connecting to wi-fi. Tried a build with an ESP-01 and a Huzzah and it never connects to my wi-fi. Build something in the Arduino IDE and it connects happily.

from esphome-core.

...so I've taken an Arduino IDE created program and built it in PlatformIO/Atom. Over the next few days, I'll try and get a minimum ESPHome program to build where I can "see" it and see what is different. One thing I have noticed - the Wifi setup features channel=-1 as a parameter, which I'm guessing just tells it to check all channels...

from esphome-core.

@aracdin Yes WiFi channel -1 means "use any channel". For the WiFi connectivity: Have you tried using the latest arduino framework version? Sometimes that helps (see esphomeyaml: section doc page and FAQ)

from esphome-core.

So, I tried to do a complete re-install of everything and having one platformio loaded under atom [because it's a nicer place to play :-)]. I symlinked platformio from pip freeze and pip list both show platformio==3.5.3 but pip install esphomeyaml doesn't find platformio, instead it complains
OSError: [Errno 13] Permission denied: '/usr/lib/python2.7/site-packages/platformio-3.5.3.dist-info'
which I guess is it wanting a quick sudo... So sudo it I hear the world cry. Then I get:
IOError: [Errno 40] Too many levels of symbolic links: '/usr/bin/platformio'

This feels less like python, and more like Ouroboros....still, I am learning a lot..... Question, (if you don't mind have you used esphomeyaml with platformio under Atom? Did it work?

from esphome-core.

I think folks have (in general) stopped installing things system wide unless using the system package manager (rpm/apt/etc) and use virtualenv with pip instead. You might try that?

from esphome-core.