Announcement

**petez69** · May 20, 2007, 02:52 AM

Evening...

I gather you have the newer KP2 only on your system and not the older KP1. What the plugin does is check for the temperature reading on the keypads to make sure it can properly talk to the ELK

st=give me the status in ascii
10x= where x is the keypad number

Possibly Ultra is going to have to change this as not everyone is going to have the older KP1 on their system ( I do).

Cheers..Pete

**ctwilliams** · May 20, 2007, 09:39 AM

Ahh...that makes sense. I have three of the new keypads and one of the older model. BTW, it is too bad that they could not include the temp in the newer models. Oh well.

Thanks for the feedback....

CT

**Ultrajones** · May 20, 2007, 11:48 AM

I have family in town, so I won't be able to get to this till later this afternoon.

**petez69** · May 20, 2007, 05:40 PM

Originally posted by ctwilliams View Post

Ahh...that makes sense. I have three of the new keypads and one of the older model. BTW, it is too bad that they could not include the temp in the newer models. Oh well.

Thanks for the feedback....

CT

CT, the quick way around this then is to change the ID's on your keypads to put the older keypad into either ID 1, 2, 3

I noticed ULTRAs code only looks for those as having TEMP capability

CHeers..Pete

**beerguy** · June 13, 2007, 07:36 AM

Hi -
I'm getting the same error codes. I also only have a KP-2 keypad. In looking at the HS Updater it looks like I have the most recent UltraM1G plugin. Currently I have to restart HS every day in order to get this to stop. Any timeline on an update to fix this?

Thanks,

Pat

**petez69** · June 13, 2007, 06:11 PM

Hi Beerguy

Understand its annoying, I like to have clean logs however it wont hurt your HS installation for the moment....

Pete

**Ultrajones** · June 13, 2007, 06:13 PM

As a work-around, delete the HomeSeer device associated with that keypad. It shouldn't attempt to get the temperature from it if the HomeSeer device doesn't exist.

**beerguy** · June 14, 2007, 08:17 AM

Thanks for the help. As long as it doesn't impact the functionality I'm good with waiting for the fix.

Thanks,

Pat

**beerguy** · July 18, 2007, 01:06 PM

Hi -
Any update on the fix for this? I tried deleting the device but that didn't seem to stop the polling. I'm also not certain that this isn't slowing response time.

Thanks,

Pat

**Ultrajones** · July 18, 2007, 10:02 PM

I plan on posting the update tomorrow. Thank you for your patience.

Note: The update requires M1 version 4.3.4 or greater.

Regards,
Ultrajones

**petez69** · July 19, 2007, 04:11 AM

Ultra

To get the output names above 32, you already need 4.4.x and the latest Ethernet Expander firmware so I would suggest anyone playing extensively with your plugin, upgrade their firmware to the latest available...

Pete

**Ultrajones** · July 19, 2007, 05:25 PM

beerguy,

The version I just posted to the HomeSeer updater should resolve the temperature query issue when using the KP-2 keypads. Please let me know if it works ...

Regards,
Ultrajones

**petez69** · July 19, 2007, 07:30 PM

Hi Ultra

How are you cheking for status now instead of testing the temp sensor on the KP ? Nice to know as if we see future issues, we can help ourselves...

Cheers..Pete

**beerguy** · July 23, 2007, 01:49 PM

So far this seems to be working great. No more errors in my log file.

Thanks much for updating it.

Pat

Announcement

No response/improper response from Elk M1 to command 'st10x'

No response/improper response from Elk M1 to command 'st10x'

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment