Author Topic: Howto Upgrade the Vera Alerts Plugin  (Read 13704 times)

Offline elordude

  • Sr. Newbie
  • *
  • Posts: 39
  • Karma: +1/-0
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #15 on: December 10, 2013, 01:47:02 am »
Richard,  I was wrong i disable all the vera alerts that is the reason i was getting none - I just turned them back on and i'm still getting Front Door Alerts for the Motion detectors  - it used to work without issues on previous version.  Can I downgrade ?  I went from ver 2.0 to 4.1


06   12/09/13 22:36:06.142   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: LastUser was: Master now: Master #hooks: 1 upnp: 0 v:0xbfd950/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.143   Event::Evaluate 24 Alarm Pin Code Entered scene Alarm Pin Code Entered is false repeat 0/-1 <0x30e62680>
06   12/09/13 22:36:06.143   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 1 now: 1 #hooks: 0 upnp: 0 v:0xbfe210/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.144   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory was: 0 now: 0 #hooks: 0 upnp: 0 v:0xbfefa8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.144   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: Alarm was: None now: None #hooks: 0 upnp: 0 v:0xbff580/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.145   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: Ready now: Disarmed #hooks: 4 upnp: 0 v:0xbff5a0/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.145   Event::Evaluate 23 Home Alarm Armed scene Home Alarm Armed is false repeat 0/-1 <0x30e62680>
07   12/09/13 22:36:06.145   Event::Evaluate 35 AlarmArmedStay scene Alarm Arm Exit GarageDoor is false repeat 0/-1 <0x30e62680>
08   12/09/13 22:36:06.146   JobHandler_LuaUPnP::HandleActionRequest device: 203 service: urn:richardgreen:serviceId:VeraAlert1 action: DeviceNotification <0x30e62680>
08   12/09/13 22:36:06.147   JobHandler_LuaUPnP::HandleActionRequest argument DeviceID=170 <0x30e62680>
08   12/09/13 22:36:06.147   JobHandler_LuaUPnP::HandleActionRequest argument Description=%20Disarmed <0x30e62680>
08   12/09/13 22:36:06.147   JobHandler_LuaUPnP::HandleActionRequest argument Name=Home%20Alarm%20DisArmed <0x30e62680>
08   12/09/13 22:36:06.147   JobHandler_LuaUPnP::HandleActionRequest argument Service=urn:micasaverde-com:serviceId:AlarmPartition2 <0x30e62680>
08   12/09/13 22:36:06.147   JobHandler_LuaUPnP::HandleActionRequest argument Variables=DetailedArmMode <0x30e62680>
08   12/09/13 22:36:06.158   JobHandler_LuaUPnP::HandleActionRequest argument Msg=Home%20Alarm%20DisArmed <0x30e62680>
08   12/09/13 22:36:06.158   JobHandler_LuaUPnP::HandleActionRequest argument SceneID=87 <0x30e62680>
08   12/09/13 22:36:06.159   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=GomezVeraAlerts <0x30e62680>
07   12/09/13 22:36:06.189   Event::Evaluate 38 Home Alarm DisArmed scene Home Alarm DisArmed is true users:270957 allow:1 <0x30e62680>
08   12/09/13 22:36:06.190   Scene::RunScene running 87 Home Alarm DisArmed <0x30e62680>
08   12/09/13 22:36:06.191   JobHandler_LuaUPnP::HandleActionRequest device: 203 service: urn:richardgreen:serviceId:VeraAlert1 action: DeviceNotification <0x30e62680>
08   12/09/13 22:36:06.191   JobHandler_LuaUPnP::HandleActionRequest argument DeviceID=170 <0x30e62680>
08   12/09/13 22:36:06.191   JobHandler_LuaUPnP::HandleActionRequest argument Description=%20Disarmed <0x30e62680>
08   12/09/13 22:36:06.192   JobHandler_LuaUPnP::HandleActionRequest argument Name=Home%20Alarm%20DisArmed%20Ready <0x30e62680>
08   12/09/13 22:36:06.192   JobHandler_LuaUPnP::HandleActionRequest argument Service=urn:micasaverde-com:serviceId:AlarmPartition2 <0x30e62680>
08   12/09/13 22:36:06.193   JobHandler_LuaUPnP::HandleActionRequest argument Variables=DetailedArmMode <0x30e62680>
08   12/09/13 22:36:06.193   JobHandler_LuaUPnP::HandleActionRequest argument Msg=Home%20Alarm%20DisArmed%20Ready <0x30e62680>
08   12/09/13 22:36:06.193   JobHandler_LuaUPnP::HandleActionRequest argument SceneID=88 <0x30e62680>
08   12/09/13 22:36:06.193   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=GomezVeraAlerts <0x30e62680>
07   12/09/13 22:36:06.195   Event::Evaluate 39 Home Alarm DisArmed Ready scene Home Alarm DisArmed Ready is true users:270957 allow:1 <0x30e62680>
08   12/09/13 22:36:06.195   Scene::RunScene running 88 Home Alarm DisArmed Ready <0x30e62680>
06   12/09/13 22:36:06.196   Device_Variable::m_szValue_set device: 170 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Disarmed now: Disarmed #hooks: 1 upnp: 0 v:0xbfe898/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.441   Device_Variable::m_szValue_set device: 180 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 1 #hooks: 1 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.442   Device_Variable::m_szValue_set device: 180 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.493   Device_Variable::m_szValue_set device: 173 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 2 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.493   Event::Evaluate 42 Front Door Opened scene Front Door Opened is false repeat 0/-1 <0x30e62680>
08   12/09/13 22:36:06.494   JobHandler_LuaUPnP::HandleActionRequest device: 203 service: urn:richardgreen:serviceId:VeraAlert1 action: DeviceNotification <0x30e62680>
08   12/09/13 22:36:06.494   JobHandler_LuaUPnP::HandleActionRequest argument DeviceID=173 <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Description=%20Door%20Front%20is%20not%20tripped <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Name=Front%20Door%20Closed <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Service=urn:micasaverde-com:serviceId:SecuritySensor1 <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Variables=Tripped <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Msg=%20Door%20Front%20is%20not%20tripped <0x30e62680>
08   12/09/13 22:36:06.496   JobHandler_LuaUPnP::HandleActionRequest argument SceneID=95 <0x30e62680>
08   12/09/13 22:36:06.496   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=GomezVeraAlerts <0x30e62680>
07   12/09/13 22:36:06.509   Event::Evaluate 43 Front Door Closed scene Front Door Closed is true users:270957 allow:1 <0x30e62680>
08   12/09/13 22:36:06.509   Scene::RunScene running 95 Front Door Closed <0x30e62680>
06   12/09/13 22:36:06.509   Device_Variable::m_szValue_set device: 173 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.510   Device_Variable::m_szValue_set device: 174 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.511   Device_Variable::m_szValue_set device: 174 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.511   Device_Variable::m_szValue_set device: 175 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.512   Device_Variable::m_szValue_set device: 175 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.513   Device_Variable::m_szValue_set device: 176 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 2 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.513   Event::Evaluate 31 Basement Room Door Opened scene Basement Room Door Opened is false repeat 0/-1 <0x30e62680>
06   12/09/13 22:36:06.513   Device_Variable::m_szValue_set device: 176 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.514   Device_Variable::m_szValue_set device: 177 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 2 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.514   Event::Evaluate 32 ManCave Door Opened scene ManCave Door Opened is false repeat 0/-1 <0x30e62680>
06   12/09/13 22:36:06.515   Device_Variable::m_szValue_set device: 177 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.516   Device_Variable::m_szValue_set device: 178 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.516   Device_Variable::m_szValue_set device: 178 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.517   Device_Variable::m_szValue_set device: 179 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 1 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.517   Device_Variable::m_szValue_set device: 179 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.542   Device_Variable::m_szValue_set device: 180 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 1 #hooks: 1 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
06   12/09/13 22:36:06.543   Device_Variable::m_szValue_set device: 180 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb954e8/NONE duplicate:1 <0x30e62680>
06   12/09/13 22:36:06.600   Device_Variable::m_szValue_set device: 203 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 22:26:43 Mon Dec 09 now: 22:36:06 Mon Dec 09 #hooks: 0 upnp: 0 v:0xc206d8/NONE duplicate:0 <0x2ba3f000>
04   12/09/13 22:36:06.601    <0x2ba3f000>
06   12/09/13 22:36:06.652   RAServerSync::SendAlert ID 2066591124,PK_Alert:2066591124 sync 0x130ea88 for https://cms2.mios.com/alert?PK_AccessPoint=30001812&HW_Key=<edited_by_admin>&DeviceID=170&LocalDate=2013-12-09%2022:36:06&LocalTimestamp=1386657366&AlertType=3&SourceType=3&Argument=38&Format=&Code=DetailedArmMode&Value=Disarmed&Description=Home%20Alarm%20DisArmed&Users=270957 <0x2c373680>
06   12/09/13 22:36:06.958   RAServerSync::SendAlert ID 2066591134,PK_Alert:2066591134 sync 0x12f1938 for https://cms2.mios.com/alert?PK_AccessPoint=30001812&HW_Key=<edited_by_admin>&DeviceID=170&LocalDate=2013-12-09%2022:36:06&LocalTimestamp=1386657366&AlertType=3&SourceType=3&Argument=39&Format=&Code=DetailedArmMode&Value=Disarmed&Description=Home%20Alarm%20DisArmed%20Ready&Users=270957 <0x2c373680>
06   12/09/13 22:36:06.993   Device_Variable::m_szValue_set device: 203 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 22:36:06 Mon Dec 09 now: 22:36:06 Mon Dec 09 #hooks: 0 upnp: 0 v:0xc206d8/NONE duplicate:1 <0x2ba3f000>
04   12/09/13 22:36:06.994    <0x2ba3f000>
06   12/09/13 22:36:07.561   Device_Variable::m_szValue_set device: 203 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 22:36:06 Mon Dec 09 now: 22:36:07 Mon Dec 09 #hooks: 0 upnp: 0 v:0xc206d8/NONE duplicate:0 <0x2ba3f000>
06   12/09/13 22:36:07.643   RAServerSync::SendAlert ID 2066591204,PK_Alert:2066591204 sync 0x1217fc8 for https://cms2.mios.com/alert?PK_AccessPoint=30001812&HW_Key=<edited_by_admin>&DeviceID=173&LocalDate=2013-12-09%2022:36:06&LocalTimestamp=1386657366&AlertType=3&SourceType=3&Argument=43&Format=&Code=Tripped&Value=0&Description=Front%20Door%20Closed&Users=270957 <0x2c373680>

