Jon00 Email V4

[jon00]

That is displayed when the email contains base64 encoded data (such as an attachment).

I think if you set HSLogenable=0 under settings, it will go.

[langenet]

Thanks Jon that did it. However, testing triggering of an event with confirmation, I see in the log:

18/12/2013 9:09:16 PM Jon00_Email Error in Confirm subroutine: Conversion from string "" to type 'Double' is not valid.

I've checked my subject string - same one used in V3 without issue. Of course, I don't get a reply back after the event fires.

Any idea?

[jon00]

Would you please post the actual entry you use in the ini file.

[langenet]

Attached is my config file. Names changed to protect the innocent.


Also like others, I saw this message in my logs. My email server is on the same box as my HS server which uses a local lan address.

19/12/2013 10:08:55 AM Event Event Trigger "Jon00 Email"
19/12/2013 10:08:55 AM Event Running script in background: Jon00Email.vben
19/12/2013 10:08:59 AM Jon00_Email Error in Pops subroutine Block B: Invalid operation at current state
19/12/2013 10:08:59 AM Jon00_Email Error in Pops subroutine Block C: Invalid operation at current state
19/12/2013 10:08:59 AM Jon00_Email Error in Pops subroutine Block D: Invalid operation at current state
19/12/2013 10:09:02 AM Vista Alarm FAULT 06 2ND FLOOR MOTION
19/12/2013 10:09:06 AM Jon00_Email Error in main subroutine: Invalid operation at current state

Any ideas?

[jon00]

Can you try the trigger without confirmation.

[langenet]

No problem when I don't ask for a confirmation.

[jon00]

OK, I'll take a look over the Christmas break.

[langenet]

Jon,

Not sure exactly what you'll be looking at, but I'm getting many errors such as:

21/12/2013 7:38:00 PM Event Running script in background: Jon00Email.vben
21/12/2013 7:38:01 PM Jon00_Email Error in Pops subroutine Block B: Invalid operation at current state
21/12/2013 7:38:01 PM Jon00_Email Error in Pops subroutine Block C: Invalid operation at current state
21/12/2013 7:38:01 PM Jon00_Email Error in Pops subroutine Block D: Invalid operation at current state
21/12/2013 7:38:01 PM Jon00_Email Error in Pops subroutine Block E: Invalid operation at current state
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block F: Invalid operation at current state
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block T: Invalid operation at current state
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block I: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block P: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block Q: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:02 PM Jon00_Email Problem with POP3 server - will need to download all mail on next run
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block R: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:02 PM Jon00_Email Error in main subroutine: Invalid operation at current state
21/12/2013 7:38:02 PM Jon00_Email Error in Pops subroutine Block S: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:02 PM Jon00_Email Cannot retrieve message 2 from POP3 server
21/12/2013 7:38:03 PM Jon00_Email Error in main subroutine: Wrong protocol or connection state for the requested transaction or request
21/12/2013 7:38:52 PM Vista Alarm


Rob

[jon00]

I don't have a resolution to this. The email component used is an old COM dll which uses M$ Winsock. The error in question is 40020 (search "Winsock 40020") and you will get many hits.

You can try and reset the Winsock (see post 39 on this thread). I'm not sure how often you check for emails but you can try decreasing the frequency to see if that helps.

[Rotech]

Jon I have installed the package at first I had issues, but then I had placed a file in the wrong place. Its seams recieving the email but I dont get the chime nor the annoucement. I can see the message in the status page, but when I try to open it, it gives me this error:

2/8/2014 2:32:25 PM - Error - Script compile error in encrypted script
2/8/2014 2:32:53 PM - Error - Script compile error in encrypted script
2/8/2014 2:33:39 PM - Error - Script compile error in encrypted script

[jon00]

I'm not sure what you mean. Did you delete the virtual devices from your previous version? If not, you should have done so.

[Rotech]

No I didnt , I will delete all related devices from previous ver. and let you know.

[Rotech]

I'm not sure what you mean. Did you delete the virtual devices from your previous version? If not, you should have done so.

Ok I deleted devices from previous ver. But still no chime nor announcement, I did notice that the password gets encrypted is this normal?

You said to me by email , that I should re-enter all the info and not to copy anything from the previous ver. When I opened the new INI it had already filled entered from old INI. This is very odd, all seams to bein working order.

[jon00]

Yes the password encryption is normal.

Can you describe your speaker setup i.e. do you just use the speaker client and nothing else for text to speech (TTS)?

[Rotech]

I don't have anything else as you can see.