larryllix

I do not detect anything outside. I use 11 Insteon MSes inside.

@beninsteon If 'Neighbourhood' Occupied is True And From Sunset To Sunrise (next day) ISY doesn't poll Insteon devices. They report in when their status changes. These conditions will auto-trigger if the program and folder is enabled. Then will run at sunset and if Neighbourhood Occupied is True. Then will run if Neighbourhood Occupied just became true and from sunset to sunrise Else will run if Neighbourhood Occupied just became true during the day time. Else will run at sunset if Neighbourhood Occupied is False Else will run at sunrise, no matter what Neighbourhood Occupied is doing Else will run if Neighbourhood Occupied just became false no matter what time it is. Clear as mud?

Insteon devices have many settings. There is a unrelated on level and ramp rate for each link/scene, local control, and ISY program control. What you set in scenes does not affect the manual on from ISY or the manual on via the switch paddle.

What iR devices do you have that support "On level" or "Ramping speed"?

Scenes can be activated by programs inside ISY or without any ISY functions by including a device in the scene as an initiator/controller? (I never remember what ISY calls it) when you include it into the scene.

First, all Insteon devices should be factory reset before linking them to your ISY. They can come with all kinds of weird things inside them. ISY admin console has a button in the top menu that creates a scene. This will appear in the device list page as another device. To add devices to the scene just mouse drag and drop the devices into the scene icon. You will be asked if you want them to be responders. All should be responders except one, if wanted . ISY will then write the links automatically to all devices involved. Battery devices need to be in linking mode first. ISY will then keep track of your scenes, can repair them with a simple mouse click etc... Once created the secene devices can be modified for different ramp rates and levels in the admin console. It's a great Scene manager, making it much easier. Your iRLink is likely full of half links going to the old SwitchLinc and needs to be factory reset to clean them out first.

Canadian source if convenient. https://www.aartech.ca/isy994-zwave-plus-upgrade-module

Did you build the Insteon Scene connection using the ISY as the scene manager? ISY doesn't know statuses unless the devices tell them. Insteon devices do not send out status changes from scenes IIRC. If so remove the scene from both units and/or factory reset them, restore them from ISY and then use ISY to build the scenes so ISY knows what you are doing or use programs to pass the information.

Insteon devices can do this quite well with their ramping. Other devices do not do it well. The look of the sequence is important though, and can be annoying looking if some care is not teken with the appearance, for sure. I only see two complete cures. Amazing protocol speed and delay all responses for a synchronised effect signal. Sonos, chromecasting, and other synchronised audio systems must be using this method.

I try to set my ramp rates to different speeds to match and the differences are not that visible.

It isn't the power supply. The 6A 12V PSU feeds multiple strips just fine in a radial configuration, but the tiny conductors in the strips have too much voltage drop to feed a sequential 5m of strip. I was thinking of beefing up the power supply trace with an external conductor also but every one of the five would need to be done or just one single negative return. The best way I have found is to use a common box with two sets of electroncs and feed both directions every 10m, 5m each direction. PSU can be shared if 6 ampere.. Only one receptacle end required and the RGBWW strips run just fine on a 3A supply anyway.

The two protocols are not complete backup for each other. The whitepapers describe dependence on each other. RF only gets repeated over powerline and vice versa. RF is dependent on powerline for synchronisation of hop timing. Of course a whitepaper is only a public concept, not what is actually being used.

Eliminate powerline? No. Decouple them them? Yes. I can see the original Insteon powerline protocol to continue to exist for distance and usually reliability. I can see the Insteon RF to completely change into a higher throughput protocol that is not coupled, nor synchronised to powerline at all. I am not sure how that would logically work but the speed of RF is desirable. RF is a problem with metal electrical boxes and short distance. Maybe it doesn't have to be.

From what I have heard (somewhere ), the manual query doesn't do it. I don't know why there there would be (or could be) a difference between program Queries and manual queries. The MS doesn't respond to manual queries anyway. Of course putting it into linking mode may help.

Which MS version do you have? The original MS doesn't have a heartbeat. and the lowBatt sgnal is only sent once. I have seen reports to use a query of the MS in an ISY program to clear that past indication. ISY only indicates the last thing it was told by the device.

Here is an example of Insteon's new promise engineering. Battery isolator strip pulls out and catches battery negative end spring, damaging it. (bottom end of battery) Here is the previous Rev2.0 design without this stupidity.

