Tasmota crashing when ssdp:discover sent to ssdp:all

[Andy Sinclair]

Hi,

Is restarting something I can prevent in the config? The logs say:

20-01-11 18:44:16 tele/tasmota/LWT Offline

20-01-11 18:44:16 tele/tasmota/LWT Online

20-01-11 18:44:16 cmnd/tasmota/POWER

20-01-11 18:44:16 tele/tasmota/INFO1 {"Module":"BSD29","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_5F7C19_fb/","GroupTopic":"cmnd/tasmotas/"}

20-01-11 18:44:16 tele/tasmota/INFO2 {"WebServerMode":"Admin","Hostname":"tasmota-7193","IPAddress":"192.168.2.209"}

20-01-11 18:44:16 tele/tasmota/INFO3 {"RestartReason":"Software/System restart"}

20-01-11 18:44:16 stat/tasmota/RESULT {"POWER":"ON"}

20-01-11 18:44:16 stat/tasmota/POWER ON

20-01-11 18:44:17 stat/tasmota/LOGGING 18:44:16 NTP: Drift 0, (UTC) Sat Jan 11 18:44:16 2020, (DST) Sun Mar 29 01:00:00 2020, (STD) Sun Oct 25 02:00:00 2020

20-01-11 18:44:17 stat/tasmota/LOGGING 18:44:16 APP: Boot Count 99

20-01-11 18:44:17 stat/tasmota/LOGGING 18:44:16 CFG: Saved to flash at F4, Count 155, Bytes 4096

20-01-11 18:44:17 stat/tasmota/LOGGING 18:44:17 UPP: Multicast (re)joined

And this is repeated every 30 minutes:

20-01-11 16:44:16 tele/tasmota/INFO3 {"RestartReason":"Software/System restart"}

20-01-11 17:14:18 tele/tasmota/INFO3 {"RestartReason":"Software Watchdog"}

20-01-11 17:44:17 tele/tasmota/INFO3 {"RestartReason":"Software/System restart"}

20-01-11 18:14:17 tele/tasmota/INFO3 {"RestartReason":"Software/System restart"}

20-01-11 18:44:16 tele/tasmota/INFO3 {"RestartReason":"Software/System restart"}

[Andy Sinclair]

OK, found the culprit - it's an ssdp:all request which is restarting both the tuya plug and a standard ESP8266

14:14:03.481362 IP rtr.42311 > 239.255.255.250.1900: UDP, length 92

E..x......*....

