LeeG

Does the button link twice when pressed when in non-toggle Off mode? Button D does not have to be in any of the other Scenes. In non-toggle mode Off button D will never be On more than the two blinks when a non-toggle mode button is pressed so it is not necessary for the other Scenes to interact with button D. If the button does not blink twice and stay Off, what is KeypadLinc firmware and what is the ISY firmware.

jmed999 Take a look at the last few posts of this topic. This user had a v.0D thermostat not reporting. It was resolved by installing a new Dual Band device. Now the v.0D firmware is reporting. viewtopic.php?f=27&t=10822&start=15

whywork Thanks very much for taking the time to post back the results. Glad to hear it is working. It may help another user who has two 2441ZTH thermostats at v.0D firmware which are not reporting. With your v.0D working that would tend to eliminate the thermostat firmware.

The only technical matter is that a Wait (and Repeat) allows the If section to be reevaluated if the conditions in the If section have changed before or during the Wait. This can prevent statements following the Wait not to be executed. This can have advantages as a new Wait interval is established. For example, a Program is triggered each time Motion is sensed with a Wait and Off of some responder when the Wait expires. Each new motion sensed triggers the Program and establishes a new Wait time. Only when the Wait time expires with no motion do the statements after the Wait execute. This can also work against the logic of the Program where the reevaluation during a Wait prevents statements after the Wait from executing. In this case a simple solution is to move the Then logic into a second Program with an empty If. That way the Wait does not cause a reevaluation. Just depends on what the Program is trying to accomplish. I tend to put related logic together in the same Program but this is personal choice.

Sure. A button on a KeypadLinc positioned at the main door, a RemoteLinc Mini (RemoteLinc2) button can trigger a Program to set a Variable. Button On can set the Variable to 1 for example to indicate Away, turning the button Off sets the Variable to 0 to indicate Home. Program(s) can be established to do different things based on whether the Variable is 1 or 0.

You want to turn button D On (to turn Fan Motor Off) and have button D LEDs Off? That is not possible for a button in Toggle mode. It would not allow the user to know if a button press will be sending an On command or an Off command. If you want button D LEDs Off after pressing the button, set button D to non-toggle Off mode.

timster Did you use Buttons Grouping (Mutually Exclusive/Radio buttons) or set the Responder On Level to 0% to turn the LEDs Off. The later is the technique that should be used. Buttons Grouping should not be used.

The Membership area for each node reflects the ISY Scene(s) that have been created where that node participates. The Membership area is from that nodes perspective. The same information is available further down My Lighting where the ISY Scenes are listed. This area is from the Scene perspective. You do not create ISY Scenes for the purpose of showing in the Membership area. ISY Scenes are defined for the function they provide. The ISY Scene information is displayed in two locations. At the bottom of the My Lighting tree which is from the Scene perspective and in the Membership area for each node which is Scene information from that nodes perspective. Perhaps if you describe what you want to see in the Membership the location of that information can be provided.

Could be. Do other RF devices report state changes correctly from the same physical location as the tstats.

I have no next.

On newest 6 button KPLs setting the OFF button to non-toggle Off mode would cause the OFF button LEDs to turn Off completely. I tried it on a v.36 button KPL and it did not work using the ISY. There is a backlight issue at 4.0.5. Not sure if that would affect setting non-toggle mode on older KPLs. There is a manual method for setting the OFF button to non-toggle OFF mode. I think it is in the KPL User Guide. If not the manual procedure is described on the Smarthome forum.

That is correct, it is running v.0B firmware. The comment about getting set point changes was more related to it being run by battery than what firmware is running. Regarding being in Off mode when adding a tstat, I have not had any problems adding a tstat when not in Off mode but all the instructions posted by UDI state the tstat should be in Off mode when adding to the ISY. Put the tstat in either Heat or Cool mode and see if set point change messages are sent. There are some things that cannot be changed from the ISY to the tstat when in Auto mode. Not sure about restrictions the other way.

The tstat should have been Off when adding to the ISY. My error in not including that in the instructions. What mode is the tstat operating in, Heat, Cool? I've had mine on batteries only for all my tests and the trace messages I’ve posted. Currently the tstat is set for Heat mode. Although not instantaneously when I press the Up/Down buttons to move the set point I do eventually get a message from the tstat that the set point has been changed.

