We have moved at community.getvera.com

Author Topic: Re: Setup  (Read 2445 times)

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Setup
« on: September 13, 2011, 02:44:45 pm »
Futzle, i must say the new revision was a wonderful change.  I loaded it up over the weekend.  Initally I was unable to register any zones..it would just search for them after I selected the tab.  The log would repeat this message:
50   09/11/11 16:19:57.239   luup_log:6: Received good message 0x04, acknowledge requested <0x3c10>
50   09/11/11 16:19:57.241   luup_log:6: Message: Incoming message body: 0x00 0x01 0x00 0x1b 0xf0 0x00 0x00 0x00 0x00 <0x3c10>
50   09/11/11 16:19:57.242   luup_log:6: Handling message: 0x04 Zone Status <0x3c10>
50   09/11/11 16:19:57.243   luup_log:6: Valid zone 1 <0x3c10>
01   09/11/11 16:19:57.243   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:515: attempt to index field '?' (a nil value) <0x3c10>
I went into the alarm to make sure my settings there made sense.  I had not turned on the "log message" that you had listed as an option in the instructions. It is listed as "log event request" in zone 3 segment3 on the NX-584. This did the trick!  Upon restart all 7 zones were instantly found it is up and running.  Thanks for your work on this.  I will start to play with it a bit more this weekend.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #1 on: September 13, 2011, 05:40:50 pm »
Hi sarabart,

It sounds a bit coincidental; the plugin doesn't actually send Log Event Request messages (yet), so it's hard to imagine how it made a difference.  But whatever, you are up and running.  Welcome to the club!

