stusviews

Every hard-wired smoke detector should have a battery backup. Otherwise it would not function if the cause of the fire was wiring.

The 4-tap test requires observing at least two devices. One is the device where you initiate the test, the one that you tap four times. The blinking on that device is only to ensure that the device is in testing mode. Nothing else can be concluded. The next step is to observe a different dual-band device to determine if the second device 1. can "hear" the first device and 2. is on the opposite leg of the split, single-phase electric supply. The Owner's Manual for the second device should indicate what to expect. Colors vary as well as blinking or solid LED.

Until all the wires are correctly identified. any suggestion is speculative. There's not much sense in giving you half a dozen possible causes when only one or none of the guesses is correct. The end game is to get everything wired correctly and only then to find a cause ─ if the flickering continues.

Does that mean that ceiling box 4 has a 3-wire cable going to a switch box (is it switch box 1?) and a 2-wire cable going to ceiling box 3? Did you use a meter at ceiling box 4 to verify 110/120VAC between the line and neutral and between the line and ground with absolutely no other wires connected to the black and white wires from the "panel." Not even the wires from the 3-wire cable (with the unused red wire)? Until the source (line and neutral) is positively identified, any wiring suggestion is speculative.The diagram shows many possibilities. Also, label each switch box, 1 and 2 or A and B or any other specific identifier. As it is, each switch has an identical label.

Just connecting a dual-band device is not sufficient to ensure coupling. What is the result of the beacon/4-tap test? It's also possible that something on the same circuit as the problem device is impeding the Insteon signal.

Insteon terminology does not include master and slave. In a multiway configuration, the devices are referred to as primary and secondary. It's important to use correct terminology to avoid ambiguity. The OP did not seem confused. The OP missed one instruction which was to connect the red wire at switch box #1. It was my error that I indicated, "At switch box#1: Connect the SwitchLinc load (red) wire to the red wire that goes to switch box #1," instead of "At switch box#1: Connect the SwitchLinc load (red) wire to the red wire that goes to switch box #2." The OP was perceptive and caught the error. I fully agree that a labelled diagram is most helpful. An immediate goal is to correctly identify the wiring.

If moving the PLM to a different circuit helped, that indicates that there's something on the original circuit that should be filtered--even though the ISY is functioning!

Switch box #1 can keep the label no matter if it houses the primary or secondary switch. What changes is the role of the switch, not the numerical designation. In fact, changing the number will lead to confusion.

The ISY has a crude communication test. Select Restore Device. The bottom left will indicate System Busy. If that succeeds, select Write Updates to Device. What is the result? And, as LeeG indicated, ensuring proper coupling is important.

What is the result of a scene test?

Do you have any other controllers for the same scene(s)?

How far away is the RemoteLinc from the PLM? How close to a dual-band device to the RemoteLinc? Are you trying with only one RemoteLinc at a time? Are you placing the RemoteLinc into linking mode first? The RemoteLinc will remain in linking mode for four minutes. I was able to use, "Write Updates to Device." BTW, this is a know problem, but not everyone experiences it.

Move the RemoteLinc further away from the PLM, place it in linking mode (hold both DIM and BRIGHT until the LED starts blinking), then start adding/updating to the ISY. I had to be more than 30 feet away. One RemoteLinc needed a distance of 45 feet. BTW, dual-band devices were near the RemoteLincs. The key seems to be distance from the PLM.

Scenes are written to the devices themselves, programs are written to the ISY, so removing the ISY disables the programming without affecting anything else. Yes, you can use an ISY26. Release 3.3.10 is the latest revision for the ISY 26. Not all new devices are supported. Yes, you can migrate from the ISY26 to a ISY994i without losing links, But, if the ISY26 is powered from the PLM (2412), then the migration may be more involved.

There's no mention of SmartHome products. A smart home (two words) is a generic term. This tells a lot, CBR contacted Tripwire to ask which three smart home hubs have been tested, but the company was unavailable to comment at the time of publication.

Spta97, That "a 14/3 wire goes to a switch" is not descriptive. That "the black wire of the 14/3 cable goes to the switch," is meaningful. Also, if you don't have ground wires, then you most likely have metal boxes. If so, then the boxes are grounded. Screwing a device to the box grounds the device. Most important: A voltage indicator is not adequate. A meter is required. A reading should be taken between the suspected line wire and both the neutral wire from that same cable and between the suspected line wire and the metal box.

The switches are labelled. See #6. The switches are labelled. See #6.

Wired Insteon thermostats (2447TH) have that behavior. Wireless thermostats do not (2441THZ) even if they're externally powered. The power source for my wired thermostats is the HVAC 24VAC supply.

The black wire (line) at switch 2 should be connected. But, that's not the major problem. The wiring should make switch 1 the primary switch. It's wired directly to the load. That it does not work suggests that the original wiring at switch box 1 is identified incorrectly. How did you identify each wire, by color? using a meter? Where doe the 3-wire cable with the "spare" red wire terminate?

The humidity sensor is working correctly. An Insteon signal is sent whenever the humidity changes. No one has found a way to turn that off for the 2441TH.

The ISY saves a log of virtually all Insteon actions. AFAIK, Excel is required to view the log. Back to you concern: Aside from curiosity, a use of notifications is alerts. A doorbell rang, a gate opened, something did happen that shouldn't have (e..g, a leak) or something did not happen that was expected to occur. BTW, there are better and easier to use tools that can monitor energy use than a log. But, a log is a great problem for a mathematics teacher to assign. I may have done that.

Verify the state of, "07.2 Den Bk A Patio Lanterns / 07.2 Den Bk G Garage Door," ensure that it's after sunset and run "If." What's the result?

Yes, just unplug the PLM Power down the ISY. Plug in the PLM, wait a few seconds, then power up the ISY. Then restore the PLM. If you have an ISY Pro, turn off writing to battery powered devices first. Update them later, one at a time, in nay case.

Start over. BTW, the PLM is used for several applications including those by a third party, for example, the ISY and virtually every software solution.

Which coupler do you have plugged into the dryer outlet? Active X10 couplers interfere with Insteon signals. Also, use to bridge/4-tap test to determine if the PLM and SwitchLinc can communicate via RF.