I do not see anything wrong in the trace. The link records created in the tstat match my 2441ZTH. The only difference I see is I have v.0B and this tstat has v.0D firmware.

Run Tools | Diagnostics | Event Viewer at LEVEL 3 so a full trace of commands issued with results are available. I added my 2441ZTH the same way I add every device (with minor exceptions for special devices). Select New INSTEON Device. Enter Insteon Address and Name of choice, leave Device Type set for Auto Discover. Put the tstat into linking mode with tstat Set button. Click Ok on New INSTEON Device. When the device add is complete Save the event trace for analysis. It is an I2CS device so link record creation is a single command rather than a long series of 1 byte commands.

If the link records check out in both the tstat and the PLM I cannot think of anything more to check.

If 543 is accurate the PLM is not full. The link records for the new tstats will be at the end of the Show PLM Links Table display. Visually verify there are Responder (starts with A2 and have tstat Insteon address) link records present. Do a Show Device Links Table for the tstat you have been testing with. Click Compare when the display is complete. Are the required link records in the tstat. I have no reason to think the link records are not in the tstat and not in the PLM with a count of 543 but running out of things that would explain the lack of messages from the tstat.

The PLM has lost it link database. A Restore Modem (PLM) should bring it back. When I did this post I see the 0 count part of the last post has been deleted?

The Admin Console has been eliminated as it can report only information it receives. With the tstat not reporting the information the UI cannot display it. The Cool set point was changed. Is the tstat is Cool mode? I would try and get objective information as to the number of link records in the PLM. Show PLM Links Table followed by Count. The Show / Count has to be done 3-4 times to insure the Count number is consistent as any Insteon activity reaching the PLM during the Show will produce a false link record count. It can be difficult to get a good Show PLM Links Table count in some installations. The alternative would be a Restore Modem (PLM) to compress out duplicates and rebuild the PLM link database. The PLM may be full such that the Responder link record needed in the PLM to receive messages from the tstats could not be written because the link table is full.

The event trace shows the set point change was successful. With Hops Left=2 comm with this tstat is good. Fri 06/07/2013 11:21:24 AM : [std-Direct Ack] 22.0D.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/07/2013 11:21:24 AM : [ 22 D 93 1] CLISPC 6 The following messages are examples of humidity (6F) and temp (6E) information being sent from tstat to PLM. I was discussing these messages. Do the tstats report humidity and temp? Fri 06/07/2013 11:23:38 AM : [iNST-SRX ] 02 50 1F.0F.B4 22.80.0B 01 6F 28 (28) Fri 06/07/2013 11:23:38 AM : [std-Direct ] 1F.0F.B4-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 11:23:38 AM : [ 1F F B4 1] CLIHUM 40 Fri 06/07/2013 11:23:39 AM : [iNST-SRX ] 02 50 1F.0F.B4 22.80.0B 01 6E 37 (37) Fri 06/07/2013 11:23:39 AM : [std-Direct ] 1F.0F.B4-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 06/07/2013 11:23:39 AM : [ 1F F B4 1] ST 55

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Do either thermostat report temp changes? If temp change messages are not being received the Admin Console would not show them. If temp change messages are being received the message structure can be analyzed to see why the ISY does not use the information.

The Program Status would become True when a C9/On is received. I'm not clear on the logic of all of this. I was pointing out that a Program True/False Status does not change as a result of the Stop Program statement. There is nothing in the original posted code snippets that would make " Program 'Use Hot Tub - On' " False.

That is correct. A node that has been assigned to an ISY Scene should indicate the Scene in the Membership area.

There is no statement Set Program 'xxx' = False I was suggesting using Stop Program ‘xxxxx’ Run Program 'xxxxx' (Else Path) The Run Program Else will change the Program Status from True to False. One of the posted examples is checking for If Program 'xxxxx' is False. For a Program to have a False Status either the If has had to evaluate to False which will run the Else clause or the Else clause has to be explicitly run.

Refer to the device User Guide (link to from Smarthome sales page) for how to Factory Reset the device. Usually pulling the air gap switch for say 60 seconds for the device power supply to bleed off. Then pressing the air gap switch all the way in past the frame level for maybe 10 seconds. It varies by device so using the device User Guide is recommended for the exact process. A Restore Device is a simple right click on the device primary node, select Restore Device.