rlanza1054

Thanks. I think I am going to give up on the motion sensor with the doorbell, I am testing it but am running in to general issues with the I/O Linc. It seems if I want to do both, using the Sensor option with the ELK-930 with a standard doorbell switch and the I/O Linc relay option to ring the doorbell using an Insteon device either it be a motion sensor or mini remote, it causes some issues. For some reasons, if I trigger the relay of the I/O Linc its turning on the Sensor. So if I have a program or scene to flash a light if the Sensor is triggered, them using the relay to trigger the doorbell, it also triggers the sensor causing a loop. I have figured out how to break out of the loop but it might not be worth it. And one would say why would I want both to be active, I guess the best answer is, to give the option of using a standard way of ringing the doorbell if the motion sensor did not trigger the doorbell. I guess this is why they say to use two separate I/O Linc's for using the Sensor and using the Relay, so you don't end up with the loop. I forget where I read it. But at least I got both ways to work, I just have to figure out what will be best for me. If I decide to go with the mini remote, I need to wait for the next sale before I place an order for it. Also, I will end up getting a second I/O Linc since I have it on back order the I/O Linc - INSTEON 50810 Remote Chime Alert Kit. This kit includes an I/O Linc. Its probably overkill at this point, but now that I know what it can do its probably good to have this available for a future project if I don't end up using the their chime bell. Sorry, woke up down in the dumps today. Rob

Hi, Just invest in a Brother Label Maker Printer, recommendiing model PT-D600 because it can be hooked up to your computer and using the included software P-Touch Editor. Or any brand 'label maker' printer you like. They come as cheap as $20. Create your own using the fonts you like. You can do tricky designs you just can't get from the etched. The labels are printer on Laminated paper with 'self-adhesive'. Here are a few pics of what I managed to create: Rob

Stusview, I just found a option called Beep, what is that? I was adding the Set Doorbell Scene on and found a command I never saw before "beep"? Is that just the beep noise a module makes? Rob

Hehehe.. Studs, thanks!

Hi all, I finally received my I/O Linc - INSTEON 24950A6 Doorbell and Telephone Ring Alert Kit http://www.smarthome.com/i-o-linc-insteon-24950a6-doorbell-and-telephone-ring-alert-kit.html ​ I purchased a cheap wired doorbell, so I could test everything out within hands reach of my computer, when everything is done, I will move the I/O Linc and hook it up to my existing doorbell. I wired up the temp doorbell with its power supply and with a simple momentary doorbell switch. Then wired it to the included ELK-930 that came with the kit. The ELK-930 is an interface between the doorbell's circuit and the input sensor of the I/O Linc. And finally wired it to the I/O Linc. ELK NEG to I/O Linc GND and ELK OUTPUT to I/O Linc SENSOR. I added the I/O Linc to the ISY994. It gets added to the ISy as two items, one is Doorbell IO Linc-Relay and the second is Doorbell IO Linc-Sensor I then setup a temporary scene called 'Doorbell Scene'. I added one Insteon light to the scene and then added the Doorbell IO Linc-Sensor. I then proceeded to physically ring the doorbell switch. It works as advertised! The issue is, because the doorbell is a momentary switch the light just does a very fast flash on and then quickly turns off. If you are not looking you would miss that it happened. So I figured it needs a program to turn on the light when it sensed a doorbell signal via the I/O Linc, where I can control how long to keep the light on and when to turn it off, possible repeating turn on and off until a tap of a light switch to stop the program and reset it for the next time the doorbell is rung. Unless there is some other way of controlling the duration of the light going on and off using the scene? After that, I will be using the I/O Linc's built-in RELAY to have a switch or motion sensor ring the doorbell, as I have read about in the forums. Thanks for an ideas on how to do this or poimting me to one that was already created! Rob I

