LeeG

I agree with oberkc's conclusion about (same day) versus (next day). The Program looks more like a contrived test Program to see what happens, Sunset + 9 hours and 43 minutes (same day) rather than something functional. With the changing of Sunrise/Sunset times the results may vary. Also these times from Sunset do not match the initial post. What is your Sunset time now, which could be different from the day in question. Also check the Programs | Summary tab Last Run Time to be sure Program was not triggered. There is a possibility of unreliable comm making it look like the Program was not triggered. A Scene failure due to comm problems would not produce errors in the event log nor in the error log. If From Sunset + 8 hours To Sunset + 9 hours and 43 minutes (same day)

Devices that have been cross-linked still respond individually when Direct commands are used. Insteon is designed to work that way. When both (all) devices should react together turn the Scene On/Off with the Admin Console, ISY Program, or App. When only an individual device should respond use a Direct command.

The algorithm checks for a link database start point at 0FFF, 1FFF, and 3FFF. The algorithm concluded the link database started at 3FFF so the ISY wrote the Input Controller records at that location. The SHN Utility could not read back those link records. The manual Set button link written by the PLM itself was written at 1FFF which is where the link database is expected to start for a 2413. The SHN Utility was able to read this link record.

Correct as needed. Breaker turned Off. Light fixture wiring accessed Breaker turned On. 6 different Insteon devices appear to not have 120v power. The most probable failure point is the wiring at the light fixture. The possibility that 6 different Insteon devices all failed at the same time is so low as to be considered impossible. It is much more likely that a wiring connection/problem was created when the wiring in the light fixture was accessed. A basic check of AC voltage at select points should locate the problem. It is possible that the breaker failed to close since it was mechanically operated but a breaker failure like that is rare.

Not if a wire is lose under a wire nut! You might consider calling an electrician. This sounds like something an experienced electrician can resolve in a few minutes.

Cycle the breaker. It sounds like the breaker tripped when wires shorted during work on light.

Any time a Wait or Repeat is executing (includes the entire Wait time) and the If conditions change the Wait/Repeat is terminated, the If reevaluated. This can result in the Then clause starting over or the Else clause running.

Brian The older EZIComms are 2412S based with a passthru outlet. They are a 2412S with a different label. The newer EZIComms are now 2413S based with no passthru outlet. Some of the EZIOxx devices that were shipped using the first 2413 shells are actually I2CS devices and they identify themselves as having an I2CS Engine. I have a few of those. The PLM supports only extended ALDB commands for link database management. The EZIOxx firmware still supports a private implementation of Set MSB/Peek/Poke so those commands are used to for device configuration. Once SHN realized they were actually I2CS PLMs they started reflashing the PLM to drop the I2CS logic. That has created some problems in the process as this topic, ELA (and others) have encountered. The memory size algorithm that SmartLabs developed produces false results with some of the reflashed PLMs. I guess it depends on the firmware level the PLM is reflashed with.

When there is no passthru outlet it is a 2413 shell which means no external power. It would normally be a Dual Band shell but not sure what the reflash does to the Dual Band capability.

A little background. Over years SmartLabs has manufactured 120v PLMs with three different size memories. One that supports 417 links, one that support 992 links and one that supports 2000+ links. SmartLabs declined to provide a command that would specifically indicate the size of memory. Eventually they provided a complex algorithm that would identify the size of memory. This algorithm indicates your PLM (EZIComm) supports 2000+ links. Your PLM (EZIComm) does not actually support 2000+ links. The algorithm should indicate 992 links (confirmed by the Set button test) but produces a false result because the PLM was reflashed by Simplehomenet/Smartenit to avoid I2CS issues. The suggestion by ELA corrected his problem. Also moving to a true 2413S PLM should also work. I’ve tested the EZIO8SA with a 2413S years ago when the 2413S first came out. It worked fine then. Since the EZIOxx firmware has not been updated in years I would expect the 2413S to continue to work.

Make sure the Subject and Body are not empty.

With the caveat that I have no idea what capability exists with the ISY firmware that runs on an ISY26 and for certain the ISY26 will not support the newest Dual Band KeypadLincs If Status 'device1' is On And Status 'device2' is On And Status 'device3' is On Then Set Scene 'kplbutton' On Else Set Scene 'kplbutton' Off Scene 'kplbutton' contains the KeypadLinc button as a Responder Assuming the KeypadLinc button is a Secondary button a Scene is required to turn the KPL button LED On and Off.

The internal PLM in the EZIComm indicates it supports 2000+ link records which is physically impossible for a 2413 PLM shell (no passthru outlet). SHN/Smartenit is reflashing the PLM firmware to avoid the I2CS issues. Looks like the older PLM firmware is causing a problem with what would normally be an I2CS PLM that supports 994 link records. Suggest a manual Set button link with a responder to one of the EZIO8SA Inputs. Use the SHN Utility Suite to display the EZIO8SA link database using the Large option, then the Medium option. I suspect the manual Set button link will show using the Medium option but the link records the ISY created will not because the PLM firmware incorrectly indicates memory large enough to handle 2000+ links.