I'll take a look on line 515 and see why it's reporting an error.

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #2 on: September 15, 2011, 10:20:12 am »
Coincidence it was.  I armed the system just find with Vera, although I must enter the code to do so.  The log after arming the system still gives the same error as before but now line 477.
50   09/14/11 22:39:47.219   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:39:47.221   luup_log:6: Message: Incoming message body: 0x00 0x60 0x00 0xe8 0x60 0x01 0x04 0xc0 <0x4011>
50   09/14/11 22:39:47.221   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
50   09/14/11 22:39:47.222   luup_log:6: Setting state for partition 1 <0x4011>
06   09/14/11 22:39:47.223   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: LastUser was: User 1 now: User 1 #hooks: 0 upnp: 0 v:0x785800/NONE duplicate:0 <0x4011>
50   09/14/11 22:39:47.241   luup_log:6: ChimeEnabled: 1 <0x4011>
06   09/14/11 22:39:47.241   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: ChimeEnabled was: 1 now: 1 #hooks: 0 upnp: 0 v:0x7996d0/NONE duplicate:1 <0x4011>
50   09/14/11 22:39:47.242   luup_log:6: AlarmMemory: 0 <0x4011>
06   09/14/11 22:39:47.243   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: AlarmMemory was: 0 now: 0 #hooks: 0 upnp: 0 v:0x785b88/NONE duplicate:0 <0x4011>
50   09/14/11 22:39:47.244   luup_log:6: Alarm: None <0x4011>
06   09/14/11 22:39:47.245   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: Alarm was: None now: None #hooks: 1 upnp: 0 v:0x7996f0/NONE duplicate:1 <0x4011>
50   09/14/11 22:39:47.246   luup_log:6: DetailedArmMode: ExitDelay <0x4011>
06   09/14/11 22:39:47.246   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: DetailedArmMode was: ExitDelay now: ExitDelay #hooks: 0 upnp: 0 v:0x7996b0/NONE duplicate:1 <0x4011>
50   09/14/11 22:39:47.247   luup_log:6: ArmMode: Armed <0x4011>
06   09/14/11 22:39:47.248   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: ArmMode was: Armed now: Armed #hooks: 0 upnp: 0 v:0x799ca8/NONE duplicate:1 <0x4011>
50   09/14/11 22:39:47.248   luup_log:6: Sending message: 0x1D Positive Acknowledge <0x4011>
50   09/14/11 22:39:47.250   luup_log:6: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x4011>
50   09/14/11 22:39:47.283   luup_log:6: Received good message 0x07, acknowledge requested <0x4011>
50   09/14/11 22:39:47.284   luup_log:6: Message: Incoming message body: 0x57 0x02 0x02 0x02 0x02 0x02 0x02 0x02 <0x4011>
50   09/14/11 22:39:47.285   luup_log:6: Handling message: 0x07 Partitions Snapshot <0x4011>
50   09/14/11 22:39:47.285   luup_log:6: Sending message: 0x1D Positive Acknowledge <0x4011>
50   09/14/11 22:39:47.287   luup_log:6: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x4011>
50   09/14/11 22:39:58.901   luup_log:6: Received good message 0x08, acknowledge requested <0x4011>
50   09/14/11 22:39:58.902   luup_log:6: Message: Incoming message body: 0x0c 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x01 0x4b <0x4011>
50   09/14/11 22:39:58.903   luup_log:6: Handling message: 0x08 System Status <0x4011>
50   09/14/11 22:39:58.904   luup_log:6: Sending message: 0x1D Positive Acknowledge <0x4011>
50   09/14/11 22:39:58.905   luup_log:6: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x4011>
50   09/14/11 22:39:59.179   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:39:59.181   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:39:59.181   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:39:59.183   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
50   09/14/11 22:40:01.679   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:40:01.680   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:40:01.681   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:40:01.682   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
50   09/14/11 22:40:04.169   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:40:04.170   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:40:04.171   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:40:04.172   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
50   09/14/11 22:40:06.669   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:40:06.670   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:40:06.671   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:40:06.672   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
02   09/14/11 22:40:07.255   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:07.356   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:07.456   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:07.557   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:07.657   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:07.758   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:08.814   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.815   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.817   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.819   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.821   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.823   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:08.824   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:08.832   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
02   09/14/11 22:40:08.852   UPnPCallbackEventHandler 4 start PIDLOG2 6543 <0x240a>
02   09/14/11 22:40:08.872   UPnPCallbackEventHandler 4 start PIDLOG2 6542 <0x2009>
50   09/14/11 22:40:09.165   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:40:09.166   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:40:09.167   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:40:09.168   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
50   09/14/11 22:40:11.659   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:40:11.661   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:40:11.661   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:40:11.662   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>
Is error message continues to repeat.
I have noticed that Vera reads the alarm as in "exit delay" state even after the alarm has disarmed and rearmed overnight and unarmed this morning all by the keypad.  Not sure if this is related. Thanks, hopefully this will help your investigation.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #3 on: September 15, 2011, 06:03:43 pm »
50   09/14/11 22:39:59.179   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/14/11 22:39:59.181   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/14/11 22:39:59.181   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/14/11 22:39:59.183   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:477: attempt to index field '?' (a nil value) <0x4011>

