larryllix

Working at -20C last week.

I didn't know you could automate apouses, at all. Mine can certainly create a scene though. Alexa! Bring me a beer!

It has been reported many times on this forum that the PLM link report will stop as soon as some data traffic happens. This means that any count with a low count may mean nothing. People pushed the idea of successive tries at the link reporting methods and not putting any value in the actual reports. Try it again, a few more times, in an Insteon quiet house.

Exactly. If they would have forced a temperature update every 60 seconds (300 on batteries) it would act as a heartbeat and a more accurate update for the primary parameter wanted from any stat. SmartiePants doesn't seem too versed in protocols. It's hard to believe they even designed Insteon. I doubt they did, or the mastermind left years ago.

Thanks you for supporting our side! :) You need a vocal input product. Once setup users get familiar with the vocal techniques and start to use them. My wife partially hates HA but she knows it is my hobby and doesn't bark too much but she has learned form my vocals to instruct Alexa to get what she wants mostly.

While I believe the point about the difference in systems was totally missed here, having a system that performs both well, would be nice. I have to agree about HA. To push the example to a ridiculous extreme....If we don't want home automation, why buy a thermostat? Just buy a HVAC switch and turn your HVAC on and off as needed. I've seen a lot of people that use their stats as a switch. One particular trade type comes to mind that should know better, from my experiences. BTW:With smart stats, amazon devices, and Google Home devices, I do NOT operate my stat from any of it. I don't even have the control connected. Stats are automatic and should never need manipulating manually. I am very picky about my comfort. If the temp is too high or too low by 1 degree C, I am sweatng or chilled. OTOH: Many like the HA, they just don't want the challenge of setting it up from scratch, so they substitute convenient manual control methods.

The humidifier companies formerly promoted themselves by claiming you would save money on your heating bill due to making you feel more comfortable at a lower temperature. I talked to a guy years back on Usenet groups that threatened legal action on a big HVAC company, and they stopped advertising that.

The Tag part could be left inside a pocket glued to the outside of the cover and the probe just penetrating the cover to the inside through a small pinhole that should seal behind the insertion. IIRC the probes are just 1-Wire temperature probes that you can buy on ebay for $0.99 usually. easily replaced except for the moulded plug they use.

Somehow this program got deleted and I had to recreate it. This is my latest using NodeLink input from the Ecobee current weather reporting. Sync.Temp.out.average - [ID 00FE][Parent 0101] If $sTag3.temp < 45 Or 'Dining Room / GathRm Stat / Current Weather' Temperature <= 45.0° Or $sWC8.outTemp.raw < 450 Then $TempAvg.sum = 0 $TempAvg.contrib.cnt = 0 // sum inputs within dev.max of past average and keep count // start with sensor 1, if within deviation allowed $TempAvg.deviation = $sWC8.outTemp.raw $TempAvg.deviation /= 10 $TempAvg.deviation -= $sHouse.outTemp Repeat While $TempAvg.deviation < 0 $TempAvg.deviation *= -1 Repeat While $TempAvg.deviation <= $cTEMPAVG.DEV.ALLOWED $TempAvg.sum += $sWC8.outTemp.raw $TempAvg.sum /= 10 $TempAvg.contrib.cnt += 1 $TempAvg.deviation = 999 Repeat 1 times // add in sensor 2, if within deviation allowed $TempAvg.deviation = 'Dining Room / GathRm Stat / Current Weather' Temperature ° $TempAvg.deviation -= $sHouse.outTemp Repeat While $TempAvg.deviation < 0 $TempAvg.deviation *= -1 Repeat While $TempAvg.deviation <= $cTEMPAVG.DEV.ALLOWED $TempAvg.sum += 'Dining Room / GathRm Stat / Current Weather' Temperature ° $TempAvg.contrib.cnt += 1 $TempAvg.deviation = 999 Repeat 1 times // add in sensor 3, if wihin deviation allowed $TempAvg.deviation = $sTag3.temp $TempAvg.deviation -= $sHouse.outTemp Repeat While $TempAvg.deviation < 0 $TempAvg.deviation *= -1 Repeat While $TempAvg.deviation <= $cTEMPAVG.DEV.ALLOWED $TempAvg.sum += $sTag3.temp $TempAvg.contrib.cnt += 1 $TempAvg.deviation = 999 Repeat 1 times // none worked, get all new Repeat While $TempAvg.contrib.cnt is 0 $TempAvg.sum = $sWC8.outTemp.raw $TempAvg.sum /= 10 $TempAvg.sum += $sTag3.temp $TempAvg.sum += 'Dining Room / GathRm Stat / Current Weather' Temperature ° $TempAvg.contrib.cnt = 3 Repeat 1 times // finish calcs with what we got $TempAvg.sum /= $TempAvg.contrib.cnt $sHouse.outTemp = $TempAvg.sum $sHouse.outTemp Init To $TempAvg.sum Else - No Actions - (To add one, press 'Action')

