Sendmail - Send email and text notifications, (notification device) no local server needed

weird my other server sees the update i just tried it.

My bad, I wasn't managing it through HPM. :man_facepalming:

did you guys manually install v3 from v2.. if so you will need to match it up with hpm, that is my guess. because it switched to 2 files.

1 Like

No, that is my issue. :man_facepalming:

2 Likes

I'm suspecting twins...

:man_facepalming: :man_facepalming:

2 Likes

Hmm, on my Primary Hub I'm getting "send failed" but the emails are coming through. Any ideas?

Screen Shot 2022-10-24 at 9.26.14 am

you can ignore that.. that can and happens a lot depending on the order the responses come back after the email was sent/socket was closed, but if you want to investigate further you can post the detailed debug log and i can see if i can lessen how often it happens..

1 Like

Cool, no biggy - I was just confused because everything looked good.

was that with testing the new multiple emails.. if so make sure both addresses were delivered otherwise it could really be a problem with the implementation with your server for some reason. As it is possible the first would be delivered but not the second if some error came back at that point.

No, it was every test I tried - they all worked. The thing that confused me the most was my secondary hub doesn't throw the errors.

The ony difference is I just swapped drivers on my second hub - on my main hub I made a new driver and used the swap device utility.

ya weird you sure you updated both becuase i was getting something like that recently and that was why i had a revision a while ago, due to that fact that since a new f/w update the socket now seems to close immediately upon issuance of the quit command with more data coming back later, whereas previously i physically had to issue a closeConnection () call.. Something must have changed in the telnet library.

You probably should double check that both the parent and child were updated on that hub and if so post a debug log so i can see. Especially if it is only occuring on one of your hubs.

my guess is that both driver code bases were not swapped. on one of the hubs. probably not the child.

It's odd - I just did a clean device and re-config and the issue persists.

Parent:

dev:4952022-10-24 09:44:22.661 AMdebugctime = 1666565062648 start time = 1666564864435, status = Complete, diff in secs = 198, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:44:22.658 AMdebugctime = 1666565062648 start time = 1666564864386, status = Complete, diff in secs = 198, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:44:22.656 AMdebugctime = 1666565062648 start time = 1666564864332, status = Complete, diff in secs = 198, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:44:22.653 AMdebugctime = 1666565062648 start time = 1666564864280, status = Complete, diff in secs = 198, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:44:22.650 AMdebugLooping through all 5 elements in the array so see if any timed out
dev:4952022-10-24 09:44:22.647 AMdebugChecking message array for timed out messages: timeout = 120 !
dev:4952022-10-24 09:44:00.442 AMdebug--> after lock release status permits now avail = 1
dev:4952022-10-24 09:44:00.439 AMinfoSent Message via child(1): test 800
dev:4952022-10-24 09:44:00.436 AMdebug-->acquired status lock locks now avail = 0
dev:4952022-10-24 09:44:00.433 AMdebugnumber of status mutex permits - 1
dev:4952022-10-24 09:44:00.430 AMdebugin update status new status = Completed
dev:4952022-10-24 09:43:51.744 AMdebugctime = 1666565031726 start time = 1666564864435, status = Complete, diff in secs = 167, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:43:51.741 AMdebugctime = 1666565031726 start time = 1666564864386, status = Complete, diff in secs = 167, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:43:51.737 AMdebugctime = 1666565031726 start time = 1666564864332, status = Complete, diff in secs = 167, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:43:51.735 AMdebugctime = 1666565031726 start time = 1666564864280, status = Complete, diff in secs = 167, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:43:51.732 AMdebugctime = 1666565031726 start time = 1666565031614, status = In Process, diff in secs = 0, attempts = 1, RetryCount = 3
dev:4952022-10-24 09:43:51.729 AMdebugLooping through all 5 elements in the array so see if any timed out
dev:4952022-10-24 09:43:51.726 AMdebugChecking message array for timed out messages: timeout = 120 !
dev:4952022-10-24 09:43:51.684 AMdebugScheduling wakeup job to run in 120 seconds.
dev:4952022-10-24 09:43:51.632 AMdebugelement retrieved = [1, more test, Completed, 1666564941571, 1]
dev:4952022-10-24 09:43:51.630 AMdebugin update for processing start indeix = 1 message = test 800 start time = 1666565031614
dev:4952022-10-24 09:43:51.627 AMdebuggot the child now calling function to send the mail now = 1666565031614
dev:4952022-10-24 09:43:51.624 AMdebugGot free child: 1 for processing!
dev:4952022-10-24 09:43:51.622 AMdebugFound Free Element id: 0, [1, more test, Completed, 1666564941571, 1]!
dev:4952022-10-24 09:43:51.619 AMdebugLooping through all 5 elements in the array to find first free one (!= In Process)
dev:4952022-10-24 09:43:51.616 AMdebugGot mutex
dev:4952022-10-24 09:43:51.613 AMdebugGetting free child for processing
dev:4952022-10-24 09:43:51.607 AMdebug-------> In lgk sendmail Version (4.8)

