LeeG

The Log shows all 20 devices turning On? There have been reports of All On events occurring with speculation they are the result of low batt in a motion sensor or PLM issues but these do not show in the Log.

This URL works fine from here http://isy.universal-devices.com/99i It retrieves the 4.0.5 (actually 4.0.11) Admin Console. It takes some time as the full Admin Console has to be downloaded from UDI.

Suggest running a Restore Device on the I/O Lincs. All the items noted working do not require link records. The reporting of Sensor status change requires a link record in the I/O Linc and the PLM.

There is another error in the URL http://isy.universal.devices.com/99i should be http://isy.universal-devices.com/99i

Is this a finger check or a bad URL ... http://isv.universal.devices.com/99i should be http://isy.......

I think UDI has fixed this as indicated in the post of page 4 of 4.2.3. I believe the post should say 4.2.4 hopefully available by Friday. viewtopic.php?f=25&t=14926&start=45#p116322

Post the URL used when its available. The messages suggest the IP address being used to access the 994i may not be correct. The 994i will by default be in DHCP mode.

I pulled these two from the 4.0.5 announcement. c. http://isy.universal-devices.com/99i/4.0.5 - Java Applet d. http://isy.universal-devices.com/99i/4.0.5/admin.jnlp - Java application

Not until 5.x when Variables and Programs are expanded. Not sure if what you want will be in that image since the details in the image have not been released but not before then.

What is the exact URL being used to invoke the admin console?

The I/O Linc User Guide assumes the KPL button and I/O Relay are being linked together with the Set button. How the I/O Linc Relay reacts is established by the state of the Sensor. When setting up the Scene under the ISY the I/O Linc Relay On Level can be changed with the UI so the results achieved can be different. Using Momentary A mode the I/O Linc Relay reacts to only one command, either On OR Off, not both. The I/O Linc Relay Scene responder On Level determines which command. Using Momentary B mode the I/O Linc Relay reacts to both On and Off commands. Using Momentary C mode the I/O Linc Relay reacts to both On and Off commands, but it depends on the state of the Sensor which command controls at that time. Which command turns the Relay On is based on Sensor state which can be reversed by changing the I/O Linc Scene Relay Responder On Level. The KPL button On Level does not affect how the I/O Linc Relay reacts in each Momentary mode. The KPL button On Level may affect what command the KPL sends but it does not change how the I/O Relay reacts to that command. How the I/O Linc Relay reacts to a given command is based on which Momentary mode is defined and what the Scene Relay Responder On Level is set to for the Controller in use.

Can you reverse the notify calls to see if it is the second email or the ISP?

What specific actuator is being used? The posted link does not work. Need to know the electrical load the actuator requires.

The Micro Module is switching 120v AC from the Line connection. The post to the actuator does not work but the post says 24v AC. That will not work.

Unfortunately my v.36 does the same thing. The link records for the Scene are defined for the other buttons to turn Off but they turn On. Ran the same test on a v.41 and it worked correctly. A Query of the v.36 does correct the ISY information. The load control button has to be queried. The ISY does not issue an actual query when requested for a secondary button.

If the KPL buttons are set to 0% On Level but still turn On what is the firmware level of the KPL?

The best way is to control the Scene with MobiLinc rather than the FanLinc Fan itself. When all the KeypadLinc buttons turn On the Scene the Program is invoking does not have the other KPL buttons set to 0% On Level. In the Low example that Scene must have the Low KPL button(s) set to 100% On Level and the other three KPL buttons set to 0% On Level so the other buttons are turned Off or stay Off.

Every Controller in a Scene can have a unique set of responder values. Setting the highest level Scene information applies to when the PLM is the Controller. Glad it is working. Thanks PurdueGuy for adding the additional post. I should have included that in my post as that is a common problem.

The ISY 99i is past End of Life. Whatever thermostat chosen will have to be available for more than a year for it to work with the 99i.

That is the same switch. It is the switch that was originally shipped with the garage kit.

I would suggest getting a NO magnetic switch or the combined NO and NC closed switch (SECO-LARM Enforcer SM-226L-3 Magnetic Garage Door Contact Switch) that originally came with the garage kit.

There would be 4 scenes. Each KPL button with 100% On Level is a Controller. Other KPL buttons with 0% On Level in the scene are Responders. FanLinc Fan is Responder in each Scene SceneFanHigh button A - 100% On Level button B - 0 % On Level button C - 0 % On Level button D - 0 % On Level FanLinc Fan - High On Level SceneFanMed button A - 0% On Level button B - 100 % On Level button C - 0 % On Level button D - 0 % On Level FanLinc Fan - Med On Level SceneFanLow button A - 0% On Level button B - 0 % On Level button C - 100 % On Level button D - 0 % On Level FanLinc Fan - Low On Level SceneFanOff button A - 0% On Level button B - 0 % On Level button C - 0 % On Level button D - 100 % On Level FanLinc Fan - Off On Level

That is correct, Query the device that is not providing the needed state information (Status). I think the better approach is to fix the noise/absorption problem with the openers rather than do a Query.

Then Set 'IO Linc-Sensor' Query

"Does the status command do a query first? If not it will give the wrong status above. Can you query within a program to change the status?" The If Status does not Query before reacting to a Status change. If the I/O Linc Sensor state change message is not making it to the PLM the If would not trigger because the Sensor state change did not reach the ISY. A Program can issue a Query. If the Query changes the Sensor state a Program checking the Status will trigger. If it is the Program that issues the Query the Program will not trigger again until the current processing is complete or a Wait/Repeat is encountered.