hart2hart

Is there anyway via physical inspection or testing I can determine if mine were in that "small batch" because I have a house full of v35 SWL that were purchased in a Jan-Feb and April timeframe last year. If I got newer versions, would the group command limitation still exist -- I'd just have SWL that were more "responsive" to commands in general? Thanks, Paul

Thanks. They are v35. Has this been fixed in a later SWL version or is it just a SWL Scene/Group limitation?

Soldered C32 pads on two T1700 using wire end cut from small resistor (make change reversable by clipping small wire). Both reporting 0% humidity and no insteon messages for humidity in 30 minutes. Assuming no unintended effects -- looks good.

I have not looked inside thermostat in a few days so forgive me if this will be obvious when viewing board. Could we get a photo or illustration posted so there can be no mistake which contact points they are referencing? I seem to remember 3 that were close together.

I have a scene with 4 SwitchLinc Relays and they are all responders (they are controllers for other scenes). I turn the scene on via ISY console or HomeSeer events through Plugin and all 4 SL show ON status on ISY console page. However one switch is not physically ON so I query it and it returns OFF. In these cases, how is the Insteon retry logic working/not working. The PLM and hence ISY are acting as controller, correct? Should there be error message to say SL did not respond? If I control a single device via ISY and there are comm issues, it will give the status bar and show system busy -- this does not occur in this case. I've deleted scene and devices a couple times but it still occurs.

Thanks for the explanation. I had just created a scene that included a KPL button as a controller and was having issues. Turns out that the Switchlinc is bad. It will not accept any links. Performed all steps reset etc but replaced with spare and it works well.

What would a sympton of this bug look like? I need more detail to understand.

Specifically, could this messsage traffic, if it occurs during the middle of creating a scene etc., cause a problem?

So to be clear, what I'm asking for would be an unlink "IRLinc Device" from the PLM?

Michel: Thanks. Currently, I've moved them to a folder so they don't accidently get selected for scenes and to keep clutter down. Not a big deal but it would be good to get rid of them if possible. Would their slots in the IRLinc be opened to learn other IR commands and create links? Paul

Michel: I've had great success with 2.7.9 -- thanks to you and your staff. However, while adding IRLinc devices, I discovered I was not holding the key on the remote long enough and the device would get added but it is not responsive to future button presses. Can these "bad" devices be removed without having to start over with the IRLinc. At this point, removing one IRLinc device deletes them all. Not Sure if I'm missing a feature or making a feature request? Again Thanks, Paul

I've got two of the t1700 sending these phantom updates. I hadn't fully considered that the protocol may allow configuration of the adapter on which variables to update. In fact, I felt it was odd that the (v1 adapter with t1700) and ISY combination showed a humidity value. I opened a t1700 thermostat and the location for the humidity sensor and the jumper are on the t1700 board. I'll be curious to see if this is a floating ground issue -- would shorting one or both of these locations on the board stop or keep the humidity setting constant? Any EE have a quess?

I now know where all the T-stat insteon traffic is coming from...the humidity sensor, which I don't even have. Is there something we can do about this? I went from a simple query every 15 minutes that worked perfect to a update every minute or two. I wish I never sent back my V1 adapter. I get the same behavior. I assume we'll have to contact Smarthome since the adapter is sending the message -- agree?

I just upgraded to 2.7.9. I've used the batch mode to add 3 v2 thermostats and all went well. The issue of adding two IRLinc discrete (on and off) devices to a scene from a few weeks ago appears to be resolved. For your information: I added the v2 thermostats as suggested and they were fine. I then used the replace function to replace an existing v1 thermostat with the v2 version- It deleted the newly added 4 items and only the thermostat proper remained. In addition, all programs (regardless of if they referenced thermostat) were deleted in the process. I reverted back to 2.7.7 and repeated the upgrade process to correct. This time I used manual method to replace old with new thermostat and all is working

Michel: I completed steps as you suggested and.. 1. After the reboot, lights flashed for a minute and then mem light did not flash or even flicker -- waited 30 minutes 2. Via Hyperterminal the following message was repeating at this point: Trap occured Vector=Access Error FMT =01 SR =2400 FS =04 Faulted PC = 00000000 D0:00000000 00000018 00000094 00000002 00000080 0229F6EC 40000214 40000208 A0:00000000 20000650 00000190 0229F6F0 40000280 0229F6AC 027FFF20 027FFEE8 Waiting 2sec to start 'A' to abort Trap occured Vector=Access Error FMT =01 SR =2400 FS =04 Faulted PC = 00000000 D0:00000000 00000018 00000094 00000002 00000080 0229F6EC 40000214 40000208 A0:00000000 20000650 00000190 0229F6F0 40000280 0229F6AC 027FFF20 027FFEE8 Waiting 2sec to start 'A' to abort Universal Devices NBUD-70-100 Monitor V1.0 Jun 13 2007 15:27:39 HELP for help nb> I've restored 2.7.7 for our next steps. Thanks, Paul

I've got the same issue but I can't even get to the ISY for 10 seconds. I've taken the same path as you and moved back to 2.7.7. I only had to do a factory reset and install 2.7.7 to get back to working order. My post is in the 2.7.7 2.7.8 thread.

I backed up, downloaded 2.7.8 upgrade, installed it, and cleared JAVA Cache. The ISY will not respond to any of the prescribed connection methods and is not listed in the Network. I can see it has an ip address via the router and the PLM flashes a few times at startup. HELP! UPDATE: I did a factory reset and that would let me get to Console and it showed 2.7.8. I restored my configuration and when complete the ISY did not respond. I did another factory reset, installed 2.7.7 firmware, and restored my configuration and it appears to be working again. Shows MY Lighting in Network. The only thing that comes to mind is that I have pulled(physically removed) the old tstat adapters (but have not deleted from ISY) and was going to install new ones(physically and in ISY) after 2.7.8 was running. Curiosity got the best of me so I reinstalled old tstat adapters and repeated process -- got same results. ISY is not "active" after update with my configuration installed. I will not take any addtional steps until I hear from the experts! Thanks