We have moved at community.getvera.com

Author Topic: UI7 and GE Caddx Plugin  (Read 31578 times)

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #30 on: November 16, 2014, 09:25:44 am »
Futzle, I just noticed the current version of the app is 81, and I'm running version 80. I didn't see the changelog on the code.mios site, is there a place I can find one? Everything is working well so I am in no urge to upgrade unless you recommend it.

I did notice on the code page that you were looking for startup logs from a system with more than 1 partition. I have 2 partitions and my Vera is connected to the Caddx via the NX584 serial card. If you still need these logs I would be happy to help.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
UI7 and GE Caddx Plugin
« Reply #31 on: November 16, 2014, 03:21:55 pm »
Revision log: http://code.mios.com/trac/mios_caddxnx584/log/trunk

I keep the version numbering in apps.mios.com consistent with this so that you can directly compare. In your specific case, revision 81 has no feature you care about, probably.

Edit: spelling

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #32 on: November 17, 2014, 11:56:57 am »
Thanks Futzle!

I spoke a little too soon about how well this was working for me. I may have misconfigured something with my NX584 during setup but I double and triple checked my config and I think it's right. I am able to arm/disarm and see armed/disarmed status, however I just realized that it appears to always be in DetailedArmMode: EntryDelay. I only realized it when I set a scene based on the EntryDelay.

Here is a clip of log where the alarm was disarmed, and my girl armed it and bypassed zone 3 (the pet sets it off all the time) and you can see that it was entrydelay even when disarmed.

Code: [Select]
50      11/17/14 9:45:45.804    luup_log:18: Sending message: 0x1D Positive Acknowledge <0x2ed78680>
50      11/17/14 9:45:45.805    luup_log:18: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x2ed78680>
50      11/17/14 9:45:45.991    luup_log:18: Received good message 0x06, acknowledge requested <0x2ed78680>
50      11/17/14 9:45:45.991    luup_log:18: Message: Incoming message body: 0x00 0x60 0x00 0xc8 0x00 0x62 0x84 0x83 <0x2ed78680>
50      11/17/14 9:45:45.992    luup_log:18: Handling message: 0x06 Partition Status <0x2ed78680>
50      11/17/14 9:45:45.993    luup_log:18: Setting state for partition 1 <0x2ed78680>
06      11/17/14 9:45:45.993    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: LastUser was: Millie now: User 98 #hooks: 0 upnp: 0 skip: 0 v:0xc40bf8/NONE duplicate:0 <0x2ed78680>
50      11/17/14 9:45:45.994    luup_log:18: ChimeEnabled: 1 <0x2ed78680>
06      11/17/14 9:45:45.994    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xc404b8/NONE duplicate:1 <0x2ed78680>
50      11/17/14 9:45:45.994    luup_log:18: AlarmMemory: 0 <0x2ed78680>
06      11/17/14 9:45:45.995    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xc40678/NONE duplicate:0 <0x2ed78680>
50      11/17/14 9:45:45.995    luup_log:18: Alarm: None <0x2ed78680>
06      11/17/14 9:45:45.995    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: Alarm was: None now: None #hooks: 1 upnp: 0 skip: 0 v:0xa9e408/NONE duplicate:1 <0x2ed78680>
50      11/17/14 9:45:45.996    luup_log:18: DetailedArmMode: EntryDelay <0x2ed78680>
06      11/17/14 9:45:45.996    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: EntryDelay now: EntryDelay #hooks: 1 upnp: 0 skip: 0 v:0xc40400/NONE duplicate:1 <0x2ed78680>
50      11/17/14 9:45:45.996    luup_log:18: ArmMode: Armed <0x2ed78680>
06      11/17/14 9:45:45.997    Device_Variable::m_szValue_set device: 19 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Disarmed now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xc40388/NONE duplicate:0 <0x2ed78680

Any ideas? I also notice that when it goes through an entrydelay it always shows user 98, which doesn't exist. I assumed that was just reflecting that the NX8 did something on it's own.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
UI7 and GE Caddx Plugin
« Reply #33 on: November 17, 2014, 06:53:56 pm »
User 98 is the user that the system reports when you press the Away or Arm button on the keypad without entering a PIN. I named that user "Keypad" on my own Vera.

Your snippet of log definitely shows that the DetailedArmMode is getting stuck. That shouldn't happen. But from that snippet I can't see what broke because it happened before the capture began. If you can catch the log around the instant the alarm goes from Exit Delay to Armed, or from Armed to Entry Delay, or from Entry Delay to Disarmed (but scrub the log to prevent me seeing your PIN), I might have a better chance.

