LeeG

Example of link records with 15% versus 40% Responder On Levels A2 45 19.70.06 26 1F 01 A2 – Responder link record 45 - ISY Scene number 19.70.06 – my PLM address 26 – 15% On Level 1F – 0.1 second Ramp Rate A2 45 19.70.06 66 1F 01 Same Responder link record with 40% (66) On Level EDIT: to determine the ISY Scene number (45 in my example) run Tools | Diagnostics | Event Viewer at Level 3. Using the Admin Console turn the ISY Scene On with the Scene On button. The event trace will look like the following with the red 45 in my example being the ISY Scene number Tue 11/20/2012 01:58:38 PM : [iNST-TX-I1 ] 02 62 00 00 45 CF 11 00 Tue 11/20/2012 01:58:38 PM : [iNST-ACK ] 02 62 00.00.45 CF 11 00 06 LTONRR (00)

I can't tell you how many hundreds of times I hear the same thing. Insteon was working 100% correctly until the upgrade and now some things are not working. Most of the time when each individual symptom is diagnosed and corrected it has nothing to do with an upgrade. I'm not referring to 3.3.4 specifically, it applies to just about every release of every product (not just ISY) that I am involved with. Not to say that applies here but it is good to maintain an open mind and analyze each situation. Note that if you do go back to 3.2.6 (which is not my suggestion) 3.3.x changes the ISY configuration information so it is necessary to restore the 3.2.6 backup taken before the upgrade once back on 3.2.6. It sounds like some communications problems have crept into the Insteon mesh network over time. A common occurrence as new electronics, new appliances are installed over time. For the device(s) that are turning On to a lower On Level that information (On Level and Ramp Rate) is maintained in the individual devices link records in the device itself making a change to the ISY firmware an unlikely candidate. Look at the link records in one of the devices link database (Show Device Link Table) for the specific ISY Scene if driven from a Program or the Responder record for the Controller device if the Scene is activated from another Controller. The information in the next to last two bytes contain the On Level and Ramp Rate for the Scene A2 xx yy.yy.yy aa bb cc xx is the ISY Scene number or Controller button number yy.yy.yy is the address of the PLM or the Controller device aa is the On Level bb is the Ramp Rate A device that is responding to a Scene at 15% must have an On Level value that represents 15% rather than the expected 40%. It could have a value that represents 40% and coming on at 15% which makes it a device problem where the load (Red wire) is connected. If the On Level in the device is set to 15% change the Scene Responder On Level to something different than the current slider position. When that update is complete move the slider to 40%. The ISY will not rewrite a value it thinks is already in the device. The device not turning on at Sunset has more possible failure points. Did the Program trigger at Sunset which can be seen in the Programs | Summary tab Last Run Time. Also check the Sunset time at the top of the Admin Console display. With the change from DST Sunset might be wrong. If the Program triggered correctly run a Scene Test on the Scene. Scenes driven from Programs can be adversely affected by Insteon mesh network problems. If the Scene Test fails then there is a link record issue either in the PLM or the device itself. If Scene Test runs successfully (link records correct) and a device does not respond to a Set Scene On it is likely an Insteon mesh network issue. The wall button not in sync with the Program turning on the Responder controlled from the wall button depends on how the device was turned On. If from an ISY Scene it could be either a link record issue or more likely an Insteon mesh network issue. Same analysis as before. Does a Scene Test show correct results. If no, look at the link records first and then a significant powerline issue second. Unless something happened to device or PLM link records Scene Test normally works and Set Scene activation is unreliable because of mesh network problems. I'm happy to work with you on the Insteon symptoms. The lack of device status on Admin Console startup is something UDI will work. When firewall and AV have been eliminated I am out of my element.

The leak sensor is supported at 3.3.4 (RC1). One user had to select the leak sensor in the Device Type pulldown. Not sure that is a requirement.

I don't think so. The 3AM Query is directed at the Sensor node. A Query command is not issued against any node as the MS is asleep but I think the Query request has to be issued against the Low Bat node for that node status to be changed from On to Off.

Two things to consider if using the existing door bell button to control the I/O Linc Sensor. If it is a lighted door bell button either remove the bulb or get a new unlighted button. It may be useful to get a new unlighted button anyway if the door bell button has been in use for some time. It has been switching 24v AC at relatively high current flows compared to the milli-amp or micro-amp when shunting Sensor to Gnd. Also being outdoors the contacts may not be able to switch the 5v DC to Gnd reliably. It is certainly worth trying as it would eliminate the extra relay hardware altogether.

The low battery message is sent once. After battery is replaced, right click the Low Bat node and select Query. A Query command is NOT sent to the Motion Sensor as it is asleep. The Query request is how the ISY is directed to reset the Low Bat node from On to Off. I have no information on average battery life. Indoors or outdoors, number of motion trips, type of battery would be some of the variables.

There is no elegant way to do that. Each device has to be checked and turned On (or not) individually. There is no easy way to check the On Level of a device and affect that device as a Responder of the "evening on" scene.

Can't say I have ever seen Conditions being added to the My Programs Folder. I did look to see if there was a user defined Folder above the Program. Never thought to ask about the My Programs Folder. Thanks for posting back the resolution.

