LeeG

I got that sense when reading from the beginning. Sorry, I am not the best resource for working through Mac remote access.

I may have misunderstood, is the ISY remote to your location and you want to do everything remotely?

3.3.10 is so old I don't you want to upgrade to that unless using a very old 99i. 4.2.30 is the latest Official release for 994i. That information is posted in Current Release, Betas and Bug Reports http://forum.universal-devices.com/topic/15795-release-4230-is-now-official/

remedy1234 I have never accessed my ISY remotely and I install every ISY image, Beta and Official released (except 5.0 Alpha). Don't know what you want to update to so I will use 4.3.3 RC2 as an example. Go to the 4.3.3 RC2 announcement and click on 2m1 line that matches your 994i. That will download the ISY image to your computer. Follow 2m2, 2m3 and 3. to install downloaded ISY image from your computer. Then click on 4.a to install matching Admin Console. If some other ISY image is desired the instruction line numbers may be different but the sequence is the same. Only takes a few minutes. Feel free to follow up with questions if needed.

The smaller the number the darker it has to be. Takes at least 3.5 minutes for Dark condition to exist before it takes effect. Keeps the Motion Sensor from changing modes do to car lights passing by. Remember the Night Only mode also has to be checked for the Motion Sensor to operate only in the dark.

I also noted that the Heartbeat is tripping every 9 seconds. That means the 3AM Query will be handling multiple variable updates during that Query sequence. Is it necessary to track the operation of the security system that frequently?

I've run my 3AM QueryAll Program several times without a problem but I keep my Insteon network running very well. I suspect you are seeing with the FanLinc what some users see with an I/O Linc which also has two nodes. The actual Query command response does not indicate which FanLinc node it applies to. Some users have seen a delay in the Query response of an I/O Linc node such that the next I/O Linc node is queried before the query response is received for the previous node. It allows the query response to the previous node to be applied to the next node (because node number is not contained in the response). This is speculation at this point since the LEVEL 1 trace does not show actual commands and response. I set the Light node to 100% On (FF) and Fan node to Med (BF). Below is what the trace of a FanLinc at LEVEL 3 should be. Thu 05/28/2015 02:49:19 PM : [iNST-TX-I1 ] 02 62 14 9E F5 0F 19 00 Thu 05/28/2015 02:49:19 PM : [iNST-ACK ] 02 62 14.9E.F5 0F 19 00 06 LTSREQ (LIGHT) Thu 05/28/2015 02:49:19 PM : [iNST-SRX ] 02 50 14.9E.F5 22.80.0B 2B 00 FF (FF) Thu 05/28/2015 02:49:19 PM : [std-Direct Ack] 14.9E.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 05/28/2015 02:49:19 PM : [iNST-TX-I1 ] 02 62 14 9E F5 0F 19 03 Thu 05/28/2015 02:49:20 PM : [iNST-ACK ] 02 62 14.9E.F5 0F 19 03 06 LTSREQ (03) Thu 05/28/2015 02:49:20 PM : [iNST-SRX ] 02 50 14.9E.F5 22.80.0B 2B 19 BF LTSREQ (BF) Thu 05/28/2015 02:49:20 PM : [std-Direct Ack] 14.9E.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 05/28/2015 02:49:20 PM : [iNST-TX-I1 ] 02 62 14 9E F5 0F 19 00 Thu 05/28/2015 02:49:20 PM : [iNST-ACK ] 02 62 14.9E.F5 0F 19 00 06 LTSREQ (LIGHT) Thu 05/28/2015 02:49:20 PM : [iNST-SRX ] 02 50 14.9E.F5 22.80.0B 2B 00 FF (FF) Thu 05/28/2015 02:49:20 PM : [std-Direct Ack] 14.9E.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 05/28/2015 02:49:20 PM : [iNST-TX-I1 ] 02 62 14 9E F5 0F 19 03 Thu 05/28/2015 02:49:21 PM : [iNST-ACK ] 02 62 14.9E.F5 0F 19 03 06 LTSREQ (03) Thu 05/28/2015 02:49:21 PM : [iNST-SRX ] 02 50 14.9E.F5 22.80.0B 2B 19 BF LTSREQ (BF) Thu 05/28/2015 02:49:21 PM : [std-Direct Ack] 14.9E.F5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

I just realized that the Event Log has an entry showing Fan as being Off/turned Off before the 3AM Query of Light and Fan which shows the Fan as Med. Need to see LEVEL 3 trace to better understand what is actually happening. Post the LEVEL 3 event trace showing well before 3AM Query of FanLinc as well as after those query calls.

The Event Log running at LEVEL 1 is not very helpful (would be better at LEVEL 3 to show command that turned Fan Off). It shows the 3AM Query of FanLinc Light and Fan, the Fan was On at Med speed. Immediately after the Heartbeat variable was changed the Fan was turned Off. Look at the Heartbeat logic to see if the Fan can be turned Off or any other Program that can turn the Fan Off based on Heartbeat status.