Edit: on further reflection I think I have enough information from you already. I think that the plugin is getting confused over the fact that there are two possible entry delays configurable per partition. I'm at work right now but when I get home I will give you a patch to try out.

Edit: Try this variant of the L_CaddxNX584Security.lua file.  It's less sensitive to the "Entry Delay" bits in the Partition Status message, one of which for you is inexplicably turned on permanently.  I hope it doesn't lead to false negatives for other users...
« Last Edit: November 18, 2014, 02:29:18 am by futzle »

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #34 on: November 18, 2014, 04:25:01 am »
User 98 is the user that the system reports when you press the Away or Arm button on the keypad without entering a PIN. I named that user "Keypad" on my own Vera.

Your snippet of log definitely shows that the DetailedArmMode is getting stuck. That shouldn't happen. But from that snippet I can't see what broke because it happened before the capture began. If you can catch the log around the instant the alarm goes from Exit Delay to Armed, or from Armed to Entry Delay, or from Entry Delay to Disarmed (but scrub the log to prevent me seeing your PIN), I might have a better chance.

Edit: on further reflection I think I have enough information from you already. I think that the plugin is getting confused over the fact that there are two possible entry delays configurable per partition. I'm at work right now but when I get home I will give you a patch to try out.

Edit: Try this variant of the L_CaddxNX584Security.lua file.  It's less sensitive to the "Entry Delay" bits in the Partition Status message, one of which for you is inexplicably turned on permanently.  I hope it doesn't lead to false negatives for other users...

Thanks Futzle! I really appreciate the help. Here are some of the before logs, but I am still not sure I captured what you are looking for. In all of the logs I have seen, it is always entrydelay no matter what. You are correct in stating there are 2 possible entrydelay timers, and I think mine are both set to a time but I don't think any zones are set on delay 2.

Also, I do have 2 partitions, one is my shop and it's pretty much always armed. I did not notice if this was an issue before I added the partition. Another item of note is that I partitioned the system after installing the plugin, but there didn't seem to be any issues with that and the new partition came up as a new device right away.

I am adding the new file now and will report back. Thanks again!

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #35 on: November 18, 2014, 05:14:00 am »
And BOOM! Just like that, you fixed it. Great job! I really appreciate the assistance. I owe you a couple of beers. Startup log attached. It's currently reporting correctly for both partitions. Hopefully that will remain true during entry and exit delay modes.

While I am here I want to clue you in on another strange thing with UI7 that you may already know about. I did some testing with my girlfriend last night while you were writing the fix and found that most of your comments about UI7 and the Caddx hold true in relation to devices (zones) being armed or bypassed when bypass is enabled on the NX584. When armed, I am able to bypass zones, and that reflects properly on the Caddx, however I noticed that when the HouseMode changes in UI7 the bypass/armed status of the devices does not sync with the Caddx (at least when the Caddx is disarmed and ready). Example: Caddx disarmed and ready, I switched the UI7 HouseMode to Home, which I have configured under "My Modes" do bypass motion sensors and some doors. The Caddx does not bypass those zones, however when the Caddx is armed and I bypass one in Vera it does switch to bypass. I did not test switching modes while the Caddx was armed. This is not really a huge issue for me, just something that I noticed.

And a question about Caddx configuration: My Caddx seems to be set to only arm when it's "ready" and an exit has to be detected during exitdelay in order to arm else it switches to stay. How does this affect my remote control with the plugin? If I disarmed my shop right now over the web, and clicked arm again, then I assume there would be a failed exitdelay and it would switch to stay. Then if my girlfriend happened to open the door the alarm would be instant instead of entrydelay. Can I just disable automatic bypass at location 23, segment 1, to resolve this issue?


Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: UI7 and GE Caddx Plugin
« Reply #36 on: November 18, 2014, 05:49:30 am »
Thanks for confirming that the change works for you. I'll include it in version 82 so you won't need to patch the file manually again.

I'm afraid that I've got no suggestions about the remote arming away/stay conundrum. My NX-4 hasn't been configured that way so it's always Worked For Me. I guess you could just try it and see. (To be honest, I didn't know that the Caddx alarm suffered from this "feature"; there's a great deal of discussion on the DSC alarm forums about a very similar behaviour, which I thought was limited to that system. So I learned something.)

