larryllix

$cTrue and $cFalse are constants equating and initialised to 1 and 0 respectively. I use many Integer variables as constants to make programs more self-documenting. I have requested this feature of UDI by simply adding another tab to the variable typecasting. Hopefully it will show up in v5. User definable tabs would be even better to organise the long list of variables we end up using for our moments of creation. I use them for room definitions in many programs to pass variables and of course True and False prefixed in the usual ISY style using the "$c" prefix.

Interesting that when you cross the times the whole program "If" doesn't get evaluated either way (true or false) even if other logic is injected. I tried various additional logic that should have tested true and false but no operations were experienced. Here is my test program. No lights ever operated. Test times - [ID 005B][Parent 0001] If From 9:35:00PM To 9:27:00PM (same day) Or $cTRUE is $cTRUE Then Set 'Gathering Room / Floor Lamp' Fast Off Wait 1 second Set 'Gathering Room / Floor Lamp' Fast On Else Set 'Gathering Room / PotLight over Desk' Fast Off Wait 1 second Set 'Gathering Room / PotLight over Desk' Fast On

Has anybody tried these bulbs? I am not sure where they are in the real world yet. http://www.digitaltrends.com/home/crees-smart-light-bulb-costs-15/ A question has risen in another forum about whether the bulb turns on with power up. The Hue bulbs are reported to do this: 100% white On. Another question I have is would the Hue bridge operate these bulbs if they are both Zigbee?

I found I had to tap the linking button one more time, sending an Off command from the MS, before it would actually respond to motion and send the "On". Then it worked fine. I have 7 of theses units now and they all seem to do this. IIRC this is stated somewhere in a PDF file but I cannot find it. As you stated, I would think they would time-out and return to "running" mode if left alone in this state, also. I haven't tried that but I am usually in a hurry to test them before hanging them back on the wall. Edit: This phenomenon may just be that the device's page already shows it On and with the Off send disabled no "On" signal can be detected on the ISY MS device page, where I am viewing testing results. Further testing will be in order, next time.

Try sliding a few small steel hex nuts over the W1 wire to give some impedance to high frequency voltage spikes.

Query will update ISY parameters like setpoints, mode, fan control but not temperature. Once the temp updates it stays in sync. I have had occasional blanks when I took one unit below 3 degrees C. There have been a few other times but I believe it was after an ISY upgrade etc..

Thanks stu but... Maybe I didn't ask my question correctly. What do the wireless units, connected into the wired unit, do or control? Can the ISY see their temps?, control outputs? Does the wired thermostat use the wireless data somehow? I understand the 2441ZTH units act as zone sensors and controllers but how can the wired unit control multiple zones? I do not have one. Does it have multiple contact outputs?

Curious: How does the control flow from the wireless units work? How do they show up in ISY or control (assuming) zones hen they are signal hooked to the 2441TH (wired) unit only?

Nope. The 2441ZTH was never listed as supported and thus maybe some of the source of the complaints that it was never implemented properly. It may have been thought to be the same interface/unit as the 2441TH (wired) perhaps causing many of the control features not to work. The 2441ZTH controls are not that important to operation as the thermostat has no outputs to be controlled anyway, only Insteon communications of temperature and humidity to the ISY. Many do not understand the concept of "report by exception" used by the thermostat (by design) and many other SCADA systems to report critical data. Because it doesn't report on a timed cycle basis many think it is defective or not-functioning. The humidity update functions as a heartbeat to ISY for the thermostat, just fine. "Report by exception" requires a value to violate the rules sets to report. ie:(A temperature change) AND (the change is outside of the change allowance) The "Report by exception" usually includes a timed "all-else-fails" update (say.. once per hour?) serving as a "heartbeat" by most systems. The 2441ZTH doesn't have one. That is a psychological problem for some, seeing a blank reading, upon ISY reboots, until the temperature changes. ISY could mask this but is being kept honest for users. I have two versions of firmware in my 2441ZTH thermostats and both work just fine with the ISY. It knows what they are, but different (unneeded to function) controls on each do not work.

The thermostat has a humidity node that sends it's data to the ISY CCell Humidity Control - [ID 005A][Parent 00B5] If Status 'Cold Cellar / CCell Therm' > 70% (Humidity) And Status 'Cold Cellar / CCell Therm' > 10° (Temperature) Then Repeat Every 8 hours Set 'Spare OnOff Module' On Wait 4 hours Set 'Spare OnOff Module' Off Else - No Actions - (To add one, press 'Action')

