June 10th, 2012, 11:42 AM
Originally Posted by jsl
Replace this file in the insteon\devices\support directory
June 10th, 2012, 06:41 PM
After my last post I disabled the devices I had added in girder. This reduced the average daily CommunicationManager log files to less than 3MB (down from 3GB).
Today I re-added the same device that I referred in my last post, and have attached the log file. At 06/10/12 19:18:19 I clicked "Update Records", and saw nothing in the lua console. I clicked it again at 06/10/12 19:19:53 and again didn't see anything in the console.
While writing this post I saw a couple errors in the lua console (attached as 'lua log.txt'), they weren't specifically about this device but I suspect they are related. I'm running girder in a VM that I've rarely needed to access since setting it up so it may have been occuring this whole time.
Thanks again for all the help! This component is the main reason I've stuck with girder for all these years!
June 10th, 2012, 09:58 PM
The lua error is fixed - this must be a keypadlinc relay - i don't have one to test against but i think its fixed.
The log file now actually looks just fine. Try adding the device to a group. Also make sure you can control it from Girder. It is a new I2CS device.
June 12th, 2012, 12:47 PM
I'm not getting any errors with the new file, but the thermostat still isn't showing up under Climate Control. Here's a shot of the Device:
Here's the log for the device:
June 12th, 2012, 04:57 PM
It does seem to be working - I guess I should have tried re-adding the device awhile ago! I also re-added the other 2 Switchlinc relays which are now working as well.
I am still seeing the errors related to the KeypadLinc Relay in the console, they appear to be every 10 minutes (group state tracking?). I am able to control this device and haven't had any problems with it, is it something to be concerned about? I tried finding the GetLightLevelRaw function it was referring to but was not successful. Anyways, I've attached the device log file.
June 19th, 2012, 09:07 AM
Hi, I think I have that error fixed and it is related to group state tracking. Next revision.
Originally Posted by jk2587
June 19th, 2012, 08:05 PM
Any thoughts on the thermostat issue I'm having?
June 19th, 2012, 09:37 PM
June 20th, 2012, 10:12 AM
Thanks Mike. I won't be able to check it for a couple of days but will let you know how it goes.
June 30th, 2012, 04:21 PM
Originally Posted by jsl