April 28th, 2012, 08:49 AM
Update for support for new I2CS devices (improved communication).
May 21st, 2012, 09:34 PM
I've just picked up several 2420M motion sensors and am having trouble.
The communications to configure them is not good...I cannot link to them (they link to the controller, but the source links are not showing up on the sensors), I cannot configure their attributes (timing, light level, etc).
They seem to show up fine on the control traffic...messages show up indicating motions, etc.
They show up as Dev Cat 01, sub Cat 01, Firmware 41 product 4A, engine 3.
The configuration traffic seems very unreliable...is there a trick to get these things configured? Keeping them awake during configuration? Any recommendations on jumper settings? They state "jumper 5" should be on for "remote software management", but this does not seem to matter in my case.
I do have a very old 2412S interface, but I have avoided replacing it because everything links to it...could this be a problem? I do have several (5) 2443's dual mode bridges.
Thanks for all the hard work!
May 23rd, 2012, 10:13 AM
they can be problematic. place them in link mode to do any setting changes. this keeps them on. make sure they are close to an AP while configuring. Any more then 2 hops will be a problem. You model may be newer then what i have to test against and i know they have done funny things with the hardware and firmware making each type specific.
May 23rd, 2012, 01:07 PM
Mike thanks as always for the feedback.
Any comments on the jumper settings?
Did your version have similar jumpers...1=sensitivity/2=disable led/3=night-only/4=on-only/5=remote software management?).
I did a quick google on the manual, and it came up with an (apparently) older manual where jumper 5 was reserved...I'm concerned that they have significantly mucked with the configuration in my newer version.
Hmmm...just looking at my INSTEON_I2CS_DevNotes_20120202.pdf they sent out a few weeks back...I'm still running .768...I wonder if that is the "engine 3" in my 2420M's?
I'll give .782 a try and let you know...
Last edited by jmbraben; May 23rd, 2012 at 01:29 PM.
May 23rd, 2012, 05:03 PM
An update on this...
.782 fixed my communication problems...apparently these 2420M's are "I2CS".
For this version, jumper 5 must be in place or the timeout and other configurations are ignored and still controlled via jumpers/potentiometer settings.
The timeout is not n x 30 seconds...actually (n+1) x 30 seconds...0=30 seconds, 1= 60 seconds, etc
Mike is correct that configuration communications are spotty (at best) unless you are in link mode.
May 28th, 2012, 11:25 AM
thanks for the update - the latest version is needed for i2cs devices. do i need to update the timeout calculations?
May 28th, 2012, 08:59 PM
Just an observation...I would just fix the dialog comment in the next release.
And thanks for having the I2CS stuff in place before I needed it...no problems with configuration (at least when I'm in link mode).
As always, thanks for the outstanding effort on the Insteon plugin.
June 4th, 2012, 05:38 PM
I have some new Switchlinc relay (2476S) devices that I believe use the new I2CS protocol. I installed them awhile ago but never got around to adding them to any groups controlled by the PLM, but I tried today and it didn't work. I have noticed that the PLM has been locking up more often, not sure if it's related to this or it is old/failing.
I've attached a log file from one of the devices, after clearing the log and restarting girder - prior to that the log file was quite large. I've noticed the Communication Manager logs are 2-3GB per day, I'm not sure if that's normal though, I've never really paid attention to these files.
I'm running version .782 of the component (I did notice that it is reporting as .768 though!)
Anything else you need from me?
Thanks in advance for any help/advice!
June 8th, 2012, 10:50 AM
I have a Venstar thermostat that will link up with the system and show up as a device, but doesn't show up under Climate Control (or anywhere else). I've attached the log files that I thought might help.
June 10th, 2012, 11:34 AM
Originally Posted by jk2587
Are there any errors in the lua console when updating the devices link database? I see problems in the log file with this. So go to the device page on the insteon tab and select update records. Post the log file and any lua output