Michel Kohanim

Hi again, thank you. Would you be kind enough to go to Tools | Diagnostics | Scene Test, choose your scene from the list, and then let me know if it succeeds. If it does not, then there is a signal strength/noise issue between your PLM and your switches. With kind regards, Michel

Hello rudyramirez, Can these device control one another? When you click on the scene icon itself (the round looking icon), what are the on levels for each of these switches? With kind regards, Michel

Hi Simon, With releases 2.7.10 and above, ISY actively tries to synch what it knows about your system with what the system has. This means that "any" update to any device will cause ISY to re-evaluate and make sure your system is in fact in synch and write updates to devices that are out of synch. I assume you have 99i PRO since you mentioned batch button. Right next to the batch button, there's the RF devices button. If you do not want ISY to keep trying to update your RF devices, please make sure that button is grayed out. Furthermore, you will get a "Writing->" icon next to devices that are being updated. Ultimately, though, you do need to figure out why those devices are out of synch and why ISY does not succeed in updating them. With kind regards, Michel

Hello Mr. Bruns, If you have recently purchased your IRLinc TX, please contact SH and request that they send you one with the older firmware. Their newest firmware breaks i2 read commands. With kind regards, Michel

Hi jkraus, Yes for the first question. With kind regards, Michel

Hi mitch236, This was related to another bug and it has been fixed. Thanks so very much for the info. With kind regards, Michel

Hello Mr. Bruns, Unfortunately PLMs v4A up to 63 were notorious for hanging while doing heavy operations. I strongly recommend getting a newer PLM. With kind regards, Michel

Hello Bonanza, I am so very sorry to hear this. In some cases, the CAT5 cable that goes from ISY to the PLM does not make good contact on the PLM side. Sometimes, pushing up the gold pins on the RJ45 jack on the PLM (where the cable gets connected) fixes this problem. Sometimes swapping the cable fixes it. With kind regards, Michel

Hi mitch236, Can you copy/paste the program that changes the ramp rate and sets the level for your outlet link? With kind regards, Michel

Hello bktong, The new V2 thermostat dongles DO send change of state back to ISY and thus you do not have to query the thermostat constantly. With kind regards, Michel

slpelts, This should not happen. Are you certain that you do NOT have any other programs that do something to this device? To test, you might to do a Find in your programs for this device. If you find any, disable them and retry. With kind regards, Michel

Hi Illusion, Yes, it seems to be a bug. With kind regards, Michel

Hello someguy, Please note that File | Enable Internet Access and what you have done are basically one and the same. In short, if you are configuring your router manually, then you do NOT need to do File | Enable Internet Access and ISY would NOT know your external IP address. I hope it make sense ... in short, you have to do "either" "or" and not both. With kind regards, Michel

Hello mbski, Apologies for the inconvenience. As jerlands suggested, it's very important to know the status of the LEDs. I do have another question: did this happen all of a sudden or after an upgrade? If you are still having problems, please do contact our tech support for a live session. With kind regards, Michel

Hi Chuck, thank you. This is quite strange ... please do keep me posted if you experience anything similar with other devices in your network. With kind regards, Michel

Hi Chuck, This is quite strange. By replace do you mean actually replacing it with a new device? With kind regards, Michel

Hello sk8er02, thank you. Please do keep me posted. With kind regards, Michel

Hello johnradams, I got your email and link to your system. I stand corrected, ISY does NOT show Unsupported Bridge devices (i.e. PLM). I sent you an email ... perhaps we can fix it remotely. With kind regards, Michel

Hello hart2hart, Not being able to get the log level is not very serious. Do you have any other types of errors or loss of communications? With kind regards, Michel

Hello johradams, First of all, it would be an impossibility (or a bug) if your topology shows a device that is NOT listed as a node. As such, please do be kind enough to click on My Network, sort the table by Address and then let me know if your device shows up in the table. Once we know the answer to this then we'll find the best course of action. As far as your other comments: 1. You are correct: ISY configuration, PLM configuration, and Device configuration are three separate entities that ISY tries to synch/manage 2. ISY does not automatically discard devices that cannot be communicated with 3. Your configuration right now includes the configuration from crawling your network + additions done via ISY With kind regards, Michel

Hi all, This topic is for discussions on the impact of different light bulb types on INSTEON communications. Thanks and with kind regards, Michel

Hello sk8er02, Thanks so very much for the information. If you have the same issue when connected directly to the router, then the Switch cannot be the issue. Would you be kind enough to let me know: 1. Make/model number of your router 2. Above and beyond MobiLinc, are there other clients connected to your ISY? With kind regards, Michel

Hello sk8er02, I am so very sorry for the inconvenience. At this point I have to assume some compatibility between your ISY and your Gigabit router. May I assume that connecting it directly to the router didn't exhibit this issue? If so, would you be kind enough to send me the brand/model number of your Gigabit router and we'll start a root cause analysis using an environment similar to yours. Again, sincere apologies for the inconvenience. With kind regards, Michel

Hello hahnt, Sincere apologies for the inconvenience. I am not sure what operating system you have so the best thing to do is to search your computer for file named udi_frame.state and remove it. And I strongly recommend upgrading to 2.7.15 if you have not already done so. With kind regards, Michel

Hi David, No. Unless you did any programming using 2.7.8-2.7.11, there's no need to do anything. With kind regards, Michel