LeeG

Jgdavis14 Either the Java cache is not being cleared or the wrong URL is being used. The link below has instructions for clearing the Java cache. http://wiki.universal-devices.com/index ... Java_Cache and the 4.1.2 announcement has the various URL possibilities.

Mdf The v.00 is the result of entering the Device Type when adding the Motion Sensor. Delete the Motion Sensor and add it with the default Device Type Auto Discover. I have a v.41 Motion Sensor but it is not likely the latest.

SmartLabs has not authorized any other manufacturer to build a device that interfaces on the powerline in Insteon protocol. The Monterey can help in measuring signal levels albeit it is analyzing what it thinks are badly formatted X10 messages.

"sensors will blink rapidly (20 times ?) in 10 sec" This indicates at least one responder linked to the motion sensor did not ACK the sense message. Perhaps out of range, unplugged, etc.

Drag the SwitchLinc to the ISY Scene, select as Controller.

The If requires parens. If ( Control 'M1-Sensor' is switched On Or Control 'M2-Sensor' is switched On ) And Program 'Motion Detected' is False Then

I have the Monterey Signal Analyzer from years ago when X10 was being used. I found it helpful. It does measure noise in an Insteon environment.

Right click the Program name, select Copy to Clipboard. Paste Program to forum. Please post all the Motion Sensor options. Remember to put each Motion Sensor into manual linking mode to read current options. Take that Motion Sensor out of linking mode before putting the next Motion Sensor into linking mode. A blank Status means the Motion Sensor has not sent a message related to that node. A value of 35 for Darkness is a very Dark level. The Motion Sensors would have to be covered with an opaque cover (at least 3.5 minutes) before the Motion Sensor will set Dusk On.

Use a REST command to display the nodes. It shows the Insteon address format the ISY is looking for. http://192.168.2.3/rest/nodes/ 1 DB B6 9 EZIO6I-New - 9 7.7.0.0 true 0 0 0 1 DB B6 9 G08 12 B9 D 1 KPL Floor Dimmer 6 1.27.54.63 true 0 0 0 12 B9 D 1 E13

Issue a Query against your device.

Those are Controller Only nodes. They carry no Status to Query. The node being blank after a power outage means the node has not sent anything since power has been restored. Same situation with the Motion Sensor for example. The nodes sit empty until the device sends a message from the node. Actually the Motion Sensor is a bad example as it is a battery device. The ControLinc nodes are Controller Only. Nothing to Query as the device carries no Status for which button was last pressed. There should be no reason for manual intervention with the detector.

The ISY does not list devices on the local LAN. Also when Start Linking is clicked a popup window should display. The lack of the popup window could indicate an issue with the AV being used. What AV is in use?

steffen707 Yes, using a Program does add a delay. The 4 Scene Mini-Remote takes it back to a direct Controller to Responder message. As I mentioned earlier the Mini Remote is not very flexible. Because it is battery powered and sleeps to extent battery life some of the nice things that can be done with a KPL button cannot be done with the Mini Remote.

The Off command was issued 1 second after the On command. It appears the On came from the same Web session.

Change the Motion Sensor options to On Only mode so it will not issue the Off command. Change the Program from "If Status" to "If Control" The Wait and Repeat statements will be interrupted when the If conditions change. The Off message from the Motion Sensor terminates the Wait, the If is now False so the Else clause runs. Take a look at the Wiki for Wait and Repeat http://wiki.universal-devices.com/index ... EON:Action

Here is the link to the Wiki section on clearing the Java cache http://wiki.universal-devices.com/index ... Java_Cache The other possible cause is using a URL that points to the older Admin Console. Make sure the URL used to invoke the Admin Console is correct for 4.1.1.

The Mini Remote in 8 Scene mode has that characteristic. With a KPL the button could be turned Off from another Controller. With the Mini Remote (Old RemoteLinc2) going to sleep it is not possible to alter the On/Off/On/Off pattern of a button when in 8 Scene mode.

steffen707 Going to 4 Scene mode will provide separate On/Off buttons. Of course you lose 4 Scenes. Depends on what is the more important item.

The Mini Remote is not very flexible when setting button modes. The only way to solve the problem is to have the Mini Remote button (both On and Off commands) trigger an ISY Program. The Program checks the Status of the in-line linc, turning it On if Off and Off if On. That way it does matter which command the Mini Remote sends. The ISY Scene with the Mini Remote as a Controller has to be deleted.

"What is the correct procedure for linking it to the ISY? " Put the Open/Close Sensor into linking mode by pressing Set button until LED blinks continuously. Use New INSTEON Device, enter Insteon address, Name of choice, Device Type at default Auto Discover. Insure Open/Close Sensor is near a functioning Dual Band device.

If Control statements trigger the Program only when the command received matches the command specified. Without the NOT SWITCHED OFF statement the Else clause will not execute.

What does Help | About display for Firmware level and UI Level? The devices are listed in Cat/Subcat level. The 2.55 is [02.37] in hex (the way Smarthome/SmartLabs lists Cat/Subcat). That device is supported in 4.1.1.

"Just to clarify that: If a trigger condition changes and logic becomes negative, resulting in the "else" clause being invoked, the "then" clause wait timers (and following lines of code) get cancelled right where they are?" The above is correct but not limited to If becoming False. A change in the trigger conditions cause the If to be reevaluated (while in Wait or Repeat statement) which may drive Then or Else clause.

The Leak Sensor nodes are Controller Only nodes. The nodes have no function to Query so a Is Not Responding is not condition that will exist past getting the device installed. Heartbeat On and Off are the two conditions to be checked.

A functioning Insteon Mesh Network is often not as easy as plugging a device in at the desired location. A pair of Access Points to couple the two 120v legs, isolating noise/attenuation sources at the PLM location are a few items that have to happen. Plugging the ApplianceLinc into the PLM location avoids the need for the above. Of course it is not a solution but does verify the PLM and ApplianceLinc function together. Now the other requirements can be implemented to get started on creating a good Insteon network.