Elve 2.1 Beta Download

[John Hughes]

Frunple, is the screenshot above from v1.5 or v2.0?

[John Hughes]

...also I took a quick look at the difference between the two driver versions and I didn't see any obvious causes for you v2 HAI driver issues.

[Frunple]

It's version 2. Funny thing is, I didn't think you changed the driver but this only happens with version 2.
When 2.0.0.6 was first released I tried it and got the same results with the Omni driver. I then went back to 1.5, no problems.
Now with 2.1, the Omni driver is doing this again, so I went back to 1.5, no problems. I then tried 2.1.0.1, Omni problems again.
Hoping I don't have to go back but this is really slowing down the system considerably and I'm missing a lot of important notifications from the Omni.
Did you change anything in the TCP/IP comm?
Probably not since my GC-100 stays connected but something is definitely wrong/different in version 2.

[broconne]

I am on 2.1 and the HAI driver appears stable for me.  Do you have debug enabled for it?

[elehuy]

I did not had time to try 2.1 yet (still with beta 2) but I remember there was a bug in comm where 0x00 (char 0 in hexadecimal, binary protocol) was removed from the data received.
It causes me problem in one driver but I can't recall if it was fixed in 1.5 version. (it was fixed for sure)
(my pt is that I build the driver thinking 0x00 was not send by the equipment, once fixed it might have misbehaved after the fix (I need to check that driver again))

[broconne]

I am on 2.1 and the HAI driver appears stable for me.  Do you have debug enabled for it?

I take it back..  After a reboot I was having the same problem as Frunple.  I then went an enabled "record diagnostic information" which restarted the driver and the problem went away.

John - you said the driver didn't change - did anything change around the general initialization logic that might impact the HAI driver?  I can try and take a look at it - but it might be a little a while.  I don't currently have a development environment and need to place an order and assemble a new computer or try and develop over VNC.

[John Hughes]

The driver did have some changes but it wasn't obvious if or how those may have caused the issues being reported.

Please keep in mind that the HAI driver uses HAI's .NET API DLL, not a direct connection through the driver.... And HAI's API is terrible... In the past I indicated that it was less than desirable in an attempt to be polite... but it really is very poorly written and architected by HAI... forgive me for my directness.

I don't recall if v2.x includes a newer version of the HAI API DLL file but I will check.

[broconne]

The driver did have some changes but it wasn't obvious if or how those may have caused the issues being reported.

Please keep in mind that the HAI driver uses HAI's .NET API DLL, not a direct connection through the driver.... And HAI's API is terrible... In the past I indicated that it was less than desirable in an attempt to be polite... but it really is very poorly written and architected by HAI... forgive me for my directness.

I don't recall if v2.x includes a newer version of the HAI API DLL file but I will check.

I recall having similar feelings when i added button support to the current HAI driver :-)  Not a great API from HAI on this one.

[Frunple]

I am on 2.1 and the HAI driver appears stable for me.  Do you have debug enabled for it?

I don't now, but I did enable it at one time. The problem is every time I try to make a change to the HAI driver it results in a corrupt master sevice, and then obviously a complete uninstall/install. did it 3 times since the first time I installed 2.1. I don't really want to do it again.
Since you brought it up though, I thinking when debug was enabled, it may have worked perfectly. I was getting a whole slew of unsolicited packets in the log though.

So you would be the third person to see this behavior (someone else in another thread reported seeing the "retrying" also), so it's definitely not just my setup.

[John Hughes]

Here is the rundown on the HAI.Controller.dll file. Keep in mind this file is provided by HAI and I do not have any control of it's behavior or stability.

• Elve v1.5 included HAI.Controller.dll v1.0.0.3
• Elve v2.0 included HAI.Controller.dll v3.9.0.7
• Elve v2.1 included HAI.Controller.dll v3.9.0.7
• Latest on HAI Website: v3.11.4.17 dated  05/14/2013

Frunple, you could try stopping the Elve Driver Service, swapping in the older HAI.Controller.dll file from Elve v1.5 or even the latest one, then starting the Elve Driver Service.  I don't know that either will work at all if any better but it would be worth a try. If the latest version seems to work I will be happy to rebuild Elve using it.

I have attached all the versions of the dll to this message as a zip file.

[Frunple]

I'll give that a shot as soon as I can.
One more note... I took a chance and enabled debug again last night. It enabled without doing any damage and since then the driver has been staying connected and working perfectly.
I get a whole lot of unsolicited packets in the log though...

Date:     7/3/2014
Time:     7:43:30 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II : HAI Omni Pro II
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 11 3B 06 0E 00 02 04 85 72 92 03 00 00 54 5B 6A 00 00 21 47 00 00 00 00 00 00 00 00 00 00 00 B6 8A FE 47 00 00 00 00 00 00 00 00 00 00 00 00 55 13 39 16 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 B6 DB ED B5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


Not sure if it's any help to figure this out though. It seems to be a different value every time but I didn't check them all.

[Frunple]

I changed the dll this morning. The 3.9 and the latest both do the same thing so I went with the one from Elve 1.5.
So far no errors but I don't think I'm getting all the notifications I should be. I have it set to notify me when the doors are unlocked and I know my father stopped by around 2 o'clock, but I never got any notifications from it.
I'll play around with it more tonight if I can.

[John Hughes]

Please try restarting the driver via elve management studio occasionally to see if it works sometimes... Perhaps the logging fix is coincidental.

[broconne]

Seeing something else very odd with 2.1 and the HAI driver.  Whenever any zone status changes rules are firing for unrelated zones and even unrelated functions.

Here is an example:
I have a rule that starts a timer when the front door is open
I have a rule that starts a timer when the mudroom door is open
I have a rule that sends a UPB link on a different network when the light level of a unit changes.

I look in my log and all three rules just fired when I opened the guest room door - which has no rules associated with it.

[broconne]

Please try restarting the driver via elve management studio occasionally to see if it works sometimes... Perhaps the logging fix is coincidental.

For me, restarting the driver fixes the issue.

Edit:  I take that back.. It looked like it did but now its still retrying.