.....G.l.d.`M-SEARCH * HTTP/1.1

Host:239.255.255.250:1900

ST:ssdp:all

Man:"ssdp:discover"

MX:3

Jan 12 14:14:03 tasmota-0909 ESP-UDP: Packet (92)

Jan 12 14:14:12 tasmota-0909 ESP-WIF: Connected

Jan 12 14:14:12 tasmota-0909 ESP-HTP: Web server active on tasmota-0909 with IP address 192.168.2.207

Jan 12 14:14:12 tasmota-0909 ESP-UPP: Multicast (re)joined

Jan 12 14:14:13 tasmota-0909 ESP-UPP: Multicast disabled

Jan 12 14:14:13 tasmota-0909 ESP-MQT: Attempting connection...

Jan 12 14:14:13 tasmota-0909 ESP-MQT: Connected

Jan 12 14:14:13 tasmota-0909 ESP-MQT: tele/tasmota/LWT = Online (retained)

Jan 12 14:14:13 tasmota-0909 ESP-MQT: cmnd/tasmota/POWER =

Jan 12 14:14:13 tasmota-0909 ESP-MQT: Subscribe to cmnd/tasmota/#

Jan 12 14:14:13 tasmota-0909 ESP-MQT: Subscribe to cmnd/tasmotas/#

Jan 12 14:14:13 tasmota-0909 ESP-MQT: Subscribe to cmnd/DVES_C0A38D_fb/#

Jan 12 14:14:13 tasmota-0909 ESP-MQT: tele/tasmota/INFO1 = {"Module":"Generic","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_C0A38D_fb/","GroupTopic":"cmnd/tasmotas/"}

Jan 12 14:14:13 tasmota-0909 ESP-MQT: tele/tasmota/INFO2 = {"WebServerMode":"Admin","Hostname":"tasmota-0909","IPAddress":"192.168.2.207"}

Jan 12 14:14:13 tasmota-0909 ESP-MQT: tele/tasmota/INFO3 = {"RestartReason":{"Exception":9,"Reason":"Exception","EPC":["40105f18","00000000","00000000"],"EXCVADDR":"00000003","DEPC":"00000000","CallChain":["40106149","402331d0","402415ec","402169dd","40250906","40216b3d","401016d3","402465b0","40244740","40218059","4023df20","40244740","402275a7","4024a423","40106005","4000050c","40000f68","40000f58","40243ee0","4024983d","40244700","4024b031","4024b0bf","4027f34c","402430b6","402683a0","40243ef2","402683ad","402683f2","40240743","40000f49"]}}

Jan 12 14:14:03 tasmota-7193 ESP-UDP: Packet (92)

Jan 12 14:14:04 tasmota-7193 ESP-WIF: Checking connection...

Jan 12 14:14:04 tasmota-7193 ESP-WIF: Connected

Jan 12 14:14:13 tasmota-7193 ESP-UPP: Multicast (re)joined

Jan 12 14:14:13 tasmota-7193 ESP-WIF: Connected

Jan 12 14:14:13 tasmota-7193 ESP-HTP: Web server active on tasmota-7193 with IP address 192.168.2.209

Jan 12 14:14:14 tasmota-7193 ESP-UPP: Multicast disabled

Jan 12 14:14:14 tasmota-7193 ESP-MQT: Attempting connection...

Jan 12 14:14:14 tasmota-7193 ESP-MQT: Connected

Jan 12 14:14:14 tasmota-7193 ESP-MQT: tele/tasmota/LWT = Online (retained)

Jan 12 14:14:14 tasmota-7193 ESP-MQT: cmnd/tasmota/POWER =

Jan 12 14:14:14 tasmota-7193 ESP-MQT: Subscribe to cmnd/tasmota/#

Jan 12 14:14:14 tasmota-7193 ESP-MQT: Subscribe to cmnd/tasmotas/#

Jan 12 14:14:14 tasmota-7193 ESP-MQT: Subscribe to cmnd/DVES_5F7C19_fb/#

Jan 12 14:14:14 tasmota-7193 ESP-MQT: tele/tasmota/INFO1 = {"Module":"BSD29","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_5F7C19_fb/","GroupTopic":"cmnd/tasmotas/"}

Jan 12 14:14:14 tasmota-7193 ESP-MQT: tele/tasmota/INFO2 = {"WebServerMode":"Admin","Hostname":"tasmota-7193","IPAddress":"192.168.2.209"}

Jan 12 14:14:14 tasmota-7193 ESP-MQT: tele/tasmota/INFO3 = {"RestartReason":{"Exception":9,"Reason":"Exception","EPC":["40105fbd","00000000","00000000"],"EXCVADDR":"ffffffff","DEPC":"00000000","CallChain":["40261c70","4026c745","40262583","402624ec","40261e0a","40000f49","40000f49","40000e19","40001878","40105865","4010586b","4010000d","40260e38","40260de9","401002ac","40100f25","40100f14","40246d4a","402475e1","402475e1","40246d4a","40246c80","402476e0","4027f185","401002ac","40100f25","4028204f","40282050","4028204f","4024715f","4000050c"]}}

I'm not sure why it's always an exception now but this is easily recreated with a dos file:

$ cat sendssdp.txt

M-SEARCH * HTTP/1.1

HOST:239.255.255.250:1900

ST:ssdp:all

MAN:"ssdp:discover"

MX:3

And sending it with netcat

$ cat sendssdp.txt | nc -w 3 -u 239.255.255.250 1900

It happens on both Belkin and Hue emulation, but not with no emulation. 

[Stephan Hadinger]

Interesting. Can you please open an issue on the Tasmota github repo with all these logs. Thanks

[Andy Sinclair]

Thanks - in the middle of doing it and just realised it hasn't happened at 15:14, but instead I see

15:14:05 UPP: Hue 3 response packets sent to 192.168.2.10:52467

Maybe it has something to do with the level 4 debugging that I turned down... some more tests needed I think...