I have reinstalled VeraAlerts recently and I am unable to get Prowl alerts to work on the newest version. The profile is fine, because test alert works. Even more strange, I can see when the notification (from PLEG) has called Prowl from the dashboard as the timestamp on veraalerts device changes. I can not for the life of me work out what is going on. Tried removing and recreating the notifications, the profile, etc. Any suggestions?
Did you turn on debug and look at the log file while you send an alert:
You can view the log file with:
http://Your.Vera.IP.Address/cgi-bin/cmh/log.sh?Device=LuaUPnP
I did now… debug shows this (for the unsuccessful message send):
50 12/04/14 11:00:42.857 luup_log:44: VeraAlert:44:SendAlert:HouseModeMask:0 <0x2b1c8000>
50 12/04/14 11:00:42.857 luup_log:44: VeraAlert:44:SendAlert:Msg:Luup Restarted <0x2b1c8000>
50 12/04/14 11:00:42.857 luup_log:44: VeraAlert:44:ExpandRecipients:Checking:redbondc <0x2b1c8000>
50 12/04/14 11:00:42.858 luup_log:44: VeraAlert:44:ExpandRecipients:Adding User Specified Profile:undefined <0x2b1c8000>
50 12/04/14 11:00:42.858 luup_log:44: VeraAlert:44:ExpandRecipients:??? redbondc <0x2b1c8000>
06 12/04/14 11:00:42.859 Device_Variable::m_szValue_set device: 44 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 10:56:50 Thu Dec 04 now: 11:00:42 Thu Dec 04 #hooks: 0 upnp: 0 v:0x8a78a8/NONE duplicate:0 <0x2b1c8000>
50 12/04/14 11:00:42.887 luup_log:44: VeraAlert:44:SendAlert:Memory:302664 LEAK this:-348160 start:720896 to 0xa2c000 <0x2b1c8000>
04 12/04/14 11:00:42.888 <0x2b1c8000>
When I use the send message for the same profile, it is like this:
50 12/04/14 10:56:49.000 luup_log:44: VeraAlert:44:SendAlert:HouseModeMask:0 <0x2b1c8000>
50 12/04/14 10:56:49.014 luup_log:44: VeraAlert:44:SendAlert:Msg:test <0x2b1c8000>
50 12/04/14 10:56:49.014 luup_log:44: VeraAlert:44:ExpandRecipients:Checking:redbondc <0x2b1c8000>
50 12/04/14 10:56:49.014 luup_log:44: VeraAlert:44:ExpandRecipients:Adding User Specified Profile:undefined <0x2b1c8000>
50 12/04/14 10:56:49.015 luup_log:44: VeraAlert:44:ExpandRecipients:??? redbondc <0x2b1c8000>
50 12/04/14 10:56:49.015 luup_log:44: VeraAlert:44:ExpandRecipients:Checking:Prowl <0x2b1c8000>
50 12/04/14 10:56:49.016 luup_log:44: VeraAlert:44:ExpandRecipients:Adding Requested Profile <0x2b1c8000>
50 12/04/14 10:56:49.016 luup_log:44: VeraAlert:44:SendAlert:Sending to:Prowl <0x2b1c8000>
50 12/04/14 10:56:49.126 luup_log:44: VeraAlert:44:ProwlSend:Body:application=Vera%20Alerts&event=Prowl&description=test&apikey=a436c149fdb886e2b310aadd3db0a9c0526cc160 <0x2b1c8000>
02 12/04/14 10:56:50.101 LOG_CHECK_MEMORY_LEAK pMem start 0xa2b000 now 0xa81000 last 0xa51000 leaked 352256 LEAK this:196608 start:1069056 to 0xa81000 <0x2b8fb680>
50 12/04/14 10:56:50.376 luup_log:44: VeraAlert:44:ProwlSend:Result:200Resp:
So it seems to be stopping before “Checking:Prowl” when using the automated method. Also should I be worried about the memory leak errors that seem to coincide with using veralerts?
- Open the settings tab of Vera Alerts
- Click the user: redbondc
- Associate a profile with this user
- Select the Notification Configuration tab
- save changes/reload Vera
Doh, what a schoolboy error! I forgot to click away from “Default Recipient”!! Thanks Richard