Update: This 2441ZTH stopped sending updates at -3.5 degrees C but has most likely reached the actual temperature of my garage where it is temporarily sitting. Since this device reports temperature by exception and not on a timed basis this is functioning correctly still. The thermostat screen reads "EE" and ISY shows this as 124.5 degrees which is, apparently, a misrepresentation of the signed 8 bit value, although correct by specification definition as an unsigned 8 bit value. Accuracy? Close but I have no comparison in the vicinity. The Humidity is still updating on a timed cycle basis every 60 seconds so the 2441ZTH electronics are still functioning at this temperature. Update: The unit appears to have stopped sending temperature and humidity updates at this temperature. I returned the unit to a heated room and it immediately resumed updates of both values.

I switched the 2441ZTH thermostat over to Celsius and watched it go below 0 degrees C this time. I thought maybe ISY was converting the Farenheit to Celsius but No the communication bits changed to C x 2 also. The display on the 2441ZTH reads "EE" at about 1-3 C but the reporting still functions, so far. ISY is not geared to interpret this reading as a signed 8 bit value even though it would work somewhat. It hasn't stopped reporting yet. Currently ISY shows the signed value as unsigned so that 254 counts displays as 127 degree C instead of -1 degrees C Wed 01/14/2015 08:30:14 PM : [VAR 2 6 ] 114203045 Wed 01/14/2015 08:30:15 PM : [ Time] 20:30:47 0(0) Wed 01/14/2015 08:30:28 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6F 31 (31) Wed 01/14/2015 08:30:28 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:30:28 PM : [D2D EVENT ] Event [22 F 53 1] [CLIHUM] [49] uom=0 prec=-1 Wed 01/14/2015 08:30:28 PM : [ 22 F 53 1] CLIHUM 49 Wed 01/14/2015 08:30:28 PM : [D2D-CMP 001C] STS [22 F 53 1] CLIHUM op=2 Event(val=49 uom=0 prec=-1) < Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:30:29 PM : [VAR 2 6 ] 114203100 Wed 01/14/2015 08:30:30 PM : [ Time] 20:31:02 0(0) Wed 01/14/2015 08:30:33 PM : [VAR 2 12 ] 210 Wed 01/14/2015 08:30:43 PM : [VAR 2 6 ] 114203115 Wed 01/14/2015 08:30:44 PM : [ Time] 20:31:17 0(0) Wed 01/14/2015 08:30:47 PM : [VAR 2 12 ] 213 Wed 01/14/2015 08:30:58 PM : [VAR 2 6 ] 114203130 Wed 01/14/2015 08:30:59 PM : [ Time] 20:31:32 0(0) Wed 01/14/2015 08:31:02 PM : [VAR 2 12 ] 216 Wed 01/14/2015 08:31:13 PM : [VAR 2 6 ] 114203145 Wed 01/14/2015 08:31:14 PM : [ Time] 20:31:47 0(0) Wed 01/14/2015 08:31:28 PM : [VAR 2 6 ] 114203200 Wed 01/14/2015 08:31:29 PM : [ Time] 20:32:02 0(0) Wed 01/14/2015 08:31:43 PM : [VAR 2 6 ] 114203215 Wed 01/14/2015 08:31:44 PM : [ Time] 20:32:17 0(0) Wed 01/14/2015 08:31:46 PM : [VAR 2 12 ] 213 Wed 01/14/2015 08:31:57 PM : [VAR 2 6 ] 114203230 Wed 01/14/2015 08:31:58 PM : [ Time] 20:32:32 0(0) Wed 01/14/2015 08:32:12 PM : [VAR 2 6 ] 114203245 Wed 01/14/2015 08:32:13 PM : [ Time] 20:32:47 0(0) Wed 01/14/2015 08:32:16 PM : [VAR 2 12 ] 208 Wed 01/14/2015 08:32:20 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6F 32 (32) Wed 01/14/2015 08:32:20 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:32:20 PM : [D2D EVENT ] Event [22 F 53 1] [CLIHUM] [50] uom=0 prec=-1 Wed 01/14/2015 08:32:20 PM : [ 22 F 53 1] CLIHUM 50 Wed 01/14/2015 08:32:20 PM : [D2D-CMP 001C] STS [22 F 53 1] CLIHUM op=2 Event(val=50 uom=0 prec=-1) < Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:32:27 PM : [VAR 2 6 ] 114203300 Wed 01/14/2015 08:32:28 PM : [ Time] 20:33:02 0(0) Wed 01/14/2015 08:32:31 PM : [VAR 2 12 ] 203 Wed 01/14/2015 08:32:42 PM : [VAR 2 6 ] 114203315 Wed 01/14/2015 08:32:43 PM : [ Time] 20:33:17 0(0) Wed 01/14/2015 08:32:56 PM : [VAR 2 6 ] 114203330 Wed 01/14/2015 08:32:57 PM : [ Time] 20:33:32 0(0) Wed 01/14/2015 08:33:11 PM : [VAR 2 6 ] 114203345 Wed 01/14/2015 08:33:12 PM : [ Time] 20:33:47 0(0) Wed 01/14/2015 08:33:21 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6E 3E (3E) Wed 01/14/2015 08:33:21 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:33:21 PM : [D2D EVENT ] Event [22 F 53 1] [ST] [62] uom=0 prec=-1 Wed 01/14/2015 08:33:21 PM : [ 22 F 53 1] ST 62 Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B1] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=180 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B0] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=170 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AF] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=160 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AE] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=156 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AD] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=152 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AC] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=148 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AB] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=146 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AA] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=144 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A9] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=142 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A8] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=140 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A7] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=138 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A6] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=136 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A5] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=130 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A4] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=126 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A3] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=120 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 009F] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=110 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 006C] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=100 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0064] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=90 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 005B] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=80 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B2] STS [22 F 53 1] ST op=2 Event(val=62 uom=0 prec=-1) < Condition(val=244 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 005A] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=70 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0058] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0055] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=50 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0002] STS [22 F 53 1] ST op=5 Event(val=62 uom=0 prec=-1) >= Condition(val=198 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0026] STS [22 F 53 1] ST op=4 Event(val=62 uom=0 prec=-1) <= Condition(val=76 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:26 PM : [VAR 2 6 ] 114203400 Wed 01/14/2015 08:33:27 PM : [ Time] 20:34:02 0(0) Wed 01/14/2015 08:33:41 PM : [VAR 2 6 ] 114203415 Wed 01/14/2015 08:33:42 PM : [ Time] 20:34:17 0(0) Wed 01/14/2015 08:33:45 PM : [VAR 2 12 ] 207