Yawn. Looks like they have no idea what to do next. We are going to, we are going to, we are going to... I just received two more defective design Leak Detectors. The PCBs do not fit inside the case. Brilliant engineering and even more impressive QC....NOT! I still use only their products though. Their basics are still the best IMHO.

CAO Wireless tags and WC8 with 1wire probes. Sent from my SM-G930W8 using Tapatalk

There are rules around venting. I can;t remember the rules from years back but vents on a roof must be x feet above the highest roof peak within y feet of the vent. Winds will cause turbulence off the roof peaks and create down draughts or venturi reactions if the placement is not right. Usually the solution is to extend your roof vent higher by one length of pipe. A proper wind proof cap designed to reject turbulence may help also. I have not relied on the geofencing ability of the Tags for anything serious so can't report on the reliability of it. I report the signal failure signal from KumoApps and I suspect it may not be totally reliable. I have caught the signal still not updated after I got home and loaded the admin console. That takes almost 10 minutes on my small laptop. I am not sure if there is a better comm path for this. I think PolyGlot node only reads the data from the same source as KumoApps, CAO's provided smart system. However I do use the signal for garage door left open after I leave so perhaps the failure is detected faster than the signal restore logic. I detected the car unit almost 2 km. away once as my wife came up the rural back road. Consider the rural to be radio quiet though.

You stated you are in Canada and that means you probably have a very air-tight house. In some homes, running a bathroom exhaust or stove exhaust fan can produce enough low air pressure backdraught that can extinguish your water heater pilot flame or, depending on the era of the DHW / fireplace design, endanger the occupants with CO2. At times a puff of air pressure or vacuum from the roof vent can extinguish the pilaot flame too. That gap between the tank and the flue is supposed to help avoid this. Your plumber should have been aware of this but...who knows? Designs and ideas are changing constantly. Even a window cracked open slightly can cause a house vacuum, depending on the direction of the window across that Venturi opening. Tight seals can be a problem in other places. My NG DHW uses outside air only but I still get an error reported, shutting the thing down from weather gusts that travel down a 45 and three 90s. stalling the power exhaust fan.

Yes. Most of us are Canadian where we have lighting and heating needs, unlike our U.S. brothers and sisters, where the sun never sets and it is always warm. I got mine all from the CAO online store but it seems like they are trying to distribute their sales to other venues. Try amazon.ca. I haven't seen them on aartech.ca yet but haven't looked either. My advice would be to at least one more Pro Tag (with 13 bit resolution and memory for months of data) because once set up you are going to like these. I have used a few to calibrate thermostats to the same offset, check duct temperatures and room temp. and humidity gradients for HVAC, outside weather, luminescence (not implemented in ISY programs yet), detection of the vehicle from 1/2 km. down the road, and many more things I can't even remember. I haven't implemented any motion detection with them but others have.

To add to that, for people with <Win 2K coding experience, the ISY Wait and Repeat are like inserting a voluntary "give up your time slice to the o/s". Early windows apps required the code writer to do regular "releases" of their time slice to make the multitasking function work since Windows wasn't a "real" multitasking o/s. In VB it was dummy = DoEvents() In C++ sleep 0

Yes. It is a sealed metal encapsulated DS18B20 chip. They are available for about 99 cents each on eBay etc... IIRC the CAO unit is more money but comes with a convenient mini plug-in jack for the plastic Tag part.

Note. to use a time frame over the end of the year you must use "OR" logic like this. If MM.DD >= 12.24 OR MM.DD <= 1.12 Otherwise you would use "AND" Logic like this If MM.DD >= 12.24 AND MM.DD <= 12.26 To isolate a month you would still have to use a range like this If MM.DD >= 12.00 AND MM.DD <= 12.99 (or 12.31) This will not work MM.DD = 12 because the variable will never be just an Integer in this logic.

The point was a clarification of what PaulBates posted above. If Program1 calls program2 while program2 is still running it will start over anyway, so it isn't a complete isolation. Eg. Program1 If whatever Then Repeat every 2 seconds call Program2 (if) Else ------ Program2 If whatever Then turn On Light Wait 5 seconds turn Off Light Else ---- Light will never turn off. Program1 will start Program2 again every 2 seconds interrupting the Wait 5 seconds, regardless of Program2 logic.