Codecore Technologies - Elve

Community Feedback => Elve Beta Versions => Elve Version 2.1 Beta => Topic started by: John Hughes on June 22, 2014, 01:55:32 pm

Title: Elve 2.1 Beta Download
Post by: John Hughes on June 22, 2014, 01:55:32 pm
The Version 2.1 beta is a minor update to the Version 2.0 beta, but has the licensing and anti-piracy logic removed.

THIS IS A FREE VERSION OF ELVE. So please note that the license agreement has changed.

While this version does support upgrading from previous versions and I believe this is as stable as the version 2.0 beta, it is recommended that you install this on a non-production machine until it has been more thoroughly tested by the community.

There are also some breaking changes that could potentially affect you. Please see the Change History (http://www.codecoretechnologies.com/content/Change%20History%20Archive.ashx) page for more breaking changes information. Please note that the POP3, Proximity, and Wiimote drivers are no longer included in Elve.

The 2.0 Feature List can still be viewed HERE (http://www.codecoretechnologies.com/community/index.php?topic=1102.0).

Since Version 2.2 has been released, the 2.1 Beta is no longer available for download.

Google Chrome users: Do not use Chrome to download, it incorrectly blocks the download.

I will be posting the current beta download in this FIRST post only.
Title: Re: Elve 2.1 Beta Download
Post by: iostream212 on June 22, 2014, 03:10:36 pm
Great start.  Looking forward to installing the new version and am excited about the future.  Thank you John!

Sent from my SCH-I545 using Tapatalk

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 23, 2014, 12:45:06 pm
I second that! Thanks a lot John!
Title: Re: Elve 2.1 Beta Download
Post by: hdjii on June 24, 2014, 07:55:20 pm
Agreed. Thanks a lot.

Howard
Title: Re: Elve 2.1 Beta Download
Post by: iostream212 on June 26, 2014, 08:04:22 am
Upgraded to 2.1 in place just fine. Can you check the elk send raw command? I'm still getting the command decorated in quotation marks in the log. Thank you.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on June 26, 2014, 05:44:49 pm
I verified that the Chrome web browser is incorrectly reporting the download as malicious. It is not malicous and I have verified with 3 different anti-virus and anti-malware software. I re-zipped the files and I still get the same result. After doing a small amount of research it looks like Chrome "likes" popular sites, sites with ssl downloads, and or signed executable files, etc.  I'll hold off on doing anything more at the moment, but for those of you using Chrome, please use a different browser to download the installer.

Thanks
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on June 26, 2014, 06:03:29 pm
Wow, I just looked at the v2.1 download log and noticed an impressive download count just within the 1st couple days!!

If you have the time and energy please feel free to post the news on other general automation forums... as I have not yet had a chance to write up a press release.

Thank you for your support.
Title: Re: Elve 2.1 Beta Download
Post by: bpwwer on June 26, 2014, 08:55:24 pm
I verified that the Chrome web browser is incorrectly reporting the download as malicious. It is not malicous and I have verified with 3 different anti-virus and anti-malware software. I re-zipped the files and I still get the same result. After doing a small amount of research it looks like Chrome "likes" popular sites, sites with ssl downloads, and or signed executable files, etc.  I'll hold off on doing anything more at the moment, but for those of you using Chrome, please use a different browser to download the installer.

Thanks

Chrome on Linux works fine. I've tried a couple of times and have no problems downloading 2.1.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 27, 2014, 06:09:37 am
You can still download it with Chrome. Just click the "show downloads" link, then it gives the option to "recover file" then "hurt me plenty" and it's yours.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on June 27, 2014, 06:26:53 pm
I posted a new version (v2.1.0.1) which fixes the SendRawCommand() Elk M1 driver method.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 27, 2014, 06:55:55 pm
Having all kinds of problems with the new beta. Posted on cocoontech:
"I just installed the newest beta and it's doing the same thing as the 2.0 beta as far as the Omni goes. Just constant disconnects/reconnects.
 
Anyone else seeing this?? This is why I went back to 1.5 from 2.0.
 
Did everyone "upgrade" or do a uninstall/install?"

Since then I've uninstalled all, then did a fresh install. This results in no connection to the master service at all even though it is running and the firewall is off.

I've also tried the latest version with same results.
Anyone else seeing this??


Just went back to 1.5 and still no connection.
Any ideas?


Got 1.5 installed and working. Did an upgrade to 2.1.0.1 and back to the Omni disconnects.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 28, 2014, 04:24:02 am
I got the omni working since last night but I am getting this error when using the activate.Task method:

Date:     6/28/2014
Time:     6:58:05 AM
Severity: Error
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II : HAI Omni Pro II
Description:
There is a bug in a driver... The driver attempted to process a device property change notification for a property named 'LightLevels' however the passed in value of '-97' is outside the range specified in the property's ScriptObjectProperty attribute.

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 30, 2014, 05:26:35 am
Woke up and couldn't connect. Checked the log and got the attached picture.

Is anyone else having constant issues with the Omni driver or is this just me?
Just started with version 2.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on June 30, 2014, 06:00:53 am
Here's another one...

Just with version 2 again.
I connect over a vpn from work to home. Elve TS viewer worked just fine this way with 1.5. Now I get this:

Date:     6/30/2014
Time:     8:55:52 AM
Severity: Fatal
Source:   TouchScreen
Computer: INSPIRONE1505
Context Type: None
Context Name:
Description:
Failed to initiate remoting.  The touch screen can not be started.The requested address is not valid in its context



What would be causing this? I tried changing machine settings on both, remote and server. Makes no difference.

Cancel this one. Started working after a reboot of the remote pc.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 01, 2014, 12:28:02 pm
This is getting bad....

Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 01, 2014, 04:22:30 pm
Frunple, is the screenshot above from v1.5 or v2.0?
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 01, 2014, 04:26:15 pm
...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.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 01, 2014, 05:17:50 pm
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.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 01, 2014, 05:33:17 pm
I am on 2.1 and the HAI driver appears stable for me.  Do you have debug enabled for it?

Title: Re: Elve 2.1 Beta Download
Post by: elehuy on July 02, 2014, 05:58:56 am
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))

Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 02, 2014, 06:13:43 am
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.

Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 02, 2014, 06:51:08 am
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.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 02, 2014, 09:56:11 am
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.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 02, 2014, 12:30:03 pm
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.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 02, 2014, 08:24:45 pm
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.

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.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 03, 2014, 04:52:08 am
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.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 03, 2014, 12:52:40 pm
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.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 03, 2014, 03:12:54 pm
Please try restarting the driver via elve management studio occasionally to see if it works sometimes... Perhaps the logging fix is coincidental.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 03, 2014, 06:51:43 pm
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.

Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 03, 2014, 08:03:22 pm
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.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 04, 2014, 07:31:30 am
Found out why (sort of) my Omni rules aren't firing off. See attached.

