LeeG

No. There is a ISY Irrigation Module which estimates the amount of water needed for irrigation. The Irrigation Module requires the ISY Weatherbug Module for weather data. However, neither of these ISY modules is required for the ISY to physically support the EZRain/EZFlora device as far as turning On/Off EZRain/EZFlora Zones under ISY Program control.

Xathros Good question. The Adjust Scene changing the Responder value(s) in the InLineLinc (or any Responder) will not write to the Motion Sensor Controller. All the information being changed resides in the InLineLinc link database.

Great news! As a final check click Help | About and verify that the Firmware line and the UI line are at the same level.

With the Programs tab blank click Tools | Diagnostics | PLM Info/Status and see if it shows Connected. The Load Controller node name being Red indicates it is a device with Controller capability. It should have been Red all along. Being Blue and a light bulb before indicates the ISY was not able to determine what type of device it was and added it as a Responder Only device. With the type of device changing from Blue to Red, a blank link table and NAK, the device has been deleted and added back using the correct level Admin Console and with good communication with the2477SA1.

The 2477SA1 is an I2CS device. The 02 response to the 0x0D command indicates I2CS. Wed 04/03/2013 04:33:36 : [iNST-TX-I1 ] 02 62 1A C7 62 0F 0D 00 Wed 04/03/2013 04:33:36 : [iNST-ACK ] 02 62 1A.C7.62 0F 0D 00 06 (00) Wed 04/03/2013 04:33:36 : [iNST-SRX ] 02 50 1A.C7.62 1E.45.BE 2B 0D 02 (02) Wed 04/03/2013 04:33:36 : [std-Direct Ack] 1A.C7.62-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Communication with the 2477SA1 is good at the time the event trace was taken. Hops Left=2 is as good as it gets. The Show Device Links Table contains more link records than the Show ISY Links Table indicates should be there. The link to 0D.55.E9 may be the manual link that was done. Show Device Links Table HOT H2O MBR - 1A.C7.62.1 / 1A C7 62 1 0FF8 : E2 01 1E.45.BE FF 1F 01 0FF0 : A2 00 1E.45.BE 00 00 00 0FE8 : E2 01 0D.55.E9 03 00 00 0FE0 : A2 00 1E.45.BE 00 00 00 0FD8 : 00 00 00.00.00 00 00 00 Device Record Count : 5 Show ISY Links Table 0FF8 : E2 01 1E.45.BE FF 1F 01 0FF0 : 00 00 00.00.00 00 00 00 Device Record Count : 2 Perhaps tech support established another remote session and fixed the problem. Any I2CS device must have at least one link record that authorizes the PLM to control the device. With the link table being empty before and the NAK that would go along with an On request from an unauthorized PLM, something has corrected the device between then and now. A Restore Device will correct the device link tables to get rid of the extra link records.

The solution of adding all the n-way devices as Controllers of the same Scene is the correct answer. The ISY will cross-link the devices as needed to insure they stay in sync. Manual linking should not be done after adding devices to the ISY. Devices added to the ISY are best added with 'erase existing links' default option. The Quick Start guides are written without the point of view of ISY. Most Smarthome documentation is written as though there is no HA package in the picture. Certainly is not written with the ISY in mind.

If you get to the point of running an Event Trace at LEVEL 3 of the On request, also right click the Load Controller node and select Diagnostics | Query Insteon Engine. My 2477SA1 is an I2CS device which requires a link record to be functional. The trace of the Query Insteon Engine will show if it is an I2CS device. Also need to click Help | About and see what is displayed for both UI and Firmware. If your Load Controller is an I2CS device the NAK is the result of a missing link record. The event trace of the On request will also confirm that.

UDI tech support is as good as it gets. If they dead-end post an event trace at LEVEL 3 of the request to turn On the Load Controller. Was the ISY updated to 3.3.10 or later? What is the Load Controller firmware level? What does a Show ISY Links Table display for the Load Controller?

I can't fix the fan turning Off when the Off paddle is pressed so long as the SwitchLinc controls the load. If you put the fan on some device then the SwitchLinc paddle is driving Program logic which can be made to satisfy just about any set of rules you want to define. Within the existing limitations, a Fast Off would turn the Fan Off and not drive the Program to turn it back On but I don't see guests being that Insteon aware.

If the SwitchLinc in question is controlling the load (fan) when the SwitchLinc is turned Off the fan stops. A Program could be triggered with an Off paddle press that turns the SwitchLinc back On for 15 minutes but that has to be an overt Program action. The posted Program turns the SwitchLinc Off in 15 minutes after being turned On manually. There is not action to turn the SwitchLinc back On after being manually turned Off.

I should have put this in the previous post. The SwitchLinc is receiving the commands, reacting to the commands, but either not sending ACKs back that the commands have been received or the Insteon Network is not passing the ACKs to the PLM. The ACKs are the 02 5x inbound messages that are missing. That is why the ISY concludes a communication problem. For most commands sent to a device the device must respond with an ACK or NAK which the PLM sends to the ISY as an 02 5x message. The 02 5x messages are inbound from a device to the PLM. The last posted event trace of On/Off message activity shows outbound commands 02 6x but no inbound 02 5x messages.