The whole House Modes fiasco in UI7, where you have to specify Arm or Bypass for every sensor without the option to leave its state unchanged, is why I'm now recommending you go back to your NX-584 or NX-8E and disable the Toggle Zone Bypass message in the interface. You lose the ability to bypass a zone from Vera, but you don't run the risk of a house mode change disabling your entire security system.

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #37 on: November 18, 2014, 08:04:34 am »
Thanks for confirming that the change works for you. I'll include it in version 82 so you won't need to patch the file manually again.

I'm afraid that I've got no suggestions about the remote arming away/stay conundrum. My NX-4 hasn't been configured that way so it's always Worked For Me. I guess you could just try it and see. (To be honest, I didn't know that the Caddx alarm suffered from this "feature"; there's a great deal of discussion on the DSC alarm forums about a very similar behaviour, which I thought was limited to that system. So I learned something.)

The whole House Modes fiasco in UI7, where you have to specify Arm or Bypass for every sensor without the option to leave its state unchanged, is why I'm now recommending you go back to your NX-584 or NX-8E and disable the Toggle Zone Bypass message in the interface. You lose the ability to bypass a zone from Vera, but you don't run the risk of a house mode change disabling your entire security system.

Thanks for such a quick fix! I have been reading the NX8 manual and if I just disable the auto bypass I think it will kill the remote arming issue. It's not even that big of a deal if it goes into stay mode as long as it gets disarmed from the app instead of opening the door. I'm really just happy to see a detailedarmmode so I can use the system to trigger scenes.

I don't mind the toggle zone bypass, as I am always deployed and I prefer to have the capability to make changes remotely. From my little bit of testing yesterday it appears that a house mode change won't disable anything, as I can only get the Caddx to bypass a sensor when I toggle it individually in Vera. Since I am always away I am would even consider entering the program mode from your plugin if that is possible. Getting my girlfriend to make changes at the keypad is not my preference.

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #38 on: November 18, 2014, 02:31:20 pm »
Futzle, once again I spoke too soon! I should stop doing that. Everything was fine until the first exitdelay. I set a scene to bypass zone 3 upon exit delay and it appears the scene ran. It also switched to away mode but it seems at that point the Vera crashed. It appeared that the exit door never closed which would have caused an exit error I suppose but indeed the door was closed. I suppose it was a bad idea to bypass a zone while in exitdelay. Now I have no connection and the log has this repeated message:

Code: [Select]
50 11/18/14 13:12:25.551 luup_log:18: Global handlers not set up yet <0x2f764680>
50 11/18/14 13:12:25.551 luup_log:18: Global handlers not set up yet <0x2f764680>
50 11/18/14 13:12:25.552 luup_log:18: Global handlers not set up yet <0x2f764680>02 11/18/14 13:18:09.823 MMSStorage::GetDataToSend sending everything--BROADCAST <0x303aa680>
01 11/18/14 13:18:09.824 XXX-MMSStorage::SendData 0xc90740 WOKE 3/0 set:1 <0x2f5aa680>
01 11/18/14 13:18:09.824 XXX-MMSStorage::SendData 0xc90740 done <0x2f5aa680>
01 11/18/14 13:18:09.825 XXX-MMSStorage::SendData 0xc90740 send 10000 <0x2f5aa680>
01 11/18/14 13:18:09.825 MMSStorage::SendData --BROADCAST <0x2f5aa680>
01 11/18/14 13:18:09.835 XXX-MMSStorage::SendData GOING TO SLEEP <0x2f5aa680>
02 11/18/14 13:18:09.829 MMSStorage::GetDataToSend before lock <0x303aa680>
02 11/18/14 13:18:09.839 MMSStorage::GetDataToSend got lock <0x303aa680>
02 11/18/14 13:18:09.840 MMSStorage::GetDataToSend send:10000 sendsize:10000 bytessent:0 buffer:16372 <0x303aa680>50 11/18/14 13:24:38.106 luup_log:18: Ignoring byte 43 <0x2c358680>
50 11/18/14 13:24:38.116 luup_log:18: Ignoring byte 42 <0x2c358680>
50 11/18/14 13:24:38.126 luup_log:18: Ignoring byte 56 <0x2c358680>

I am currently rebooting equipment to see if it will come up, and then I will perhaps try to restore the original file.

Status Update: Sorry for the alarm. That was quite odd, but a couple of Vera reboots and a refresh of the serial port configuration seems to have resolved the issue. I may have had an exiterror, so my girl is going to test the door sensor several times. I've modified the questionable scene to wait 5 minutes to bypass the zone, we'll see how that goes.

