LeeG

Glad it was helpful. I come free, like so many in the ISY community. This is best forum, the best group of folks (users and UDI) and best product I have had the pleasure to work with. Hope you have the same experience.

There is no Status of a Scene if that is what you are looking for. Insteon has no concept of Scene Status. A more extensive query of a node would be //192.168.2.2/rest/nodes/15%20B2%206A%201 <?xml version="1.0" encoding="UTF-8" ?> - - 15 B2 6A 1 ICON Dimmer 1 1.30.57.53 true I02 -

Post an example of what is being issued. EDIT: here is a working example http://192.168.2.2/rest/status/15 B2 6A 1 <?xml version="1.0" encoding="UTF-8" ?> -

sperok The cmd2 value in the ACK from 19.BE.06 is not correct. The cmd2 value in the ACK from 19.AB.A1 is correct. The outbound commands 45/46 specify index values of 0-7 in cmd2 representing output units 1-8. The ACK from commands 45/46 should contain a bit map representing all the output unit states. The ACKs from 19.BE.06 appear to be an index number rather than a bit map. What I found on mine, which has v.28 firmware is the result before and after a Query is different. When I issue On/Off commands to the EZIO8T after plugging it in I am seeing an index number being returned rather than the expected bit map. If I Query using the SHN Utility it shows the correct output units as being On but the Utility uses a different command to retrieve the output unit information. After doing the Query from the SHN Utility the Query from the ISY shows the correct information and subsequent On/Off commands return the expected bit map in the ACK. I take this to be a bug in the v.28 level of firmware. This is an output unit 3 On before doing a Query from the SHN Utility. The ACK has an index value. Sun 08/14/2011 02:29:13 PM : [iNST-ACK ] 02 62 19.AC.54 0F 45 02 06 IOON (02) Sun 08/14/2011 02:29:13 PM : [iNST-SRX ] 02 50 19.AC.54 12.9F.E4 2B 45 02 IOON (02) Same On to output unit 3 after doing a Query from the SHN Utility. The ACK has the expect bit map. Sun 08/14/2011 02:35:06 PM : [iNST-ACK ] 02 62 19.AC.54 0F 45 02 06 IOON (02) Sun 08/14/2011 02:35:07 PM : [iNST-SRX ] 02 50 19.AC.54 12.9F.E4 2B 45 04 IOON (04)

Calculate 85% of 255. A direct cause/effect can be viewed by running Tools | Diagnostics | Event Viewer with Device communications events selected (important). Set the device to a particular On percentage and view the command issued. I set a device to 85% ON using the Admin Console Current State slider. The On command issued used a value of hex D8 decimal 216. The byte immediately after the hex 11 ON command contains the On Level (hex D8). Sun 08/14/2011 11:57:49 AM : [iNST-ACK ] 02 62 15.9A.F9 0F 11 D8 06 LTONRR (D8)

Sorry, I am not able to provide any direction with the information provided.

The ISY is using Extended commands to update the Scene information. That is somewhat unusual for most devices. What type of device and firmware level is the device that is having the Scene information updated. Also, check Link Management | Advanced Options and make sure the Automatic option is selected.

rslaufer With everything being the same up to the point where either a network command or Insteon command is issued the first thing I would look at is the reliability of communication to the device being turned On. Insteon automatically retries multiple times so the device may turn On but is actually reacting to one of the retries. Try a test with different devices. Pick some closer to the ISY PLM where powerline quality is less a question. Lee EDIT: also remember powerline speed is orders of magnitude slower than an Ethernet connection. It will always take longer to send an Insteon command over the powerline compared to sending a network message.

backinthelab Lets go through these a few at a time. The I/O Linc Sensor changing from OFF to ON but not ON to OFF is odd. Does your configuration run with the I/O Linc Trigger Reverse option set? Is the actual I/O Linc Sensor (green LED on front of I/O Linc) On or Off when door is closed? The Scene On Level/Ramp Rate change causing "Error: Request Failed", would you please expand on how the Scene values are being changed. Through the Admin Console, with the Adjust Scene Program function, etc. Run Tools | Diagnostics | Event Viewer with Device communications events selected (important), attempt the Scene changes (however done) and post the Event Log. If I might suggest posting the original information and your response to the above in a new topic under Questions and Answers. It will be easier to track and these may have nothing to do with 3.1.5. Lee