Then maybe a blub that strobes as suggested. You don't have to get the ISY to do the flashing, just turn it on. As a teenage, my first Heathkit was a strobe light, the box with the strobe light had one knob for adjusting the speed of the strobe and an on/off switch. Just leave the on/off switch on and have the ISY turn it on. That might be what your looking for. That kit at the time (1971) was $30. They sell strobe lights on 14th Street lighting store between 5th and 6th ave. Ok, you might not live in NYC. You can get these strobe lights online very cheap. Again, this was only a suggestion for your needs. I wanted to do some thing else. Rob

Hi, I would rather they focus on getting 5.0 out, then go back to this! The reason for starting the thread, was because I had not known this was a known issue and wondered if it was ever going to be addressed. I was told that it could be taken care of locally and was not going to be fixed, but it turns out its a software only setting, so it does need for it to be fixed. This was the reason for making the request by starting this thread. I never never asked for a time frame. UDI has asked us not to mix in another central controller such as the Insteon Hub. So the only thing left is for them to fix it, but again no one ever asked for a time frame. And I was just trying to verify if LED on Tx was the same as Blink on Traffic which some users think it is the same. (I never thought it was) So today we have the confirmation they are indeed two different things. For me, I own a Insteon Hub. Until UDI does fix the missing settings. (maybe next year, that it a mental time frame in my head) My method to accessing and using these missing options is as follows: (if you disagree with my steps let me know so if anyone wants to do the same it is correct) 1) Remove the device from any scenes on the ISY. There is no need to delete the scene just the device because it will be added back in later) 2) Remove the device from ISY 3) Manually reset to factory defaults, so that all links are removed and any optional settings are set back to defaults that the ISY does support 4) Add device to Insteon Hub (Just plug it back in to AC. Hopefully your not using Hub so it should not have any devices on it, and hopefully you still have your account setup otherwise you have to do the initial setup all over again) 5) Set the options you want that are missing when using ISY. examples: Blink on Traffic Beep on Button Press (the switch does make the sound but its very low, but a blind person would hear it, so there is a reason to use it) There might be other options depending on device And you can fix any LED brightness issue you had with ISY. (I know in my case even though I had LED at 255 it was only going to 50%. the Hub got it back to 100%.) 6) Delete from Hub (those setting should stay in place as long as you do not reset to factory defaults) 7) Add back into ISY (and you can use default setting of 'remove all existing links, it does not touch default optional settings you just made as far as my tests shows) Add back into your scenes. 9) Disconnect the Hub That's my steps. Again If anyone thinks these steps should be modified or wrong please let me know. And one day in the future, we will not need to do this. Rob

Finally! A confirmation that what I was saying from the beginning. So that being the case. Is there a possibility in some future (no date required) that the missing options settings functions can be added to those devices that are missing it now using the ISY. That way we won't have to go back to the Insteon Hub to activate those functions. (Bear in mine, that these functions cannot be done locally as I was told they can. Its in the end user documentation.) Thank you. Rob PS At this point the moderator Can close this thread. Sent from my SM-N910P using Tapatalk

Hi, I also wan to do something similar and did not want to start a new thread. In my case, I have some spare buttons on my Keypadlinc. I cannot find it again, but read something on the web where a user used his Keypadlinc to light up one of his spare buttons, he place a red defuser behind the button, so when lit it would glow red. He had it light up only when there was an error. I do not remember if this person had an ISY but is seems like he would have to. My question is: Besides running an error log to text file, is there a place on the ISY where a error variable is stored that I can tap into. This way, if there is ever an error event on the ISY or maybe something being reported to the ISY, and when that happens turn on the LED on the spare button on the Keypadlinc. I do know that if my motion sensor's batteries are low, I could easily do this and have the button turn on its led. I have it presently sending out a email and text message. But other than the battery low, I guess I want to know if there is a variable stored somewhere that a error event is happening or happened. This person, also set the button that if it is tapped, it will reset the LED on the button and it will go off. One must assume if he tapped the button to turn off the LED, he took care of the issue whatever it was. And as far as GMD99, maybe instead of flashing a light, if possible just use a light fixture where you can install a RED light blub or put a red defuser on it. This way if you see that lit up you would know that you have an issue. Its a suggestion, that you might try instead of the flashing repeatedly. Rob

For what device? I was showing a Insteon decvice that has both Blink on Traffic and LED on TX. The original reason for starting this thread is that a different Insteon device, not the new On/Off Plug-in module, does not contain 'Blink on Traffic' only LED on TX. Replies are stating that LED on TX is the same as Blink on Traffic. I was trying to point out that if that is indeed true, then why does the On/Off Plugin Module contain both options if they are exactly the same thing. The original topic has turned to point out things that some of the replies are not explaining. And then my last post was pointing out a third item, that when using the option LED on TX, when that is checked off and you make a change in the LED brightness on the Insteon dimmer 2477D, it turns on the option setting of 'Lock Programming'! I have not been saying anything that conflicts. If I have a grammar mistake, I try to fix those after I posted and am sorry if my posts have confused anyone. I am not angry over any of this, its just as a new user of the ISY, I have been encountering things that are strange. I try to ask questions so we can determine if its something I don't yet understand or making sure I am not encountering a bug in the software or point out a development issue. This Blink on Traffic issue has apparently been brought up by other users at a different time and thread, who have even commented here. So if you wish to think this out logically, today I found out that if I check LED on TX, it seems to turn on the Blink on Traffic functionality when the Blink on Traffic option is missing in older devices. Again, think logically, if LED on Tx is the same exact thing as Blink on Traffic, then why are the two options provided on the particular device that is offering both options. Let's take this one step more logicallly, if the two option are the same thing, and presented on the same device, which option should I check if I want that option. Again, take it one more step logically, if I check off for example LED on Tx, and do a query, then if the are indeed the same function, after the query, a check box should show up on both options. If I could get a copy of the developer documentation, maybe I would understand why the term LED on TX is being used over what the end user documentation is listing as the available option of Blink on Traffic. It has been stated that the ISY development team only uses the development documentation not the end user documentation. Again, look at this logically, if everyone is using only the development documentation, then why does the Insteon HUB never use the term LED on Tx but only uses the term that is in the end user documentation of 'Blink on Traffic' and I pointed out that even a third product Houselinc software only offer Blink on Traffic? Trying to solve this puzzle of inconsistencies, I have to logical say that ISY is not getting the same developer documentation as those two other products receive? Is it that Insteon is not providing ISY with a complete details of the developer documentation. To use another industry, Apple provides developer documentation to third party developers and I know for a fact (my brother was a developer of application that was/is used on a Macintosh) that it requires compliance to using standard terms and look. Google is now requiring Android developers to code using the new Material Design look and function. I realize that my examples are mostly UI standards but I was trying to make a point that usually a company of a product wants end users to see a standard set of terms. i asked in a previous post, if the ISY is designed for ONLY developers, if that is the case, then the usually developers and programmers don't really care if the terms are swapped on occasion. I realized that Harry (not a real person) might write the code for Insteon device X and Harold might write the code for device Y. Harry and Harold are not talking to each other, so the pick the term they want to use. Unless there is oversight by a team leader. These few paragraphs are based on a unproven fact that LED on TX and Blink on Error are exactly the same thing. It might turn out that they are different but can look like they are the same, example to prove my point, the command ON and Fast ON can at times result in a light being turned on, but we know they actually do different things. Rob UPDATE: After some additional testing, the paragraph: And then my last post was pointing out a third item, that when using the option LED on TX, when that is checked off and you make a change in the LED brightness on the Insteon dimmer 2477D, it turns on the option setting of 'Lock Programming'!​ Turns out that it is a totally separate issue/bug/problem not related to the LED on Tx. Its mostly like a bug or maybe its a 'feature'? I will ask this question in a different thread. Also, I asked in a previous post if there is a consolidated list of 'known' issues/bugs/problems that I could look over, so I don't waste anyone's time on something that Universal Devices is already aware of. And I understand that some things just cannot be fixed for whatever reason. But at least I will know.

Hi, So my question is this, is the ISY designed for developers only or for end users. End users are reading the documentation that comes with the device. Today was the first time I heard that there is totally different documentation for developers. I actually blame this on Insteon not ISY. The developer documentation shoud contain the terminology used for programming but also let the developer know that the end user should get the programming terminology translate to putting the label that the end's documentation is using. Remember, the HUB, when it was designed, if the developer of the product used the developer documentation, they actually used the end user the label from the end user documentation. So there is nothing labled LED on TX in any of the devices when using the HUB. And its just not Insteon's Hub, the Houselinc software does not user these developer terms. So honestly, Its either Insteon fault by not being clear in the developer documentation of what term to present to the end user. And this does not explain why then if LED on Tx is equal to Blink on Traffic, then why does the On/Off plugin module offer in options both LED on Tx and Blink on Traffic. If the above line is true, then ISY is beng sloppy by offer both terms within the same device. I have a feeling these two labels are actually different things. The reason, as you will read, I tested it out to by checking off LED on TX to get the 'Blink on Traffic', it did work but now I am getting something odd. What I am about to say, just might be a bug. I think I need to see if there is a list of know problems. I don't want to ask questions about things that are already known. Ok, here is what is happening after I turned on option LED on TX, whenever I adjust the LED brightness, it takes the setting change just fine but then when you go and look at options, it then checked off to 'Lock Programming'? Why when adjusting the LED brightness, is it Locking Programming? Rob

Hi, The on/off module does offer both, its in the user documentation. Rob

Ok, I tried to turn on the 'LED on TX' on a different device from the one I use the HUB to turn on the 'Blink on Traffic'. The results: Astounding! It seems that the 'LED on TX' is the same as 'Blink on Traffic'! I checked off the option for a dimmer that is right next to the other dimmer that I used the HUB to set the Blink on Traffic, I saw the blinking when I turned on the dimmer, then I went to see if it was all traffic, I started to turn on and off other devices around the house. This dimmer is showing the Blink On Traffic!!!! WTF!!!! All of this thread devoted to Blink on Traffic and in the end, LED on TX is 'Blink on Traffic'! What I don't understand after all this time spent, is why is the ISY naming it 'LED on TX', why not use the terminology used everywhere (HUB, Houselinc, etc) why did they rename it to something confusing. And why with the Plug-In On/Off Module, it's Options setting choices are ((I listed them in the previous post) 'LED on TX' and 'Blink on Traffic'? If it's the same thing, why offer it with two different labels? It could be that they are indeed different, but the device just picks up that 'LED on TX' and assumes it's 'Blink on Traffic'. I'm sorry, but this isn't right! If it really really is the same thing, then either get rid of all mention of Blink on Traffic, or better yet, rename 'LED on TX' to what it is: 'Blink on Traffic'. Why is it necessary to confuse the users with these two different labels. Just change the naming of the label to be 'Blink on Traffic'. Was this done, because that is how it's listed in the developer documentation whereas the user documentation prints it as 'Blink on Traffic'? I'm repeating but... I really feel like I was made a fool of here! It is Blink on Traffic on the HUB, there is no setting at all in any of the devices 'LED on TX. The same holds for the Houselinc software. I'm beginning to think this is some kind Unix priest thing, make it so hard to figure out that the regular Joe will never be able to understand how to use it. Rob

Hi, Today, I need to spend time cleaning up my apartment; I'm so embarrassed, I've been on the computer all day for the past week. And now dishes in the sink have reached the bottom of the kitchen cabinet hanging over the sink. I live alone, but my friend came over last night and just stopped in his tracks and said: Holy Sh*t!. So I will write this post and then turn off the computer until I can walk without stepping over garbage. Again, I live alone, that's the only reason I could get away with it. LOL! I'm going to answer your question but I need to tell you what happened when I tried something this morning. I thought that maybe I could install a device with the auto-discovery turned off and just select a device that contains the 'Blink On Traffic', set it to be on, then remove it and reinstall it using the proper device or use Auto-Discovery. Well, it seems the ISY is too smart, it won't allow me to do that. It reads the device and jus installed the proper one. So there is no way to fake it to get the options even if only temporarily. And I found something interesting regarding the Keypadlinc devices. I own one Keypadlinc Dimmer (8-Button) 2334-222 and I own two Keypadlinc On/Off Switches (8-Button) 2487S. It seems the ISY for the Keypadlinc Dimmer has the Options settings available. But according to documentation, it does not offer the Blink On Traffic, but offers something else, 'Error Blink'. That setting is only available via software from a central controller, such as HUB or ISY. The ISY is missing that 'Error Blink' Option. Now for what is really interesting: The Keypadlinc On/Off Switch (8 Button, only the A button is the hardwired on/off switch) 2487S, is not showing any Options settings. For this particular Keypadlinc there is no way to adjust those software only options using the ISY. Now to answer your question: If you looked at the screenshots I posted, one is a screenshot of the On/Off Plugin Module, the settings available in its Option settings are the following: Program Lock LED on TX LED Blink On Error Beep RF Powerline Send Cleanup Messages Smart Hops It seems the ISY does indeed offer the complete set of Options Settings for this particular device. If 'LED on Tx' was actually another way of saying 'Blink on Traffic', then there would not be a separate selection for 'Blink On Traffic'. That is how I know the two are two different things. LED on TX is Flash LED when transmitting a communication signal. It does not mean Blink on Traffic, which means Flash the LED on any and all Insteon traffic it hears from all of your devices, not just itself. ALL traffic. While composing this post, I kept going to the documentation of each type of device. Dimmers, On/Off Switches, Micro Dimmers, Micro On/Off, Plug-in Modules both Dimmers and On/Off and lastly the Keypadlincs. I was looking at All the information on 'Blink on Traffic' if a device offers it, is clearly explains on what it does and what it does not do and how to enable or disable the function. What I am not finding is this 'LED on TX', this is interesting. I do know from a technical stand point, that TX stands for Transmit Data and RX stands for Receive Data. Standard terminology that is used to explain for example a RS-232 serial port. It has TX, RX, DTS, etc. I will see what happens when I turn that on in a dimmer and see what it actually does. And you asked where I get the information, besides just a screenshot. I'm reading the supplied documentation that comes with each of these devices. You mentioned 'Developer' documents. I have never seen a developer document. Maybe Insteon does not want third party developers to know or program for these extra functions. Maybe the reason is so that it holds something over the customers. Because if I can only use these functions from software via a central controller, then I would need to get a Insteon Hub or a Houselinc software. Maybe they did not provide the full information to a third party like ISY. Is there a way to get these so called 'Developer' documentation? And if you don't have copies of the documentation that is included inside each box of a device when you purchase that device, I will attach a few of those pdf files here so you can look for yourself. Rob 2334-2xx-keypaddim.pdf 2442-x22-en-microdim.pdf 2443-x22-en-microonoff.pdf​​ 2477S-en-onoffswitch.pdf 2478D-en-dimswitch.pdf​ 2487S-en-keypadonoff.pdf This on/off plug-in module's documentation was too big and wasn't allowed to be attached, so I zipped it up.​ 2635-222.pdf.zip

Hi all, OK, I did my first upgrade. Only had two issues which I got immediate help with. Thank you! But now for the news about the 'option settings' for Insteon dimmer 2477D. I now does indeed have the option settings available. But the bad news, it does not contain what I was looking for in the first place, the 'Blink on Traffic' I'm going to post the screenshot. One screenshot of the 2477D options, notice how its missing the 'Blink on Traffic', which is different from 'LED on TX' the other screenshot is of the on/off module, notice that it does indeed contain both the 'Blink on Traffic' and the 'LED on TX'. I believe that the only devices that are in the ISY's database that contain ALL the options are the very very new Insteon devices. The older devices might contain some of the options but not all. As this just proved it. I have said for sometime that ISY could just use the 'devices.xml' to obtain and update ISY's Insteon devices database, without the need to figure out what options are available on each device. This is the newest database of devices that the Houselinc software uses. I posted that file a few posts back. I asked if there was a way to read that file so it could be used, if ISY developers are interesting in providing those option settings to the users. And if not we will have to maintain a Hub or Houselinc (with its PLM) should we need to alter those missing options. I've added that devices.xml file again PS I might have been wrong about the devices.xml file. it might not contain the info. I found another file but at this point I'm just guessing. I found something called SmartLabs.Insteon.Devices.dll. the system won't allow me to upload this file. But maybe there is a way t get those missing settings applied. What if I lie to the ISY and install my dimmer and say its the on/off module which contains the missing option, apply the option and then fix the device to now say its the dimmer and not the on/off module. Its what we call a 'white lie'. I just use the incorrect device to send the command get the option I wanted and then go back to the correct device. I might try it just to see if it can be done, proof of concept as it were. Rob Devices.xml

I never did remove the PLM, I just manually set the PLM to factory default. Which did get rid of all those 600 links. I'm sure it was storing all the older crap (no other way to put it), when I was installing and uninstalling devices, when I removed everything from the ISY and re-installed everything. I think those 600 lines had so much crap, that it was probably why I had all those issue with that micro dimmer every night. I'm working great now. But maybe not all the links have been written to the PLM, since I only have 1o lines now in the report. I can just make a change to each scene and device to get everything into PLM. If I do a restore to PLM, what I'm afraid of is putting back all the crap. Is there a way to get the ISY to clean up its database, something like a 'defrag' would do, so that only current stuff it contained? Rob

Oh, this has nothing to do with changing scene dim levels at different times of the day. That would require the ISY to be involved. Your are mentioning it when just setting it up. In my case, if the ISY becomes disconnected, the device be dim med at the level that was last adjusted. So if I lose the ISY in the middle of the night, when I wake up the devices will be stuck at the 20% value I adjusted at the beginning of the night before. The device won't be able to revert back to 100% (as I have it programmed to do) because the ISY is not available to make the change back to day time usage. That's what you are trying to let us know. Am I correct now, in what you are trying to get across? Rob

Thanks, but I'm not sure what that means. Safe mode? Is that something one would want? Without it going into safe mode, means the ISY will just send commands because it cannot tell if the PLM is attached? And I will assume again its because version 5.0 is still in beta and that functionality hasn't been added just yet? Thanks, but as I said, its probably best to just try 4.3.18 learn what's involved with upgrading, look at the options for the dimmer and later on I can play around with 5.0; which I am looking forward to. Rob

Quick question: Do I download the first one in the list of the two offerings: ISY 994i Series including Z-Wave Support ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM) My ISY has this printed on the label on the bottom of the ISY: ​ ISY994i ZW/IR PRO and it came with the 2413s PLM. I downloaded the first one listed, both 4.3.18 and 5.0 I think I will just use the 4.3.18 and try and learn how to do the upgrade, the 5.0 might introduce more complications that I don't need right now while I am still learning the upgrade. Then I will check the options for the switch 2478d. The original reason for starting this thread. Thanks Rob ​

Well, it might be good to start to learn how to do these upgrades. / Is there anything I need to do prior to doing the upgrade and do I have to worry about losing my current setting, scenes and programs? And because I was told by Steve that 5.0 has some better support for the iMeter, I would like to try that, it you think its ok, if not I will try the 4.3.18 you suggested? Rob

Hi, What I did before I started this thread was to actually erase by factory resetting the PLM. What I have now when doing the PLM Link Table report is only 10 lines. I suspect this will grow back as I end up using the devices. Everything is working correctly. So what is the reason again for the PLM needing to store all of the links? I have not setup any local links as far as I know. Everything was setup using the ISY. Question, if for example: I use the ISY to link a button on the Keypad and I set it as a crosslink. That requires me to create a scene for the button and device. When setting up that scene I set each device (device plus button on keypad) to be controller. That how I was told to do a crosslink. So when I do that, is the link settings being controlled by the ISY which I am assuming it is, or was it written to the PLM, or was it written to the local devices. The reason I am asking this is that I have a feeling your going to write back that by resetting the PLM to factory settings I have messed up things, even though everything is working. And that if I unplug the ISY and the PLM, nothing will work, unless it was actually written locally? Rob

Hi, I do know that local linking where its stored on the device and independent of the ISY. But what I'm not understanding from your program or what you are trying to inform us is: The devices have no clock internally, so the cannot make the changes based on time to an internal scene. So I am assuming you are just modifying the dim level on the internally stored scene using the ISY which the ISY is able to do based on the time, am I correct? Rob

Hi, I deleted a previous post because the program I attsched to that post was incorrect and not working as I thought it would. When it did not work, I quickly realized how I set it up incorrectly. The problem was that I set the wrong item to 'adjust' the dim level in the scenes. I was trying to dim a device being controlled by a motion sensor. I needed to adjust the motion sensor in the scene, not the scene itself. I did not want anyone to try and use the incorrect program and cause them headaches. Here is the post again but with the corrected program. Nighttime Dim Levels - [iD 001D][Parent 0001] If From 12:01:00AM To Sunrise (same day) Then In Scene 'Bathroom Small-Sensor' Set 'Bathroom Small Micro Dim' 2.0 Sec (Ramp Rate) In Scene 'Bathroom Small-Sensor' Set 'Bathroom Small Micro Dim' 20% (On Level) In Scene 'Bathroom Big-Sensor' Set 'Bathroom Big Micro Dim' 2.0 Sec (Ramp Rate) In Scene 'Bathroom Big-Sensor' Set 'Bathroom Big Micro Dim' 20% (On Level) In Scene 'Hallway Motion-Sensor' Set 'Hallway Dimmer' 0.2 Sec (Ramp Rate) In Scene 'Hallway Motion-Sensor' Set 'Hallway Dimmer' 20% (On Level) In Scene 'Foyer Motion-Sensor' Set 'Foyer Dimmer' 2.0 Sec (Ramp Rate) In Scene 'Foyer Motion-Sensor' Set 'Foyer Dimmer' 20% (On Level) Else In Scene 'Bathroom Small-Sensor' Set 'Bathroom Small Micro Dim' 0.1 Sec (Ramp Rate) In Scene 'Bathroom Small-Sensor' Set 'Bathroom Small Micro Dim' 100% (On Level) In Scene 'Bathroom Big-Sensor' Set 'Bathroom Big Micro Dim' 0.1 Sec (Ramp Rate) In Scene 'Bathroom Big-Sensor' Set 'Bathroom Big Micro Dim' 100% (On Level) In Scene 'Hallway Motion-Sensor' Set 'Hallway Dimmer' 0.1 Sec (Ramp Rate) In Scene 'Hallway Motion-Sensor' Set 'Hallway Dimmer' 100% (On Level) In Scene 'Foyer Motion-Sensor' Set 'Foyer Dimmer' 0.1 Sec (Ramp Rate) In Scene 'Foyer Motion-Sensor' Set 'Foyer Dimmer' 100% (On Level) Thank you for the help! Rob

So you mean I would have to downgrade the software to get the options availability back. Why did they remove those options when upgrading, does make sense that they did that. Let's face it, Insteon is making the options available on the latest firmware of the HUB? I have a HUB, so I probably would not downgrade the software, I don't know what I would lose that I have setup and working now. But I obviously was just asking these questions for a reason. We do need these abilities to fully use or Insteon, Smartlinc or Keypadlinc devices, without having to rely on other central controllers or having to downgrade the software, As I suggested, maybe provide a way of sending the individual command even if the option is missing, it will either work or it won't. Rob

Hi, Wow, your right, there doesn't seem to be a way to rename it using the App. It can be done for the screen buttons of the Touchscreen handheld remote. I would put in a feature request to Harmony asking for the ability to rename a code without needing to learn it again from scratch. You know I have some of the very old Harmony remotes which used the locate app not this new web based software. I remember in that you could rename codes. If you have that windows application for an older Harmony remote, add the ISY into that older remote, rename the codes, then you can actually import an activity and device using the new web based software. But it would require you to delete your Harmony Link completely, which would remove all settings, when you go to add it back in, the software asks you if you are upgrading from an old Harmony remote. Make sure your old software still works before even attempting this. Granted its work but if you really want this it is a way. Rob