I'm getting this whenever I click on an Omni rule in EMS Rules. All but one actually, and that one seems to work fine.
thought maybe they needed the newest dll so I put that back in but I still get the error. Funny thing is now I'm not getting the "retrying" but it hasn't been a long time yet since I put the new dll back. I'll keep an eye on it, just wondering if all the HAI rules need to be remade when using the newer dll's?? Maybe that's causing the disconnects? Just a thought at the moment, I'll update when I can.

Anyway I can get these rules back though?? Right now they come up blank. Not sure if I remember them all. I tried importing them through EMS but I get the same thing.
Title: Re: Elve 2.1 Beta Download
Post by: iostream212 on July 04, 2014, 08:07:43 am
Interesting.  I noticed the same thing happened with my Elk rules.  I just have to go back and redo them.  Haven't had the time yet.

Sent from my SCH-I545 using Tapatalk

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 04, 2014, 08:33:36 am
I just deleted and remade all HAI rules and so far so good!
All rules are firing as they're supposed to and no driver disconnects yet.
Using the latest HAI.Controller.dll.

I'll monitor over the weekend and see if that's the fix!
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 04, 2014, 05:04:34 pm
The rules issue doesn't sound good... Is anyone able to send me their master config file from when the issue was occurring.  I don't recall a breaking change in that area.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on July 05, 2014, 04:04:37 am
So I played around with it again last night. Definitely related to the rules.
I changed back to the Elve 1.5 dll with the rules from the latest dll and I got the disconnects again.
Went back to the latest dll, was still getting disconnects so I deleted all HAI rules that I had and not one hiccup since then.
I'm gonna recreate the rules now, leaving the latest dll in use, and see what happens from there.

I'll pm you 'a' master config file...not sure if the issue was happening in it or not. Can't remember the timing of it. If not, let me know and I'll send an earlier one.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 06, 2014, 07:41:55 am
Found out why (sort of) my Omni rules aren't firing off. See attached.

I'm getting this whenever I click on an Omni rule in EMS Rules. All but one actually, and that one seems to work fine.
thought maybe they needed the newest dll so I put that back in but I still get the error. Funny thing is now I'm not getting the "retrying" but it hasn't been a long time yet since I put the new dll back. I'll keep an eye on it, just wondering if all the HAI rules need to be remade when using the newer dll's?? Maybe that's causing the disconnects? Just a thought at the moment, I'll update when I can.

Anyway I can get these rules back though?? Right now they come up blank. Not sure if I remember them all. I tried importing them through EMS but I get the same thing.

Is anyone else able to reproduce this error (the FormatException error window Frunple posted above)? I saw mention of it with regards to the omni and elk drivers but I have not been able to reproduce it. If you have a masterserver.config file that has this issue please send me the file and I can fix it.

Thanks
Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 06, 2014, 03:09:30 pm
Found out why (sort of) my Omni rules aren't firing off. See attached.

I'm getting this whenever I click on an Omni rule in EMS Rules. All but one actually, and that one seems to work fine.
thought maybe they needed the newest dll so I put that back in but I still get the error. Funny thing is now I'm not getting the "retrying" but it hasn't been a long time yet since I put the new dll back. I'll keep an eye on it, just wondering if all the HAI rules need to be remade when using the newer dll's?? Maybe that's causing the disconnects? Just a thought at the moment, I'll update when I can.

Anyway I can get these rules back though?? Right now they come up blank. Not sure if I remember them all. I tried importing them through EMS but I get the same thing.

Is anyone else able to reproduce this error (the FormatException error window Frunple posted above)? I saw mention of it with regards to the omni and elk drivers but I have not been able to reproduce it. If you have a masterserver.config file that has this issue please send me the file and I can fix it.

Thanks

When I upgraded from 1.5 to 2.1 I did notice that all of my HAI rules broke.  I can't recall if it was that exact error or not.  I still have my 1.5 VM so I can clone it again and upgrade to 2.1 to verify if it is that exact same error or not.
Will let you know.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on July 06, 2014, 03:10:38 pm
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.

John -
  Finished fixing the Google Calendar Driver.. If you want to send me the latest HAI driver I can take a look at fixing the issues above, start issues, etc. 


Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 07, 2014, 03:10:06 pm
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.

