{"action":"closed","issue":{"url":"https://api.github.com/repos/nrwiersma/ConfigManager/issues/6","repository_url":"https://api.github.com/repos/nrwiersma/ConfigManager","labels_url":"https://api.github.com/repos/nrwiersma/ConfigManager/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/nrwiersma/ConfigManager/issues/6/comments","events_url":"https://api.github.com/repos/nrwiersma/ConfigManager/issues/6/events","html_url":"https://github.com/nrwiersma/ConfigManager/issues/6","id":187557523,"number":6,"title":"AP remains available after connecting node to wifi","user":{"login":"robertoostenveld","id":899043,"avatar_url":"https://avatars.githubusercontent.com/u/899043?v=3","gravatar_id":"","url":"https://api.github.com/users/robertoostenveld","html_url":"https://github.com/robertoostenveld","followers_url":"https://api.github.com/users/robertoostenveld/followers","following_url":"https://api.github.com/users/robertoostenveld/following{/other_user}","gists_url":"https://api.github.com/users/robertoostenveld/gists{/gist_id}","starred_url":"https://api.github.com/users/robertoostenveld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robertoostenveld/subscriptions","organizations_url":"https://api.github.com/users/robertoostenveld/orgs","repos_url":"https://api.github.com/users/robertoostenveld/repos","events_url":"https://api.github.com/users/robertoostenveld/events{/privacy}","received_events_url":"https://api.github.com/users/robertoostenveld/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-06T12:03:56Z","updated_at":"2016-11-06T12:47:24Z","closed_at":"2016-11-06T12:47:24Z","body":"I noticed this with an NodeMCU ESP8266 development board. I consider it undesired behaviour that the AP remains available, as it allows anyone to reconfigure the Thing. Let me outline the steps that allow me to reproduce.\r\n\r\nWhen the Thing is not connected to my local wifi network, I see “Starting Access Point” in the serial console and can connect my laptop as follows:\r\n\r\nLaptop Wi-Fi is connected to ESP-THING and has the IP address 192.168.1.100.\r\n\r\nAll is fine and I configure the SSID and Password of my wifi router. In the serial console I can see it connecting. The ESP-THING wifi network shortly disappears, and then reappears. With the Thing  connected to my local wifi network, I can again connect to its AP as follows:\r\n\r\nLaptop Wi-Fi is connected to ESP-THING and has the IP address 192.168.4.2.\r\n\r\nIn the latter case (i.e. with the thing connected), I can access the /index.html endpoint at 192.168.1.13 (when I connect my laptop to my router network) and at 192.168.4.1 (when I connect my laptop to the ESP-THING network).\r\n\r\nWhat I do not understand is where the 192.168.4.x network comes from, as there is nothing in the code with this IP address. There is this\r\n\r\n````\r\n    IPAddress ip(192, 168, 1, 1);\r\n    WiFi.mode(WIFI_AP);\r\n    WiFi.softAPConfig(ip, ip, IPAddress(255, 255, 255, 0));\r\n    WiFi.softAP(apName);\r\n````\r\n\r\nI do not find in the code where the mode is being switched, but I get the feeling that - once connected - it is in WIFI_AP_STA and not in WIFI_STA mode.\r\n "}}
{"actor":{"display_login":"nrwiersma"}}