Child:

dev:29592022-10-24 09:44:01.112 AMdebugIn quit case
dev:29592022-10-24 09:44:01.109 AMdebugGot server response 221 value = 2.0.0 lastCommand = (other)
dev:29592022-10-24 09:44:01.106 AMdebuglastCommand = other
dev:29592022-10-24 09:44:01.103 AMdebugIn parse - 221 2.0.0 Bye
dev:29592022-10-24 09:44:01.081 AMdebugGot server response 250 value = 2.0.0 lastCommand = (other)
dev:29592022-10-24 09:44:01.069 AMdebuglastCommand = other
dev:29592022-10-24 09:44:01.066 AMdebugIn parse - 250 2.0.0 Ok: queued as 8314F1A00022
dev:29592022-10-24 09:44:01.037 AMdebugGot server response 354 value = End lastCommand = (Sent Ok)
dev:29592022-10-24 09:44:01.035 AMdebuglastCommand = Sent Ok
dev:29592022-10-24 09:44:01.032 AMdebugIn parse - 354 End data with .
dev:29592022-10-24 09:44:01.012 AMdebugIn quit case
dev:29592022-10-24 09:44:01.009 AMdebugGot server response 250 value = 2.1.5 lastCommand = (quit)
dev:29592022-10-24 09:44:01.003 AMdebuglastCommand = quit
dev:29592022-10-24 09:44:01.000 AMdebugIn parse - 250 2.1.5 Ok
dev:29592022-10-24 09:44:00.495 AMdebugquit
dev:29592022-10-24 09:44:00.477 AMinfosending quit
dev:29592022-10-24 09:44:00.474 AMdebugIn send message case
dev:29592022-10-24 09:44:00.471 AMdebugGot server response 250 value = 2.1.0 lastCommand = (sendmessage)
dev:29592022-10-24 09:44:00.468 AMdebuglastCommand = sendmessage
dev:29592022-10-24 09:44:00.466 AMdebugIn parse - 250 2.1.0 Ok
dev:29592022-10-24 09:44:00.425 AMdebugMy internal id = 1
dev:29592022-10-24 09:44:00.422 AMinfoSent Message: test 800
dev:29592022-10-24 09:43:59.957 AMwarntelnet input stream closed
dev:29592022-10-24 09:43:59.920 AMdebugquit
dev:29592022-10-24 09:43:59.417 AMdebug.
dev:29592022-10-24 09:43:58.915 AMdebug
dev:29592022-10-24 09:43:58.413 AMdebugtest 800
dev:29592022-10-24 09:43:57.911 AMdebug
dev:29592022-10-24 09:43:57.409 AMdebugContent-Transfer-Encoding: quoted-printable
dev:29592022-10-24 09:43:56.906 AMdebugContent-Type: text/plain; charset="utf-8"
dev:29592022-10-24 09:43:56.404 AMdebugMIME-Version: 1.0
dev:29592022-10-24 09:43:55.902 AMdebugSubject: Home Activity Event
dev:29592022-10-24 09:43:55.400 AMdebugMessage-ID: <7054bcf102a94bbaaa5f42b1bced41ef.1666565032340@2LGKSendmailV3>
dev:29592022-10-24 09:43:54.897 AMdebugDate: Mon, 24 Oct 2022 9:43:52 +1100
dev:29592022-10-24 09:43:54.395 AMdebugRCPT TO:
dev:29592022-10-24 09:43:53.892 AMdebugFrom: derekjosborn@msn.com
dev:29592022-10-24 09:43:53.390 AMdebugDATA
dev:29592022-10-24 09:43:52.887 AMdebugRCPT TO:
dev:29592022-10-24 09:43:52.388 AMdebugMAIL FROM:
dev:29592022-10-24 09:43:52.385 AMdebugin sendData, message = [MAIL FROM: , RCPT TO: , DATA, From: derekjosborn@msn.com, RCPT TO: , Date: Mon, 24 Oct 2022 9:43:52 +1100, Message-ID: <7054bcf102a94bbaaa5f42b1bced41ef.1666565032340@2LGKSendmailV3>, Subject: Home Activity Event, MIME-Version: 1.0, Content-Type: text/plain; charset="utf-8", Content-Transfer-Encoding: quoted-printable , , test 800, , ., quit]
dev:29592022-10-24 09:43:52.381 AMdebugFrom = derekjosborn@msn.com, To = derekjosborn@gmail.com, Subject = Home Activity Event modifiedTo = RCPT TO: <derekjosborn@gmail.com>
dev:29592022-10-24 09:43:52.370 AMdebugNumber of To addresses = 1
dev:29592022-10-24 09:43:52.346 AMdebugEither got 250 for helo or 235 for password, Now Sending Message or ehlo
dev:29592022-10-24 09:43:52.343 AMdebugIn helo/ehlo/Password case
dev:29592022-10-24 09:43:52.340 AMdebugGot server response 250 value = msn.com lastCommand = (helo)
dev:29592022-10-24 09:43:52.338 AMdebuglastCommand = helo
dev:29592022-10-24 09:43:52.335 AMdebugIn parse - 250 msn.com
dev:29592022-10-24 09:43:51.801 AMdebughelo [192.168.1.170]
dev:29592022-10-24 09:43:51.793 AMdebugIn initialConnect case
dev:29592022-10-24 09:43:51.790 AMdebugGot server response 220 value = msn.com lastCommand = (initialConnect)
dev:29592022-10-24 09:43:51.784 AMdebuglastCommand = initialConnect
dev:29592022-10-24 09:43:51.780 AMdebugIn parse - 220 msn.com ESMTP Postfix
dev:29592022-10-24 09:43:51.675 AMdebugConnecting to 192.168.1.104:25
dev:29592022-10-24 09:43:51.664 AMdebugset last command to initialConnect
dev:29592022-10-24 09:43:51.661 AMdebugFound ok initial state (Sent Ok) ... going on!
dev:29592022-10-24 09:43:51.658 AMdebugInitial state found: (Sent Ok)
dev:29592022-10-24 09:43:51.653 AMdebug-------> In lgk sendmail Version (4.8)

PS, I actually deleted the v2 driver code.

That is bizarre.

that log looks fine.. last state should be sent ok as the flow looks perfect in the child.

1 Like

oh ok, very odd.

your log looks exactly the same as my test.. are so your only seeing that status in the device panel?

Yes, I think I know why it's throwing the error - the Subject isnt coming through.

i know whats going on.. lastcommand state is no longer in the parent app. its in the child and that is probably a left over state that never gets updated once you switched over an existing v2 to v3 wihtout reinstalling..

as for subject. double check your settings in the parent driver.. the subject is there and it is very easy to miss input stuff in hubitat because it will look like its there but once you refresh it is gone.. because if you say input a parameter and hit save settings without first clicking off the input field.. it never gets saved correctly.

It's defiantly there:

How do we confirm that the child code odd updated... There is no version info on the child code.