Works fine. Dimmer can control a Relay (non-dimming). A Relay (non-dimming) can control a Dimmer.

Use the ISY Finder. With multiple ISY devices in use it allows the selection of the appropriate ISY. No Browser involved.

At cache.insteon.com/documentation/2443-en.pdf is later manual but covers the pre-v2 LED operation on page 5

Device 0F.2E.0B did give a response on the third try indicating it is an I2 device but failed to give any response to the command asking for the device type. An update to a link record in 06.D5.75 failed to get any response. Was any new appliance added? Could one of the devices that are coupling the 120v legs lost power? There is a comm problem.

unplugme71 If the name assigned to the motion sensor is long you many not see the additional words. This is what Motion Sensor nodes should look like.

The PAR38 Halogen bulbs are dim-able and the LED bulbs (if used) must be dim-able. That indicates to me the motion sensor output is still electronic rather than relay driven. I suspect if a scope is used the motion sensor output is not pure 120v. The Flood Light display usually has the less expensive relay driven models. The relay can be heard as the motion is detected.

I copied the Then/Else sections of your Program to maintain your device names but in the process lost the Else section of my suggestion. The Else clause requires an Off to catch the case where the Fan is turned On say 30 minutes before the To time. This drives the Else clause at the To time, missing the Off command in the Then clause. Then Wait 1 hour Set Scene 'Children's Rooms / Asher's Room / Asher's Fan' Off Else Set Scene 'Children's Rooms / Asher's Room / Asher's Fan' Off

I think you want something like this ... FanOff - [iD 008F][Parent 0001] If ( Time is 7:29:39AM Or From 8:29:50AM To 6:30:00PM (same day) ) And Status 'Children's Rooms / Asher's Room / Asher's Fan' is On Then Wait 1 hour Set Scene 'Children's Rooms / Asher's Room / Asher's Fan' Off Else - No Actions - (To add one, press 'Action') This ORs the times along with ANDing the Fan On

That Program cannot work as the If will never be True. The initial Time is outside the From/To range.

You should have enough to get started. Once the equipment has been connected electrically run the 4 tap Set button test from the PLM. That will show how well the PLM and Range Extender are working to couple the 120v legs.

The Wiki information and the ISY User Manual accessed from the Wiki or UDI Support tab cover the information you will use. The ISY forum itself is also a good reference source as well as the many ISY users who contribute to the forum. As long as both power panels are powered from the same meter a single pair of devices for coupling is okay to start. If there are comm problems on circuits on the second panel more can be added later. The RF range of the PLM or other Dual Band devices is difficult to forecast. Metal J-Boxes, wall construction, etc are hard to project. There is a 4 tap Set button test that shows RF coverage and on which 120v leg.

The ISY Admin Console has the interactive functions to add devices, define Scenes, and create ISY Programs. A Scene would not be used in this case as there is no timing function in a Scene. The Program to accomplish 3) would look something like this .... HallLight - [iD 008E][Parent 0001] If From Sunset To Sunrise (next day) And Control 'OpenClose1-Opened' is switched On Then Send Notification to '?????' Set 'HallLight' On Wait 5 minutes Set 'HallLight' Off Else - No Actions - (To add one, press 'Action') Of course the timing values of Sunset and Sunrise would likely be different in your case. The Logging (Send Notification) is dependent on your configuration There are additional items to consider. Insteon requires Coupling between the 2 120v legs. Range Extenders can be used for this purpose. Also a Dual band device must be in range of the Door Sensor. The PLM may satisfy this but you may need an additional Dual Band device.

Not directly. However with some application in between it is certainly possible. ISY 1 has a Program that monitors the Door Sensor. It could send a REST command with the Network module to ISY 2 to control an I/O Linc Relay.

The Heath Zenith motion sensor does not output a voltage that will trigger micro module. The motion sensor has dual bright feature that affects the sensor signal. This has been discussed on the Smarthome forum in the past. It was suggested that a relay be driven by the sensor (if my memory is correct) but I don't think an actual working solution was posted.

If the only device not reporting Status changes was the I/O Linc that device had an issue with it's link database. If this is the only time it has happened with the I/O Linc I suspect some problem with the electrical power going to the device, perhaps a storm that caused a surge or drop in power to the device. Normally devices do not have link database problems. I would not be concerned unless it happens again. Then see what else is being powered from that circuit in the garage. Power tools often have a heavy draw of current as they power up.

raymondh The color of the flashing reflects the wiring in the residence. With the circuits being on the same 120 v leg coupling may not be an issue. The same 4 tap test should be done from the PLM to see it is on the same 120 v leg. Is there a comm issue being being evaluated with this 4 tap test?