I forgot about the digital range in this. As a point of interest here is an event recording of a 2441ZTH passing through freezing but unfortunately is sending out F bits so positive readings are maintained in this case. Wed 01/14/2015 08:30:14 PM : [VAR 2 6 ] 114203045 Wed 01/14/2015 08:30:15 PM : [ Time] 20:30:47 0(0) Wed 01/14/2015 08:30:28 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6F 31 (31) Wed 01/14/2015 08:30:28 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:30:28 PM : [D2D EVENT ] Event [22 F 53 1] [CLIHUM] [49] uom=0 prec=-1 Wed 01/14/2015 08:30:28 PM : [ 22 F 53 1] CLIHUM 49 Wed 01/14/2015 08:30:28 PM : [D2D-CMP 001C] STS [22 F 53 1] CLIHUM op=2 Event(val=49 uom=0 prec=-1) < Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:30:29 PM : [VAR 2 6 ] 114203100 Wed 01/14/2015 08:30:30 PM : [ Time] 20:31:02 0(0) Wed 01/14/2015 08:30:33 PM : [VAR 2 12 ] 210 Wed 01/14/2015 08:30:43 PM : [VAR 2 6 ] 114203115 Wed 01/14/2015 08:30:44 PM : [ Time] 20:31:17 0(0) Wed 01/14/2015 08:30:47 PM : [VAR 2 12 ] 213 Wed 01/14/2015 08:30:58 PM : [VAR 2 6 ] 114203130 Wed 01/14/2015 08:30:59 PM : [ Time] 20:31:32 0(0) Wed 01/14/2015 08:31:02 PM : [VAR 2 12 ] 216 Wed 01/14/2015 08:31:13 PM : [VAR 2 6 ] 114203145 Wed 01/14/2015 08:31:14 PM : [ Time] 20:31:47 0(0) Wed 01/14/2015 08:31:28 PM : [VAR 2 6 ] 114203200 Wed 01/14/2015 08:31:29 PM : [ Time] 20:32:02 0(0) Wed 01/14/2015 08:31:43 PM : [VAR 2 6 ] 114203215 Wed 01/14/2015 08:31:44 PM : [ Time] 20:32:17 0(0) Wed 01/14/2015 08:31:46 PM : [VAR 2 12 ] 213 Wed 01/14/2015 08:31:57 PM : [VAR 2 6 ] 114203230 Wed 01/14/2015 08:31:58 PM : [ Time] 20:32:32 0(0) Wed 01/14/2015 08:32:12 PM : [VAR 2 6 ] 114203245 Wed 01/14/2015 08:32:13 PM : [ Time] 20:32:47 0(0) Wed 01/14/2015 08:32:16 PM : [VAR 2 12 ] 208 Wed 01/14/2015 08:32:20 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6F 32 (32) Wed 01/14/2015 08:32:20 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:32:20 PM : [D2D EVENT ] Event [22 F 53 1] [CLIHUM] [50] uom=0 prec=-1 Wed 01/14/2015 08:32:20 PM : [ 22 F 53 1] CLIHUM 50 Wed 01/14/2015 08:32:20 PM : [D2D-CMP 001C] STS [22 F 53 1] CLIHUM op=2 Event(val=50 uom=0 prec=-1) < Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:32:27 PM : [VAR 2 6 ] 114203300 Wed 01/14/2015 08:32:28 PM : [ Time] 20:33:02 0(0) Wed 01/14/2015 08:32:31 PM : [VAR 2 12 ] 203 Wed 01/14/2015 08:32:42 PM : [VAR 2 6 ] 114203315 Wed 01/14/2015 08:32:43 PM : [ Time] 20:33:17 0(0) Wed 01/14/2015 08:32:56 PM : [VAR 2 6 ] 114203330 Wed 01/14/2015 08:32:57 PM : [ Time] 20:33:32 0(0) Wed 01/14/2015 08:33:11 PM : [VAR 2 6 ] 114203345 Wed 01/14/2015 08:33:12 PM : [ Time] 20:33:47 0(0) Wed 01/14/2015 08:33:21 PM : [INST-SRX ] 02 50 22.0F.53 2A.1C.95 01 6E 3E (3E) Wed 01/14/2015 08:33:21 PM : [Std-Direct ] 22.0F.53-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 01/14/2015 08:33:21 PM : [D2D EVENT ] Event [22 F 53 1] [ST] [62] uom=0 prec=-1 Wed 01/14/2015 08:33:21 PM : [ 22 F 53 1] ST 62 Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B1] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=180 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B0] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=170 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AF] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=160 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AE] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=156 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AD] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=152 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AC] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=148 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AB] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=146 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00AA] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=144 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A9] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=142 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A8] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=140 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A7] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=138 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A6] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=136 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A5] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=130 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A4] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=126 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00A3] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=120 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 009F] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=110 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 006C] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=100 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0064] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=90 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 005B] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=80 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 00B2] STS [22 F 53 1] ST op=2 Event(val=62 uom=0 prec=-1) < Condition(val=244 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 005A] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=70 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0058] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=60 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0055] STS [22 F 53 1] ST op=3 Event(val=62 uom=0 prec=-1) > Condition(val=50 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0002] STS [22 F 53 1] ST op=5 Event(val=62 uom=0 prec=-1) >= Condition(val=198 uom=0 prec=-1) --> false Wed 01/14/2015 08:33:21 PM : [D2D-CMP 0026] STS [22 F 53 1] ST op=4 Event(val=62 uom=0 prec=-1) <= Condition(val=76 uom=0 prec=-1) --> true Wed 01/14/2015 08:33:26 PM : [VAR 2 6 ] 114203400 Wed 01/14/2015 08:33:27 PM : [ Time] 20:34:02 0(0) Wed 01/14/2015 08:33:41 PM : [VAR 2 6 ] 114203415 Wed 01/14/2015 08:33:42 PM : [ Time] 20:34:17 0(0) Wed 01/14/2015 08:33:45 PM : [VAR 2 12 ] 207