Thanks for the updates. The trace file has not arrived yet. I'll look at it when it arrives.

What does the right side of the node display indicate for device type? It sounds like the ISY does not understand it is a motion sensor. What does Help | About show for Firmware and UI lines? I created the Scene on 4.0.5 and did not get the motion sensor as a responder. That suggests an issue with the level of the UI or the type of device.

Post the Program, right click Program name, select Copy to Clipboard, paste to forum. If the Off Program is separate from the On make sure it is Enabled, not in a Folder that is False. With nothing in the event trace the conditions driving the Program are not producing the results you expect. Often a Wait is being canceled when the If conditions change so the statement(s) after the Wait do not execute.

Until Michel jumps in again, the 170001 message number has many possible texts associate with it. 170001 is a placeholder message number the ISY uses for informational messages that are primarily for UDI usage. If there is a problem that requires UDI assistance the 170001 messages provide additional data to help UDI evaluate the problem. These are informational messages, progress messages, activity messages, indicate how far a particular piece of code has executed, etc which do not themselves indicate any failure but can be helpful to UDI. They can be ignored. They should occur only when the event trace is running at LEVEL 3.

The Heartbeat message should occur every 24 hours. The next Heartbeat message interrupts the Wait 25 hours at the 24 hour mark, starting a new 25 hour Wait. The X10 message will not be issued so long as the Leak Sensor sends a Heartbeat message every 24 hours. It makes more sense to issue a Notify rather than the X10 message. I don't use a Notify because this Leak Sensor is in a test bed.

Battery life is advertised in the 10 year range. There is a Heartbeat node that sends a message every 24 hours. This node can be monitored to insure that Leak Sensor messages are reaching the ISY/PLM.

ISY Programs are triggered by a "change" in Status. There would not normally be a change in Heartbeat Status. Use If Control to monitor the Heartbeat node. If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action') The command sent with the Heartbeat message depends on the Wet/Dry state of the Leak Sensor. Each Leak Sensor has to be monitored individually as they are all on a different 24 hour cycle.

Do other Insteon devices show state changes? Does the EZIComm have a passthru outlet on the face? Were any changes made using the Utility Suite (should not have)? Be sure analog inputs 5 & 6 are connected to EZIO8SA Gnd to prevent them from cycling. Delete the EZIO8SA from the ISY. Factory reset EZIO8SA. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Add the EZIO8SA using New INSTEON Device. Enter Insteon address, Name of choice, Device Type at default Auto Discover. Post the event trace. If too large to post send to lwgwork@embarqmail.com

A KeypadLinc has one Insteon address with each KPL button identified by a Group number. 8 button KPL Buttons A-H use Group numbers 01-08. Group number is the second byte xx in the link record. E2 04 xx.yy.zz aa bb cc - this represents KPL button D with xx.yy.zz the device that is being controlled. Any given button number can have multiple E2 link records 6 button KPL ON/OFF buttons use Group 01 Secondary buttons A-D use Group 03-06. Can you confirm there is an ISY Scene with the RemoteLinc button and KeypadLinc button as Controllers

Put the RemoteLinc into linking mode, right click the RemoteLinc primary node, select Diagnostics| Show Device Links Table. Same thing with the KeypadLinc but not necessary to put it into linking mode because it is not battery powered. Perhaps a sanity check of the configuration. There is an ISY Scene with the RemoteLinc button and the KeypadLinc button as Controllers with some other device(s) as Responders or Controllers. The RemoteLinc turns the other devices On and Off but the KeypadLinc button LED does not turn On and Off.

Links exist in both the Controller and Responder. Resetting only one device leaves broken links. If the Responder still has a link it will respond to the Group Broadcast message from the Motion Sensor even though the Motion Sensor does not contain a link pointing to the Responder.

Motion Sensors as well as the other battery powered RF only devices have to be added using New INSTEON Device. They do not stay awake long enough to use Start Linking. The jumpers do not matter when adding the Motion Sensor. Jumper 5 is needed to configure the Motion Sensor from the ISY. It is best to post the actual Program by right clicking the Program name and selecting Copy to Clipboard. Then paste into forum post. Posting pseudo code that is missing important keywords means an answer is based on probabilities rather than absolutes. When using If Status the Status HAS TO CHANGE to trigger a Program. A static On does not trigger a Program with If Status xxxx is On. Same applies to the EZIO8SA Input. Do not reboot the ISY. This can be done remotely but that is not the solution. Change the Motion Sensor Status and/or the EZIO8SA Input. If using the Motion Sensor in On Only mode then the Program must be triggered with If Control 'xxxxx' is switched On.