Author Topic: Elve 2.1 Beta Download  (Read 27458 times)

broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #75 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.

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #76 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.

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #77 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

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #78 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.

broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #79 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.


Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #80 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

broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #81 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.

broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #82 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)...


Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #83 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

broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #84 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?

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #85 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.

John Hughes

  • Administrator
  • Hero Member
  • *****
  • Posts: 2851
    • View Profile
    • Codecore Technologies
Re: Elve 2.1 Beta Download
« Reply #86 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.
John Hughes
Codecore Technologies

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #87 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

Frunple

  • Hero Member
  • *****
  • Posts: 774
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #88 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


broconne

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
Re: Elve 2.1 Beta Download
« Reply #89 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.