AS608 Hardware watchdog reset and wifi problems

[boaschti]

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.
If I enable AS608 tasmota resets after about one day with Hardware Watchdog or it is disconnected from wifi. In tried a few versions and its alway th same problem. Without AS608 it runs stable.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [ x] Read the Contributing Guide and Policy and the Code of Conduct
• [x ] Searched the problem in issues
• [ x] Searched the problem in discussions
• [ x] Searched the problem in the docs
• [x ] Searched the problem in the chat
• [x ] Device used (e.g., Sonoff Basic): Wemos D1 mini
• [ x] Tasmota binary firmware version number used: Project tasmota - Tasmota Version 12.4.0.2(allsensors)-2_7_4_9(2023-03-06T16:21:42)
  • [x ] Pre-compiled
  • Self-compiled
• [ x] Flashing tools used: OTA
• Provide the output of command: Backlog Template; Module; GPIO 255:

  Configuration output here:
14:22:25.287 CMD: Backlog Template; Module; GPIO 255
14:22:25.353 MQT: stat/tuerpanel/RESULT = {"NAME":"Generic","GPIO":[1,1,1,1,1,1,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}
14:22:25.590 MQT: stat/tuerpanel/RESULT = {"Module":{"18":"Generic"}}
14:22:25.847 MQT: stat/tuerpanel/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"5504":"AS608 Tx"},"GPIO2":{"224":"Relay1"},"GPIO3":{"5536":"AS608 Rx"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"194":"Switch_n3"},"GPIO13":{"161":"Switch2"},"GPIO14":{"160":"Switch1"},"GPIO15":{"225":"Relay2"},"GPIO16":{"163":"Switch4"},"GPIO17":{"0":"None"}}

• If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:
14:23:09.270 CMD: Backlog Rule1; Rule2; Rule3
14:23:09.338 MQT: stat/tuerpanel/RESULT = {"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":58,"Free":453,"Rules":"ON switch1#state DO publish cmnd/ring2/power %value% ENDON"}}
14:23:09.579 MQT: stat/tuerpanel/RESULT = {"Rule2":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
14:23:09.829 MQT: stat/tuerpanel/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}

• Provide the output of this command: Status 0:

  STATUS 0 output here:
