Vera Alerts Failed To Specific User

I have a UI5 Vera Alerts that has been sending notifications to a Sonos user for some time. Recently the notifications stopped.

I found that the UserID was missing from Vera Alerts and From Vera/MCV, although the profile for that user was still in Vera Alerts. Weird but whatever. I add the notification only user back to Vera/MCV user, but the user refused to show up in Vera Alerts. After a lot of fighting, I “upgraded” Vera alerts to v6.43 (30461) in an effort to reinstall Vera Alerts. Following the reinstall and a reboot, Vera Alerts sees the user, assigned the correct profile to the user and everything looks as it should/did. In Vera Alerts, I can manually send a notification to this user and it works.

But, when the notification is triggered by a device, it is sent to the Default Recipients instead of the proper user and there is an error in the log.

50 10/15/16 18:17:39.097 luup_log:62: VeraAlert:62:SendAlert:UsingDefaultRecipients:nil <0x2b50d000> 50 10/15/16 18:17:39.098 luup_log:62: VeraAlert:62:SendAlert:Msg:Whisper something to Z-Waver. <0x2b50d000> 01 10/15/16 18:17:39.098 LuaInterface::CallFunction_Job device 62 function SVeraAlert_VeraAlert1_DeviceNotification_job failed [string "module("L_VeraAlert", package.seeall)..."]:1246: bad argument #1 to 'gmatch' (string expected, got nil) <0x2b50d000> 01 10/15/16 18:17:39.099 Lua_Job::Run job#17 : dev:62 (0xfcafa8) P:50 S:0 failed <0x2b50d000>

Does anyone have a clue they can lend me?

You have a notification … without a user (possibly related to the user disappearing.)

Because the user is not specified, it tries to use the default recipient, but it’s nil (not defined) and you get the error.

You might associate your profile with the default recipient as well.

Duh… Sometimes I just can’t think.

Thanks Richard.