I would put the SwitchLinc on an Appliance cord (plug on one end, bare wires on the other) and plug it into the PLM plug point. Could be a SwitchLinc issue but I always assume Insteon Network issue until proven otherwise. Run the same Event Viewer at LEVEL 3, On/Off test and look for 02 5x entries in the event trace. If no 02 5x entries with the SwitchLinc responding and plugged into the PLM plug point then the SwitchLinc has a problem. I would Factory Reset the SwitchLinc to see if that restores the 02 5x message activity before replacing it. A Restore Device is needed after a Factory Reset.

There are problems with it now. The event trace shows no 02 51 responses to any of the On/Off messages. Should look at the SwitchLinc to see if it is physically responding to the commands and the 02 51 response is not making it back or the On/Off messages are not making it to the SwitchLinc.

Actually that is very good news. The others were transient in nature. The ApplianceLinc trace had no actual updates to write. The ISY sent a command to determine link database location, the ApplianceLinc responded as expected. Had the effect of doing a successful Query. This time the SwitchLinc Relay trace does not include the Query Insteon Engine command. The ISY sent the Set MSB command three times and three times the SwitchLinc did not respond. With the Event Trace at LEVEL 3, send some On and Off commands, say three each alternating, and post the trace. This may be more a conventional powerline issue since the other devices are not showing the same symptom. The event trace should provide some information as to the general health of communication with the SwitchLinc.

I don't see how the ISY itself could be causing this. The device is not responding to commands that the PLM has accepted and should have sent. Can you run an Event Trace at LEVEL 3, right click the ApplianceLinc with a Red ! and select Write Updates to Device. I assumed all the devices produced the Red ! for the same reason. That assumption is worth verifying.

paauto Sorry, the SmartLinc is not supported as the powerline interface. The SHN Utility makes no changes to the PLM so if you have a Serial port the ISY PLM can be temporarily connected to the PC and use it as the powerline interface. I believe you will need a new EZFlora with v28 firmware to control with the ISY.

The "If Status" requires a change in Status to trigger a Program. Since the Status of the iMeter Solo is normally "is Responding" there is no change in Status to cause the Program to trigger. Setting the Program option to "Run at Startup" drives the Program when the ISY starts. Could also add a specific Time trigger to start the Program.

Spread across 3 device types there is something else common. Was the 99i running 3.3.10 from its release or was the 99i updated to 3.3.10 ahead of moving to the 994i

I did some Show Device Links Table testing on a 3.3.10 system. The only difference I can see is the Show does not Query the Insteon Engine type before reading the device link database. The Write Updates to Device does Query the Insteon Engine to be sure it knows how to write the updates. What the Query Insteon Engine has to do with the device not responding to the Set MSB command attempt I have no idea since it would start out with Set MSB command to do the Show Device Links Table. The fact that basic On/Off commands work is not surprising since this does not look like normal communications problem. What are the Device Types of the other devices that have the Red !?

Is the same PLM being used with the 994i? What is the Device Type of 12.EC.D7? It took two attempts to Query the Insteon Engine of 12.EC.D7 which is an I2 device. Three attempts were made to start to access to the device link database. The device failed to respond to each of the three attempts which is strange since the Show Device Links Table would have done a similar command sequence. Very hard to explain the results with the available information. Has anything changed from when the Show Device Links Table was successful and when the Write Update to Device failed?

Do not remove it. Don't think it can be Deleted. Has something to do with power management.

Nothing obvious from the link table display 0FF8 : A2 00 19.71.B8 FF 1F 00 0FF0 : A2 01 13.C1.7A FF 1F 00 0FE8 : A2 10 19.71.B8 FF 1F 00 0FE0 : E2 01 13.C1.7A FF 1F 01 0FD8 : E2 01 19.71.B8 00 00 01 0FD0 : 00 00 00.00.00 00 00 00 Device Record Count : 6 Do not know what the SSL error means. What does the Event Viewer at LEVEL 3 indicate when one of the devices with a Red ! is selected with Right click and Write Updates to Device is selected.

Pull the air gap switch and/or unplug device(s) before Deleting from the ISY. To be sure I understand, these devices will not be referenced by any device(s) that remains defined to the ISY? You are not trying to create what will look like broken/half links to the ISY?

lukeharrington “all I need to do is simply remove it and my newly installed switches should work at full brightness?†I would think so.

A Query of the OutletLinc Relay, either with the QueryAll Program at 3 AM, a User Program or through the Admin Console will set the OutletLinc node to the current state of the device. If the state changes as a result of the Query, a Program with If Status will be triggered. It sounds like load sense may be On in the OutletLinc such that when the washer turns Off load sense sees the washer Off and turns the OutletLinc Off. There is a procedure in the OutletLinc User Guide for turning the load sense Off. If it is load sense there is no need to turn the OutletLinc back On. Load sense will turn the OutletLinc back On when the washer turns On.