User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Sat Jan 26, 2013 1:40 am

ELK issues that I still see as of latest - several of these have been documented in the previous posts:

1.) ELK T-Stat variable names that are created have inconsistent naming convention based on scenes 0019 and 0028:

* Scene is using {{climate_{{currenttempzone_{{clientname}}}}_TempRnd}} (note _TempRnd) and in the ELK you use Climate_1_TEMP (not _TempRND). There is no Climate_1_TempRND.

* I guess the same goes for the variable for cool set point and heat set point. They all have RND references in the variable name in the scenes but not in the ELK driver. ELK uses Climate_1_CoolSetPoint and Climate_1_HeatSetPoint names.


* Same goes for Climate|{{CurrentTempZone}}~Mode~Heat whereas in the ELK variables you call it Climate~1~HVACMode

You seem to have two standards, which one is the official that will be used across all scenes and thermostats?
Am I correct that you overall are not consistent in the naming convention across scenes and plugins?


2.) I am only getting Security_Counters_1_Name but not the value of the counter.

The log shows that the ELK panel is sending them but you appear to not be processing them into variables. That is if I am interpreting your log correctly. You may not have been processing these in the V3 driver either. But this is valuable for me as I populate the counters with important information.
1/26/2013 12:42:40 AM ProcessResponse RX: <<0DCV4400000003B>>
1/26/2013 12:42:40 AM ProcessResponse RX: <<0DCV4500000003A>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV46000000039>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV47000000038>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV48000000037>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV49000000036>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV5000000003E>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV5100000003D>>
1/26/2013 12:42:41 AM ProcessResponse RX: <<0DCV5200000003C>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV5300000003B>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV5400000003A>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV55000000039>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV56000000038>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV57000000037>>
1/26/2013 12:42:42 AM ProcessResponse RX: <<0DCV58000000036>>
1/26/2013 12:42:43 AM ProcessResponse RX: <<0DCV59000000035>>
1/26/2013 12:42:43 AM ProcessResponse RX: <<0DCV6000000003D>>
1/26/2013 12:42:43 AM ProcessResponse RX: <<0DCV6100000003C>>

Art Dustman
Expert
Expert
Posts: 614
Joined: Fri Nov 10, 2006 3:22 pm
Location: NJ
Contact: Send private message

Re: V4 Elk Driver

Sat Jan 26, 2013 11:51 am

Dave, ping me before you try to remote in since the pass may have changed.

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Sat Jan 26, 2013 1:31 pm

Dave, seems easiest for you to connect to my panel from your MLServer/development environment. That way you don't have to use remote control software. Just need to know a source address so that I can set up a firewall rule.

Art Dustman
Expert
Expert
Posts: 614
Joined: Fri Nov 10, 2006 3:22 pm
Location: NJ
Contact: Send private message

Re: V4 Elk Driver

Sat Jan 26, 2013 1:55 pm

While I see the same issues as you, I'm having issues with mixed naming from Vera climate controls to my Aprilaire stats thru the Elk - so we are dealing with a few issues.

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: V4 Elk Driver

Sat Jan 26, 2013 2:11 pm

The changes I made to the Elk driver yesterday only normalized some Security Zone issues for another customer. The rest of the changes are forthcoming.

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: V4 Elk Driver

Mon Jan 28, 2013 2:24 pm

Today's release of the Elk driver should resolve the Climate and Counter issues reported here.

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Tue Jan 29, 2013 12:34 am

Started testing - so far so good. Thanks!

How does one set or change the counters?

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: V4 Elk Driver

Tue Jan 29, 2013 11:08 am

I forgot to add that. Install the new version. It will be Security|<<any zone id>>~SetCounter~Counter#~CounterValue

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Thu Jan 31, 2013 12:20 am

Appears that the command set between the V4 ELK Climate and the regular Climate controls is different. Are you intending these to be differnt or are you attempting to consolidate command sets? I hope the latter as it would bring consistency to the climate based controls on scenes. It isn't a big deal for us to change them but then we will be out of spec each time you guys release updates to scenes.