« Last Edit: January 20, 2014, 05:39:49 am by mcvflorin »

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10070
  • Karma: +761/-141
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #16 on: December 10, 2013, 06:42:48 am »
Well you can shoot the proverbial messenger (Vera Alerts). But from the log it looks like your alarm plugin setup has problems. It is sending a bunch of change requests to Vera when nothing has changed.

In the future, please put long logs in an attachment. It's good forum etiquette.

Offline elordude

  • Sr. Newbie
  • *
  • Posts: 39
  • Karma: +1/-0
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #17 on: December 10, 2013, 05:50:03 pm »
Richard,


I did not write the Alarm plugin, to me it looks like the alarm plugin sent a status of all items in the alarm when any item is triggered (not just the one that is triggered) I only received trigger for the front door because i have a notification there (for open/close) - if i had a notification for all 8 items I would receive 8 notification twice (it send a report for sensor Tripped = 1 and then for Tripped = 0 for motion).  This was not a problem on previous version of the Veralerts plugin, can I help you debug the problem (if you think is a problem)

Below door sensor was not tripped Tripped was: 0 now: 0 (Alarm sent a full summary along with motion triggered) but a Veralert notification was sent but the event itself was not triggered (Event::Evaluate 42 Front Door Opened scene Front Door Opened is false repeat 0/-1 <0x30e62680>)

