Goto Vera ALerts - Verify that the Scene does not show up in the list for notifications.
Goto the scene that is alerting.
Do you see LUA code ?
If so than post it
If not than it should not be reporting … If you are getting notifications, what is the Text of the notification ?
Have you done a Report to see where the identified message text is coming from ?
Maybe you also have a device notification.
@RTS - i had to factory reset my vera and start rebuilding it from scratch (fun times) and have so far just setup my z-wave nodes and the Ademco plug-in and Vera Alerts plug-in from the app store. Once in a while when luup reloads i get these errors in my log and then Luup restarts by itself and all is fine (Vera Alerts is device #3):
01 12/11/14 11:09:44.794 Device_LuaUPnP::LoadDeviceDoc can't load /etc/cmh-lu//D_VeraAlert.xml <0x2b0eb000>
01 12/11/14 11:09:44.795 JobHandler_LuaUPnP::CreateDevice_LuaUPnP failed to load 3/D_VeraAlert.xml so device 3 is offline <0x2b0eb000>
01 12/11/14 11:09:45.054 Device_LuaUPnP::CreateServices Aborting device 3 because the topmost device has no interface <0x2b0eb000>
01 12/11/14 11:09:45.055 JobHandler_LuaUPnP::CreateAllServices failed to create 3 <0x2b0eb000>
01 12/11/14 11:09:45.329 UPnPAction_Send::ParseState can't find name <0x2b0eb000>
01 12/11/14 11:09:45.525 Device_LuaUPnP::CreateImplementations Aborting 3 because it failed to load <0x2b0eb000>
01 12/11/14 11:09:45.525 JobHandler_LuaUPnP::CreateAllImplementations failed to create 3 <0x2b0eb000>
Odd that Vera is looking for Vera Alerts /etc/cmh-lu//D_VeraAlert.xml since (a) it never is there and (b) its in /etc/cmh-ludl (where i think it belongs).
The “ParseState can’t find name” error seems to come from the Ademco plug-in and not be related to this (i get that on every reload, do not think it causes a problem, and have already opened a ticket with TS since Florin wrote it – though i don’t expect a fix from MCV sadly)
Do you have any idea what might be going on / what i should do to fix VA? Thanks much.
Looks like it failed to Download the plugin.
That message is generated by Vera itself.
This may be a timing issue because MCV just approved a Vera Alerts release this morning. So it’s tying to download, and maybe having a problem.
Actually the // in the file is strange … but when it works properly with the detailed log turned on it also has // in the file names. (Not just my plugin)
The pictures are stored in /tmp space and cleaned up quickly on the Vera side.
There might be some way to store pictures for your cameras locally … need to check in the security forum.
I heard rumors of Vera providing the ability to store images on the cloud .
Thank You version 6.29 has stopped alerting all the scenes. However when running report they are still listed. Going to scene shows no LUUP code defined or user notified.
Is there a way to remove those scenes from reporting
Even though version 6.31 doesn’t seem to be available yet on apps.mios.com I have already installed it (I reported this bug years ago).
I was surprised and excited to see pushbullet support. I am able to send camera-images with “{Picture(DeviceID)}” to my devices. Then I wanted to add a title (according to Pushbullet API and Vera Alerts - Vera Plugin for Notifications) this should work like this “{title=TEST}{Picture(DeviceID)}”. The image is still sent, but no changes in title. Did I get something wrong?
When I send a Picture … I use a file PUSH. The file PUSH does not support the title attribute.
When I send a url … I use a link PUSH. Otherwise I use a note PUSH.
I fixed the spelling errors … thanks for reporting.
You can NOT use this technique to remotely upgrade UI6 or UI7. You must be local … If you have AutoUpdate turned on for that plugin, it should update itself.
But then you are assuming I will make no mistakes … and you know what they say about people that AssUMe.
Hi. I am trying to use VeraAlerts to send events to my Eventghost but I am struggeling. I have created a “Vera-Alerts-LAN” profile and entered the host ip (192.168.0.44) and port (80). I want VeraAlert to make a request like this: “192.168.0.44/ajax.html?.”.
When looking in the Vera log it seems as the host and port is combined (as they should) into “192.168.0.44:80” but if I add “/ajax.html?test.test” it is combined into the GET statement I am looking for. I have not been able to work out if the {url:Destination;Description} thing can be used in some way. I have looked at the traffic on the Eventghost side (with Wireshark) and the message as specified in VeraAlerts appears as a separate segment.
It seems to be a great plugin, I just don’t understand how to do this (hopefully) simple thing