Perhaps you could attempt to re-download the firmware package and star again. Before or after that you should contact UDI for inside help.

This may be the cheapest and simplest option if you can solder and you only need one sensor an area and the 2441ZTH is kept in a heated area. You would want a 5v adapter to run it from AC as the thermostat sends updates more appropriately when not on batteries. This will take stripping a 5v adapter cable and connecting the fine wires to terminals as well as the probe extension but the upside is you have battery backup built in.

There are repair tips for the PLM posted here, if you can fine solder.

I use two 2441ZTH units to monitor only. I don't attempt to control them with ISY as they don't seem to be supported properly and I did have my out building unit act strangely about 3 degrees C. Now I have switched to a CAI WC8 board with probes indoors and outdoors. It works well for this but has a long learning curve, lots of fiddling and it never worked properly with the humidity sensor. There are much more ready-to-go solution boxes out there for the cheap 1-wire temperature sensors.

While agree with the sentiment, isn't predicting that a bit like predicting the weather? I think the Zwave took more resources than expected. Let's kick those Insteon strayers. (sarc)

Here are the two that are triggered by this heartbeat. $CAI1_MMDDhhmmss is a state variable and gets stuffed by the CAI WC8 board every 15 seconds. I have watched the program status, sorted by "Last Run" and it seems to be at the top mostly. CAI Heartbeat.fail - [ID 00B4][Parent 003A] If $CAI1_MMDDhhmmss < 101000000 Then $CAI_Readings_Current = $cFALSE Wait 2 minutes Set 'Workshop / Shop Webcontrol Board' Off Wait 20 seconds Set 'Workshop / Shop Webcontrol Board' On Else $CAI_Readings_Current = $cTRUE Wait 1 minute Run Program 'CAI Heartbeat.fail' (Then Path) CAI Date - [ID 00B9][Parent 003A] If $CAI1_MMDDhhmmss > 0 And $ISY_Initialised is $cTRUE Then $CAI1_MMDDhhmmss Init To $CAI1_MMDDhhmmss $CAI_Time.Last_Known = $CAI1_MMDDhhmmss $CAI_Time.Last_Known Init To $CAI_Time.Last_Known Wait 1 second Run Program 'CAI Date' (Else Path) Else - No Actions - (To add one, press 'Action')