14:23:43.829 CMD: Status 0
14:23:43.838 MQT: stat/tuerpanel/STATUS = {"Status":{"Module":18,"DeviceName":"Tasmota","FriendlyName":["TuerPanel","Tasmota2"],"Topic":"tuerpanel","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[3,0,15,15,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
14:23:43.876 MQT: stat/tuerpanel/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-DE.bin.gz","RestartReason":"Power On","Uptime":"0T00:07:12","StartupUTC":"2023-03-11T13:16:31","Sleep":50,"CfgHolder":4617,"BootCount":79,"BCResetTime":"2020-10-17T20:06:41","SaveCount":5902,"SaveAddress":"F4000"}}
14:23:43.908 MQT: stat/tuerpanel/STATUS2 = {"StatusFWR":{"Version":"12.4.0.2(allsensors)","BuildDateTime":"2023-03-06T16:21:42","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"403/699"}}
14:23:43.930 MQT: stat/tuerpanel/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["SmartHomeZeig","Servus nachad!"],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A002800000000","00000080","00006000","00004000","00000000"]}}
14:23:43.978 MQT: stat/tuerpanel/STATUS4 = {"StatusMEM":{"ProgramSize":742,"Free":260,"Heap":14,"ProgramFlashSize":1024,"FlashSize":4096,"FlashChipId":"164020","FlashFrequency":40,"FlashMode":"DOUT","Features":["00000809","8F908787","04146001","FFFFB7CF","8F7417FB","303E0AD3","1159785A","26204FFF","5408F0F3","00000080"],"Drivers":"1,2,3,4,7,8,9,10,12,14,15,20,21,24,28,29,34,43,47,50,60,62,66","Sensors":"1,2,3,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,24,26,27,29,30,31,32,38,40,41,42,44,45,46,50,51,54,55,56,57,58,59,63,64,65,66,67,70,71,72,73,74,75,76,78,79,81,82,85,86,88,89,90,91,92,93","I2CDriver":"1,2,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,28,29,30,31,32,34,35,36,40,41,42,43,44,45,46,48,49,50,51,52,53,55,56,58,60,61,62,63"}}
14:23:44.002 MQT: stat/tuerpanel/STATUS5 = {"StatusNET":{"Hostname":"tuerpanel","IPAddress":"192.168.178.30","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.1","DNSServer2":"0.0.0.0","Mac":"50:02:91:FE:55:40","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
14:23:44.024 MQT: stat/tuerpanel/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.178.38","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_FE5540","MqttUser":"mqttClients","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
14:23:44.049 MQT: stat/tuerpanel/STATUS7 = {"StatusTIM":{"UTC":"2023-03-11T13:23:44","Local":"2023-03-11T14:23:44","StartDST":"2023-03-26T02:00:00","EndDST":"2023-10-29T03:00:00","Timezone":"+01:00","Sunrise":"07:12","Sunset":"18:47"}}
14:23:44.072 MQT: stat/tuerpanel/STATUS10 = {"StatusSNS":{"Time":"2023-03-11T14:23:44","Switch1":"OFF","Switch2":"OFF","Switch3":"OFF","Switch4":"OFF"}}
14:23:44.085 MQT: stat/tuerpanel/STATUS11 = {"StatusSTS":{"Time":"2023-03-11T14:23:44","Uptime":"0T00:07:13","UptimeSec":433,"Heap":14,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":177,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"SmartHomeZeig","BSSId":"00:E0:4C:13:96:F9","Channel":11,"Mode":"11n","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:03"}}}

• Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:
enable AS608 with connected sensor and wait.

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[Pipitapi]

If such a programme were included. It would be nice. I have no contact every 2-3 days!
https://www.reddit.com/r/tasmota/comments/nvdedp/comment/h14nxac/
https://www.reddit.com/r/tasmota/comments/imgakh/possible_resetting_the_routers_power_if_it_doesnt/

[MaceMoneta]

I just use a simple rule:

on Time#Minute|5 do ping8 routerIP endon on Ping#routerIP#Success==0 do restart 1 endon

Replace the two occurrences of 'routerIP' with your router's IP address. Every five minutes it will ping the router. If it gets no response, it will restart the module. I have this running on over 100 assorted modules.

[pawol]

the command ping8 is not available in regular (precompiled) builds

[sfromis]

Indeed, you may have to build to include features you want.

[pawol]

https://gregology.net/2020/12/router-rebooter/
There you can download and try tasmota 9.1 compiled with ping8, regular expressions and if statement.
Works lik a charm as watchdog :)

I prefer this implementation:
PowerOnState 5
PulseTime 100
Rule1 ON Time#Minute|10 DO Ping8 192.168.2.1 ENDON ON Ping#192.168.2.1#Success==0 DO Backlog Power1 0; ENDON
Rule1 1
Reset 1

Power state 5 ensures immunity against power instabilities in case of lost power and ensures power on state after Pulsetime time.
Implementation sends 8 pings to 192.168.2.1 every 10 minutes and if there are 0
successful responses, it powers off the router for 10 seconds, then powers it back on.

In my opinion USE_PING, USE_EXPRESSION, & SUPPORT_IF_STATEMENT should be implemented by default in precompiled builds :)

[davlaw]

ping8 set me back a sec too, but is tasmota command ping or ping#, where # equals # of packets to send...

[barbudor]

The command is Ping but like many commands can take an index such as with Power1
In the case of Ping, the index is used to specify the number of ping packets to send. If not specified it is equivalent to Ping1 (just like Power == Power1)

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[arendst]

Is this still an issue?

[pawol]

@arendst
Is it possible to add USE_PING, USE_EXPRESSION, & SUPPORT_IF_STATEMENT in the precompiled builds ?

[boaschti]

Yes. I already tried a better LDO for supplying the sensor and ESP.
I can try it with a new ESP. But i have to unmount it from my door for this test, if i find any time for this.
Can i do some additional test to find out what is going on here?

[boaschti]

Ping and automatically reset is no solution for me. Sometimes if ESP got stuck my door bell on same device also rings. (But not on reeboot!!!) But here I have to double check hardware, if the pulldown and everything else is working.