Let me know how can i help


06   12/09/13 22:36:06.493   Device_Variable::m_szValue_set device: 173 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 2 upnp: 0 v:0xb954a8/NONE duplicate:0 <0x30e62680>
07   12/09/13 22:36:06.493   Event::Evaluate 42 Front Door Opened scene Front Door Opened is false repeat 0/-1 <0x30e62680>
08   12/09/13 22:36:06.494   JobHandler_LuaUPnP::HandleActionRequest device: 203 service: urn:richardgreen:serviceId:VeraAlert1 action: DeviceNotification <0x30e62680>
08   12/09/13 22:36:06.494   JobHandler_LuaUPnP::HandleActionRequest argument DeviceID=173 <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Description=%20Door%20Front%20is%20not%20tripped <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Name=Front%20Door%20Closed <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Service=urn:micasaverde-com:serviceId:SecuritySensor1 <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Variables=Tripped <0x30e62680>
08   12/09/13 22:36:06.495   JobHandler_LuaUPnP::HandleActionRequest argument Msg=%20Door%20Front%20is%20not%20tripped <0x30e62680>
08   12/09/13 22:36:06.496   JobHandler_LuaUPnP::HandleActionRequest argument SceneID=95 <0x30e62680>
08   12/09/13 22:36:06.496   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=GomezVeraAlerts <0x30e62680>

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10070
  • Karma: +761/-141
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #18 on: December 10, 2013, 09:58:10 pm »
Which Alarm Plugin is this ?
I do not know why the previous version would have worked ... Maybe it never sent an alert for the Door closed because you never ran "Notifications Configure" after you added it. You can disable that one event, since that's alerting you of the normal state.
 