John -
  Finished fixing the Google Calendar Driver.. If you want to send me the latest HAI driver I can take a look at fixing the issues above, start issues, etc.

Thank you. I probably won't be able to get to this until Tuesday night. Thanks again.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on July 07, 2014, 07:08:43 pm
...If you want to send me the latest HAI driver I can take a look at fixing the issues above, start issues, etc.

I have sent you the HAI driver source, thanks again!!!
Title: Re: Elve 2.1 Beta Download
Post by: Paul_Sharrock on August 10, 2014, 07:43:59 am
Found out why (sort of) my Omni rules aren't firing off. See attached.

I'm getting this whenever I click on an Omni rule in EMS Rules. All but one actually, and that one seems to work fine.
thought maybe they needed the newest dll so I put that back in but I still get the error. Funny thing is now I'm not getting the "retrying" but it hasn't been a long time yet since I put the new dll back. I'll keep an eye on it, just wondering if all the HAI rules need to be remade when using the newer dll's?? Maybe that's causing the disconnects? Just a thought at the moment, I'll update when I can.

Anyway I can get these rules back though?? Right now they come up blank. Not sure if I remember them all. I tried importing them through EMS but I get the same thing.

Is anyone else able to reproduce this error (the FormatException error window Frunple posted above)? I saw mention of it with regards to the omni and elk drivers but I have not been able to reproduce it. If you have a masterserver.config file that has this issue please send me the file and I can fix it.

Thanks

I am getting this same exact issue.

I am also using my own version of the HAI driver, but get the same issue with the standard driver.
Re-creating the rule doesn't fix the problem, however, if I paste in my existing flags based rule, it errors on save, and shows blank, however, the log file, has all the comments from the rule, so it is working, but just not displaying in the rules engine.

Paul
Title: Re: Elve 2.1 Beta Download
Post by: dvand on August 11, 2014, 03:27:48 pm
Finally upgraded last night and I'm getting the same issue with the elk driver.  So I deleted my rules and started over. I'll play more tonight.

Sent from my Nexus 4 using Tapatalk
Title: Re: Elve 2.1 Beta Download
Post by: dvand on August 11, 2014, 04:27:16 pm
Finally upgraded last night and I'm getting the same issue with the elk driver.  So I deleted my rules and started over. I'll play more tonight.

Sent from my Nexus 4 using Tapatalk

So far deleting and re-creating my rules seems to work...
Title: Re: Elve 2.1 Beta Download
Post by: Paul_Sharrock on August 12, 2014, 05:54:19 am
Finally upgraded last night and I'm getting the same issue with the elk driver.  So I deleted my rules and started over. I'll play more tonight.

Sent from my Nexus 4 using Tapatalk

So far deleting and re-creating my rules seems to work...

I get the error even when creating a new rule, and paste in the previous script.

Paul
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on August 31, 2014, 05:29:44 am
How's the HAI driver coming along?? Had to reinstall 1.5, then the license expired, so I did a complete new install of 1.5 again and the license is about to expire again. I guess John doesn't come around at all anymore so I have no way of validating the license. 2.1 is completely useless to me with the HAI problems it has so I'm kinda screwed until there's a fix for it.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on September 24, 2014, 06:42:18 pm
How's the HAI driver coming along?? Had to reinstall 1.5, then the license expired, so I did a complete new install of 1.5 again and the license is about to expire again. I guess John doesn't come around at all anymore so I have no way of validating the license. 2.1 is completely useless to me with the HAI problems it has so I'm kinda screwed until there's a fix for it.

I have not had a lot of time to look at it.  In October I start taking Friday's off and I have it on my todo list.  I did get the driver up and running in a test harness and the error was not immediately obvious so it will probably take some digging. 
Title: Re: Elve 2.1 Beta Download
Post by: Paul_Sharrock on October 04, 2014, 01:30:50 pm
How's the HAI driver coming along?? Had to reinstall 1.5, then the license expired, so I did a complete new install of 1.5 again and the license is about to expire again. I guess John doesn't come around at all anymore so I have no way of validating the license. 2.1 is completely useless to me with the HAI problems it has so I'm kinda screwed until there's a fix for it.

I have not had a lot of time to look at it.  In October I start taking Friday's off and I have it on my todo list.  I did get the driver up and running in a test harness and the error was not immediately obvious so it will probably take some digging.

If you need any help with testing, then please let me know.
I have an HAI system, and already use a custom driver that I modified from the original.

Regards
Paul
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 03, 2014, 05:13:12 am
How's the HAI driver coming along?? Had to reinstall 1.5, then the license expired, so I did a complete new install of 1.5 again and the license is about to expire again. I guess John doesn't come around at all anymore so I have no way of validating the license. 2.1 is completely useless to me with the HAI problems it has so I'm kinda screwed until there's a fix for it.

I have not had a lot of time to look at it.  In October I start taking Friday's off and I have it on my todo list.  I did get the driver up and running in a test harness and the error was not immediately obvious so it will probably take some digging.

If you need any help with testing, then please let me know.
I have an HAI system, and already use a custom driver that I modified from the original.

Regards
Paul
Just a quick note.  I played with this a little bit this weekend.  I can't get the driver to replicate the behavior in the test harness.  I will have to do further testing running inside elve itself. 
Title: Re: Elve 2.1 Beta Download
Post by: Paul_Sharrock on November 04, 2014, 01:23:30 am
From where it is erroring, it looks to be a problem within Elve itself and not the driver, as Elve won't even save the rule when certain driver functions are used.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 04, 2014, 07:04:00 am
From where it is erroring, it looks to be a problem within Elve itself and not the driver, as Elve won't even save the rule when certain driver functions are used.

