shannong

No. They never have been. Neither shows Master status. Both were added to ISY removing existing links. Neither is linked as a controller or responder to anything. I've also tried a restore on the ZTH. The interesting thing is that no commands are sent from the ISY so it seems to focus the problem there vs on the devices.

I found one problem with my program for the SPHs acting odd. The SPCs are still inexplicably sent but SPH 69 works now. Problems with Fan mode persist.

Oops. Guess that was in response to my second post. Also not the case there. I'm going up from SPH 68 to SPH 69. SPH 68 reflected in my variables and on the tstat. When I advance one more up to SPH 69 nothing is sent. When I descend back down to SPH 67 it's finally sent along with some SPCs to the wired tstat (no program entries anywhere for SPC commands).

No. I've tried all values. Nothing is sent for any of them except for the first send of Fan Mode. Also, did you note the popup error when trying to set Fan On from the Admin console?

Pretty sure I have a few more. One of my Heat Set Point program changes doesn't work - only one. Setting to SPH 69 doesn't send ANY command to the wireless tstat although all the others work. Later when I change to SPH67 (and only 67) the current valid SPH is sent and a COOLING Set Point is sent to the wired (no commands should be sent to it , especially cooling) and then immediately afterwards the previously SPH 69 is sent to the wireless as it should have been previously a few changes ago. I've tried going up several more degrees and it's not until I get back down to SPH 67 that it's finally sent. I haven't yet defined any programs to send anything but Heat Set Points and Fan mode. Nothing about cooling has been programmed. EDIT: Found one problem with my program. The SPCs are still sent but SPH 69 works now. Problems with Fan mode persist.

I've been creating some programs to provide control of the HVAC system from the wired (2441TH) and wireless (2441ZTH) Insteon thermostats. I'd like to see the status of and control the fan from the wireless tstat and have that reflected on the wired and vice verse. I think there is an ISY bug with Fan control for the wireless tstat. When I try to change the mode from Fan Auto to Fan On in the ISY Admin Console I get an error "Request Failed" in a popup window. There are no messages sent to the tstat. If I create a program (using Run Then) to send the Fan On or Fan Auto commands to the tstat the ISY doesn't send any commands at all. The Event viewer is totally silent. If I send the Mode Fan command to the tstat from the program, the ISY sends CLIMD 4, CLIMD 1, and then CLIMD 7 in quick succession. The Admin Console which show the state as Fan On. However, that is not reflected on the tstat. Also, any subsequent commands for Fan On, Fan Auto, and Fan Mode commands will not result any commands actually being sent to the tstat and the Fan status in the Admin Console does not change. If I press the Fan button on the tstat itself the Fan Always status lights and the CLIFS 7 is sent to the ISY. If I toggle it back to Fan Auto (no Fan status for the tstat) the CLIFS 8 is sent and the Fan Auto is now reflected in the Admin Console.

I have a 2441ZTH v.0D that is running on an external power supply with ISY 4.1.2 & PLM 2413S v.9B. I've noticed updates are not sent in real time but rather every 60 seconds. Not a big deal but annoying. Not wanting to wait, I queried the tsat to immediately update the current temp to test a program I had just written. The temp did not update. I opened the event viewer and queried it again. I saw all the fields returned except for current temp. I've tried multiple times with no ST value returned. Does the 2441ZTH send temp updates for others with this tstat in ISY? I'd opened a case with Smartlabs but decided to start here since I figured their first response would be "It's probably something wrong with your network or controller". Any thoughts or assistance is appreciated.

If ISY has an "On" status for the device it won't send another "On" to it and when checking it's looking at it's current status database rather than a live query to the device. Therefore, adding your own checks is unnecessary unless required to create a specific logic event. Assuming your time for on is 330pm - 12am. Water Heater Control (On/Off) If From 3:30:00PM To 11:59:00PM (same day) Then Set 'Water Heater Widget' On Else Set 'Water Heater Widget' Off Monitor Unscheduled Use If From 12:00:00AM To 3:29:00PM (same day) And Status 'Water Heater Widget' is On Then Send Notification to 'Default' Else - No Actions - (To add one, press 'Action') Monitor Water Heater During On Schedule If From 3:30:00PM To 11:59:00PM (same day) And Status 'Water Heater Widget' is not On Then Send Notification to 'Default' Else - No Actions - (To add one, press 'Action') The notification will fire every time the water heater is turned off during the On schedule.

I usually use two separate programs and rarely use Else. Only specific finite conditions will fire for Then based on your If's. The else is EVERYTHING else and you might not even be able to consider them all depending on the complexity of the If's. In this particular case, when the module is turned on the If's are evaluated again and now fires the Else. Make it two programs to turn on the module and another to monitor the status. If your network isn't reliable and it's often not getting turned on my might even add a query to run every hour during the appropriate time period and then fire the notification

Nope. Smarthome sells blank keys you can put on keys that don't have a programmed use to help remind.

All connected and working. Heat, AC, and Fan control. The Energy mode hasn't magically turned itself on, yet. It's probably cycled on about 40 times. The surge suppressor is grounded on the same circuit as the furnace and I verified the frame of the furnace is grounded. I'm not sure why I'd add the MOV considering all leads are connected to the surge suppressor which I would assume has an MOV of some flavor.