I try to keep my humidity above 36% in the winter. This is almost impossible if my HRV runs more than a few minutes per day in this -15C degree weather. If I have ISY manage it about as tight as I can get I only have to cart less than 3-4 gallons of water per day for my humidifier. When I built my house many people commented if it was vapour sealed as tight as I have it I would never need a central humidifier, (so common here) on my furnace. I made the mistake of listening to them and now do not have enough room around my air-handler to add a humidifier. With an HRV removing new paint and other household fumes for the last ten years, the vapour barrier being enough to keep in humidity is BS. I have co-ordination programs in ISY to maximise the efficiency by running ventilation, humidity and HRV simultaneously. MWaremans logging programs have helped me immensely to debug what I was doing, all inside the ISY spare memory space. These ISY programs have saved ma a lot of heating bill size as well as reduced my water hauling for the humidifier, and maximised home comfort. I use ISY to compensate the thermostat when the outside home chill factor is below a certain temperature factor, by adding in the square of the wind speed times a factor, to the difference between the average temperature outside (three sensors) and the setpoint inside. This adds 0.5C to the stat setpoint temporarily so that cold periods are not felt. My window panes only condense slightly at below -16C. I don't adjust my humidity for my house structure. I have extreme vapour barrier and insulation. The housing inspector told me I didn't need the vapour barrier with 2 inches of foam on the outside, lap sealed. The double vapour barrier worries me somewhat but the wood was well dried and the outside seal isn't sealed on the top plate of the wood construction. Yes. You can drive yourself crazy worrying about all the things you don't know about. Ignorance is bliss usually

Try plugging the LampLinc into the same circuit. You may have new noisemaker in your wiring. Linking takes a lot more data transfer than a simple report an event data length. More chances to fail.

