EnvisaLink Trigger on Zone Open doesn't work....

[sorka]

It's clear from the logs that your parsing the Envisalink protocol correctly as each event is seen and logged in plain english.

So the problem must be further upstream where you're mapping parsed high level notifications/events to event trigger API.

[sorka]

Well something happened which I hope provides a clue.

I changed the event to "Device Status Change"

In the "Status:" dropdown, there is just one that works and that is "Set Any Status" But it fires when the zone opens and closes. I tried "Set On" and no luck.

Also even if that worked there doesn't appear to be a way to trap:

Alarm Armed Away
Alarm Armed Stay
AC Panel Fualt
TLM Fault

and about a half dozen other DSC events that I use that don't seem to have corresponding devices analogs.

[spud]

I don't think the problem is the EnvisaLink firmware, a lot of users are successfully running the HS3 plugin with a EVL4

I would need to fire my old HS2 install to debug (which I' m a bit reluctant to). Since the devices are correctly updating can' t you use that to triggers your events instead of using the specific EnvisaLink triggers?

[sorka]

I'm wondering if this is such a new version that anyone has tested it with HS3 as well?

[sorka]

After your sugestion, I started contemplating upgrading in the near future.

I just missed the Black Friday Coupon for 50% off.

HS3PRO (Upgrade from HS2)
$237.47
(reg. $474.95)

Looks like there are several such sales a year so I'll put it on my list to upgrade when the next sale comes around and put a chunk of time into migrating.

[sorka]

Nothing looks wrong in the debug level logging:

8/10/2016 12:00:37 PM EnvisaLink INFO Zone 8 status change: Opened
8/10/2016 12:00:37 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
8/10/2016 12:00:37 PM EnvisaLink INFO Partition 1 status change: ReadyForceArmingEnabled
8/10/2016 12:00:39 PM EnvisaLink DEBUG ZoneOpen 007
8/10/2016 12:00:39 PM EnvisaLink INFO Zone 7 status change: Opened
8/10/2016 12:00:43 PM EnvisaLink DEBUG ZoneRestored 007
8/10/2016 12:00:43 PM EnvisaLink INFO Zone 7 status change: Closed
8/10/2016 12:00:45 PM EnvisaLink DEBUG ZoneRestored 008
8/10/2016 12:00:45 PM EnvisaLink INFO Zone 8 status change: Closed
8/10/2016 12:00:45 PM EnvisaLink DEBUG PartitionReady 1
8/10/2016 12:00:45 PM EnvisaLink INFO Partition 1 status change: Ready
8/10/2016 12:01:00 PM ISY Insteon EVNT: ISY Heartbeat message.
8/10/2016 12:01:00 PM ISY Insteon EVNT: Event Queue is now empty.
8/10/2016 12:01:24 PM EnvisaLink DEBUG ZoneOpen 008
8/10/2016 12:01:24 PM EnvisaLink INFO Zone 8 status change: Opened
8/10/2016 12:01:24 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
8/10/2016 12:01:24 PM EnvisaLink INFO Partition 1 status change: ReadyForceArmingEnabled
8/10/2016 12:01:25 PM ISY Insteon EVNT: ISY Heartbeat message.
8/10/2016 12:01:25 PM ISY Insteon EVNT: Event Queue is now empty.
8/10/2016 12:01:28 PM EnvisaLink DEBUG ZoneRestored 008
8/10/2016 12:01:28 PM EnvisaLink INFO Zone 8 status change: Closed
8/10/2016 12:01:28 PM EnvisaLink DEBUG PartitionReady 1
8/10/2016 12:01:28 PM EnvisaLink INFO Partition 1 status change: Ready
8/10/2016 12:01:32 PM ISY Insteon EVNT: ISY is busy.
8/10/2016 12:01:32 PM ISY Insteon EVNT: Event Queue is now empty.
8/10/2016 12:01:32 PM ISY Insteon EVNT: ISY is idle.
8/10/2016 12:01:32 PM ISY Insteon EVNT: Event Queue is now empty.
8/10/2016 12:01:34 PM EnvisaLink DEBUG ZoneOpen 008
8/10/2016 12:01:34 PM EnvisaLink INFO Zone 8 status change: Opened
8/10/2016 12:01:34 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
8/10/2016 12:01:34 PM EnvisaLink INFO Partition 1 status change: ReadyForceArmingEnabled
8/10/2016 12:01:38 PM EnvisaLink DEBUG ZoneRestored 008
8/10/2016 12:01:38 PM EnvisaLink INFO Zone 8 status change: Closed
8/10/2016 12:01:38 PM EnvisaLink DEBUG PartitionReady 1
8/10/2016 12:01:38 PM EnvisaLink INFO Partition 1 status change: Ready

[sorka]

Do the HS devices are updated correctly?

Yes, the device statuses are updating correctly. That was true even with the parsing error log message prior to your update.

Is info the most verbose log level? Is there a secret more verbose level

[spud]

Do the HS devices are updated correctly?

[sorka]

I tried a variety of other Envisalink Trigger types to see if anything else such as arming, disarming, turning on off chimes, etc.


All those DSC events show in the log file but the HS event itself isn't triggered.

So close

[sorka]

Interesting. So the logs are now showing zone trip events:

8/10/2016 11:27:01 AM EnvisaLink INFO Zone 8 status change: Opened
8/10/2016 11:27:01 AM EnvisaLink INFO Partition 1 status change: ReadyForceArmingEnabled
8/10/2016 11:27:03 AM EnvisaLink INFO Zone 7 status change: Opened
8/10/2016 11:27:05 AM EnvisaLink INFO Zone 8 status change: Closed
8/10/2016 11:27:07 AM EnvisaLink INFO Zone 7 status change: Closed
8/10/2016 11:27:07 AM EnvisaLink INFO Partition 1 status change: Ready
8/10/2016 11:27:08 AM EnvisaLink INFO Zone 8 status change: Opened
8/10/2016 11:27:08 AM EnvisaLink INFO Partition 1 status change: ReadyForceArmingEnabled
8/10/2016 11:27:12 AM EnvisaLink INFO Zone 8 status change: Closed
8/10/2016 11:27:12 AM EnvisaLink INFO Partition 1 status change: Ready


But trigger is still not activating on Zone Open.

[spud]

I really appreciate you doing this. If it works, how do I pay for it without having the updater overwrite it? Should I just recopy the dlls in your zip after it tries to download the store version again?

yes, overwrite the dll in your HS folder with the one from this thread

[sorka]

Awesome. I will give it a try tonight and report back the results.

I hear what you're saying. This is the very first time that I've run into an issue where something didn't work because I was still on HS2. If it happens again, I'll probably have to consider upgrading. If ISY comes out with an all new plugin in the future for some future device after the 994, that would probably be the breaking point.

Although if I get some free time, I may again try HS3. My first attempt was early on and the forums were full of similar stories to mine. Maybe the transition is more seamless now.

I really appreciate you doing this. If it works, how do I pay for it without having the updater overwrite it? Should I just recopy the dlls in your zip after it tries to download the store version again?

[spud]

try the attached dll (version 3.0.0.11), I have recompiled the HS2 version with all the latest changes made in the HS3 version.

even if it works (I haven't tested), if I were you I would reconsider upgrading to HS3 because you are going to face this kind of issues everytime you want to change something in your system.

[sorka]

I was afraid you were going to say something like that. Perhaps you can pull the plugin from the HS2 store or change the description to include that it is not compatible with the EVL4?

I tried upgrading to HS3 several years ago and honestly it was a total disaster. Nothing worked. Hundreds of events were broken and the events I fire from external programs through vb scripts also stopped working. After several day of working on it, I decided to call it quits and restore back to HS2. Since HS2 has continued to do everything I need, I've just left it that way.

As I see it, my options are:

1) Return the EVL4 and get an EVL3 instead. As far as I can tell from my research there isn't much difference between the two other than the EVL3 is no longer being updated while the EVL4 has more memory in case they want to add more features or capabilities......which they may ore may not do.

2) Try and upgrade to HS3 again - Is there any reason to believe a second attempt will go better this?

3) Keep both the IT100 and EVL4 and use the EVL4 only for the services that Eyezon offers. However, my 5010 doesn't have enough power reserve left in it's 550 ma allowance to allow both boards. However, I'm already going to be adding a 5204 for extra power because I'm about to addd 8 4 wire smoke detectors and 8 more zones with a 5108 so that option is still on the table.

4) Somehow convince you to update the plugin anyways given that you probably already fixed this or are about to have to fix it for the EVL4 for HS3. From your reaction, this sounds like a surprise to you and you didn't know the EVL4 wasn't going to work? You previously stated there was no difference in the API from the EVL3 and EVL4. It sounds like you believe there might be now based on the logs? If you have to fix the HS3 version, wouldn't the fix for the HS2 version be the same fix? It would allow you to continue to collect revenue for the HS2 version. There are still a lot of people using HS2.

[spud]

sorry for the delay
According to the logs you posted, it looks like the HS2 version of the plugin cannot parse the data sent by the newest EnvisaLink firmware version.

Could you upgrade to HS3?
I dropped support for the HS2 version 2 years ago.