Offline elordude

  • Sr. Newbie
  • *
  • Posts: 39
  • Karma: +1/-0
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #19 on: December 12, 2013, 10:26:46 pm »
Richard,

Alarm plugin is Caddx/GE/NetworX NX-584/NX-8E Security System by futzle

This is what i found so far
I had two Front Door notifications one for Door Open (tripped) and the other one for Door Closed (not tripped) - for some reason after upgrade Veralaerts would send a "Door Closed"notification  for ever motion sensor trigger - I assume because the alarm sends a full summary of all sensors with every trigger and the Door is Closed (Not tripped) - this used to work OK before upgrade but not with the latest version.

I removed all the notifications for the (not tripped) for the doors for now and it works but i'm not able to log or know when the doors are closed after they are opened.

I still get all the alarms notification duplicated for some reason - not a big deal just annoying

regards
Harry
 
 

Offline Cor

  • Hero Member
  • *****
  • Posts: 1184
  • Karma: +7/-4
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #20 on: January 09, 2014, 05:28:44 am »
Just updated to 4.5 ... thanks for the user information in the report :-)

Couple of things:
Since no password is required when people are on my  LAN and can  acces the vera GUI and also acces vera alerts  ( which is offcourse not good , but hey , that's vera) . The password from my email adress is very much viewable :-s   Any change to make that hidden?


I just looked at the report , and there is something strange there. I have for 1 smoke detector ,2 notifications ( one for me and one for family and friends) On the report there are 3 notifications , where one has no user. This last one does also not show on the "configuration notification". Not a big thing , but it would be nice to have it all correct.

In the profile setup I see there is a posibility to use templates. The link to to the help page it a bit to tech for me. Is it possible to have in the body a fix message followed by whatever is written in the "notification configuration"?

Thanks,
Cor

Offline mikee123

  • Hero Member
  • *****
  • Posts: 1521
  • Karma: +18/-11
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #21 on: January 08, 2015, 02:43:40 pm »
I am trying to upgrade from 6.29 to 6.31 as i want the pushbullett profile. I have done the manual upgrade (http://myip:3480/data_request?id=update_plugin&Plugin=3008) a fcouple of times followed by a reload and browser refresh. It is downloading some Vera alert files, but it is still stuck on 6.29 without the pushbullet profile

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10070
  • Karma: +761/-141
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #22 on: January 08, 2015, 04:16:57 pm »
Not approved by MCV yet ...

Offline mikee123

  • Hero Member
  • *****
  • Posts: 1521
  • Karma: +18/-11
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #23 on: January 08, 2015, 05:23:15 pm »
That explains it. At least its not my system. I'll be patient and wait...

Offline Jamr

  • Hero Member
  • *****
  • Posts: 738
  • Karma: +22/-8
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #24 on: June 25, 2016, 05:19:28 pm »
Thanks Richard. Your upgrade worked fine top the latest version.
I have a lot of customization of the alerts in your add on. Is there a way to save that in case I have to uninstall and reinstall?

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10070
  • Karma: +761/-141
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #25 on: June 25, 2016, 07:21:23 pm »
I will add it to the list ... I have a release pending the next Vera Release ... I will try to get that in that release.

Offline mr leaver

  • Jr. Member
  • **
  • Posts: 79
  • Karma: +2/-0
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #26 on: July 08, 2016, 02:15:39 am »
How do i a automatically upgraded vera alerts (7.11 now) on a UI5 machine downgrade to the latest UI5 version ?

I found this:
Code: [Select]
http://YourVeraIPAddress:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=3008&Version=30461

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10070
  • Karma: +761/-141
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #27 on: July 08, 2016, 09:51:47 am »
See the first entry!

Offline Jamr

  • Hero Member
  • *****
  • Posts: 738
  • Karma: +22/-8
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #28 on: November 13, 2016, 03:32:00 pm »
I will add it to the list ... I have a release pending the next Vera Release ... I will try to get that in that release.

I missed this. Thanks!

Offline apexi

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Re: Howto Upgrade the Vera Alerts Plugin
« Reply #29 on: April 17, 2017, 03:48:15 am »
Folks have asked how to update the Plugin if you have an older version installed.
The auto-update feature does not work well.

You can update it with the following:

http://YourVeraIPAddress:3480/data_request?id=update_plugin&Plugin=3008


If you accidentally upgrade your Vera running UI5 to a UI7 version, you can recover by restoring the latest UI5 version:

http://YourVeraIPAddress:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=3008&Version=30461

Richard does this still work? I've accidentally upgraded Vera Alert and tried to downgrade it again but it won't go any lower than version 6.43, which doesn't appear to be compatible with my license or UI5. How do I get back to a UI5 version again? THANKS