Somewhere in the archives of this forum I reported the reading from my 2441ZTH stat below the freezing point. IIRC the temperature reported down to about -3C (26F) but since the binary values are only for positive interpretation the figures became 250 counts and appeared as +125.0C For you binary mathematicians this is easy for one byte aritmetic (250 - 28 ) / 2 = - 2.5 degrees C. At about -3.0 C the electronics crapped out and just stopped sending Insteon. (It couldn't even cry for help but I may have heard faint whimpers ) Hopefully you will know before that ever happens. You need some better house insulation if you get those gore -b Al ly warmed temperatures He doesn't live in Canada, so it's not a problem here.

Several times I have been away with my tenps set down to 10C and it takes about two weeks to achieve that low temperature in the house, with our typical -10 to -20C outside temperatures. OTOH: I have slab heating in the basement and it leaks somewhat into the ground taking several days to come up to temp for normal heating, so the cool down will be longer also. (large thermal mass) When I was building, I spent a winter with no ceiling drywall, no vapour barrier and no insulation, but only 2" of styrofoam on the outside walls. No hydro or NG yet, and no heating attempted either. My future sump pit (no concrete on the basement floor) froze for one day and then thawed the next day, by itself. Now that is in the ground also.We don't get the sun like you do out west of here so not as much radiant solar.

hmmmm...I didn't know bateries affected the reporting of temperate. Good point. I am probably talking 1.5 degrees C too and that is pretty coarse.

I would be worried that the detection of temperature chnage for a heartbeat, would fail occasionally. You could OR in a humidity change detection as well, Humidity seems to be reported on a timed constant basis on my units. I cut the plug off a 5v adapter and wired it. The batteries are left in as a backup and you should be able to get 5 years out of a set of batteries then. Humidity reports about every 60 seconds on AC but only every 5 minutes on batteries. A simple USB PSU would work for that and commonly available. The 0.5F exception reporting would be awesome. Most report about 1.5F change to report. Have you actually seen this in ISY? The 2441ZTH screen changes do not coincide what the stat reports to ISY , on my older units. This could affect your heartbeat technique.

I find the devices usually cause some problem indicating it is needed about once every few months, only. Sent from my SGH-I257M using Tapatalk

I have to agree with Scott, Here. I prefer my programs and devices simple and let ISY do all the decisions where possible. Things that flip back and forth complicate this a lot and can cost many hours later when things fail. Let the KPL buttons not toggle and trigger a program with a Wait 1 seconds in it that turns on a scene to light the LED, avoiding Insteon traffic congestion. The LED scene can also be tied to the KPL button (I think) for a faster response for the human eye.

After my father died my mother didn't bother to maintain the humidifier on her furnace. Her 30 year old maple buffet side panel spilt from top to bottom with an 1/8" gap. Her dining room table with full 1" maple top split almost down the middle from end to end with about a 3/8" gap. I could put a screwdriver blade down through it to the handle. In the summer, the gap closed completely and then she sanded the top down, and refinished it with new stain and urethane finish. The next winter the gap split again to the same 3/8" gap. Looking at the construction, they glued and screwed the top planks to another piece of hard maple, crosswise to the top lamination planks. That's a woodworking no-no. They should have had slide slots for screw fastening, or used a metal undersupport that doesn't swell or contract. Lasted 30 years though. Without humidity added our homes here will drop to about 10-15% RH, especially if not lived in, with breathing, sweating, showers, and cooking moisture

allows turning off updates. Careful with this. I have MSes that are not capable of using delayed update writes, and my system ground to a halt sometimes when an MS would see motion. ISY was trying to use my auto-update programs to update a device, ad nauseum, and Insteon comms were tied up for 20-30 seconds at a time, before other any other traffic could go through. The busy box was almost always present in the admin console.

Welcome to the forums!!! No lists but... Right click on a device in the device tree page using admin console. Select view device link table. Then click compare once it is done. You will see a line with all 0s. Battery devices have to be put into linking mode first.

I always use this vocal syntax. "Alexa. Turn On XXXX <to 50%>" <...> optional "Alexa. Turn Off XXXX"

Have you just tried to insert a Wait 2 seconds between each scene in the list? You may have created an Insteon data storm with some new device, or some change in system, or a failing PLM etc.. It would be worth a try. Insteon is the weak link in the ISY system most of the time. Also, I should mention the delayed write to Battery operated devices can cause big problems. I have MSes that cannot handle it, and everytime an MS saw motion, ISY would operate my delayed update programs to write to devices, that couldn't handle it. They would never ACK. It seemed like my ISY write caches were laden full, and bogging my whole Insteon system down with every motion sensed. About ten minutes of clearing these caches with my MSes, deleting the update programs, and turning that nonsense off worked wonders. Now I can put an MS into linking mode, write an option change and it finishes in 30 seconds instead of ten minutes. Now my constant Busy Box in admin console actually goes away.

I used all 5/8" thick baseboard (Alexandria Moldings @ HD) but trying to buy a few more lengths recently, it has become really expensive at about $5 / foot for the pressed cardboard stuff. This is when you start cutting lengths in the store and leaving the waste 1' pieces there.

Either is most kleenex! "2 x 4" has become a trade name for a product. The patent ran out! I would be sure you worked with some real 2x4s in your day. Always fun to drill through 2 or 3 of them laminated. WoW!

Since this got lost... This comes back to the OP. Why do you need to run a wire for Insteon? EDIT: Ohh re-reading the OP this is a cable with two conductors.