The Enable column will show a "-" when the Program is not Enabled or On when Enabled (Enable check box checked). Let us know if the Program works tonight after being saved and reaching Sunset.

jay5 To reverse the On/Off commands sent by the I/O Linc Sensor click on the Sensor node in the My Lighting tree and click Set Options. Check Trigger Reverse. Normally when the Sensor turns On it sends an On command and visa versa. Trigger Reverse reverses that. When the Sensor turns On it will send an Off command and visa versa. Not that Trigger Reverse only reverses the commands sent. If the I/O Linc is Queried the true On/Off status of the Sensor is returned. I do not like the idea of sharing a KeypadLinc button between indicating the door is open/closed and controlling the door open/close. It can be done and generally centers around using the KPL button in non toggle Off mode. I'm sure someone can explain the process but there is always a combination where the door did not move and the button shows the wrong status. If you have the space on the KPL I suggest using separate buttons for controlling door open/close versus door open/close status. Lee

frankv The "Not Saved" indicates the Program has not been saved which means it is not functional yet. Click on the Save Changes button in the lower left corner of the Program | Details screen when this Program has been selected. Lee

Archean The “Adjust Scene†function has to issue multiple commands to the responder as the data being changed lives in the responder device. Note that Adjust Scene does not change the immediate On Level or Ramp Rate of the responder. Adjust Scene adjusts the values that are used the next time the responder receives an On/Off command for the Scene being adjusted. Also note that Fast On turns the responder On to full On Level and uses a fast Ramp Rate so “adjusting scene†values and using Fast On are working cross purposes. Most times On/Off commands are used. Any time a Program is invoked versus use of a Scene directly to control the responder will always have some latency about it. In the Program case a command is sent to the ISY, it invokes a Program which sends a command to the responder. When a Scene is used a command is sent from the controller directly to the responder. To have a Controller use a Scene directly to control a Responder, define an ISY Scene, add the Controller device as Controller of the Scene and add the Responder device as a Responder of the Scene. After the Scene information has been written into both the Controller and Responder devices a press of the Controller paddle/button will cause the Responder to turn On/Off without the slight delay associated with using a Program. Lee

RBC Some things to consider when working with KeypadLincs Button Grouping works only on the KeypadLinc where a button is actually pressed. Even though other KeypadLincs may be linked together and have Button Grouping defined, only the KeypadLinc where the button is physically pressed honors Button Grouping. Backlight levels have nothing to do with turning a KeypadLinc button On/Off. The Backlight level controls how bright the KeypadLinc buttons are when On and Off, not whether a button is actually On or Off. Secondary KeypadLinc buttons cannot be turned Off with an On command. Most Insteon devices when linked as responders can have the responder On Level set to 0% such that when the controller On is pressed the responder turns Off. This does not work with Secondary KeypadLinc buttons. An On from a controller always turns On a Secondary KeypadLinc button regardless of responder On Level. To accomplish the appearance of button grouping in KeypadLincs other than where the button is physically pressed, ISY Programs are required and Scenes which have the other KeypadLinc buttons as responders controlled by the ISY Programs. For each KeypadLinc button as a controller, the responders can be set to different On Levels. KeypadLinc A button A can turn its responders On to 80%. KeypadLinc A button B can turn its responders On to 50%. Button A and button B can have the same set of responders. Just about everything mentioned can be done with ISY Scenes. This is the preferred method (IMO) because there is no delay in responders reaction. Button Grouping in the other KeypadLincs (those other than where a button is physically pressed) is the challenge. Can be done but generally requires multiple ISY Programs and multiple ISY Scenes dedicated to creating Button Grouping visual. Lee

gadgetguru69 Is this a new EZIO8SA or one that has been refurbished/upgraded by SHN? Run Tools | Diagnostics | Event Viewer with Device communications events selected (important) and post the Event Log. Also AN1 and AN2 (inputs 5 & 6) should be connected to GND so avoid message floods if the electrical environment is noisy. Also please edit the duplicate post and delete the entry. Thanks Lee