Yes I have a few heartbeat checkers but on different variables, not that same one.

Here is my addition to Xathros' technique to lock the light on. Notes: - the Wait 2 hours will time off the routine in case you forget the light is not on a timer anymore. Adjust time or remove the line as you see fit. - I like to directly control the lamp so that I get instant on but slow ramping when I turn it off set in the device control page. MBR Lamp.manual - [ID 0038][Parent 000A] If Control 'Master Bedroom / MBR KeyPad.A' is switched On And Control 'Master Bedroom / MBR KeyPad.A' is not switched Off Then Set 'Master Bedroom / MBR Wall Lamp' Fast On Disable Program 'MBR Lamp.auto' Disable Program 'MBR Lamp Level adjust' In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 100% (On Level) Wait 2 hours Run Program 'MBR Lamp.manual' (Else Path) Else Set 'Master Bedroom / MBR Wall Lamp' Off Run Program 'MBR Lamp Level adjust' (If) Wait 1 second Enable Program 'MBR Lamp Level adjust' Enable Program 'MBR Lamp.auto' Lamp will get direct hit by MS so adjusted scene level. This is the lighting level adjust program complete with it's subroutine to accomplish three levels. MBR Lamp Level adjust - [ID 0084][Parent 000A] If From 11:30:00PM To 9:30:00AM (next day) Then In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 15% (On Level) Else In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 70% (On Level) Edit: Second level.adjust program removed. It didn't work properly.

I use MobiLincPro v2.02 for Android. I do not have any Apple devices. No folders in favourites. Folders do show in devices but too much hassle drilling down.

I follow Paul's style with rooms for programs and devices. One caveat though. Mobilinc doesn't show folders and only end devices so I break my usual room prefix style with device prefixes by using labels such as MS.GathRm, MS.MBR, Dark.Libr, Dark.LLand so that MobiLinc shows all the MS units together without room folder prefixes whereas Admin Console shows them by room folder prefixes such as Master Bedroom/MS.MBR, Gathering Room/Dark.GathRm Common items like general mult-use subroutines and time keeping gets their own folders like they were another room in the house.

Can somebody get over to the cocoontech.com forum and put ISY on the map? They have a "select your best match HA system" engine link right in the header for the forum. ISY isn't even listed there and should be. We need to win this one or at least be in the running. I don't know enough about ISY's side features to do this without guessing too much. ISY needs to be represented there. There is already too much negative discussion about Insteon in that forum by people that totally live in the HA gadget world with many followers. http://cocoontech.com/forums/page/home-automation-software Thanks!

I have this busy box on my Admin Console every time my WebControl sends it's heartbeat /current date and time. This is sent via the REST interface and is comprised of a single 32 bit value every 15 seconds. It appears to pause ISY processing and may be the cause of some severe program response delays I get occasionally.