Use the link below. Just about all posts by Michel have the last line of the post as this link for opening a ticket. http://sales.universal-devices.com/contact-support I have some concern using the old 2414 PLC at the beginning of this process may have done some damage although with the Rx LED Off now that would indicate the ISY has some communication with the PLM. Just not sure why the safe mode with the Rx LED Off.

It is looking more and more like a communications problem with the OutletLinc location. Right click the ISY Scene name, select Diagnostics | Scene Test. What are the results? Are there Access Points installed on opposite 120v legs and do they pass the 4 tap Set button test that verifies they are in RF range of each other and on opposite 120v legs.

Avast would not resolve safe mode but I thought it might be blocking the data needed to display the PLM Info/Status. Now that the Rx light is Off there is some communication with the PLM but apparently not enough. I suggest opening a ticket with UDI so they can determine why safe mode even though we have gotten the PLM powered up and the Rx LED now Off.

See my previous post about checking the Responder On Level slider for being set at 0% rather than the needed 100%

When the KeypadLinc button H node name listed below the Scene name is selected what is the slider set to that represents the OutletLinc. It sounds like the slider is set to 0% when it should be set to 100%. A slider set to 0% actually turns the OutletLinc Off when the KPL button is pressed On.

There are other computers that have no issue connecting to the ISY and seeing device status? If you do consider using Kaspersky or Avast in the future consult the forum for the solution to lack of status before using. They are common blocking sources to the ISY pushing data to the Admin Console. It may be time to open a ticket with UDI tech support. Any post by Michel has a link at the end of the post for opening a support ticket.

Now that the PLM is allowed to power up so it is in a position to communicate before starting the ISY the PWR LED is the only LED On. The Rx LED is no longer On? Is Kaspersky or Avast being used? I would have expected Tools | Diagnostics | Show PLM Info/Status to display something.

What AV is being used? Is Kaspersky or Avast used?

Is this an OutletLinc Dimmer? Verify an ISY Scene defined, KeypadLinc button x (?) is Controller and OutletLinc is Responder. EDIT: when turning the OutletLinc On from the Admin Console does the cabinet light actually turn On? If so click the KeypadLinc button name below the Scene name and check the OutletLinc Responder On Level to be sure it is not set to 0%.

What does Tools | Diagnostics | PLM Info/Status display? Is the PLM powered before rebooting the ISY?

The Scene image is actually the Program Summary but I don't think that is important at this point. The Program summary information is not explainable. The QueryAll Program which runs every night shows a last run date of 11/10 rather than the expected 11/17. The Stair_Way_On Program has a next run date of 11/18 but nothing reflects it running on 11/17. What does Help | About show for Firmware and UI?

GordonGale I've been through the doc that came with the various ISY's I have. Everything says the 2413S requires a power supply. If you can scan and post when you get home it would be good to get whatever you are referencing fixed.

The QS guide is wrong. It should say 2412S does not need the external power supply. Can you scan and post the document?

Remove the 2414S immediately. Not sure about the pinout of the old 2414 PLC and it uses a completely different command set from the 2412S/2413S PLM. Only the now discontinued 2412S PLM provided 12v DC power from the PLM. The 2413S Dual Band PLM does not provide power to connected devices. The ISY requires an external power supply when using a 2413S which is normally included with the ISY 994.. Safe mode usually means the ISY cannot communicate with the PLM. Check the RJ45 connectors are fully seated on both ends (click heard) and the PLM is connected to Port A. Click Tools | Diagnostics | PLM Info/Status. What does it say?

wuench Set the Advanced Options back to Automatic. These are I2CS devices which should be added using Automatic. You are having Insteon mesh network problems as indicated by the comment that multiple attempts are needed to get devices added and the fact that these two Dual Band SwitchLincs are not responding at all to the commands sent. Double check the Insteon address being used. Use New INSTEON Device, enter Insteon Address, Name of choice, and leave Device Type set to Auto Discover. The event trace shows no device response (no 02 50 or 02 51 messages) to the command that was tried three times. Since multiple devices (including the ones that have eventually added) have problems look for something common such as interference from other devices at the PLM plug point. Other electronic devices, UPS, etc (even possibly noisy CFLs) should be on a FilterLinc. The PLM should be plugged directly into an outlet, no surge/noise suppressor power strip. Insure the Access Points (or whatever is being used for phase coupling) passes the 4 tap Set button test for being in RF range and on opposite 120v legs.

That is the Set Options problem at 3.2.6 using an I2CS I/O Linc. The Momentary hold time actually is set correctly. However, the new value is not displayed the next time giving the appearance that Momentary hold time is not being set. The other Set Options require a different command when it is an I2CS device.

If it happens all the time the cause is generally AV such as Kaspersky or Avast blocking the push of data from the ISY to the Admin Console app. If it happens the first time up with the Admin Console and then works when the Admin Console is restarted it is some timing situation that happens very rarely on mine and has across years of images. If my PC has been doing other things were some of the memory has been rolled out the Java based Admin Console is a little slower starting the very first time up and sometimes has blank status as the connection between the Admin Console and ISY did not get connected in time. Generally Exit the Admin Console and restart will bring it up with Status the next time. Sometimes I can go months and not see a blank Current State column. Other times after Norton has done a background virus scan and rolled out lots of memory pages during the scan I see it.