Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - broconne

Pages: [1] 2 3 ... 6
1
Rules Configuration / Re: Get status of "all" devices?
« on: December 16, 2014, 01:01:45 pm »
There is no simple way to do all in the elve script language as far as I know.  C# itself could do it, but that isn't exposed into the scripting language..

I haven't tested it, but something like this:
Code: [Select]
boolean allLocked = true;
for(counter=0; counter<omni.LockStatus.Length; counter++){
  allLocked = allLocked && omni.LockStatus[counter] == 0;
}

2
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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. 

3
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.


4
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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?

5
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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)...


6
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.

7
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.


8
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.

9
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.

10
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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?

11
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.

12
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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..

13
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.


14
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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.






15
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« 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. 


Pages: [1] 2 3 ... 6