This is intended to be an example as other commands appear different at quick glance:

ELK: (Note DEC/INC versus Down/Up)
Climate|zone~Heatsetpoint~10-90 or Dec or Inc
Climate|zone~Coldsetpoint~10-90 or Dec or Inc


Climate: (Note DEC/INC versus Down/Up)
Climate|zone~Heatsetpoint~10-90 or Down or Up
Climate|zone~Coldsetpoint~10-90 or Down or Up


This is still an issue - Same goes for Climate|{{CurrentTempZone}}~Mode~Heat whereas in the ELK variables you call it Climate~1~HVACMode

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Thu Jan 31, 2013 12:28 am

CinemarDave wrote:I forgot to add that. Install the new version. It will be Security|<<any zone id>>~SetCounter~Counter#~CounterValue
Doesn't seem to update the counter. I tried the following and didn't change it's value. Log information below:

Security|3~SetCounter~63~100

1/30/2013 11:31:46 PM ProcessResponse RX: <<0DCV63000140035>>
1/30/2013 11:31:46 PM RX Counter Value
1/30/2013 11:31:46 PM ProcessResponse RX: <<0DCV64000140034>>
1/30/2013 11:31:46 PM RX Counter Value
1/30/2013 11:31:57 PM ProcessResponse RX: <<xxxxxxxxxxx>>
1/30/2013 11:31:57 PM RX Network Heartbeat
1/30/2013 11:32:27 PM ProcessResponse RX: <<xxxxxxxxxxx>>
1/30/2013 11:32:27 PM RX Network Heartbeat
1/30/2013 11:32:27 PM ProcessCommand Cmd=[3~SetCounter~63~100] Client=[MyClient1]
1/30/2013 11:32:27 PM SendCommand TX: 10cx6300100000A
1/30/2013 11:32:35 PM ProcessResponse RX: <<0DCV01000000042>>
1/30/2013 11:32:35 PM RX Counter Value
1/30/2013 11:32:35 PM ProcessResponse RX: <<0DCV02000000041>>
1/30/2013 11:32:36 PM RX Counter Value
1/30/2013 11:32:36 PM ProcessResponse RX: <<0DCV03000000040>>
.....
1/30/2013 11:32:46 PM RX Counter Value
1/30/2013 11:32:46 PM ProcessResponse RX: <<0DCV63000130036>>
1/30/2013 11:32:46 PM RX Counter Value
1/30/2013 11:32:46 PM ProcessResponse RX: <<0DCV64000130035>>

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: V4 Elk Driver

Thu Jan 31, 2013 10:01 am

I had the command starting with a "10" when it should have been a "0D". Should be ok now.

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Sat Feb 02, 2013 9:06 am

CinemarDave wrote:I had the command starting with a "10" when it should have been a "0D". Should be ok now.
Yep, that fixed the issue. Thanks!

Art Dustman
Expert
Expert
Posts: 614
Joined: Fri Nov 10, 2006 3:22 pm
Location: NJ
Contact: Send private message

Re: V4 Elk Driver

Sat Feb 02, 2013 7:58 pm

Elk controls seem to be missing entirely under the control family (relay & other outputs)

Elk temp sensors should show under climate family

User avatar
Krumpy
Developer
Developer
Posts: 1410
Joined: Thu Sep 04, 2003 11:17 pm
Location: Minneapolis, Mn
Contact: Send private message

Re: V4 Elk Driver

Sun Feb 03, 2013 10:08 am

Been meaning to add these to my Elk system. So, I would be interested in this feature as well.

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: V4 Elk Driver

Sun Feb 03, 2013 1:41 pm

There should be at least 16 Control devices defined after the panel is scanned. Do you not see 16 Control Output devices in the Control Family? If they are there what else is missing?

Return to “MLServer 4 Device Drivers”

Who is online

Users browsing this forum: No registered users and 1 guest