!!! One more update.... And finally some good news! Earlier I had posted about using a surge suppressor with protected "network" ports to filter out the noise/voltage spikes of the electric igniters on my gas furnace that was causing the Energy mode to turn itself on. It did prevent the Energy mode from coming on but only worked for Heat. For some reason I was unable to turn on Fan or Cool. I tried removing just Cool (Y) and Fan(G) from the suppressor but then the noise was back and tripping the Energy mode again. Considering it a failure, I deleted the post. I was thinking about this method again and thought it strange that Heat would work and not Cool or Fan. They all use the same voltage. I decided to try this workaround with another surge suppressor I have on hand that also has network ports. I connected it the same as before and the Energy mode has not yet turned on after 20 cycles of the Heat. (the most I've gone without Energy mode being enabled is 10 times. Usually it's about one out of 5) And this time I CAN turn on Cool and Fan!!! It seems there was something funky about the way the first suppressor was handling the filtering. Ethernet calls for a 4-pair RJ-45 (8 wires) but in reality only uses 4 of the wires. 1,2,3 and 6. Perhaps it was handling the others differently. Not sure..... The surge suppressor is simply connected inline between the tstat and the furnace using the network ports. I created two pigtails so that one is used to connect the wire in from the tstat to the suppressor and another to go from the suppressor to my furnace control board. I have my ISY monitoring it looking to see if Energy mode is turned on. However, I'm in TX and it's 70F today so there won't be any heat cycles until sometime later tonight when it gets "cold". I'll update if anything changes.

Are you setting nighttime=0 every time you set daytime=1 and vice versa. I only use one variable for this since you'd have to change both each time anyways. daytime=1 means the sun is shining. daytime=0 means the sun is not shining (night time). Should the nightlight turn on only when ALL those lights are off or any one is off? You'll need parentheses for the Or clauses.

The program I posted seems to do what you're asking. What differs in my program than what you're asking?

The pressed button turns on. Of course the OFF button also lights up since the backlights are turned back on. You cannot control the lighting of buttons on the KPL individually. They all must have the same brightness level.

Dude, it would be helpful if you'd be more specific in a single, inclusive request.

Success. If Control '1st Floor / Utility / Devices / Utility-EC-KPL-ExtLights.A' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.B' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.C' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.D' is switched On And ( On Sat From 1:20:00PM To 1:30:00PM (same day) ) Then Set '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.1' On 1 / Off 0 (Backlight Level) Wait 5 seconds Set '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.1' On 0 / Off 0 (Backlight Level) Else - No Actions - (To add one, press 'Action')

I think I'll add this to mine. Turn on briefly and turn back off after 5 seconds. Thanks for the idea!

All lights were Off. 0/0 I pressed "Fan Med" (button and the LEDs turned back on. If you added a wait you could turn them back off again. If Control '1st Floor / Utility / Devices / Utility-EC-KPL-ExtLights.A' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.B' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.C' is switched On Or Control '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.D' is switched On Then Set '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.1' On 1 / Off 0 (Backlight Level) Else - No Actions - (To add one, press 'Action')

So you want the press of a button to turn the backlights back on?

It worked. If On Sat Time is 12:54:00PM Then Set '2nd Floor / Bedroom3 / Devices / Bed3-E-KPL.1' On 0 / Off 0 (Backlight Level) Else - No Actions - (To add one, press 'Action')

Access is easy on both ends. I just made the whole in the wall a little bigger to able to slip a bead inside the wall. I added a single ferrite bead on the tstat side but could only loop the wires through once (thus two passes of the wires) and the problem persisted. I didn't know the ISY had a temp sensor on board.

BTW. Your post wasn't encrypted. Mine is turned off by a program only using a RemoteLinc2 as the trigger. However, it's turned back on in the morning using sunrise. I'll test with a time trigger now.

I run a program that simply sets the KPL LEDs Backlight Level to 0/0. All lights including the OFF button are not lit even though the scenes are active and still usable.

I spent an hour in chat with Smarthome yesterday. They sent a 24VAC power supply to provide external power. Their first wiring instructions were "just connect it to the C & R". I made them be specific about how they wanted it connected so that when the issue wasn't resolved it would show their work around does not work. They wanted me to connect it such that the C and R terminals of the tstat were connected to the power supply only so the noise would be separated. I argued with him for about 15 min explaining that wouldn't work because there would be no return path for the W,G, and Y signals back to the furnace. He specifically said the C could not be connected to the furnace because that would allow the noise back in. That's the only thing we agreed upon. After he sent me a few drawings that weren't legible I finally relented and tried it his way to prove him wrong so we could move on. As you already know it didn't work for the stated reason. I explained to him there needed to be a common/neutral wire to provide a return path. So he now relented and said connect the C from the furnace and the new PS. I asked him which terminal on the PS I should use and he said the "black one". There isn't one and their both just labeled "AC". He didn't initially get that it was important to identify which was the common/neutral vs hot/line. Luckily, I had a multimeter handy to identify it. So I connected it and it of course now worked but again the noise/spikes were back in the system thus no resolution to the Energy mode issue. He then really pissed me off and said I should get an HVAC technician to look at the furnace to see what's wrong with it. I quickly replied it's the tstat allowing noise in and nothing is wrong with the furnace. He also suggested replacing the 2441THs with the Venstar+2441V. I asked him how that would help if the problem is my furnace and not the tstats as he stated. He replied it was just something to try. I suggested the engineering team instead should identify an inline filter that would work. He then suggested then ACT AF300 20amp inline filter. I asked him how he would suggest I wire that in. I didn't get a response. I asked for an RMA on the damn things and he readily agreed. On the forms he put the reason as "Not working as expected". I forced him to change it and he then put "defective firmware or software". I pointed out that also isn't true since they could then fix it with a software update, which of course they can't but I was done with him at that point. I closed with reminding him it's a known issue and complained about by many people and they were unethically making more and selling them with the known issue. I suggested they at least should list compatibility issues if they weren't going to fix it. No reply to that. I'm going to file a complaint with the BBB they're a member of.