LeeG

jwagner010 Comm with this device is poor Sun 03/03/2013 06:51:58 PM : [std-Group ] 20.93.9B-->11.00.01, Max Hops=3, Hops Left=0 Sun 03/03/2013 06:51:59 PM : [std-Direct Ack] 20.93.9B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 03/03/2013 06:52:00 PM : [std-Direct Ack] 20.93.9B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 If an Off message is missed the On/Off/On/Off paddle sequence will get out of sequence with the ISY status. Also why are two Querries being done? One in Then, one in Else?

barrygordon Refer to the 3.3.10 announcement. There is a separate link for 99i versus 994i download

oberkc Right click the device primary node, select Group/Ungroup Devices

Great that it is working with the nodes Grouped. I have no explanation for the results.

"The problem started when I changed out the Switchlinc to a dualband switchlinc" There is a problem with Dual Band SwitchLincs at 4.0.1 where a paddle press may not trigger a program if the paddle is pressed too quickly. It is corrected in 4.0.2

rpsa The Smoke Bridge is sending Scene/Group messages with an unexpected/undocumented Scene/Group number. For sure 3.3.10 and 4.0.1 will not work. The 4.0.2 release indicates the Smoke Bridge has to be deleted and added back to the ISY. Assume that means 4.0.2 has a fix but I do not have a Smoke Bridge to confirm.

If the email is repeating it is likely the result of the humidity changing slightly above or below 62%, coming back to 62%. Not uncommon trait of these thermostats. What is the objective of the humidity check? An Integer variable can be set to a value of 1 when the email is sent. A test of the variable value being 0 is Anded with the Humidity check preventing further emails after one is sent. Another Program checks if Humidity is below 58% or above 66% and resets the variable to 0 so that further emails will be sent if humidity returns to 62%. What resets the variable back to 0 depends on the requirement.

There is a File | Restore Modem (PLM) to rebuild the PLM link database. File | Restore Devices will rebuild all the device link databases. Do not put all the battery RF devices into linking mode at once as they will cancel each other out of linking mode. After a Restore is finished, put one battery device into linking mode, right click device node and select Write Updates to Device. As one battery RF device completes move to the next.

That is correct.

There is a known problem, fixed in 4.0.2, where the temp was not being updated in the Admin Console. A Query was necessary to get temp value displayed. Perhaps Query was clicked by accident giving the appearance Group Devices affected the temp display.

That was long past Friday closing. Sometimes one of the UDI folks will jump in mid weekend but I would assume Monday.

scubaguyjohn Yes, the UI should be the same as the ISY Firmware. Either the Java cache was not cleared including the Applications and Applets, something using Java was not closed such as a Browser or the Admin Console itself, or the URL used to invoke the Admin Console (UI) was not updated for 4.0.2

The old ISY is yours to keep. Not suppose to sell it with that upgrade price. Don't think UDI covers the weekend 24/7 unless something was arranged ahead of time. What time and time zone Friday was the request made to shift module(s) to the new UUID ?

Using "If Control" the ISY looks at commands flowing from the device being check. The specific command being checked must be received for the Program to be triggered. Since the On command is the only command that was being checked the Program triggered only when an On command is received. The If is True driving the Then clause. Nothing triggers the Program on any other command when using If Control so the Else clause never executes. The second part of the If which checks for an Off command causes the Program to be triggered when an Off command is received. Because it is coded as 'not Off' the If evaluates to False and drives the Else clause. It does not matter whether the two parts of the If are Anded or Ored together when using only If Control. This is unique to If Control because it triggers the Program only when the specific command is received. If the ISY implemented an And as an And the Program would never trigger as True as there is never a case where two commands exist at that same time. Multiple If Control statements execute as though they are Ored together. The above applies no matter why the motion sensor sends an Off message. The Off can be generated with a Set button press, the Off can be generated after the Timeout expires with the correct set of options in effect.

No. The Program never executes the Else clause. The following change will drive the Else if/when the motion sensor sends an Off. Whether the motion sensor sends an Off depends on the options in use. If Control '11.A5.0E-Sensor' is switched On Or Control '11.A5.0E-Sensor' is not switched Off Then Set Scene 'SS Stairs' On Else Set Scene 'SS Stairs' Off

The ISY received the Motion On message and marked the Sensor On. sam. 03/02/2013 12:42:29 : [iNST-SRX ] 02 50 11.A5.0E 00.00.01 C3 11 01 LTONRR (01) sam. 03/02/2013 12:42:29 : [std-Group ] 11.A5.0E-->Group=1, Max Hops=3, Hops Left=0 sam. 03/02/2013 12:42:29 : [ 11 A5 E 1] DON 1 sam. 03/02/2013 12:42:29 : [ 11 A5 E 1] ST 255

The Smarthome instructions discuss connecting the I/O Linc Sensor to relay contacts provided by the alarm panel. None of the alarm panel information in the previous post is discussing relay contacts provided by the alarm panel. HW1 and HW2 provide a means for connecting external reed switches to the alarm panel. HW1 can be configured to drive an interior siren or provide a signal for various conditions. This is not a relay contact that can control the I/O Linc Sensor. It may be possible to connect HW1 to a small relay which is driven when the alarm panel is configured to turn HW1 On for the various conditions indicated. Would have to measure the voltage provided which may be 12v DC since it can drive an interior siren. That voltage would damage the I/O Linc if connected directly to the I/O Linc Sensor.

"I read there is a way, but that is without using the ISY." That is the way. The ISY does not support setting many configuration options that are set through the thermostat itself.

For sure move to 3.3.10 at a minimum. It sounds like the variable used in the folder condition is an Integer Variable. Integer Variables do not trigger Folders or Programs when the value changes. The Folder Variable has to be a State Variable when it is the only Folder condition. Also note that the Folder going True does not cause the Programs in the Folder to execute. It only allows the Conditions in the Program to trigger the Programs.

That is often a low battery issue. Try a fresh battery.

That means there are two distinct problems as the device responds to each in a different way. Suggest running Tools | Diagnostics | Show Device Links Table for the device that is responding to both a Program initiated Scene and a Controller initiated Scene (button/paddle press). Post the Show results along with the Insteon address of the Controller that turns the device On. Run a Show Device Links Table for the Controller device and post that Show result. Also run Tools | Diagnostics | Event Viewer with LEVEL 3. Run the Program that invokes the Scene that turns the device On and post the event trace along with the PLM Insteon address.

Take a look at this topic viewtopic.php?f=27&t=10076&hilit=auto

Is it reacting to a Scene initiated by an ISY Program/Admin Console or is it reacting to the paddle/button press of another Controller?

That is a 3 conductor cable with pins 1,7,8 used on the RJ45 end.

Direct feedback to SmartLabs/Smarthome is difficult. The Smarthome forum is a user-to-user forum, not meant to be a mechanism for communication with either company. There is an Insteon Gold Line phone number which Smarthome provides for assistance with Insteon products. Changing the basic Query response content is very unlikely. That command response structure has existed since the beginning of Insteon. The impact on all the applications that are written to that structure would make changes for all practical purposes impossible. Also there is no unused space in the Standard ACK structure for additional information. There are folks who have disabled the Query All. If the Insteon Mesh network is otherwise providing accurate device state information throughout the day the Query All is redundant.