Unable to get device to connect to wifi #1366
Comments
|
I tried a "reset 1" and it seemed to try a few more times to connect and then was able to fully connect... Then I reset it by unplugging it in and then plugging it back in, and it failed to associate again Any idea why this seems so "temperamental" ? |
|
Argh, I have tried 5 Sonoff basics and I am getting the same behavior from each... Very frustrating.. |
|
Did you enter your wifi config in the user_config.h before ? Did u connect to the tasmota wifi manager and enter your wifi config? |
|
@reloxx13 - Thanks for the response... so I am going to answer your questions below, inline
Yes, I put my wifi config in user_config.h before flashing.
This part has never been entirely clear to me... I have this right now and what would you have me change this to? Also when is it necessary to change this value ?
I was under the impression that this was unnecessary when puting the credentials in user_config.h.
Thanks again |
|
Changing the config_holder does not help because he already executes a "reset 2". This securely wipes out any strange config for sure.
|
The SSID I setup for testing is dyer-iot. I also specifically used a simplistic password that has no special characters ( dyeriotsecret ).
There is no mac filter on the router.
I am using the default config, which AFAIK mean's it will do DHCP. I have included the wifi section is below #define STA_SSID1 "dyer-iot" // [Ssid1] Wifi SSID
#define STA_PASS1 "dyeriotsecret" // [Password1] Wifi password
#define STA_SSID2 "indebuurt2" // [Ssid2] Optional alternate AP Wifi SSID
#define STA_PASS2 "VnsqrtnrsddbrN" // [Password2] Optional alternate AP Wifi password
#define WIFI_CONFIG_TOOL WIFI_WPSCONFIG // [WifiConfig] Default tool if wifi fails to connect \
// (WIFI_RESTART, WIFI_SMARTCONFIG, WIFI_MANAGER, WIFI_WPSCONFIG, WIFI_RETRY, WIFI_WAIT) |
|
Please check on your router, if you have assigned an IP to the device. In the firmware you can, but with "reset 2" you're for sure back on DHCP You can also look which IP is/was assigned last time and ping it. If you get a reply you have a problem :-) |
|
If you go to WIFI_MANAGER as a failover configuration you should be able to connect to the AP of the ESP itself and discover for the Wifi networks the devices can see. Maybe this gives you more insight into the problem. |
|
On Fri, 15 Dec 2017, John Dyer wrote:
> => than did you change the config holder in the top section of user_config.h?
This part has never been entirely clear to me... I have this right now
```
#define CFG_HOLDER 0x20161209 // [Reset 1] Change this value to load following default configuration parameters
```
and what would you have me change this to? Also when is it necessary to change this value ?
When Tamota starts up, it looks in the existing config on the flash to see if
the value of CFG_HOLDER is there. If it is, Tasmota assumes that the config
there is valid and ignores whatever is compiled into user_config.h
If it's not there, it replaces the config in the flash with what's in
user_config.h
so whenever you want to override whatever is in the existing config with what
you have compiled into the image, you need to change the CFG_HOLDER value (or
hold button0 for 4 seconds (if you haven't disabled it), or issue the reset
command to tell it to replace the config with what was compiled into
user_config.h)
David Lang
|
|
@DavidLang - just increment the serial by 1 each time ? |
|
hey, yes, in- or decrement, doesnt matter. it just has te be not the same as before. i usually just change the last number to a diffrent number. |
|
On Fri, 15 Dec 2017, John Dyer wrote:
@DavidLang - just increment the serial by 1 each time ?
just making it different than before, it doesn't matter how it's different.
It looks like arendst is using the date there, and that's a good convention, but
all that matters is that it's different.
|
|
I think it might have something to do w/ the Meraki AP, though I have no idea what... I tried having it connect to the AP on my iPhone ( Tethering mode ) and it worked first time.. I have my Meraki set to 2.4 and 5ghz, WPA2.... not really sure what the heck it could be... |
|
Hi @johntdyer did you find any solution on this problem? I have the exact same issues except, that my TH16 isn´t connecting to any AP, including AndoridAP and iOS-Hotspot... |
|
@johntdyer I also have a Meraki AP and was experiencing this problem. Before this happened, I set it to a fixed IP. Setting it back to dynamic solves the issue, however, it then get an IP address I might not want it to have. |
|
Strange thing is, that instead of getting the same IP after resetting it, it gets a different IP (even though it's recognized as the same device). |
|
@niklasfink - Honestly I never got it working on Meraki and finally gave up and switched everything to Unifi and it worked first try... I know thats probably not the answer you were looking for.... |
|
@davidelang Thank you for your explanation on the CFG_HOLDER! I have a Sonoff S31 and it was failing to reconnect to my WIFI AP after a power outage. I reflashed a few times with no luck. I just changed that number for CFG_HOLDER, recompiled and reflashed, and bingo! |
|
Yes, this can happen. I requested a CRC check for the configuration to detect a defect. But this was declined. The problem is, that the device is not detecting the defect configuration at boot time and start with bullshit. Sometimes it start and just do not connect, sometimes it just reboot all the time. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stale
bot
added
the
stale
|
Gents, I have the same issue with my Meraki MR53 and MR32 AP's after flashing my Sonoff devices with Tasmota FW. I tried all possible combinations and no success! I have more than 30 Sonoff devices at home with stock FW and they work perfectly with my Meraki AP's so is there any workaround to make them work with Tasmota and Meraki? Thanks, |
stale
bot
removed
the
stale
|
There seems to be a new issue with the 6.0.0a firmware. I had the same problem getting connected to my Fritzbox and with this change it now works again. No idea about side effects. I have deleted/comment out the command in support.ino near line 1000
Please give Feedback, if this works for you, because this is intresting for the rest of the community |
Fix possible wifi connection problem (#1366)
|
stefanbode, thanks for the feedback but searching inside the "support.ino" I found 3 lines with the same command.
Thanks, |
|
Interesting to know. I was expecting it only once. Anyhow I would comment ALL of the lines out. The command itself seems to have some problems. |
|
Ok, testing now... I will let you know the results. |
|
Just tested by removing the "WiFi.persistent(false); // Solve possible wifi init errors" from "support.ino" but unfortunately this didn't work! same problem.....
|
|
can you double check on the INFO. "status 2" that the build time is correct and you really have the NEW firmware up and running.
|
|
sure here is the output.! |
|
I also had to revert 20a5395 , because all of my Sonoffs get time out and no wifi connection - multiple different access points are in use here. |
|
How to revert to 20a5395 ? |
|
I have my own repository so I reverted back all changes done by 20a5395 |
|
This is committed 4 hours ago, but I am strugling with the WiFi issue from yesterday morning !!! When I stated to flash my devices with Tasmota ! |
|
You may have this problem longer (I also use AVM Routers) but after this fix the problems you described happend for me too. I had never seen this problem before. And after the revert the problems for me are gone. |
|
Hi, I have just tested the actual v6.0.0b and works for me without problems. So, I think that your issue is not Tasmota code or any commit, could be a config issue or a compilation issue. I found that sometimes platformio compiles but the firmware have wifi issues. With just compiling twice, and then do the upload, the wifi issues are gone. If you compile with arduino ide, this weird behaviour is not there. There is an open issue at platformio with this at: Hope this helps |
|
Ok, so I deleted all WiFi clients and DHCP reservations from my Meraki and then I flashed my Sonoff with |
|
Great! Good to know that now it is working for you! 👍 |
|
Thanks ascillato2 for the hint - twice compiling fix my problems |
|
Ascillato, from where you got the 6.0.0b version? |
|
From this repository. In the readme say v6.0.0a but in the code say v6.0.0b
El jue., 28 de jun. de 2018 17:45, senadaruc <[email protected]>
escribió:
… Ascillato, from where you got the 6.0.0b version?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1366 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h-yEmmpFMoVad1eFR_kN7TM7q2DNks5uBUBngaJpZM4RCyEO>
.
|
|
Ok, and can you please compile a bin file for me so I can flash directly? |
|
Thanks, |
Fix possible wifi connection problem (arendst#1366)
|
I had same problem and I solved following these tasmota oficial steps (with termite) using-serial-terminal After send the command Backlog ssid1 ; password1 <your_password>; ssid2 <your_ssid2>; password2 <your_password> device connected automatically. IMPORTANT: put always ssid1 and ssid2 even if it is the same. |
S20 Sonoff ( Firmware 5.10.0a)
Serial Logs:
I jhave tried re-flashing many times but it doesnt seem to help. Appreciate any suggestions
The text was updated successfully, but these errors were encountered: