Vera Alerts - Plugin Version 7.23

I upgraded from 3.95 today. I wasn’t able to get SMTP to work in 3.95 either, but now on 4.0, I can’t get the profiles tab to load, only the progress bar on the page, and the words: “Opening va_Profiles…”. I thought i might have been because I upgraded from 3.95, so I uninstalled the plugin, and then re-installed the 4.0 version. Still when I click on the profiles tab, I get the same result. Thoughts?

10      12/04/13 13:42:31.382           Device 111 Description: VeraAlerts <0x2b624000>
10      12/04/13 13:42:31.383   Parsing device 111: template urn:richardgreen:device:VeraAlert:1 controlled via 0 room 0 IPaddress  mac  disabled 0 <0x2b624000>
10      12/04/13 13:42:31.672   Device_LuaUPnP::LoadDeviceDoc 111 file D_VeraAlert.xml size 653 result 0 <0x2b624000>
10      12/04/13 13:42:31.673   Device_LuaUPnP::LoadDeviceDoc 111 file /etc/cmh-ludl//D_VeraAlert.xml finished <0x2b624000>
10      12/04/13 13:42:32.658   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: ProcessNotifications startup: 0 v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.658   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: InternalAlerts startup: 0 v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.659   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: Debug startup: 1 v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.659   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: Profiles startup:  v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.660   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: UserProfileAssociation startup:  v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.660   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastUpdate startup: 1386183831 v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.660   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: RegisterID startup:  v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.661   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastRecipient startup:  v:0x1093708/NONE <0x2b624000>
10      12/04/13 13:42:32.661   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent startup: 13:33:00 Wed Dec 04 v:0x1093aa0/NONE <0x2b624000>
10      12/04/13 13:42:32.661   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: SMTPServer startup: mail.the-borg.com v:(nil)/NONE <0x2b624000>
10      12/04/13 13:42:32.662   Device_Variable::m_szValue_set device: 111 service: urn:richardgreen:serviceId:VeraAlert1 variable: SMTPSSL startup: 1 v:(nil)/NONE <0x2b624000>
25      12/04/13 13:42:32.722   JobHandler_LuaUPnP::ParseAllImplementations parsed I_VeraAlert.xml <0x2b624000>
10      12/04/13 13:42:32.724   Device_LuaUPnP::MatchupImplementations device 111 using implementation: I_VeraAlert.xml with 1 services <0x2b624000>
25      12/04/13 13:42:38.134   LuaInterface::LuaInterface 0x116b918 device 111 VeraAlerts <0x2b624000>
25      12/04/13 13:42:38.152   LuaInterface::LuaInterface build device id's 0x116b918 device 111 VeraAlerts <0x2b624000>
25      12/04/13 13:42:38.153   LuaInterface::LuaInterface done 0x116b918 device 111 VeraAlerts <0x2b624000>
    package.loaded.L_VeraAlert = nil
    VA = require("L_VeraAlert")
  function SVeraAlert_VeraAlert1_SendAlert_job(lul_device,lul_settings,lul_job)
function SVeraAlert_VeraAlert1_SetProperty_run(lul_device,lul_settings)
function SVeraAlert_VeraAlert1_DeviceNotification_job(lul_device,lul_settings,lul_job)
09      12/04/13 13:42:38.551   JobHandler_LuaUPnP::Run device 111 VeraAlerts room 0 type urn:richardgreen:device:VeraAlert:1 id  parent 0/0xfe6cf8 upnp: 0 <0x2b624000>
10      12/04/13 13:42:42.470   XXX-UpdateSystemMessagesTasks now 1=VeraAlerts[111]: Starting Lua Engine timeout 0 (-1386186162) count: 5pend:Starting Lua Engine/err:(null)/done:(null) <0x2bd57680>
25      12/04/13 13:42:42.601   LuImplementation::StartLua device: 111 file:I_VeraAlert.xml startup:Initialize pLuaInterface: 0x116b918 ip:  port 0 protocol: (null) <0x2bf57680>
10      12/04/13 13:42:42.603   XXX-UpdateSystemMessagesTasks now 1=VeraAlerts[111]: Starting Lua Engine timeout 0 (-1386186162) count: 5pend:Starting Lua Engine/err:(null)/done:(null) <0x2bd57680>
25      12/04/13 13:42:42.604   LuImplementation::StartLua running startup code for 111 I_VeraAlert.xml <0x2bf57680>
50      12/04/13 13:42:42.607   luup_log:111: VeraAlert:111:ProcessNotifications:0 <0x2bf57680>
50      12/04/13 13:42:42.608   luup_log:111: VeraAlert:111:InternalAlerts:0 <0x2bf57680>
50      12/04/13 13:42:42.609   luup_log:111: VeraAlert:111:Debug:1 <0x2bf57680>
50      12/04/13 13:42:42.609   luup_log:111: VeraAlert:111:Profiles: <0x2bf57680>
50      12/04/13 13:42:42.609   luup_log:111: VeraAlert:111:UserProfileAssociation: <0x2bf57680>
50      12/04/13 13:42:42.610   luup_log:111: VeraAlert:111:LastUpdate:1386183831 <0x2bf57680>
50      12/04/13 13:42:42.610   luup_log:111: VeraAlert:111:RegisterID: <0x2bf57680>
50      12/04/13 13:42:42.611   luup_log:111: VeraAlert:111:LastRecipient: <0x2bf57680>
50      12/04/13 13:42:42.612   luup_log:111: VeraAlert:111:LastMsgSent:13%3A33%3A00%20Wed%20Dec%2004 <0x2bf57680>
50      12/04/13 13:42:42.612   luup_log:111: VeraAlert:111:Initialize:Registered[20]: false nil <0x2bf57680>
10      12/04/13 13:42:42.616   XXX-UpdateSystemMessagesTasks now 1=VeraAlerts[111]: Running Lua Startup timeout 0 (-1386186162) count: 5pend:Running Lua Startup/err:(null)/done:(null) <0x2bd57680>
10      12/04/13 13:42:44.234   XXX-UpdateSystemMessagesTasks StartupTask #4 = 4 OK / VeraAlerts[111] <0x2bd57680>
10      12/04/13 13:42:47.104   XXX-UpdateSystemMessagesTasks now 2=VeraAlerts[111]: Is Not Initialized! Open Profiles Tab! timeout 0 (-1386186167) count: 5pend:(null)/err:Is Not Initialized! Open Profiles Tab!/done:(null) <0x2bd57680>

It amazes me the number of times that I here that people uninstall/re-install plugin.
The only thing this accomplishes is to reset the parameters for the plugin.
All of which are accessible from the Advanced tab for the plugin.

So NO I do not think you need to re-install the plugin. All of the parameters for the SMTP mail protocol are accessible from the Profile. You can just delete the profile and create a new one if you want to start again.

Did you do the standard Vera Dance … You need to Refresh the Browser when you change ANY plugin.

I have done that and does not works. I was talking about restalling to be sure that I have the most recent files. Give me a clue where else can I try? I have make the Vera Dance, I always do.

Standard “F5” on chrome didn’t do it, but “Ctl-F5” did it.

@Vreo
Unless you want to sent me the details of your SMTP profile … there is not much I can do.
As I said in my documentation … setting up SMTP is tricky … there are so many options … and different ISPs do things differently. The default’s in the profile are setup for minimal change to use GMAIL.

Now suddenly after modificating profiles several times, I get this (attached) and I can’t do anything else.

About the details of my smpt, I have created a test account I can share.

mail: rts@vreo.net
username: rts@vreo.net
password: rts123!
server: mail.vreo.net
port: 587
Auth SMPT required
SSL: No

Go to the Advanced tab … and delete the contents for the parameter called Profiles.
You might want to save it first and see if you can see what is screwed up in it.

I still can’t seem to get SMTP working either.

I’m using an SMTP host on my LAN, and I’ve verified that the username and password work correctly using telnet.

However, I can’t seem to get VeraAlerts to work with it.

Using the fully qualified domain name of the SMTP host fails with name not found. Using the IP address of the server gets me further, but in the mail server logs, I see “lost connection after UNKNOWN from vera.host.name”.

Here is the log from me sending a test message:

08      12/04/13 15:52:03.102   JobHandler_LuaUPnP::HandleActionRequest device: 111 service: urn:richardgreen:serviceId:VeraAlert1 action: SendAlert <0x2e207680>
08      12/04/13 15:52:03.102   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=111 <0x2e207680>
08      12/04/13 15:52:03.102   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:richardgreen:serviceId:VeraAlert1 <0x2e207680>
08      12/04/13 15:52:03.102   JobHandler_LuaUPnP::HandleActionRequest argument action=SendAlert <0x2e207680>
08      12/04/13 15:52:03.103   JobHandler_LuaUPnP::HandleActionRequest argument Message=Test <0x2e207680>
08      12/04/13 15:52:03.103   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=SMTP-MySmtp <0x2e207680>
08      12/04/13 15:52:03.103   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.4120334736071527

And the corresponding log from the SMTP server

Dec  4 15:52:23 vm-mail postfix/smtpd[3851]: connect from vera01[xxx.xxx.xxx.xxx]
Dec  4 15:52:23 vm-mail postfix/smtpd[3851]: lost connection after UNKNOWN from vera01[xxx.xxx.xxx.xxx]
Dec  4 15:52:23 vm-mail postfix/smtpd[3851]: disconnect from vera01[xxx.xxx.xxx.xxx]

[quote=“RichardTSchaefer, post:68, topic:175819”]Go to the Advanced tab … and delete the contents for the parameter called Profiles.
You might want to save it first and see if you can see what is screwed up in it.[/quote]
That did the trick. The value before deleting it was “nil”.

I sent a test notification via my SMTP profile again with some more verbose logging on my SMTP server, and this is what I get in the server logs…

Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostname: vera.local ~? 127.0.0.0/8
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostaddr: xxx.xxx.xxx.250 ~? 127.0.0.0/8
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostname: vera.local ~? xxx.xxx.xxx.0/24
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostaddr: xxx.xxx.xxx.250 ~? xxx.xxx.xxx.0/24
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: > vera.local[xxx.xxx.xxx.250]: 220 vm-mail.the-borg.com
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: watchdog_pat: 0x9db0320
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: < vera.local[xxx.xxx.xxx.250]: ???
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_string: ??? ~? CONNECT
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_string: ??? ~? GET
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_string: ??? ~? POST
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_list_match: ???: no match
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: > vera.local[xxx.xxx.xxx.250]: 502 5.5.2 Error: command not recognized
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: watchdog_pat: 0x9db0320
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: smtp_get: EOF
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostname: vera.local ~? 127.0.0.0/8
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostaddr: xxx.xxx.xxx.250 ~? 127.0.0.0/8
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostname: vera.local ~? xxx.xxx.xxx.0/24
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: match_hostaddr: xxx.xxx.xxx.250 ~? xxx.xxx.xxx.0/24
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: lost connection after UNKNOWN from vera.local[xxx.xxx.xxx.250]
Dec  4 17:17:10 vm-mail postfix/smtpd[6713]: disconnect from vera.local[xxx.xxx.xxx.250]

The curious part is where it looks like vera is sending “???” to the mail server. That seems like a configuration error on my part, but I can’t tell where. I only have authentication checked, then just the smtp server’s IP, username, password, to address, and port of 25.

Well I fixed the problem with mail. It will be in the next release. I might wait a few days to see if there are other bugs.

It was ALWAYS using Authentication and SSL.
This was a bug in handling the Toggle Buttons on the profile.
Thanks for the test account. You should have received two email from that account sent from the my Vera using the Mail Template.

@scottresnik
Unless your mail was setup to use SSL you will have the same bug as @Vreo.
I was always initiating the connection with a SSL socket.

I’m glad you found the problem. Tell me if you still need the test account or I should delete it.

In the custom URL for Twilio. Can a variable with the message be there? Because I get it to work with the custom URL, but only with a predefined message , which makes no sense.

Regards.

The message should be tied to variable:
Message

But you can pass addition parameters from Vera ALerts using
{VariableName=VariableValue}
In the message.
It looks like you already deleted the mail account …

Share your custom URL’s other’s may be interested.

Thanks Richard. Yes I deleted the account because I saw your email after my post, but if you need it I can leave as long as you need, just tell me.

[quote=“RichardTSchaefer, post:49, topic:175819”]The purpose for the USB stick is to add more memory for Vera to work with.
In general Vera does not have much spare memory space.
If you add a memory stick and enable this in Setup then Logs

I place the snapped pictures in the same place as the log files …
That’s one of the few writable areas on Vera.
And if you use a USB stick this area usually has plenty of free space.

Vera Alerts does not use any MCV video archive.[/quote]

well… I have plug in the USB and have the USB status “enable” in the logs.
give it a try again and still Download Errorr : File Not Found on Vera. :cry:
anything that I should setup 1st to get this video function ?

I try to search on Vera Alerts section but can’t find an answer…

when you say that "I place the snapped pictures in the same place as the log files … "
does it means that If I take out the USB and view it in PC I can see my picture and video ?
is it in the root ? or in the Directory ?

btw I understand that VeraALert can capture multiple pictures from multiple device.
just wondering… how about multiple pictures in X duration from 1 single device ?

many thanks

I think I some how managed to brake VeraAlerts this morning.
I noticed that it had automatically updated to the 4.0 version so I opened the Notification Configuration tab and some other tabs to see what was changed.
I closed and saved. Everything seemed to be working fine. Then I changed a few things in a PLEG and added some notifications to some device and saved/reloaded many times along the way.

Then I opened VeraAlerts again first I get the message “Error Parsing Profiles” and now the “Send Alerts”,“Profiles” and “settings” tabs don’t open anymore. I only get the progress bar and a message like “Opening va_Control…” .
And when I try to open the “Notification Configuration” tab I get a bunch of messages saying for example “Device: 98 Scene Obj:32 Trigger Index:0”. Basically for all devices that has a notification enabled I get a similar message.

I noised that under advanced the property named “Profiles” sais “nil”. Is it supposed to be like this?

Refreshing or changing browser does not help.

I’m connected through cp.mios.com. I’ll try local connection when I get home. If there is a easy solution for this let me know otherwise I will revert to a backup.

[quote=“RichardTSchaefer, post:73, topic:175819”]@scottresnik
Unless your mail was setup to use SSL you will have the same bug as @Vreo.
I was always initiating the connection with a SSL socket.[/quote]

Okay, I wasn’t aware of that. I unchecked SSL just to eliminate a variable. Thanks.

@korttoma
I am sorry for your problem. I can only recommend the following:

Go to the Advanced Tab!
Delete the content of the Profiles and MsgOverride parameter …
Save … Browser Refresh (Control F5) Then Open the Vera Alerts Device Again.
It would be nice to know what sequence caused the NIL in the profiles. Another has
mentioned this. But did not know the sequence of events that led to it.

@scottresnik
Did you have it set ? Does your mail server require it to be set ?
If your mail server requires it to be clear than there is a bug in the current release until I make my change … That’s the problem the @Vreo was having. I am always doing a SSL connection … even if your mail server can’t handle it.