I did log most of that activity in putty, so if any of it interests you I can upload it.

Reason for edit:Status update
« Last Edit: November 18, 2014, 03:34:53 pm by YzRacer »

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #39 on: November 22, 2014, 05:28:51 pm »
Futzle, your patch is still working very well, however I rebooted today and it seemed to end up in a strange state again. I fixed it by once again changing my baud rate, wait a minute, then change it back.

Code: [Select]
50 11/22/14 14:47:59.572 luup_log:18: Ignoring byte 28 <0x2bc5a680>
50 11/22/14 14:47:59.583 luup_log:18: Ignoring byte 40 <0x2bc5a680>
50 11/22/14 14:47:59.593 luup_log:18: Ignoring byte 81 <0x2bc5a680>
50 11/22/14 14:47:59.603 luup_log:18: Ignoring byte 18 <0x2bc5a680>
50 11/22/14 14:47:59.613 luup_log:18: Ignoring byte ff <0x2bc5a680>
08 11/22/14 14:48:00.620 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: ModifyUserData <0x2ea9b680>
08 11/22/14 14:48:00.620 JobHandler_LuaUPnP::HandleActionRequest argument inUserData={"devices":{"devices_83":{"states":{"states_5":{"value":"38400"}}}},"scenes":{},"sections":{},"rooms":{},"InstalledPlugins":[],"PluginSettings":[],"users":{}} <0x2ea9b680>
08 11/22/14 14:48:00.621 JobHandler_LuaUPnP::HandleActionRequest argument DataFormat=json <0x2ea9b680>
06 11/22/14 14:48:00.622 Device_Variable::m_szValue_set device: 83 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x7f6610/NONE duplicate:1 <0x2ea9b680>
06 11/22/14 14:48:00.622 Device_Variable::m_szValue_set device: 83 service: urn:micasaverde-com:serviceId:HaDevice1 variable: LastUpdate was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2ea9b680>
01 11/22/14 14:48:00.845 UserData::WriteUserData saved--before move File Size: 39629 save size 39629 __LEAK__ this:229376 start:290816 to 0xec3000 <0x2ba5a680>
02 11/22/14 14:48:00.845 UserData::TempLogFileSystemFailure start <0x2ba5a680>
02 11/22/14 14:48:00.874 UserData::TempLogFileSystemFailure 5206
-rw-r--r--    1 root     root             0 Sep 24 19:15 /etc/cmh/320.reset
-rw-r--r--    1 root     root            33 Nov 16 11:54 /etc/cmh/HW_Key


Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: UI7 and GE Caddx Plugin
« Reply #40 on: November 22, 2014, 08:05:46 pm »
Unfortunately that part of the log hasn't got any information that is useful to me. Even the first line of it will only happen after some other error, probably the true cause. The symptoms are indicative of an intermittent serial connection dropout. These are buggers to pinpoint, unfortunately.

Catch the log right from the Luup restart and I might be able to point to something less vague.

Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #41 on: November 23, 2014, 03:04:33 am »
Unfortunately that part of the log hasn't got any information that is useful to me. Even the first line of it will only happen after some other error, probably the true cause. The symptoms are indicative of an intermittent serial connection dropout. These are buggers to pinpoint, unfortunately.

Catch the log right from the Luup restart and I might be able to point to something less vague.

Futzle, thanks for the reply and sorry for the incomplete log. I hopped in after the issue already started and didn't catch the beginning, then assumed you might just recognize the issue. Just knowing that it's a possible issue with the actual serial connection is a big help. If it happens again I'll be sure to just reboot and grab the whole event.

Perhaps someone can suggest an easy solution to a scene I am trying to create. My zone 3 motion sensor is somewhat sensitive and even though it's mounted at 9 feet the cat is still able to trip it fairly easily. I want to bypass zone 3 each time the alarm is armed, however I discovered this is best done while disarmed. I should have just read the book:

BYPASSING ZONES
If you wish to bypass one or more zones, this must be done while the
system is in the disarmed state.

Maybe someone has a suggestion on how to accomplish the bypass? The Vera does successfully bypass the zone when commanded while disarmed.

The manual does state that pressing "Bypass" when armed will disarm interior zones. However I don't see a "bypass" command in the device actions for the plugin. I am pretty sure my keypads are 1448e models. Here's a clip from the book:

CHANGING MODES WHILE SYSTEM IS ARMED
 Pressing the [STAY] key will turn on/off (toggle) a delay on entry/exit
