lilyoyo1

It's all about perspective. That 1 feature worked because there was a single common element... insteon. Now you can add zwave, hue, ecobee, harmony, lifx, and more to a scene....all of which requires their own specific coding in order to work properly. What it boils down to is whether you prefer to use 1 single protocol which is insteon or a multitude of disparate devices with your system.

That's not part of 5.0 due to being able to use different devices into a scene. The best method is to add your responders to the scene, configure them and then add the controllers

I have an easy way..... Turn off the lights. Lol

I have a couple of their motion sensors and not once have I had an issue with them timing out or re-triggering. Granted I use programs vs direct linking which may have something to do with things. From my personal experience with them, they work well for being a motion sensor but not for anything else.

Insteon was always aware that he worked for udi. When insteon asked him to come back, his being able to continue to work on his own projects and udi was part of his terms and in his contract. With that said, he's no longer with insteon at this time. The plm fiasco had nothing to do with that person. As I said before, short sighted decision making. It's this decision making that made them jump in bed with apple in the first place and almost bought the company down. That single decision is the main reason why JD ended up needing to sell the company.

Yes

I highly doubt this is a conspiracy of insteon to see to UDI's demise. In fact it hurts them more since UDI is a large part of their consumer base. Having those users unhappy doesn't serve them well in any capacity. All that would do is make them use devices from a competitor. Being that one would need a strong mesh, that means additional devices from zwave instead of insteon. Their issue is short-sightedness. They make insteon only for themselves vs involving other companies in the process to ensure products work in full with other controllers.

Setting the iolinc to Momentary C will allow this

My goodnight programs simply issues close and lock commands. I don't worry about the checking status of something. That way if the status is wrong the action still happens

I only use the Isy so ai can't speak on integrating the 2 together for your program to work. However, I would recommend using a kpl and fanlinc together (I use them myself) but they are linked and controlled directly by the scene itself. You didn't say what specific problems you were having with syncing. One thing I would check would be to ensure the isy itself is receiving the information from HA and is updating itself with the proper status. If the statuses are being updated properly then the programming portion would be easy. The main thing that jumps out at me is that there is nothing to trigger your "or else" statement. If status of fanlinc is low And status of fanlinc low is not off Then set kpl on Or else turn kpl off

Did you set your isy to static when you previously had it set up on your old router?

Channel vision has a smoked plexiglass cover as well for the front which looks extremely good https://www.homecontrols.com/Channel-Vision-Smoked-Plexi-Glass-Hinged-Enclosure-Door-CVC01xxD

That's because of the certificate expiration

I would get some type of siren to put in the house and shed which would go off when the door is open. If you're asleep you may not notice the flash but would hear the siren. One in the unit as well would potentially scare them off too as they would hear it and assume someone else did too.

Their certificate expired. With them being on the west coast it may be a bit before it's up and running again

Did you get your isy address from the portal? If so, make sure that you're using your portal user name and password

Hopefully sooner

I get that. I prefer hard-line too but we're talking 15 + years from now. Whatever wire we run today for someone won't benefit the buyer today. By the time anyone catches up, it won't be worth the extra cost

The 6a isn't nearly as bad as 7^. No special pieces either for fiber. Seeing how things are moving, I'm hard pressed to see the need for installing anything higher than 6a for future proofing. I wouldn't waste money on anything more than 6a. By the time we get to where it's needed, the cables would probably need to be replaced anyway or the home would be gutted for a remodel. At that point, put in cat 25 or super duper fiber. Lol. Hell, everything will probably be wireless at that point anyway

Cat 6 is good. I use Cat 6a on my jobs though

I personally prefer insteon over zwave for lighting and zwave for everything else. Regardless of whatever other issues I've had with zwave, I can't get past the popcorn effect it has when turning off/on (1 device at a time). I've used insteon in many projects throughout Orange county. Many were condos and apartments. All ran without issue. Still do. There's 1 building off the 55 specifically that has multiple units on the same floor with insteon and none has called about any issues yet. That's not to say you wouldn't, just letting you know it's possible. If you're fully renovating and redoing the wiring, there are steps you can take (which I would do regardless of which system) to lessen the chance of issues. The main thing is to properly plan from the start so that you aren't throwing things at the wall hoping they'll stick.

Perfect example

My very first words were clarity is in the eyes of the beholder, implying what's clear to some may not be for others. Due to your background, how you read things may be and probably is different than those without such background. It's like when I was in boot camp. The Drill Sergeants talked about those accustomed to hunting would have a harder time on the range than those who didn't (they were right). Programming the isy is a different beast than programming systems or coding. They have to make it so that a person with no programming knowledge can use it. Due to this, those with a programming background have a harder time grasping the different nuances that comes with the Isy. Unfortunately when it comes to examples, there are way too many variables and ways to accomplish a task without causing confusion. Have you seen the isy cookbook? It may have some examples of things that you may come across in the future. https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cookbook

In addition to what MrBill said, I would add a wait to the then command. I do this with my ceiling fans so that they arent triggered due to a temporary temperature change. Its not needed but its helped prevent my fans from cycling on and off for no reason.

I think clarity is in the eyes of the beholder and how they choose to interpret something. My wife is my guinea pig on simplicity. As smart as she is with her line of work, when it comes to this stuff; it might as well be in farsi. Anyhow, I wrote a quick line that said from 7pm to 5am the next day then turn on the light. Her interpretation (without explantion) of 7pm to 5am the next day was the light would be on from 7 at night until 5 in the morning. When I asked how she figured that, her response was the next day starts at midnight. People's minds work differently. For some, a new day begins when they wake up or the sun comes up. However when it comes to time itself, a new day starts at midnight. The same for the week. I know many (due to work schedules) who look at a new week starting on Monday vs Sunday. They know when the week truly starts but in their mind it starts on Monday. I think this may be the same situation that you are in. You're processing the next day as when you wake up vs Midnight when a new day actually starts.