LeeG

I would think the cost of a good 5V DC supply to be not much more than buying the components and some type of component box to package the converter from 24V AC to 5V DC. The 2441ZTH specs on the sales page indicates a 5V supply as the optional supply but the same sales page refers to a 6V power supply (which is what I am using and have an excess of Humidity messages). A cell phone charger supply may not be regulated enough to power the 2441ZTH

The 2441ZTH has been found sensitive to voltage much over 5v. The specs would indicate a 6 volt supply will work (which is what I have) but the 2441ZTH sends many Humidity messages with the 6 volt supply. A user on the Smarthome forum posted a solution, putting a diode in series with the + leg of the 6 volt supply to bring the supply down close to 5v. That solved his many Humidity message problem. Have not tried that yet but it is simple solution if it works for all 2441ZTH devices.

If an ISY Program that is turning the lights Off check Programs | Summary for Last Run Time and Status (True/False) to see when Program was last triggered and whether the Then or Else clause ran. Also post the Program. If a motion sensor Dusk.Dawn node is turning Off the lights then look at the ISY Log to see what happened.

A KeypadLinc button in non-toggle Off mode cannot turn a Responder On. Not within Insteon capability.

larryllix It is the design of Insteon. There never has been a field in the Direct message that could be used to contain the button Group number. No spare unused fields. The insteondetails.pdf document on insteon.com has the various Insteon messages. This is an factor in applications only as devices other than the PLM always control other devices with Scenes.

Insteon Direct commands cannot turn On/Off Secondary KeypadLinc buttons. Does not matter if the Direct commands are issued from an ISY Program or an application like the Admin Console or MobiLinc. The structure of an Insteon Direct command does not have a field that can specify the Group number of a Secondary KeypadLinc button. A Scene Responder link for a KeypadLinc button identifies the Group number of the button the link is associated with.

For the Program timer to be restarted, set the Motion Sensor to On Only commands. Each additional On command from more motion sensing will retrigger the Program establishing a new Wait cycle. If Control 'ms1' is switched On Then Wait 5 minutes turn Off device Else

KeypadLinc Secondary buttons cannot be turned On/Off with Direct commands. A Direct command has no means of identifying which Secondary button. Define an ISY Scene with the KeypadLinc button as a Responder. Turn the Scene On and Off to affect the Secondary KeypadLinc button LED.

Maybe in a few months when Variables are updated with new features that will be possible. For now it is difficult. You would need a series of Programs that could be triggered by a motion sensor motion On ANDed with a range of On Level values. Maybe in 10-20% range for each Program. If Control 'motionOn' is switched On And 'lightOnlevel' is => 20 And 'lightOnlevel' is <= 40 Then blink light Set 'light' On 30 Else

That combination is fine. The other non load Insteon device can be a different device type. The load control device can be a Dimmer, the other non load Insteon device can be a Relay. One can be a SwitchLinc, the other a KeypadLinc, for example. Note that the non load controlling device is not wired to the load switch in a conventional 3-way connection. The non load device is simply powered with unswitched 120v power. The 3-way relationship is established by linking the two devices together, not wiring them together.

The LOW button can be set to non-toggle On mode. This will not allow the button to turn Off the Fan. Another alternative would be to have a Program triggered when LOW is turned Off. The Program would turn On the Off button.

I prefer the use of Access Points as they couple at maximum signal strength. The wired coupler is passive, placing the signal on the other phase at whatever reduced signal strength the message arrives with. Also noise can be coupled to the other 120v leg. Some folks put the Access Points near the power panel although that can reduce general RF coverage for battery devices.

Glad to hear things are resolved.

That is the problem. When Start Linking was clicked a popup should display. Without that popup there is no Finish button to end Start Linking. The lack of popup normally indicates an issue with AV/firewall. What AV is being used? The probable AV issue has to be solved first. Then the ISY must be rebooted to clear Start Linking.

Some routers will accept the external IP address from the LAN side, some will not. Can you try accessing the ISY from the external side, not the LAN side. Also try https://xx.xx.xx.xx:port# Using http sends the request over port 80

If blinking consistently and Red the PLM is reaching the SwitchLinc over RF and on the same phase. The Discovering Nodes message indicates at one point Start Linking was initiated and the Finish button on the Start Linking popup was not clicked to complete Start Linking. Was a Start Linking popup displayed when Start Linking was selected?

Tap the Set button on the PLM 4 times. This puts the PLM into an RF test mode for 4 minutes. It sends a test RF message during the 4 minutes. The Dual Band devices that receive the test RF message will blink and the color of the blinking indicates whether the receiver is on the same or opposite phase. Check the User Guide for the receivers to see how they react when receiving the test message. If the test is reversed the PLM LED blinks Red when receiving the test message from a device on the same phase, blinks Green when receiving the test message from a device on the opposite phase. The best way to couple phases is with a pair of Access Points. In wall Dual Band devices do not have the same range and if in a metal box the RF range is even less.

Set button linking should not be done when using the ISY. Define an ISY Scene and add the devices as Controllers to the ISY Scene.

The PLM could be on one phase and the SwitchLincs on the other. Has the 4 tap set button test been run to see if the PLM reaches the SwitchLincs over RF? Also note that when the SwitchLincs are added to the ISY select the first option that erases existing links. Set button linking should not be done as the ISY does not know about them. Once the Insteon network is operational create an ISY Scene and cross-link the devices that way.

Insteon has no concept of Scene status and the ISY has not invented one. The "ISY" Scene, is that the element above all the device definitions when under the Admin Console? If so that is not to be deleted.

The door sensor is a battery device. Put it into linking mode, then do the Update.

Approx 1,000,000. That is the read/write cycles of the eeprom.

My 2441TH will react to Auto but the thermostat does not change from its current mode when Program Auto is selected.

If Fade Up/Down is used be sure to end the sequence with a Fade Stop. Devices that issue a Fade Up/Down always end with a Fade Stop when the button/paddle is released. Failing to do the same with a Program can leave the responder(s) in odd states.

Sitting behind metal cabinets will not help the RF range. The range estimates for devices are clear line of site. It sounds like the RF range is marginal. Also blinking Red indicates the PLM and Access Point are on the same phase.