Well, that's nuts.  That's a status message for partition 4.  (You've only got one partition, right?)  That partition hasn't been configured, so why would it be sending you a status update for it?  It's unlikely that this is a transmission bitflip, since the checksum was OK.

Oh well, I suppose that when reverse-engineering a protocol one must accept even the improbable as mandatory.  I've added a paranoid check to the plugin that will silently ignore partition status updates for partitions that don't exist. 

Please update (all files) to the latest version (@42 is where I checked in the change), and let me know if your panel is happier.

There are other places in the code where I'm being lazy about checks too, so we will probably have to go through this cycle one or two times more.  Sorry.

Quote
I have noticed that Vera reads the alarm as in "exit delay" state even after the alarm has disarmed and rearmed overnight and unarmed this morning all by the keypad.  Not sure if this is related.

Definitely related.  With the fix in version @42, this shouldn't happen (at least not in that line of code).

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #4 on: September 15, 2011, 09:44:20 pm »
Correct, I should just have one partition (although I will look to make sure it was programed in the alarm correctly). It just wouldn't be any fun if it just made complete sense. I will test it out when I get a chance and let you know the results.  Thanks!

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #5 on: September 19, 2011, 10:37:02 pm »
It looks like the latest revision @42 helped with my errors.  I can arm/disarm with a code only, but I wonder if quick arm etc is not programed into my system...I will check.  Now I have been trying to set a scene that notifies me if the armed partition is tripped by any one of the 7 sensors (i.e. the siren is sounding).  The choices for event triggers for partition 1 are as follows:
armed state
armed detailed state
alarm active
PIN code entered
vendor status code

My UI always shows each zone as "armed" regardless whether the system is armed or on standby, the appropriate exception is in "stay" mode when it truthfully reflects 1 motion sensor as disarmed.  I assume this is related to the fact that the keypad will beep each time a door is opened.  (We set this because we have a 4 year old escape artist).  My next best choice is "alarm active" but this does not trigger a notification when when the siren sounds.  I have tried my best to attempt this without bothering you but once again I reach across the pond for help!  Thanks-

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #6 on: September 20, 2011, 12:16:26 am »
Hi sarabart,

It should be "alarm active", yes. If that's not triggering when the siren sounds, then there's a bug, or your system is configured in a way I'm not expecting. I might need a Luup log showing your system deliberately entering the siren state, so I can see what I'm missing.

On zones, think of "Armed" as "not bypassed". Zones' armedness has nothing to do with the state of the partition. It's MCV's terminology; I am just using their device file.

Edit: to check if Quick Arm is enabled, open the alarm device's Configuration panel, and look for Secondary Keypad Function.  If that option is on, then you should be able to do Quick Arm and Quick Stay.  (Oh, I see that the partition also has to be programmed to allow it.  You will need to go into the program mode to check that.)

Normally there's an entry delay in between a zone being tripped and the siren sounding.  I don't know what your expectations are of how the plugin should deal with that intervening time with respect to notifications.  It would be informative to know, since you're a Real User and I don't get many of them.

You say you've got some zones set up so that the keypad chimes when the zone is tripped. Reading the manual for the NX-8E, I think that this option is programmed on a per-zone basis; it's probably another coincidence.
« Last Edit: September 20, 2011, 06:55:23 am by futzle »

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #7 on: September 22, 2011, 10:07:54 pm »
Hi Futzle- I finally got a chance to log the alarm being tripped. I set up a scene for partition 1 with "alarm active" to trigger a notification.  The log from the alarm being set to the repeating error after zone 1 triggered the siren is shown:

50   09/22/11 20:27:36.285   luup_log:6: ArmMode: Armed <0x4011>
06   09/22/11 20:27:36.286   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:AlarmPartition1 variable: ArmMode was: Armed now: Armed #hooks: 0 upnp: 0 v:0x79e250/NONE duplicate:1 <0x4011>
50   09/22/11 20:27:36.287   luup_log:6: Sending message: 0x1D Positive Acknowledge <0x4011>
50   09/22/11 20:27:36.288   luup_log:6: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x4011>
50   09/22/11 20:27:36.314   luup_log:6: Received good message 0x07, acknowledge requested <0x4011>
50   09/22/11 20:27:36.316   luup_log:6: Message: Incoming message body: 0x1f 0x02 0x02 0x02 0x02 0x02 0x02 0x02 <0x4011>
50   09/22/11 20:27:36.316   luup_log:6: Handling message: 0x07 Partitions Snapshot <0x4011>
50   09/22/11 20:27:36.317   luup_log:6: Sending message: 0x1D Positive Acknowledge <0x4011>
50   09/22/11 20:27:36.318   luup_log:6: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x4011>
50   09/22/11 20:27:37.469   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:37.471   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:37.471   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:37.473   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:39.969   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:39.971   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:39.971   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:39.972   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:42.462   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:42.464   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:42.464   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:42.465   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:44.959   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:44.961   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:44.961   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:44.962   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
02   09/22/11 20:27:45.748   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:27:45.848   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:27:45.948   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:27:46.048   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:27:46.148   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:27:46.249   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
50   09/22/11 20:27:47.457   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:47.459   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:47.459   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:47.461   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:49.949   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:49.950   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:49.951   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:49.952   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:52.449   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:52.451   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:52.451   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:52.452   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:54.944   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:54.945   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:54.946   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:54.947   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:57.439   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:57.440   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:57.441   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:57.442   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:27:59.939   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:27:59.940   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:27:59.941   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:27:59.942   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
50   09/22/11 20:28:02.429   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:28:02.431   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:28:02.431   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:28:02.432   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>
02   09/22/11 20:28:03.984   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:03.985   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:03.987   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:03.989   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:03.991   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:28:03.993   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:28:03.995   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:04.002   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
02   09/22/11 20:28:04.022   UPnPCallbackEventHandler 4 start PIDLOG2 25497 <0x2009>
02   09/22/11 20:28:04.042   UPnPCallbackEventHandler 4 start PIDLOG2 25498 <0x240a>
50   09/22/11 20:28:04.929   luup_log:6: Received good message 0x06, acknowledge requested <0x4011>
50   09/22/11 20:28:04.931   luup_log:6: Message: Incoming message body: 0x03 0x28 0x00 0x00 0x00 0x00 0x04 0x80 <0x4011>
50   09/22/11 20:28:04.931   luup_log:6: Handling message: 0x06 Partition Status <0x4011>
01   09/22/11 20:28:04.932   LuaInterface::CallFunction-2 lu_incoming failed /etc/cmh-ludl/L_CaddxNX584Security.lua:480: bad argument #2 to 'format' (integer expected, got nil) <0x4011>

This looks like the same error message as before just a couple of lines past, hopefully i updated that revision properly. The pattern of incoming message to critical error is repeated.  My interface showed the appropriate status of the partition in real time until the siren sounded.  I'm sure it doesn't surprise you that after that it continued to read "stay" as the status, and each zone devise no longer displays the real time status of the door opened etc. (the red guy running").  I presume it just gets hung up on this error and can no longer receive a partiton status and zone status.  Obviously the scene was never triggered and the notification never sent.


Normally there's an entry delay in between a zone being tripped and the siren sounding.  I don't know what your expectations are of how the plugin should deal with that intervening time with respect to notifications

I have only 1 zone with an entry delay, all the rest trigger the siren immediately.  We really only use one entrance when returning by car and that is the only time we would set the alarm.  I did, by the way, not use that zone to test this scene so there was an immediate siren.
Thanks-

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #8 on: September 22, 2011, 11:29:21 pm »
Oh, how embarrassing. I can see the typo in the Lua file.

I can't fix it right now (I'm at work) but if you want this before I get home, you can open The L_*.lua  file in a text editor, go to line 480 and replace the variable "p" with "partition".

Edit: Now fixed in version @47.  Update all the files, because there are interactions between them.  This might still not trigger the "alarm active" event, but at least now the log will tell me why.
« Last Edit: September 23, 2011, 05:25:21 am by futzle »

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #9 on: September 23, 2011, 09:06:10 am »
Thanks for the fast reply.   I will likely not be able to give it a run until Sunday but I will let you know how it goes!

Offline sarabart

  • Newbie
  • *
  • Posts: 13
  • Karma: +0/-0
Re: Re: Setup
« Reply #10 on: September 25, 2011, 09:37:21 pm »
Hi Futzle- that little change in the Lua code seemed to do the trick.  Siren sounds and notifications fly.  I even added the Vera Alert plugin and Android app so I get a great siren sound on my phone.  I will test it a few more times to stress it.   Anything in particular that you would like me to check please let me know.  Thanks-