Problem with the notification

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
Seba12
New user
Posts: 3
Joined: 13 Nov 2020, 19:00

Problem with the notification

#1 Post by Seba12 » 13 Nov 2020, 19:10

Hello,
I have a problem with the notification, I added a simple rule and wants to have an email notification. Unfortunately sending once works and once not.
Regardless of whether I use smtp2go or other services, emails come differently, either both or one or not. Someone will tell me what I do wrong ?

the difference between the first and second attempt is 4 seconds

on Door#State do
if [Door#State]=0
gpio,2,1
pulse,2,0,50
delay 50
pulse,2,0,50
delay 50
pulse,2,0,50
timerSet,2,7
else
gpio,2,1
pulse,2,0,50
delay 50
pulse,2,0,50
delay 50
pulse,2,0,50
timerSet,3,2
endif
endon

on Rules#Timer=2 do
notify 1, "close %ip% - %lcltime%"
timerSet,2,0
endon

on Rules#Timer=3 do
notify 1, "open %ip% - %lcltime%"
timerSet,3,0
endon


Nov 13 18:54:16 X-1 EspEasy: EVENT: Door#State=0.00
Nov 13 18:54:16 X-1 EspEasy: ACT : gpio,2,1
Nov 13 18:54:16 X-1 EspEasy: Command: gpio
Nov 13 18:54:16 X-1 EspEasy: GPIO : port#2: set to 1
Nov 13 18:54:16 X-1 EspEasy: ACT : pulse,2,0,50
Nov 13 18:54:16 X-1 EspEasy: Command: pulse
Nov 13 18:54:16 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 13 18:54:16 X-1 EspEasy: ACT : delay 50
Nov 13 18:54:16 X-1 EspEasy: Command: delay
Nov 13 18:54:16 X-1 EspEasy: ACT : pulse,2,0,50
Nov 13 18:54:16 X-1 EspEasy: Command: pulse
Nov 13 18:54:16 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 13 18:54:16 X-1 EspEasy: ACT : delay 50
Nov 13 18:54:16 X-1 EspEasy: Command: delay
Nov 13 18:54:16 X-1 EspEasy: ACT : pulse,2,0,50
Nov 13 18:54:16 X-1 EspEasy: Command: pulse
Nov 13 18:54:16 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 13 18:54:16 X-1 EspEasy: ACT : timerSet,3,2
Nov 13 18:54:16 X-1 EspEasy: Command: timerSet
Nov 13 18:54:18 X-1 EspEasy: EVENT: Rules#Timer=3,1
Nov 13 18:54:18 X-1 EspEasy: ACT : notify 2, "open 192.168.43.240 - 2020-11-13 18:54:17"
Nov 13 18:54:18 X-1 EspEasy: Command: notify
Nov 13 18:54:18 X-1 EspEasy: ACT : timerSet,3,0
Nov 13 18:54:18 X-1 EspEasy: Command: timerSet
Nov 13 18:54:18 X-1 EspEasy: TIMER: disable timer
Nov 13 18:54:18 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 13 18:54:18 X-1 EspEasy: EMAIL: Error connecting to poczta.os.pl587

Nov 13 18:54:20 X-1 EspEasy: WD : Uptime 37 ConnectFailures 0 FreeMem 22216 WiFiStatus WL_CONNECTED ESPeasy internal wifi status: Conn. IP Init
Nov 13 18:54:22 X-1 EspEasy: EVENT: Rules#Timer=2,1
Nov 13 18:54:22 X-1 EspEasy: ACT : notify 2, "close 192.168.43.240 - 2020-11-13 18:54:21"
Nov 13 18:54:22 X-1 EspEasy: Command: notify
Nov 13 18:54:22 X-1 EspEasy: ACT : timerSet,2,0
Nov 13 18:54:22 X-1 EspEasy: Command: timerSet
Nov 13 18:54:22 X-1 EspEasy: TIMER: disable timer
Nov 13 18:54:22 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 13 18:54:22 X-1 EspEasy:
Nov 13 18:54:23 X-1 EspEasy: Timeout while reading input data!
Nov 13 18:54:23 X-1 EspEasy:
Nov 13 18:54:23 X-1 EspEasy: 220 poczta.os.pl ESMTP#015
Nov 13 18:54:23 X-1 EspEasy: EHLO os.pl
Nov 13 18:54:23 X-1 EspEasy: 250-poczta.os.pl#015
Nov 13 18:54:23 X-1 EspEasy: 250-STARTTLS#015
Nov 13 18:54:23 X-1 EspEasy: 250-PIPELINING#015
Nov 13 18:54:23 X-1 EspEasy: 250-8BITMIME#015
Nov 13 18:54:23 X-1 EspEasy: 250-AUTH LOGIN PLAIN#015
Nov 13 18:54:23 X-1 EspEasy: 250 SIZE 104857600#015
Nov 13 18:54:23 X-1 EspEasy: AUTH LOGIN
Nov 13 18:54:24 X-1 EspEasy: 235 ok, go ahead (#2.0.0)#015
Nov 13 18:54:24 X-1 EspEasy: MAIL FROM:<xxxx@os.pl>
Nov 13 18:54:24 X-1 EspEasy: 250 ok#015
Nov 13 18:54:24 X-1 EspEasy: Email: To xxxx@gmail.com
Nov 13 18:54:24 X-1 EspEasy: RCPT TO:<xxxx@gmail.com>
Nov 13 18:54:24 X-1 EspEasy: 250 ok#015
Nov 13 18:54:24 X-1 EspEasy: DATA
Nov 13 18:54:25 X-1 EspEasy: 354 go ahead#015
Nov 13 18:54:25 X-1 EspEasy: From: X_1 <xxxx@os.pl>#015#012To: xxxx@gmail.com#015#012Subject: Test#015#012Reply-To: X_1 <xxxx@os.pl>#015#012MIME-VERSION: 1.0#015#012Content-type: text/html; charset=UTF-8#015#012X-Mailer: EspEasy v20111#015#012#015#012close 192.168.43.240 - 2020-11-13 18:54:21#015#012.#015
Nov 13 18:54:25 X-1 EspEasy: 250 ok 1605290065 qp 18911#015
Nov 13 18:54:25 X-1 EspEasy: EMAIL: Connection Closed Successfully

User avatar
ThomasB
Normal user
Posts: 1064
Joined: 17 Jun 2018, 20:41
Location: USA

Re: Problem with the notification

#2 Post by ThomasB » 13 Nov 2020, 21:29

Try this:
- Go to Tools-Advanced page.
- Check (enable) the Force WiFi B/G box.
- Check (enable) the Periodical send Gratuitous ARP box.
- Submit page (save settings).
- Reboot.

Does this improve the email reliability?

Also during your tests please confirm that ESPEasy's WiFi RSSI value has reliable signal strength. For example, -73dBm or better.

BTW, you don't need the timer disable statements in the two timer rule events. I suggest removing these:

Code: Select all

timerSet,2,0
timerSet,3,0
- Thomas

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Problem with the notification

#3 Post by TD-er » 13 Nov 2020, 23:06

I did a query for the name server for your domain and right now I don't get a reply

Code: Select all

gijs@DESKTOP-QLB7N8I:~$ dig ns poczta.os.pl

; <<>> DiG 9.16.1-Ubuntu <<>> ns poczta.os.pl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5309
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;poczta.os.pl.                  IN      NS

;; Query time: 130 msec
;; SERVER: 172.24.240.1#53(172.24.240.1)
;; WHEN: Fri Nov 13 23:02:36 CET 2020
;; MSG SIZE  rcvd: 30
But a moment ago I could fetch its IP-address, so I know it does somehow work (probably cached somewhere)

So it does seem like there may be a DNS issue with this domain as I am not able to query the DNS records to see what nameservers are responsible for this domain.
This then also is a possible explanation for why it sometimes works and sometimes it doesn't.

Edit:
Now I do receive the NS records:

Code: Select all

gijs@DESKTOP-QLB7N8I:~$ dig ns poczta.os.pl

; <<>> DiG 9.16.1-Ubuntu <<>> ns poczta.os.pl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11220
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;poczta.os.pl.                  IN      NS

;; AUTHORITY SECTION:
os.pl.                  43188   IN      NS      ns3.os.pl.
os.pl.                  43188   IN      NS      ns1.os.pl.
os.pl.                  43188   IN      NS      ns2.os.pl.

;; Query time: 90 msec
;; SERVER: 172.24.240.1#53(172.24.240.1)
;; WHEN: Fri Nov 13 23:06:43 CET 2020
;; MSG SIZE  rcvd: 84

mrwee
Normal user
Posts: 225
Joined: 31 Aug 2016, 12:52

Re: Problem with the notification

#4 Post by mrwee » 14 Nov 2020, 11:07

Remember that ESPEasy does not support encrypted SMTP. The hostname "poczta.os.pl587" indicates that either you've misconfigured it, or ESPEasy doesn't show the port correctly. Should it be: "poczta.os.pl:587"?

You can use https://mxtoolbox.com to test the mailserver, and e.g. also use telnet to see the response from the mailserver.
e.g. "telnet poczta.os.pl:587"

User avatar
ThomasB
Normal user
Posts: 1064
Joined: 17 Jun 2018, 20:41
Location: USA

Re: Problem with the notification

#5 Post by ThomasB » 14 Nov 2020, 19:38

The hostname "poczta.os.pl587" indicates that either you've misconfigured it, or ESPEasy doesn't show the port correctly.
ESPEasy's log string formatting is the reason for the mangled message. Here's the addlog statement.

Code: Select all

addLog(LOG_LEVEL_DEBUG, String(F("EMAIL: Connecting to ")) + aHost + notificationsettings.Port);
As I understand the OP's complaint, emails are intermittent and the problem occurs using several different email servers. Would be nice to know more details, such as the names to the other servers that were tried, and screenshots of the settings in the plugin.

Reviewing the logs, the first email experienced a timeout due to something like server no-response or connectivity. The second email log entry indicates a successfully sent email. So that would suggest that the Plugin's settings are valid.

FWIW, I'm using email Notifications on all of my ESPEasy nodes. I have no complaints, it's very reliable. My SMTP account is from my hosted domain, port 587. So I can confirm the Notification plugin works.

- Thomas

Seba12
New user
Posts: 3
Joined: 13 Nov 2020, 19:00

Re: Problem with the notification

#6 Post by Seba12 » 18 Nov 2020, 18:16

Hi, unfortunately I still have problems with sending email.
In my espeasy I don't have the option "Periodical send Gratuitous ARP box", once it sends and once it doesn't !?!?
I've already tried to change my domain to IP, different SMTP servers and still the same.

Free RAM: 20744
Heap Max Free Block: 18752
Heap Fragmentation: 10%
Free Stack: 3664
Wifi: 802.11N (RSSI -63 dB)
IP Config: DHCP
IP / Subnet: 192.168.43.240 / 255.255.255.0
Gateway: 192.168.43.1
Client IP: 192.168.43.115
DNS: 192.168.43.1 / (IP unset)
Allowed IP Range: 192.168.43.0 - 192.168.43.255
STA MAC: 84:F3:EB:DB:52:C7
AP MAC: 86:F3:EB:DB:52:C7
SSID: SEBA (8C:F5:A3:41:85:28)
Channel: 6
Connected: 10h56m
Last Disconnect Reason: (201) No AP found
Number Reconnects: 3
WiFi Settings
Force WiFi B/G: true
Restart WiFi Lost Conn: true
Force WiFi No Sleep: false
Connection Failure Threshold: 30

Firmware
Build:⋄ 20111 - Mega
System Libraries:⋄ ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support
Git Build:⋄
Plugin Count:⋄ 46 [Normal]
Build Origin: Travis
Build Time:⋄ Nov 2 2020 13:13:15
Binary Filename:⋄ ESP_Easy_mega_20201102_normal_ESP8266_4M1M
Build Platform:⋄ Linux-4.19.104-microsoft-standard-x86_64-with-glibc2.29
Git HEAD:⋄ mega-20201102_ca0be3f


Nov 18 17:58:47 X-1 EspEasy: HTTP: GPIO,12,1
Nov 18 17:58:47 X-1 EspEasy: Command: GPIO
Nov 18 17:58:47 X-1 EspEasy: GPIO : port#12: set to 1
Nov 18 17:58:47 X-1 EspEasy: SW : GPIO=12 State=0 Output value=0
Nov 18 17:58:47 X-1 EspEasy: EVENT: Door#State=0.00
Nov 18 17:58:47 X-1 EspEasy: ACT : gpio,2,1
Nov 18 17:58:47 X-1 EspEasy: Command: gpio
Nov 18 17:58:47 X-1 EspEasy: GPIO : port#2: set to 1
Nov 18 17:58:47 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:58:47 X-1 EspEasy: Command: pulse
Nov 18 17:58:47 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:58:47 X-1 EspEasy: ACT : delay 50
Nov 18 17:58:47 X-1 EspEasy: Command: delay
Nov 18 17:58:47 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:58:47 X-1 EspEasy: Command: pulse
Nov 18 17:58:47 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:58:47 X-1 EspEasy: ACT : delay 50
Nov 18 17:58:47 X-1 EspEasy: Command: delay
Nov 18 17:58:47 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:58:47 X-1 EspEasy: Command: pulse
Nov 18 17:58:47 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:58:47 X-1 EspEasy: ACT : timerSet,2,7
Nov 18 17:58:47 X-1 EspEasy: Command: timerSet
Nov 18 17:58:54 X-1 EspEasy: EVENT: Rules#Timer=2,1
Nov 18 17:58:54 X-1 EspEasy: ACT : notify 2, "close 192.168.43.240 - 2020-11-18 17:58:53"
Nov 18 17:58:54 X-1 EspEasy: Command: notify
Nov 18 17:58:54 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 18 17:58:54 X-1 EspEasy:
Nov 18 17:58:56 X-1 EspEasy: Timeout while reading input data!
Nov 18 17:58:56 X-1 EspEasy:
Nov 18 17:58:56 X-1 EspEasy: 220 poczta.os.pl ESMTP#015
Nov 18 17:58:56 X-1 EspEasy: EHLO os.pl
Nov 18 17:58:56 X-1 EspEasy: 250-poczta.os.pl#015
Nov 18 17:58:56 X-1 EspEasy: 250-STARTTLS#015
Nov 18 17:58:56 X-1 EspEasy: 250-PIPELINING#015
Nov 18 17:58:56 X-1 EspEasy: 250-8BITMIME#015
Nov 18 17:58:56 X-1 EspEasy: 250-AUTH LOGIN PLAIN#015
Nov 18 17:58:56 X-1 EspEasy: 250 SIZE 104857600#015
Nov 18 17:58:56 X-1 EspEasy: 235 ok, go ahead (#2.0.0)#015
Nov 18 17:58:56 X-1 EspEasy: MAIL FROM:<xxxx@os.pl>
Nov 18 17:58:56 X-1 EspEasy: 250 ok#015
Nov 18 17:58:56 X-1 EspEasy: Email: To xxxx@gmail.com
Nov 18 17:58:56 X-1 EspEasy: RCPT TO:<xxxx@gmail.com>
Nov 18 17:58:56 X-1 EspEasy: 250 ok#015
Nov 18 17:58:56 X-1 EspEasy: DATA
Nov 18 17:58:57 X-1 EspEasy: 354 go ahead#015
Nov 18 17:58:57 X-1 EspEasy: From: xxxx<xxxx@os.pl>#015#012To: xxxx@gmail.com#015#012Subject: xxx#015#012Reply-To: xxxx<xxxx@os.pl>#015#012MIME-VERSION: 1.0#015#012Content-type: text/html; charset=UTF-8#015#012X-Mailer: EspEasy v20111#015#012#015#012close 192.168.43.240 - 2020-11-18 17:58:53#015#012.#015
Nov 18 17:58:57 X-1 EspEasy: 250 ok 1605718737 qp 1774#015
Nov 18 17:58:57 X-1 EspEasy: EMAIL: Connection Closed Successfully

Nov 18 17:59:00 X-1 EspEasy: SYS : -63.00,11.38
Nov 18 17:59:00 X-1 EspEasy: EVENT: SysInfo#Rssi=-63.00
Nov 18 17:59:00 X-1 EspEasy: EVENT: SysInfo#Load=11.38
Nov 18 17:59:00 X-1 EspEasy: EVENT: Clock#Time=Wed,17:59
Nov 18 17:59:04 X-1 EspEasy: WD : Uptime 2875 ConnectFailures 0 FreeMem 22376 WiFiStatus WL_CONNECTED ESPeasy internal wifi status: Conn. IP Init
Nov 18 17:59:04 X-1 EspEasy: HTTP: GPIO,12,1
Nov 18 17:59:04 X-1 EspEasy: Command: GPIO
Nov 18 17:59:04 X-1 EspEasy: GPIO : port#12: set to 1
Nov 18 17:59:04 X-1 EspEasy: SW : GPIO=12 State=0 Output value=0
Nov 18 17:59:04 X-1 EspEasy: EVENT: Door#State=0.00
Nov 18 17:59:04 X-1 EspEasy: ACT : gpio,2,1
Nov 18 17:59:04 X-1 EspEasy: Command: gpio
Nov 18 17:59:04 X-1 EspEasy: GPIO : port#2: set to 1
Nov 18 17:59:04 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:59:04 X-1 EspEasy: Command: pulse
Nov 18 17:59:04 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:59:04 X-1 EspEasy: ACT : delay 50
Nov 18 17:59:04 X-1 EspEasy: Command: delay
Nov 18 17:59:05 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:59:05 X-1 EspEasy: Command: pulse
Nov 18 17:59:05 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:59:05 X-1 EspEasy: ACT : delay 50
Nov 18 17:59:05 X-1 EspEasy: Command: delay
Nov 18 17:59:05 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 17:59:05 X-1 EspEasy: Command: pulse
Nov 18 17:59:05 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 17:59:05 X-1 EspEasy: ACT : timerSet,2,7
Nov 18 17:59:05 X-1 EspEasy: Command: timerSet
Nov 18 17:59:12 X-1 EspEasy: EVENT: Rules#Timer=2,1
Nov 18 17:59:12 X-1 EspEasy: ACT : notify 2, "close 192.168.43.240 - 2020-11-18 17:59:11"
Nov 18 17:59:12 X-1 EspEasy: Command: notify
Nov 18 17:59:12 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 18 17:59:12 X-1 EspEasy: EMAIL: Error connecting to poczta.os.pl587




Nov 18 18:03:43 xxxx EspEasy: EMAIL: Connecting to mail.smtp2go.com2525
Nov 18 18:03:43 xxxx EspEasy: 220 mail.smtp2go.com ESMTP Exim 4.92-S2G Wed, 18 Nov 2020 17:03:43 +0000#015
Nov 18 18:03:43 xxxx EspEasy: EHLO smtp2go.com
Nov 18 18:03:43 xxxx EspEasy: 250-mail.smtp2go.com Hello smtp2go.com [37.225.51.134]#015
Nov 18 18:03:43 xxxx EspEasy: 250-SIZE 52428800#015
Nov 18 18:03:43 xxxx EspEasy: 250-8BITMIME#015
Nov 18 18:03:43 xxxx EspEasy: 250-DSN#015
Nov 18 18:03:43 xxxx EspEasy: 250-PIPELINING#015
Nov 18 18:03:43 xxxx EspEasy: 250-AUTH CRAM-MD5 PLAIN LOGIN#015
Nov 18 18:03:43 xxxx EspEasy: 250-CHUNKING#015
Nov 18 18:03:43 xxxx EspEasy: 250-STARTTLS#015
Nov 18 18:03:43 xxxx EspEasy: 250-PRDR#015
Nov 18 18:03:43 xxxx EspEasy: 250 HELP#015
Nov 18 18:03:44 xxxx EspEasy: 235 Authentication succeeded#015
Nov 18 18:03:44 xxxx EspEasy: MAIL FROM:<xxxx@smtp2go.com>
Nov 18 18:03:44 xxxx EspEasy: 250 OK#015
Nov 18 18:03:44 xxxx EspEasy: Email: To xxxx@gmail.com
Nov 18 18:03:44 xxxx EspEasy: RCPT TO:<xxxx@gmail.com>
Nov 18 18:03:44 xxxx EspEasy: 250 Accepted <xxxx@gmail.com>#015
Nov 18 18:03:44 xxxx EspEasy: DATA
Nov 18 18:03:45 xxxx EspEasy: 354 Enter message, ending with "." on a line by itself#015
Nov 18 18:03:45 xxxx EspEasy: From: xxxx<xxxx@smtp2go.com>#015#012To: xxxx@gmail.com#015#012Subject: test#015#012Reply-To: xxxx<xxxx@smtp2go.com>#015#012MIME-VERSION: 1.0#015#012Content-type: text/html; charset=UTF-8#015#012X-Mailer: EspEasy v20111#015#012#015#012192.168.43.240 - 2020-11-18 18:03:42#015#012.#015
Nov 18 18:03:45 xxxx EspEasy: 250 OK id=1kfQrw-9EFLBN-V8#015
Nov 18 18:03:45 xxxx EspEasy: EMAIL: Connection Closed Successfully

Nov 18 18:03:56 xxxx EspEasy: EMAIL: Connecting to mail.smtp2go.com2525
Nov 18 18:03:56 xxxx EspEasy: EMAIL: Error connecting to mail.smtp2go.com2525

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Problem with the notification

#7 Post by TD-er » 18 Nov 2020, 18:52

Could there be a send rate limit on both mail hosts?
I notice you try again withing a few seconds.

Seba12
New user
Posts: 3
Joined: 13 Nov 2020, 19:00

Re: Problem with the notification

#8 Post by Seba12 » 18 Nov 2020, 19:36

Time does not matter here, even if I send every 10 minutes the effect is the same. The behavior is random.
On smtp2go there is a limit of 1000 emails per month,
there is no limit on os.poczta.pl. I don't know what it is about anymore.
WiFi comes from a router or phone but the effect is identical. What other services offer smtp without encryption ? Maybe the problem lies with smtp servers ?

difference of ~2 minutes

Nov 18 19:41:17 X-1 EspEasy: HTTP: GPIO,12,1
Nov 18 19:41:17 X-1 EspEasy: Command: GPIO
Nov 18 19:41:17 X-1 EspEasy: GPIO : port#12: set to 1
Nov 18 19:41:17 X-1 EspEasy: SW : GPIO=12 State=0 Output value=0
Nov 18 19:41:17 X-1 EspEasy: EVENT: Door#State=0.00
Nov 18 19:41:17 X-1 EspEasy: ACT : gpio,2,1
Nov 18 19:41:17 X-1 EspEasy: Command: gpio
Nov 18 19:41:17 X-1 EspEasy: GPIO : port#2: set to 1
Nov 18 19:41:17 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:41:17 X-1 EspEasy: Command: pulse
Nov 18 19:41:17 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:41:17 X-1 EspEasy: ACT : delay 50
Nov 18 19:41:17 X-1 EspEasy: Command: delay
Nov 18 19:41:17 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:41:17 X-1 EspEasy: Command: pulse
Nov 18 19:41:17 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:41:17 X-1 EspEasy: ACT : delay 50
Nov 18 19:41:17 X-1 EspEasy: Command: delay
Nov 18 19:41:17 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:41:17 X-1 EspEasy: Command: pulse
Nov 18 19:41:17 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:41:17 X-1 EspEasy: ACT : timerSet,2,7
Nov 18 19:41:17 X-1 EspEasy: Command: timerSet
Nov 18 19:41:24 X-1 EspEasy: EVENT: Rules#Timer=2,1
Nov 18 19:41:24 X-1 EspEasy: ACT : notify 2, "close 192.168.43.240 - 2020-11-18 19:41:23"
Nov 18 19:41:24 X-1 EspEasy: Command: notify
Nov 18 19:41:24 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 18 19:41:24 X-1 EspEasy: EMAIL: Error connecting to poczta.os.pl587

Nov 18 19:43:14 X-1 EspEasy: HTTP: GPIO,12,1
Nov 18 19:43:14 X-1 EspEasy: Command: GPIO
Nov 18 19:43:14 X-1 EspEasy: GPIO : port#12: set to 1
Nov 18 19:43:15 X-1 EspEasy: SW : GPIO=12 State=0 Output value=0
Nov 18 19:43:15 X-1 EspEasy: EVENT: Drzwi#State=0.00
Nov 18 19:43:15 X-1 EspEasy: ACT : gpio,2,1
Nov 18 19:43:15 X-1 EspEasy: Command: gpio
Nov 18 19:43:15 X-1 EspEasy: GPIO : port#2: set to 1
Nov 18 19:43:15 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:43:15 X-1 EspEasy: Command: pulse
Nov 18 19:43:15 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:43:15 X-1 EspEasy: ACT : delay 50
Nov 18 19:43:15 X-1 EspEasy: Command: delay
Nov 18 19:43:15 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:43:15 X-1 EspEasy: Command: pulse
Nov 18 19:43:15 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:43:15 X-1 EspEasy: ACT : delay 50
Nov 18 19:43:15 X-1 EspEasy: Command: delay
Nov 18 19:43:15 X-1 EspEasy: ACT : pulse,2,0,50
Nov 18 19:43:15 X-1 EspEasy: Command: pulse
Nov 18 19:43:15 X-1 EspEasy: GPIO : port 2. Pulse set for 50 ms
Nov 18 19:43:15 X-1 EspEasy: ACT : timerSet,2,7
Nov 18 19:43:15 X-1 EspEasy: Command: timerSet
Nov 18 19:43:22 X-1 EspEasy: EVENT: Rules#Timer=2,1
Nov 18 19:43:22 X-1 EspEasy: ACT : notify 2, "close 192.168.43.240 - 2020-11-18 19:43:21"
Nov 18 19:43:22 X-1 EspEasy: Command: notify
Nov 18 19:43:22 X-1 EspEasy: EMAIL: Connecting to poczta.os.pl587
Nov 18 19:43:22 X-1 EspEasy:
Nov 18 19:43:23 X-1 EspEasy: Timeout while reading input data!
Nov 18 19:43:23 X-1 EspEasy:
Nov 18 19:43:23 X-1 EspEasy: 220 poczta.os.pl ESMTP#015
Nov 18 19:43:23 X-1 EspEasy: EHLO os.pl
Nov 18 19:43:23 X-1 EspEasy: 250-poczta.os.pl#015
Nov 18 19:43:23 X-1 EspEasy: 250-STARTTLS#015
Nov 18 19:43:23 X-1 EspEasy: 250-PIPELINING#015
Nov 18 19:43:23 X-1 EspEasy: 250-8BITMIME#015
Nov 18 19:43:23 X-1 EspEasy: 250-AUTH LOGIN PLAIN#015
Nov 18 19:43:23 X-1 EspEasy: 250 SIZE 104857600#015
Nov 18 19:43:24 X-1 EspEasy: 235 ok, go ahead (#2.0.0)#015
Nov 18 19:43:24 X-1 EspEasy: MAIL FROM:<xxxx@os.pl>
Nov 18 19:43:24 X-1 EspEasy: 250 ok#015
Nov 18 19:43:24 X-1 EspEasy: Email: To xxxx@gmail.com
Nov 18 19:43:24 X-1 EspEasy: RCPT TO:<xxxx@gmail.com>
Nov 18 19:43:24 X-1 EspEasy: 250 ok#015
Nov 18 19:43:24 X-1 EspEasy: DATA
Nov 18 19:43:25 X-1 EspEasy: 354 go ahead#015
Nov 18 19:43:25 X-1 EspEasy: From: xxx <xxxx@os.pl>#015#012To: xxxx@gmail.com#015#012Subject: test#015#012Reply-To: xxx<xxxx@os.pl>#015#012MIME-VERSION: 1.0#015#012Content-type: text/html; charset=UTF-8#015#012X-Mailer: EspEasy v20111#015#012#015#012close 192.168.43.240 - 2020-11-18 19:43:21#015#012.#015
Nov 18 19:43:25 X-1 EspEasy: 250 ok 1605725005 qp 24164#015
Nov 18 19:43:25 X-1 EspEasy: EMAIL: Connection Closed Successfully

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Problem with the notification

#9 Post by TD-er » 18 Nov 2020, 20:47

I still think it is a DNS issue....
See my attempt here to simply query what name server records the domain has:

Code: Select all

gijs@DESKTOP-QLB7N8I:~/GitHub/letscontrolit/ESPEasy$ dig ns poczta.os.pl

; <<>> DiG 9.16.1-Ubuntu <<>> ns poczta.os.pl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2722
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;poczta.os.pl.                  IN      NS

;; Query time: 140 msec
;; SERVER: 172.22.80.1#53(172.22.80.1)
;; WHEN: Wed Nov 18 20:44:14 CET 2020
;; MSG SIZE  rcvd: 30
In other words... no answer.

And a few seconds later...

Code: Select all

gijs@DESKTOP-QLB7N8I:~/GitHub/letscontrolit/ESPEasy$ dig ns poczta.os.pl

; <<>> DiG 9.16.1-Ubuntu <<>> ns poczta.os.pl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63737
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;poczta.os.pl.                  IN      NS

;; AUTHORITY SECTION:
os.pl.                  14398   IN      NS      ns3.os.pl.
os.pl.                  14398   IN      NS      ns2.os.pl.
os.pl.                  14398   IN      NS      ns1.os.pl.

;; Query time: 50 msec
;; SERVER: 172.22.80.1#53(172.22.80.1)
;; WHEN: Wed Nov 18 20:45:59 CET 2020
;; MSG SIZE  rcvd: 84
Can you add a ping task and ping to os.pl right before trying to send out a message?

mrwee
Normal user
Posts: 225
Joined: 31 Aug 2016, 12:52

Re: Problem with the notification

#10 Post by mrwee » 18 Nov 2020, 20:51

Well from your log, it seems like SMTP connection does work.
Have you tried e.g. pinging the host for a long time to check stability?
Have you tried testing with regular e-mail program or e.g. https://sourceforge.net/projects/blat/?

It's becoming increasingly difficult to find e-mail hosts which does not require encryption, due to privacy issues but I assume there are still some out there.

Post Reply

Who is online

Users browsing this forum: No registered users and 33 guests