doors and turn on/off (toggle) the instant icon.
 (Optional) Press the [BYPASS] key at this time to turn on/off (toggle)
all designated interior zones.

Offline dinochronos

  • Full Member
  • ***
  • Posts: 116
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #42 on: January 03, 2015, 09:39:37 am »
Futzle,  I upgraded my Vera from Vera 3 to Vera Edge.  The Version of the plugin is 81 that ti dowloaded.

Before the Serial Port worked fine with the RS232 USB Adapter on my Vera 3 and app works perfectly.
 
When I plug in the same exact cable to the Vera Edge, the Serial Port selection dropdown stays stuck on "NONE" and does not allow me to choose the FTDSIO Adapter on the drop down menu so I can configure the rest of the parameters for connecting.

I have tried to plug/unplug and reset the unit but no ability to connect the vera edge to the USB port as before on the Vera 3....

Any thoughts?
Thanks

Offline dinochronos

  • Full Member
  • ***
  • Posts: 116
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #43 on: January 03, 2015, 02:15:01 pm »
Futzle, I just spoke with Vera Support today Re the USB Direct Serial port connection issue, they reported they were aware that the Edge did have an issue with USB connectivity and would be publishing a firmware update to resolve this sometime this month.  Unless you have another solution or workaround I can wait to see if this resolves and I can get my GE Security system back working again same as the Vera 3  :)


Offline YzRacer

  • Full Member
  • ***
  • Posts: 139
  • Karma: +0/-0
Re: UI7 and GE Caddx Plugin
« Reply #44 on: January 04, 2015, 03:26:06 pm »
Thanks for confirming that the change works for you. I'll include it in version 82 so you won't need to patch the file manually again.

I'm afraid that I've got no suggestions about the remote arming away/stay conundrum. My NX-4 hasn't been configured that way so it's always Worked For Me. I guess you could just try it and see. (To be honest, I didn't know that the Caddx alarm suffered from this "feature"; there's a great deal of discussion on the DSC alarm forums about a very similar behaviour, which I thought was limited to that system. So I learned something.)

The whole House Modes fiasco in UI7, where you have to specify Arm or Bypass for every sensor without the option to leave its state unchanged, is why I'm now recommending you go back to your NX-584 or NX-8E and disable the Toggle Zone Bypass message in the interface. You lose the ability to bypass a zone from Vera, but you don't run the risk of a house mode change disabling your entire security system.

Thanks for such a quick fix! I have been reading the NX8 manual and if I just disable the auto bypass I think it will kill the remote arming issue. It's not even that big of a deal if it goes into stay mode as long as it gets disarmed from the app instead of opening the door. I'm really just happy to see a detailedarmmode so I can use the system to trigger scenes.

I don't mind the toggle zone bypass, as I am always deployed and I prefer to have the capability to make changes remotely. From my little bit of testing yesterday it appears that a house mode change won't disable anything, as I can only get the Caddx to bypass a sensor when I toggle it individually in Vera. Since I am always away I am would even consider entering the program mode from your plugin if that is possible. Getting my girlfriend to make changes at the keypad is not my preference.

Futzle, thanks again for all of your help with UI7. I have been busy reading the forum and learning all about the Vera and I feel like I have gained a lot of knowledge in the last couple of months. I want to clarify a couple of things I mentioned:

My system will arm remotely without a door being opened/closed for a proper "exit". I have successfully done that several times when my girlfriend left without arming.

A motion sensor can be bypassed with the Vera. It doesn't work well with mode changes unless your patterns are very specific since there are a lot of variables involved. I am currently using PLEG, with a condition that will bypass my interior problem zone whenever the system is "Ready" for > 1 minute. As I mentioned before attempting to bypass a zone when in exit delay or armed mode can cause issues, so it's best to avoid that situation.

Your fix for the continuous ExitDelay indication on the UI7 dashboard is holding up well, however I have noticed some issues with PLEG:

Using triggers to monitor detailed arm mode status doesn't always work. For some reason PLEG doesn't see triggers as true when they are in fact true or it may see triggers as true when they are false. I suspect this may have something to do with the fix you implemented but I am not certain. I have had better luck using device properties with PLEG and monitoring the detailed arm mode with conditions of eq "ExitDelay" and such. This always works well for Armed and Ready modes, however today I noticed it missed "ExitDelay" twice. I'm not 100% certain that isn't an issue with the order of my PLEG conditions but I would think it should identify true when the state changes and is true. I've attached my PLEG status report for your review if you are interested. It clearly shows some discrepancy between the triggers and the device properties.