And it pretty much happens with any version of the dll.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 07, 2014, 10:39:15 pm
I spent about 5 or 6 hours on it so far today and have narrowed down exactly where the driver is having an issue.  It appears to be related to the "PagedList*" properties of the driver.  Specifically, when Elve calls into HAI driver for the names and status for the paged list.  If I comment out those calls, in my limited test, the driver doesn't suffer from the connection dying, restarting process. 

I need to spend some more time and figure out exactly why that is an issue (since I see those calls elsewhere and they are fine) and figure out how to resolve it permanently. 


Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 08, 2014, 11:46:38 am
I spent about 5 or 6 hours on it so far today and have narrowed down exactly where the driver is having an issue.  It appears to be related to the "PagedList*" properties of the driver.  Specifically, when Elve calls into HAI driver for the names and status for the paged list.  If I comment out those calls, in my limited test, the driver doesn't suffer from the connection dying, restarting process. 

I need to spend some more time and figure out exactly why that is an issue (since I see those calls elsewhere and they are fine) and figure out how to resolve it permanently.

A little more detail, the function calls to get details about the units/zones/etc of the PageList* objects appear to be very expensive into the HAI library itself.  When those calls come from the HAI dispatch thread, they don't return control back quickly enough and the driver then disconnects because of some sort of internal timeout. 
I can can throw the PagedList* event dispatches into another thread and the system appears stable, but that is not a valid long term fix. 

Would someone be willing to test the driver without PagedList* properties and let me know if it is stable for them while I work on a long term fix?

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 09, 2014, 01:35:00 pm
I'll give it a shot. Send me what you have.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 10, 2014, 10:07:49 am
I'll give it a shot. Send me what you have.

PM Sent. I have had it running for 48 hours without issue.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 11, 2014, 02:30:23 pm
So far so good!
I still get this error:

Code: [Select]
Date:     11/11/2014
Time:     3:51:40 PM
Severity: Error
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
There is a bug in a driver... The driver attempted to process a device property change notification for a property named 'LightLevels' however the passed in value of '-96' is outside the range specified in the property's ScriptObjectProperty attribute.

But I've been getting that since the beginning of Elve. Not sure if it's showing as a negative level or what? 96 should not be out of range.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 11, 2014, 06:58:16 pm
So far so good!
I still get this error:

Code: [Select]
Date:     11/11/2014
Time:     3:51:40 PM
Severity: Error
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
There is a bug in a driver... The driver attempted to process a device property change notification for a property named 'LightLevels' however the passed in value of '-96' is outside the range specified in the property's ScriptObjectProperty attribute.

But I've been getting that since the beginning of Elve. Not sure if it's showing as a negative level or what? 96 should not be out of range.

How often do you see it?  Can you enable debug logging.. If in debug mode you see a line like this:  "HAI Omni Driver received unsolicited packet" followed by a bunch of a hex, right before you see the error I can reverse engineer pretty easily what is causing it.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 13, 2014, 04:22:18 am
It happens multiple times a day.
This is the packet right before the error.

Code: [Select]
Date:     11/13/2014
Time:     4:46:47 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 F3 13 27 21 74 92 CE 00 00 00 00 00 00 00 00 00 4A 56 96 24 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 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 C9 71 90 E0 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
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 13, 2014, 04:26:13 am
By the way, I had a problem, master service corrupt, and had to start over but since the new install the HAI driver is working great! Other than the out of range error, I see no problems.
I think the corrupt MS was due to the upgrade from 1.5 to 2 and the HAI rules. Last time I upgraded all the HAI rules needed to be recreated and I did not do that this time. So after I reinstalled, I checked the rules and they threw an error when clicking on them. I then deleted them all and recreated. So far everything working as expected.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 13, 2014, 06:10:58 pm
By the way, I had a problem, master service corrupt, and had to start over but since the new install the HAI driver is working great! Other than the out of range error, I see no problems.
I think the corrupt MS was due to the upgrade from 1.5 to 2 and the HAI rules. Last time I upgraded all the HAI rules needed to be recreated and I did not do that this time. So after I reinstalled, I checked the rules and they threw an error when clicking on them. I then deleted them all and recreated. So far everything working as expected.

Ok, sent you a new driver that might help me narrow down this error. 

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 14, 2014, 08:14:25 am
Sounds good.
Another thing I'm noticing... things aren't updating as they should be. Especially with the mobile app but it's happened with the Viewer also.
If I unlock a door, I have a boolean that should update with the status and it's not. If I stop the touch Service and restart it, the boolean shows correctly but it's not changing "on the fly". I thought it was just the doors at first but I just tried with some lights and I'm seeing the same thing. I can turn on a light from the mobile app and the light will respond but the app still shows the light off.
Also, I unlocked a door from the Viewer, it showed correct status. Then I locked it from the mobile app, the status didn't change on either the Viewer or mobile. I restarted the Touch Service and did the same thing again, status changed correctly on the Viewer but not the mobile.
Elve is seeing all the correct changes, I know this because I also have it set to send alerts when a door is unlocked when no one is home. I'm getting all the correct notifications, so it seems to be the mobile app mostly. I've never seen it do this with the previous versions.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 14, 2014, 11:39:46 am
Disregard the "not updating" from last post.
Something weird going on... I shut down all 3 services to add the new driver, went to start them up again and couldn't connect to the master service. Had to uninstall/install again. all seems to be working now.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 15, 2014, 02:30:48 pm
Two packets before the error:

Code: [Select]
Date:     11/15/2014
Time:     4:14:41 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 F9 04 00 00 00 00 ED ED 00 00 F4 0E 09 CF 36 00 00 00 00 00 00 00 00 00 00 00 B9 2E 99 7D 00 00 00 00 00 00 00 00 00 00 00 00 07 4A 61 65 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 B9 8C 7E EE 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

Code: [Select]
Date:     11/15/2014
Time:     4:14:41 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative: -96 original status: 4
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 17, 2014, 08:12:04 am
Two packets before the error:

Code: [Select]
Date:     11/15/2014
Time:     4:14:41 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 F9 04 00 00 00 00 ED ED 00 00 F4 0E 09 CF 36 00 00 00 00 00 00 00 00 00 00 00 B9 2E 99 7D 00 00 00 00 00 00 00 00 00 00 00 00 07 4A 61 65 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 B9 8C 7E EE 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

Code: [Select]
Date:     11/15/2014
Time:     4:14:41 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative: -96 original status: 4

Ok.. The driver has logic in it that subtracts 100 from the status which is why you are getting that error.  That appears to be intentional logic.. so a good question is why for a certain unit its not working.  I will have to add some logging to figure out which unit is causing that trigger and then we can see why you are getting that error.

FYI on status.  I have had to redo major portions of the driver to fix the underlying issue with pagedlists.. It has nothing to do with John's work on the driver, its just the underlying library supplied by HAI is aweful. 

So far, the redone driver has converted over units(lights, flags, outputs) and I finished thermostats yesterday.  I need to still tackle areas and zones and then will be ready for some serious beta testing.





Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 21, 2014, 07:41:19 am
I have finished converting over the entire HAI driver to use the new methods...  So I need someone to help me test it out..
Also, if there is any functionality someone wants in the HAI driver now is a good time to ask while the details are still fresh for me.

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 21, 2014, 08:54:37 am
I'm in!
Still need access control added.
Also, if you can find a way to get the actual "running" status of the thermostats, that would be great. Meaning when the system is actually heating or cooling.
I'll see if I can think of other things that were missing.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 21, 2014, 12:43:34 pm
I'm in!
Still need access control added.
Also, if you can find a way to get the actual "running" status of the thermostats, that would be great. Meaning when the system is actually heating or cooling.
I'll see if I can think of other things that were missing.

What is missing from an access control perspective?  I see Lock/Unlock for doors..
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 21, 2014, 01:14:29 pm
No status. Nothing to bind to a boolean to tell if the door is locked or unlocked.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 21, 2014, 01:56:17 pm
No status. Nothing to bind to a boolean to tell if the door is locked or unlocked.

Ok, I will take a look at that.  I just sent you a new driver with the thermostat support you requested.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 22, 2014, 10:24:50 am
So far...WOW! So much better! Even just clicking the device in EMS, it used to take up to 5 minutes to populate, now it's almost instant. Everything about the driver is faster. Great job!

I knew there was a thread about this so I looked it up. Here it is:
http://www.codecoretechnologies.com/community/index.php?topic=430.msg2168#msg2168

Most may have already been included but I would still like to be able to view the logs from Elve. This is the equivalent of "read from controller" in pc access.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 22, 2014, 04:19:45 pm
Finding some issues with rules that trigger off of flag changes. They seem to trigger multiple times and sometimes multiple rules are triggering from one flag, a flag that should only trigger one rule.
I remade all HAI rules and will see if theres any change.
Also, still getting the negative light error.

Code: [Select]
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(UNIT 137) original status (5)

Code: [Select]
Date:     11/22/2014
Time:     5:01:39 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 4E 4D 91 07 72 65 65 74 8D 94 00 00 00 00 00 00 86 00 19 4A 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 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 98 D2 3A FA 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

Code: [Select]
Date:     11/22/2014
Time:     4:58:36 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(UNIT 137) original status (4)

Code: [Select]
Date:     11/22/2014
Time:     4:58:35 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 04 00 00 00 00 E6 DD 00 00 6F 39 68 2F 91 00 00 00 00 00 00 00 00 00 00 00 77 A9 F5 38 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 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 98 D2 3A FA 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

The weird thing is unit 137 isn't even used. But in Elve it does now show a level of 5, and in pc access in shows Scene D??
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 23, 2014, 07:54:56 am
Finding some issues with rules that trigger off of flag changes. They seem to trigger multiple times and sometimes multiple rules are triggering from one flag, a flag that should only trigger one rule.
I remade all HAI rules and will see if theres any change.
Also, still getting the negative light error.

Code: [Select]
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(UNIT 137) original status (5)

Code: [Select]
Date:     11/22/2014
Time:     5:01:39 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 4E 4D 91 07 72 65 65 74 8D 94 00 00 00 00 00 00 86 00 19 4A 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 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 98 D2 3A FA 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

Code: [Select]
Date:     11/22/2014
Time:     4:58:36 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(UNIT 137) original status (4)

Code: [Select]
Date:     11/22/2014
Time:     4:58:35 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 04 00 00 00 00 E6 DD 00 00 6F 39 68 2F 91 00 00 00 00 00 00 00 00 00 00 00 77 A9 F5 38 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 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 98 D2 3A FA 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

The weird thing is unit 137 isn't even used. But in Elve it does now show a level of 5, and in pc access in shows Scene D??
Do you have an example rule I can make a test case?  Also, is this a rule where the hai changes the flag and elve observes?  Or is elve also adjusting flag value?
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 23, 2014, 07:58:37 am
So far...WOW! So much better! Even just clicking the device in EMS, it used to take up to 5 minutes to populate, now it's almost instant. Everything about the driver is faster. Great job!