pakratt Use the Scene definition and turn the Scene On and Off to have both devices react together. Turning an individual device On and Off does not cause any linked devices to respond. Insteon is not designed that way. Use individual device control for that specific device or use the Scene to control all devices in the Scene. Lee

archean Are you using a Program triggered by a Fast On from the SwitchLinc to turn on the Scene or is the Scene Controller the SwitchLinc with the three KPLs the Responders? Lee

archean The KeypadLinc backlight level applies to all the buttons. The KeypadLinc does not support setting individual button backlight levels. Lee

I do not have the SDK. Wish I did at times but have heard it does not always have the latest information. Do not want to be restricted by an NDA anyway. I do read everything I can find. Another wish would be that SmartLabs did not hold so much information confidential. Insteon is constantly changing/evolving, hard to stay up with new things. One thing for sure, the day one thinks they know Insteon something new comes along. Actually makes this fun. There are many folks on this forum and others whose willingness to share knowledge is so essential in an environment where the manufacturer keeps so much information secret.

iostream212 No need to change power supplies. The 1800 is its max capacity. Perfectly fine to supply only 300. Folks have speculated the lack of a passthru outlet is to avoid possible RF interference with the Dual Band function. Lee

There is no mechanism to change all responders in a Scene with a single statement. Each responder has to be updated individually as the On Level and Ramp Rate data lives in each responder. Using a Scene On to turn Off devices by setting the On Level to 0% has been around for as long as I can remember. In the past this could be defined only by an application that could write a link record with a 0% On level. In the last year or two many devices now support this with Set button linking. The Off condition is locked into a responder prior to linking using the Set button. The KeypadLinc does not support turning a Secondary button Off with a Scene On to 0%.. The KeypadLinc firmware turns a Secondary KPL button On with a Scene On command regardless of the On Level in the link record. The approach to KPL Secondary button control is to have them in a separate Scene. That way the Scene can be turned Off when the KPL button LED needs to be turned Off.

klundy There is an inherent difference between a Scene On/Off and an individual device On/Off. The device On/Off is accomplished with an Insteon Direct command which has automatic command retry built into it. The Scene On/Off uses a Scene (Group) command which does not have automatic command retry built into it. Any deficiency in powerline reliability will be observed with Scene commands before being observed with individual device commands. Lee

jkraus Adding the EZX10RF to the ISY and defining the first X10 code can be combined by starting with the Add X10 Device to EZX10RF function. Or the EZX10RF can be added to the ISY with New INSTEON Device (be sure to select the EZX10RF device type), then use the Add X10 Device to EZX10RF to define the X10 code. Either way the process described in the popup instructions must be followed for one X10 code only. Repeat the Add X10 Device to EZX10RF for each X10 code. Note that some EZX10RF devices require one additional Set button press to complete the process. If the EZX10RF status LED does not react as the last step indicates press the Set button one more time. The possible need for this is covered in the EZX10RF Quick Start guide. Depends on the internal PLM variant. Lee

gwarthur Best to not reset the ISY anymore. What happens when you click on Start Linking? It could be the new install location is outside communication range, or it does not have 120V on the Neutral and Line connections. The simplest way to eliminate both questions is to connect the SwitchLinc Relay to a 3-wire Appliance cord. One that has a plug on one end and bare wires on the other. All the home improvement stores and many hardware stores carry them for a few dollars. Plug the SwitchLinc Relay at the location of the ISY PLM, then do the start linking and identify the device. Does the ISY react to it now? If so continue with the device add process. Move it back to the current install location. Failure to work there indicates either a wiring problem or lack of powerline communication at the location. Lee

jodok The SeriaLinc is not a supported device type by the ISY. My attempts to use a SeriaLinc outside of the ISY were only partially success. The Utility that loads the SeriaLinc with the serial strings and link records trapped when entering more than a simple string. Smarthome sent the automated acknowledgement they received the bug report but that was the end of it. Never received a fix such that I could run a good test. That was about a year ago. They might have released a new Utility by now but I gave up on the device. Lee