Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
446 views
Skip to first unread message
Jibun no Kage
Oct 19, 2023, 2:56:11 PM10/19/23
to TasmotaUsers
Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1? I can flash lite and core tasmota 13.1 or 13.2 fine. I get the typical 192.168.4.1 AP setup. But then things go weird. My android phone will not connect to 192.168.4.1 no matter what I try, just get connection failed. My PC via wireless will connect to 192.168.4.1 on the ESP8266, but once I enter my SSID and passphrase, the ESP8266 reports "00:01:28.564 WIF: Connect failed as AP cannot be reached". And I am stuck. This has happened on 4 different ESP8266 (wemos d1) modules. I just flashed 4 band new sonoff S31 switches yesterday with no issues, happen to be using 13.1.0.1, but apparently 13.2 came out just today? Maybe a bug?
Philip Knowles
Oct 19, 2023, 3:08:46 PM10/19/23
to Jibun no Kage, TasmotaUsers
According to the release notes nothing really has changed. Which bin did you flash with? The best way to flash a device is to use the Web Installer on the Tasmota website as it does the WifI connection for you.
Sent from Mail for Windows
--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com.
Jibun no Kage .
Oct 19, 2023, 5:12:15 PM10/19/23
to Philip Knowles, TasmotaUsers
Phil,
Thanks for the reply, I was able to re-flash with 9.3.1, and now the
WiFi if working on the modules. I plan to move forward to each official
release and see where things break again. I know for a fact, that 13.2
via OTA breaks the WiFi communication.
Below is the hardware specification for the ESP8266 modules that are
having issues. I have been using Tasmota for many years, this is first
time I have seen the WiFi just flat out refuse to communicate like this.
As I said, I could not even get my phone to connect to 192.168.4.1 on
13.2, and inconsistently with my PC wireless.
As a counter point, 9.3.1 worked as expected, straight from initial
flash, not hiccups or quirks at all.
-JnK
Sonoff Basic Module
Tasmota
Program Version 9.3.1(lite)
Build Date & Time 2021-03-09T16:12:49
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 0T00:02:18
Flash write Count 7 at 0xF5000
Boot Count 3
Restart Reason Software/System restart
Friendly Name 1 Tasmota
AP1 SSId (RSSI) DD (78%, -61 dBm)
Hostname tasmota_XXXXXX-XXXX
MAC Address XX:XX:XX:XX:XX:XX
IP Address (wifi) 192.168.1.218
Gateway 192.168.1.2
Subnet Mask 255.255.255.0
DNS Server 192.168.1.253
MQTT Host
MQTT Port 1883
MQTT User DVES_USER
MQTT Client DVES_8FF589
MQTT Topic tasmota_%06X
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota_8FF589/
MQTT Fallback Topic cmnd/DVES_8FF589_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 9434505
Flash Chip Id 0x1640EF
Flash Size 4096 kB
Program Flash Size 4096 kB
Program Size 479 kB
Free Program Space 524 kB
Free Memory 30.9 kB
On 10/19/2023 12:08 PM, Philip Knowles wrote:
> According to the release notes nothing really has changed. Which bin did
> you flash with? The best way to flash a device is to use the Web
> Installer on the Tasmota website as it does the WifI connection for you.
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
>
> *From: *Jibun no Kage <mailto:jibun...@gmail.com>
> *Sent: *19 October 2023 19:56
> *To: *TasmotaUsers <mailto:sonof...@googlegroups.com>
> *Subject: *Tasmota 13.x drop support for older ESP8266 devices, such as
>
Thanks for the reply, I was able to re-flash with 9.3.1, and now the
WiFi if working on the modules. I plan to move forward to each official
release and see where things break again. I know for a fact, that 13.2
via OTA breaks the WiFi communication.
Below is the hardware specification for the ESP8266 modules that are
having issues. I have been using Tasmota for many years, this is first
time I have seen the WiFi just flat out refuse to communicate like this.
As I said, I could not even get my phone to connect to 192.168.4.1 on
13.2, and inconsistently with my PC wireless.
As a counter point, 9.3.1 worked as expected, straight from initial
flash, not hiccups or quirks at all.
-JnK
Sonoff Basic Module
Tasmota
Program Version 9.3.1(lite)
Build Date & Time 2021-03-09T16:12:49
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 0T00:02:18
Flash write Count 7 at 0xF5000
Boot Count 3
Restart Reason Software/System restart
Friendly Name 1 Tasmota
AP1 SSId (RSSI) DD (78%, -61 dBm)
Hostname tasmota_XXXXXX-XXXX
MAC Address XX:XX:XX:XX:XX:XX
IP Address (wifi) 192.168.1.218
Gateway 192.168.1.2
Subnet Mask 255.255.255.0
DNS Server 192.168.1.253
MQTT Host
MQTT Port 1883
MQTT User DVES_USER
MQTT Client DVES_8FF589
MQTT Topic tasmota_%06X
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota_8FF589/
MQTT Fallback Topic cmnd/DVES_8FF589_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 9434505
Flash Chip Id 0x1640EF
Flash Size 4096 kB
Program Flash Size 4096 kB
Program Size 479 kB
Free Program Space 524 kB
Free Memory 30.9 kB
On 10/19/2023 12:08 PM, Philip Knowles wrote:
> According to the release notes nothing really has changed. Which bin did
> you flash with? The best way to flash a device is to use the Web
> Installer on the Tasmota website as it does the WifI connection for you.
>
>
> *From: *Jibun no Kage <mailto:jibun...@gmail.com>
> *Sent: *19 October 2023 19:56
> *To: *TasmotaUsers <mailto:sonof...@googlegroups.com>
> *Subject: *Tasmota 13.x drop support for older ESP8266 devices, such as
> wemos d1?
>
> Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
> I can flash lite and core tasmota 13.1 or 13.2 fine. I get the typical
> 192.168.4.1 AP setup. But then things go weird. My android phone will
> not connect to 192.168.4.1 no matter what I try, just get connection
> failed. My PC via wireless will connect to 192.168.4.1 on the ESP8266,
> but once I enter my SSID and passphrase, the ESP8266 reports
> "00:01:28.564 WIF: Connect failed as AP cannot be reached". And I am
> stuck. This has happened on 4 different ESP8266 (wemos d1) modules. I
> just flashed 4 band new sonoff S31 switches yesterday with no issues,
> happen to be using 13.1.0.1, but apparently 13.2 came out just today?
> Maybe a bug?
>
> --
> You received this message because you are subscribed to the Google
> Groups "TasmotaUsers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sonoffusers...@googlegroups.com
> <mailto:sonoffusers...@googlegroups.com>.
>
> Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
> I can flash lite and core tasmota 13.1 or 13.2 fine. I get the typical
> 192.168.4.1 AP setup. But then things go weird. My android phone will
> not connect to 192.168.4.1 no matter what I try, just get connection
> failed. My PC via wireless will connect to 192.168.4.1 on the ESP8266,
> but once I enter my SSID and passphrase, the ESP8266 reports
> "00:01:28.564 WIF: Connect failed as AP cannot be reached". And I am
> stuck. This has happened on 4 different ESP8266 (wemos d1) modules. I
> just flashed 4 band new sonoff S31 switches yesterday with no issues,
> happen to be using 13.1.0.1, but apparently 13.2 came out just today?
> Maybe a bug?
>
> --
> You received this message because you are subscribed to the Google
> Groups "TasmotaUsers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sonoffusers...@googlegroups.com
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com <https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
Philip Knowles
Oct 20, 2023, 2:06:39 AM10/20/23
to Jibun no Kage ., TasmotaUsers
You would have been better flashing with 13.1 (I know that works with ESP8266 but I've just upgraded a Sonoff TH from 12.1 to 13.2 without any issues). You've also flashed a 'lite' version. You have a 'strange' DNS server - I would expect it to be your gateway.
Sent from
Outlook for Android
From: Jibun no Kage . <jibun...@gmail.com>
Sent: Thursday, October 19, 2023 10:12:10 PM
To: Philip Knowles <knowles...@gmail.com>; TasmotaUsers <sonof...@googlegroups.com>
Subject: Re: Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
Sent: Thursday, October 19, 2023 10:12:10 PM
To: Philip Knowles <knowles...@gmail.com>; TasmotaUsers <sonof...@googlegroups.com>
Subject: Re: Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
Jibun no Kage .
Oct 20, 2023, 2:23:54 AM10/20/23
to Philip Knowles, TasmotaUsers
Yes, I did more testing this evening, and 9.3.1 works, as does 12.0.2,
etc., even 13.0 worked, but once I tried 13.1 or 13.2 (even lite) things
broke. The Wemos ESP8266s go into an endless loop failing to connect to
the access point. So something has changed/resulted specific to the
older Wemos ESP8266s I have. The ESP8266 memory size does not seem to
be an issue, I tested on 4MB ESP8266s and 1MB older ESP01Ss (using lite
variant), the issue is persistent as noted above, specific to the Wemos
devices, exhibit the issue consistently. But other variants, at least
the ones I have, don't exhibit the behavior, nor do any of other ESP8266
based Smart devices I have, for example Sonoff S31s. Really is an
interesting issue. For what I am doing I can live with older firmware
image on the Wemos ESP8266 variants.
I don't use 192.168.1.1 at all, since that is the default for various
routers when reset. My gateway is pro/customer firewall/appliance, not
your typical consumer ISP router/cable modem. I have a local DNS
server, which really can be any IP address on the local LAN segment,
.253 in my case. DNS does not care, nor does any DHCP server. It is
common to use .1, or lower .X references for infrastructure devices, but
not required. For example Google uses 8.8.8.8 and 8.8.4.4 for its
public DNS servers. Where my local ISP uses x.x.x.61 and x.x.x.62 for
example. So I am not sure what a 'strange' IP address is for a DNS
server. Where I worked for years as IT support our gateways were always
.1 and .129, and DNS servers always .2 and .130, just happened to be the
establish standard.
-Jnk
On 10/19/2023 11:06 PM, Philip Knowles wrote:
> You would have been better flashing with 13.1 (I know that works with
> ESP8266 but I've just upgraded a Sonoff TH from 12.1 to 13.2 without
> any issues). You've also flashed a 'lite' version. You have a 'strange'
> DNS server - I would expect it to be your gateway.
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Jibun no Kage . <jibun...@gmail.com>
> *Sent:* Thursday, October 19, 2023 10:12:10 PM
> *To:* Philip Knowles <knowles...@gmail.com>; TasmotaUsers
> <sonof...@googlegroups.com>
> *Subject:* Re: Tasmota 13.x drop support for older ESP8266 devices, such
>> *From: *Jibun no Kage <mailto:jibun...@gmail.com <mailto:jibun...@gmail.com>>
>>
etc., even 13.0 worked, but once I tried 13.1 or 13.2 (even lite) things
broke. The Wemos ESP8266s go into an endless loop failing to connect to
the access point. So something has changed/resulted specific to the
older Wemos ESP8266s I have. The ESP8266 memory size does not seem to
be an issue, I tested on 4MB ESP8266s and 1MB older ESP01Ss (using lite
variant), the issue is persistent as noted above, specific to the Wemos
devices, exhibit the issue consistently. But other variants, at least
the ones I have, don't exhibit the behavior, nor do any of other ESP8266
based Smart devices I have, for example Sonoff S31s. Really is an
interesting issue. For what I am doing I can live with older firmware
image on the Wemos ESP8266 variants.
I don't use 192.168.1.1 at all, since that is the default for various
routers when reset. My gateway is pro/customer firewall/appliance, not
your typical consumer ISP router/cable modem. I have a local DNS
server, which really can be any IP address on the local LAN segment,
.253 in my case. DNS does not care, nor does any DHCP server. It is
common to use .1, or lower .X references for infrastructure devices, but
not required. For example Google uses 8.8.8.8 and 8.8.4.4 for its
public DNS servers. Where my local ISP uses x.x.x.61 and x.x.x.62 for
example. So I am not sure what a 'strange' IP address is for a DNS
server. Where I worked for years as IT support our gateways were always
.1 and .129, and DNS servers always .2 and .130, just happened to be the
establish standard.
-Jnk
On 10/19/2023 11:06 PM, Philip Knowles wrote:
> You would have been better flashing with 13.1 (I know that works with
> ESP8266 but I've just upgraded a Sonoff TH from 12.1 to 13.2 without
> any issues). You've also flashed a 'lite' version. You have a 'strange'
> DNS server - I would expect it to be your gateway.
>
> ------------------------------------------------------------------------
> *From:* Jibun no Kage . <jibun...@gmail.com>
> *Sent:* Thursday, October 19, 2023 10:12:10 PM
> *To:* Philip Knowles <knowles...@gmail.com>; TasmotaUsers
> <sonof...@googlegroups.com>
> *Subject:* Re: Tasmota 13.x drop support for older ESP8266 devices, such
>> *Sent: *19 October 2023 19:56
>> *To: *TasmotaUsers <mailto:sonof...@googlegroups.com <mailto:sonof...@googlegroups.com>>
>> *Subject: *Tasmota 13.x drop support for older ESP8266 devices, such as
>> wemos d1?
>>
>> Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
>> I can flash lite and core tasmota 13.1 or 13.2 fine. I get the typical
>> 192.168.4.1 AP setup. But then things go weird. My android phone will
>> not connect to 192.168.4.1 no matter what I try, just get connection
>> failed. My PC via wireless will connect to 192.168.4.1 on the ESP8266,
>> but once I enter my SSID and passphrase, the ESP8266 reports
>> "00:01:28.564 WIF: Connect failed as AP cannot be reached". And I am
>> stuck. This has happened on 4 different ESP8266 (wemos d1) modules. I
>> just flashed 4 band new sonoff S31 switches yesterday with no issues,
>> happen to be using 13.1.0.1, but apparently 13.2 came out just today?
>> Maybe a bug?
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "TasmotaUsers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to sonoffusers...@googlegroups.com
>> <mailto:sonoffusers...@googlegroups.com
> <mailto:sonoffusers...@googlegroups.com>>.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com <https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com> <https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com?utm_medium=email&utm_source=footer <https://groups.google.com/d/msgid/sonoffusers/5730a065-c266-47b3-a4f7-ab80b850fafcn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>> wemos d1?
>>
>> Tasmota 13.x drop support for older ESP8266 devices, such as wemos d1?
>> I can flash lite and core tasmota 13.1 or 13.2 fine. I get the typical
>> 192.168.4.1 AP setup. But then things go weird. My android phone will
>> not connect to 192.168.4.1 no matter what I try, just get connection
>> failed. My PC via wireless will connect to 192.168.4.1 on the ESP8266,
>> but once I enter my SSID and passphrase, the ESP8266 reports
>> "00:01:28.564 WIF: Connect failed as AP cannot be reached". And I am
>> stuck. This has happened on 4 different ESP8266 (wemos d1) modules. I
>> just flashed 4 band new sonoff S31 switches yesterday with no issues,
>> happen to be using 13.1.0.1, but apparently 13.2 came out just today?
>> Maybe a bug?
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "TasmotaUsers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to sonoffusers...@googlegroups.com
>> <mailto:sonoffusers...@googlegroups.com
> <mailto:sonoffusers...@googlegroups.com>>.
>> To view this discussion on the web, visit
>>
Philip Knowles
Oct 20, 2023, 7:23:36 AM10/20/23
to Jibun no Kage ., TasmotaUsers
Philip Knowles
Oct 21, 2023, 4:17:24 PM10/21/23
to Jibun no Kage ., TasmotaUsers
I‘d try the Tasmota Web Installer with erase flash.
From: Jibun no Kage .
Sent: 20 October 2023 07:23
To: Philip Knowles; TasmotaUsers
Reply all
Reply to author
Forward
0 new messages