I knew there was a thread about this so I looked it up. Here it is:
http://www.codecoretechnologies.com/community/index.php?topic=430.msg2168#msg2168

Most may have already been included but I would still like to be able to view the logs from Elve. This is the equivalent of "read from controller" in pc access.
Glad you like it.  The reason its faster is because I had to change the core of the driver and maintain the hai state in my own objects in memory.  I have no idea what the core hai library does when you query its fields, but that is why it was breaking in 2.1 the underlying hai library was too slow.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 23, 2014, 11:39:06 am
Do you have an example rule I can make a test case?  Also, is this a rule where the hai changes the flag and elve observes?  Or is elve also adjusting flag value?

Elve isn't adjusting, just monitoring for changes.
Basically, I have to use flags to determine the status of my doors since the driver never had lock status. So I have one flag set to each door, locked is a 1, unlocked is a 0.
So the rule is set to "Flag level changed" as the event. On the "whenever" tab, property index is the correct flag, flag level to filter on is 0.
Action List tab:

Code: [Select]
// Get the lock status
if (omni.FlagLevels[406]==1)
backlockStatus = "Locked";
else
backlockStatus = "Unlocked";

// Determine if it changed.
changed = false;
if (vars.IsDefined( "BackLockStatus" ) == false)
changed = true;
else if (vars.BackLockStatus != backlockStatus)
changed = true;

// If it changed then set the global variable and send email.
if (changed)
{
vars.BackLockStatus = backlockStatus;
}

System.Sleep((6) * 1000);

if (omni.FlagLevels[406]==0)
{
"Sends me a message"
}

vars.BackLockStatus = backlockStatus;

I also have a rule that triggers from a "zone physical state changed" and it seems like it's being triggered from the above rule and maybe others. I think it may be that any zone is triggering every rule that is set to be triggered from a zone violated. So it's not respecting the zone set for a rule, and any zone violated is triggering all if that makes sense.
I'll try to create more zone state based rules to test this.


Update:
I just created another zone rule and sure enough, any zone violated will trigger any rule set as "zone physical status changed" . Also, the door lock rules I have filter on a flag that goes 0, I just checked them also, they trigger on any flag that goes to a 0. I tested by changing a flag I have for determining which season it is (nothing to do with any Elve rules), and setting it to a 1 did nothing, setting it to a 0 triggered all 4 door rules.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 23, 2014, 03:12:19 pm
As an update to the negative light setting, I went into pc access last night and set unit 137 off manually. I noticed the error came in when my "sunset lighting" event would trigger (in the omni, not Elve).
With the unit turned off, I didn't get any errors today. Not sure why that unit was ever on or what turned it on but it may be corrected now. I'll monitor it to see if it comes back.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 23, 2014, 06:58:35 pm
Spoke too soon.

Code: [Select]
Date:     11/23/2014
Time:     5:24:04 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(UNIT 137) original status (4)

Not sure why it's triggering or what's triggering it now.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 24, 2014, 11:42:36 am
Do you have an example rule I can make a test case?  Also, is this a rule where the hai changes the flag and elve observes?  Or is elve also adjusting flag value?

Elve isn't adjusting, just monitoring for changes.
Basically, I have to use flags to determine the status of my doors since the driver never had lock status. So I have one flag set to each door, locked is a 1, unlocked is a 0.
So the rule is set to "Flag level changed" as the event. On the "whenever" tab, property index is the correct flag, flag level to filter on is 0.
Action List tab:

Code: [Select]
// Get the lock status
if (omni.FlagLevels[406]==1)
backlockStatus = "Locked";
else
backlockStatus = "Unlocked";

// Determine if it changed.
changed = false;
if (vars.IsDefined( "BackLockStatus" ) == false)
changed = true;
else if (vars.BackLockStatus != backlockStatus)
changed = true;

// If it changed then set the global variable and send email.
if (changed)
{
vars.BackLockStatus = backlockStatus;
}

System.Sleep((6) * 1000);

if (omni.FlagLevels[406]==0)
{
"Sends me a message"
}

vars.BackLockStatus = backlockStatus;

I also have a rule that triggers from a "zone physical state changed" and it seems like it's being triggered from the above rule and maybe others. I think it may be that any zone is triggering every rule that is set to be triggered from a zone violated. So it's not respecting the zone set for a rule, and any zone violated is triggering all if that makes sense.
I'll try to create more zone state based rules to test this.


Update:
I just created another zone rule and sure enough, any zone violated will trigger any rule set as "zone physical status changed" . Also, the door lock rules I have filter on a flag that goes 0, I just checked them also, they trigger on any flag that goes to a 0. I tested by changing a flag I have for determining which season it is (nothing to do with any Elve rules), and setting it to a 1 did nothing, setting it to a 0 triggered all 4 door rules.


I got good news and I got bad news..  The good news is I can recreate the issue.  The bad news is that I thought I had seen this issue w/ the original driver (when it could stay up) and the issue is and I am not sure what could cause it.  I will have to email John and see if he has any ideas.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 25, 2014, 05:40:39 am
If it helps any, I remember it doing this too and it definitely started with Version 2 of Elve.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 25, 2014, 12:18:18 pm
Got a new error popping up.

Code: [Select]
Date:     11/25/2014
Time:     2:59:39 AM
Severity: Error
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
There is a bug in a driver... The driver attempted to process a device property change notification for a property named 'ThermostatModes' however the passed in value of '7' is not in the property's ScriptObjectProperty attribute's number list.

Code: [Select]
Date:     11/25/2014
Time:     2:59:39 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 11 3B 06 0E 00 02 04 79 F8 92 07 00 00 51 5B 6A 00 00 F7 2F 00 00 00 00 00 00 00 00 00 00 00 04 6F F4 E5 00 00 00 00 00 00 00 00 00 00 00 00 A2 E1 39 15 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 E9 F9 CE 21 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
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 26, 2014, 07:12:02 am
They're coming in pretty frequently all of the sudden.
I can't come up with any correlation to any rules I have, or manual use, that are triggering it. When it happens, pc access always shows unit 137 as either Scene C or Scene D.
All of the HAI errors are the negative lighting in the image.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 26, 2014, 12:54:14 pm
Got a new error popping up.

Code: [Select]
Date:     11/25/2014
Time:     2:59:39 AM
Severity: Error
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
There is a bug in a driver... The driver attempted to process a device property change notification for a property named 'ThermostatModes' however the passed in value of '7' is not in the property's ScriptObjectProperty attribute's number list.

Code: [Select]
Date:     11/25/2014
Time:     2:59:39 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 11 3B 06 0E 00 02 04 79 F8 92 07 00 00 51 5B 6A 00 00 F7 2F 00 00 00 00 00 00 00 00 00 00 00 04 6F F4 E5 00 00 00 00 00 00 00 00 00 00 00 00 A2 E1 39 15 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 E9 F9 CE 21 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

OK, I will see if I can reproduce.

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 28, 2014, 07:42:31 am
Some updates.

I set the "room" unit 137 is in to zwave. This seems to have stopped the negative error until this morning. Now I got one error for unit 249 instead of 137. Setting that room to something other than HLC to see if it happens again.

There's all kinds of craziness going on with thermostats.
See the attached. There cannot be the same setting for heat and cool. If I check pc access or the tstat itself, they both show the correct settings (heat 68, cool 74 at the moment). So Elve is seeing them both as the same somehow. Also, if I click the arrows on that screen to change the setpoints, the up arrow (for heat or cool) will change it one degree, then the next click of the UP arrow will change the temp down 3 degrees. Every next click will go down 3 degrees.

Arrows are set for 1 degree up and -1 degree down.

Forgot the attachment
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 28, 2014, 11:30:01 am
Some updates.

I set the "room" unit 137 is in to zwave. This seems to have stopped the negative error until this morning. Now I got one error for unit 249 instead of 137. Setting that room to something other than HLC to see if it happens again.

There's all kinds of craziness going on with thermostats.
See the attached. There cannot be the same setting for heat and cool. If I check pc access or the tstat itself, they both show the correct settings (heat 68, cool 74 at the moment). So Elve is seeing them both as the same somehow. Also, if I click the arrows on that screen to change the setpoints, the up arrow (for heat or cool) will change it one degree, then the next click of the UP arrow will change the temp down 3 degrees. Every next click will go down 3 degrees.

Arrows are set for 1 degree up and -1 degree down.

Forgot the attachment

Ok.  I sent you another beta last night.. It should log some more info about that negative number business.  I can see where it can happen with any HLC room controller based on the code (but it should have been happening before too...).

I will check out the thermostat issue.
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 28, 2014, 09:42:36 pm
Some updates.

I set the "room" unit 137 is in to zwave. This seems to have stopped the negative error until this morning. Now I got one error for unit 249 instead of 137. Setting that room to something other than HLC to see if it happens again.

There's all kinds of craziness going on with thermostats.
See the attached. There cannot be the same setting for heat and cool. If I check pc access or the tstat itself, they both show the correct settings (heat 68, cool 74 at the moment). So Elve is seeing them both as the same somehow. Also, if I click the arrows on that screen to change the setpoints, the up arrow (for heat or cool) will change it one degree, then the next click of the UP arrow will change the temp down 3 degrees. Every next click will go down 3 degrees.

Arrows are set for 1 degree up and -1 degree down.

Forgot the attachment

What type of thermostats are you using? If they are the HAI thermostats can you send me the details of your setup?  How many thermostats? Are there any rules that fire off thermostats?

I can't replicate this with my setup currently (not that that helps anyone)...

Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 29, 2014, 06:29:58 am
Omnistat 2000's, 2 of them. Tstat1 is the master, Tstat2 is a slave.
No rules firing from Tstat's, rules that make changes to Tstat's though.


I had a total of 8 negative errors yesterday since using the new driver. I'm showing two of them here.
Just so you know, I renamed unit 137 to "test" and unit 249 to "test2" so they show in pc access.

Code: [Select]
Date:     11/28/2014
Time:     4:29:46 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 F9 04 00 00 00 00 ED ED 00 00 B9 F9 E7 0D 00 00 00 00 00 00 00 00 00 00 00 00 EF 8A BF 75 00 00 00 00 00 00 00 00 00 00 00 00 06 BA 0E F1 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/28/2014
Time:     4:29:46 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(test2) original status (4) unit type: HLCRoom

Code: [Select]
Date:     11/28/2014
Time:     6:09:26 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 96 2B B1 F3 72 6F 73 20 AE 1A 00 00 00 00 00 00 73 F1 A3 21 00 00 00 00 00 00 00 00 00 00 00 00 06 BA 0E F1 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/28/2014
Time:     6:09:26 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(test) original status (5) unit type: HLCRoom
Title: Re: Elve 2.1 Beta Download
Post by: broconne on November 29, 2014, 09:26:37 pm
Omnistat 2000's, 2 of them. Tstat1 is the master, Tstat2 is a slave.
No rules firing from Tstat's, rules that make changes to Tstat's though.


I had a total of 8 negative errors yesterday since using the new driver. I'm showing two of them here.
Just so you know, I renamed unit 137 to "test" and unit 249 to "test2" so they show in pc access.

Code: [Select]
Date:     11/28/2014
Time:     4:29:46 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 F9 04 00 00 00 00 ED ED 00 00 B9 F9 E7 0D 00 00 00 00 00 00 00 00 00 00 00 00 EF 8A BF 75 00 00 00 00 00 00 00 00 00 00 00 00 06 BA 0E F1 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/28/2014
Time:     4:29:46 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(test2) original status (4) unit type: HLCRoom

Code: [Select]
Date:     11/28/2014
Time:     6:09:26 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 96 2B B1 F3 72 6F 73 20 AE 1A 00 00 00 00 00 00 73 F1 A3 21 00 00 00 00 00 00 00 00 00 00 00 00 06 BA 0E F1 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 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 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/28/2014
Time:     6:09:26 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(test) original status (5) unit type: HLCRoom
How does the master/slave work for the tstat?  Can the slave only adjust the set points for the master? 

Is this something you configure in PC access?

When you adjust the tstat in elve, are you always adjusting the master?
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on November 30, 2014, 07:03:02 am
How does the master/slave work for the tstat?  Can the slave only adjust the set points for the master? 

Is this something you configure in PC access?

When you adjust the tstat in elve, are you always adjusting the master?

No, it's a 2 zone system. So tstat1 is set as a "zone controller" in the system settings of the tstat. Tstat2 is basically set in auto mode so that tstat1 can determine heat, cool or auto. They both wire to the zone controller instead of wiring directly to the furnace. Then the zone controller is wired to the furnace.
So if Tstat1 is set to heat, because tstat2 is in auto, it is also then heating. I can set different heat/cool setpoints for each one and each one only controls "it's" zone (one downstiairs, one up).

I don't think there are any settings for this in pc access, all in the tstat themselves.

I can adjust each zone independently of each other for heat/cool setpoints. The master will always control the mode, with the slave always being in auto mode.
Title: Re: Elve 2.1 Beta Download
Post by: John Hughes on December 01, 2014, 06:50:17 am
All,

Just a quick note before the more public announcement... Elve 2.2 has been released and includes a major bug fix...

* Fixed Rules issue that caused some rules to be triggered when a property index value changed even if the rule was for a different index than the rule specified.
* Fixed an error that could occur when attempting to edit a rule which had a blank property index.
* Fixed issues with the Google Contacts driver.
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on December 03, 2014, 06:08:37 am
Access control with the latest driver:

Code: [Select]
Date:     12/3/2014
Time:     8:05:20 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Received Access Control Lock Message.

Code: [Select]
Date:     12/3/2014
Time:     8:05:20 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Message Object Length: 5

Code: [Select]
Date:     12/3/2014
Time:     8:05:20 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Lower Order Byte: 0

Code: [Select]
Date:     12/3/2014
Time:     8:05:20 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Reported Count: 16

Code: [Select]
Date:     12/3/2014
Time:     8:05:20 AM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Lock Message Details. Lock ID: 0 Lock Status: 1 Lock Status Text: UNLOCKED Number: 0 Address:000.000.000.000
Title: Re: Elve 2.1 Beta Download
Post by: Frunple on December 03, 2014, 07:05:26 am
All,

Just a quick note before the more public announcement... Elve 2.2 has been released and includes a major bug fix...

* Fixed Rules issue that caused some rules to be triggered when a property index value changed even if the rule was for a different index than the rule specified.
* Fixed an error that could occur when attempting to edit a rule which had a blank property index.
* Fixed issues with the Google Contacts driver.

So far 2.2 is running great. Is there anything we can do about the wellknownlocalhost errors?
I use a laptop that is sometimes wired, sometimes wireless so I can't bind to one address. I do have a hostname set but I still get the error due to the ip binding I guess.

Code: [Select]
Date:     12/3/2014
Time:     9:03:51 AM
Severity: Warning
Source:   TouchScreen
Computer: INSPIRONE1505
Context Type: None
Context Name:
Description:
Elve has detected more than one ethernet network interface on 'INSPIRONE1505' but the WellKnownLocalHostName and/or BindToIPAddress settings in the MachineSettings.config file is not set. You may experience network connectivity issues if running apps remotely until the WellKnownLocalHostName setting is set to an IP address on 'INSPIRONE1505' which the Master Server can connect to.

Ethernet Network Interfaces on 'INSPIRONE1505':
  Local Area Connection 2 - TAP-Windows Adapter V9
  Bluetooth Network Connection - Bluetooth Device (Personal Area Network)
  Local Area Connection - Broadcom 440x 10/100 Integrated Controller

Title: Re: Elve 2.1 Beta Download
Post by: broconne on December 05, 2014, 07:09:06 am
Quick update for those following along.  I have been testing the updated driver locally and its working well.  I contacted HAI, who indicated they have a bug in their SDK related to obtaining the access control lock number.  Once that is resolved, I will update the driver to support locks, send it back to John for everyone to use.

Title: Re: Elve 2.1 Beta Download
Post by: broconne on December 12, 2014, 05:30:19 am
Frunple has been testing the updated driver and it appears we are squishing the last of the bugs.  Once we think they are all gone I will push the code back to John for inclusion into elve.