Teken

Don, Worry not lots of the young folks like to throw good money out the window with out much care or thought about how to solve a problem. This is something I've seen for ages which I am sure you can relate. We are fast approaching critical mass in automating ever facet of our lives. With out real people thinking about alternate solutions its safe to say the next generation are doomed to fail. As I stated above, you taking the time to read the e-mail headers is something easy to do, free, and resolves the issue at hand. Kudo's to you in using your noggin in the way that also provides a solution down the road here and somewhere else. I am not quite at your age group but rest assured *Old School* has led us to the moon and back . . . Rock On . . .

Don, You're so old school I love it . . .

?!?!

The jumper number 5 should be set by *default* to allow software to control the MS settings. This is how all new MS come from the factory.

Larry, That forum is full of people who know nothing more than ELK which is like living in 1980. Every protocol has limits, good, bad, ugly. By a large margin there are many that use Z-Wave, UPB, etc. Some of the members come off as snobs and perpetual fan boys. It doesn't take away the great information and knowledge some of them have. Just quite a few regular posters who are narrow minded and feel the need to take a turd on Insteon at each turn. I can freely admit when you read bashing from me regarding Insteon it is intended to first answer a question posed and to educate those about the limits or failings. I always try to follow up in how they could do better and that should always be the goal for anyone who replies. I live by the credo of *Come to me with solutions - Not problems* Many people are quick to bitch, whine, complain, but few ever offer suggestions to resolve, solve, or provide insight into how to do better. Every forum has a few *dicks* in their group but I do believe most of them mean well. Nothing is worse when you get burnt from a product you bought and the vendor leaves you stranded. I can truly understand the bitterness that ensues from there. Having said this, these same people have to move on and engage the vendor to let them know whats going on. Sometimes it takes some public shaming before something happens, sad but true. Back on topic: UDI should make a concerted effort to spread the word and show their power, flexibility, and on going development of the ISY Series Controller. As I recall UDI mention in the past, the company doesn't want to be swiss army knife where its the: *Jack of all trades - Master of none* Its about doing something right the first go round and slowly building from there. These building blocks are what makes a product great and provides a strong foundation to build upon. This is something I explain to others when the opportunity arises. It doesn't matter if its this forum or others my reply is always the same. The only Home Automation Controller that IS an Investment. Larry, Sorry for taking your thread in a 180' direction . . .

If you can find a method to push the data to SEG or similar aggregate sites you're golden! Sent from my iPhone using Tapatalk

Please be aware if you want updates consistently you need to plug it in. Being on battery it only pushes information based on a 2-3 degree change in temp. If that type of delay and resolution is OK it can work. Otherwise you have just traded one hobbled piece of gear for another. Sent from my iPhone using Tapatalk

It comes down to budget and your long term needs. You could buy a remote TSTAT from SH but that solution has issues too. Or you could purchase any third party 1 wire solution. If you want reliable, expandable, accurate temperature data 1 wire is the way to go. Go to the Autelis forum here look at the 1.3.0 thread you will see information via my install thread. Sent from my iPhone using Tapatalk

No, I created a POLL where I asked UDI to support all features and options for each device. To your original question there is no method to use this device as a remote temp sensor. Search under my profile of threads I created that will let you see the content etc. Sent from my iPhone using Tapatalk

I made a post about supporting all Insteon features please cast your vote in that POLL. Also indicate the energy meter which I have 4 of them. Sent from my iPhone using Tapatalk

For lots of programs you should be using the notes section so you know whats going on.

There is no alternative method to disable local control outside of what you just described.

Brian, That's it! I had assumed the system would recall its last known state after a reboot. As always your insight and feed back is most appreciated and welcome! I was trying to figure out why another persons controller always appeared to lose its state. I should have asked them what the hell they were doing over night. They replied they have the ISY rebooted every night to ensure some unknown issue does not appear? Your Rock and you know it . . .

If you purchase directly from SH all of the current shipping PLM's will be hardware 2.0 with firmware v.9E. Hardware 2.XX has addressed the early failures by identifying bad capacitors and replacing them with higher quality ones. The v.9E firmware has removed the ALL ON / ALL OFF commands from the data base which seems to impact a small segment of users. NOTE: UDI is currently testing their own PLM replacement unit. Expected release is Q1 or early Q2 of this year.

I wanted to know if the ISY is supposed to remember the last user selection for this option tab. I have seen various results when opening the Admin UI Console. Specifically, I want to know if I turned it off and close the UI and open it back up should that tab be grayed out and disabled?? I have high lighted the box in red for those unsure what I speak of.

Ha! [emoji2] I always find its the small things (details) that just make the user experience so much better. Much thanks goes out to the ISY forum members for enlightening me. [emoji5]️ One would think this would be a obvious thing to do while creating such variables. I had assumed the system would do this for me. [emoji16] It only came to play when I started crafting lots of variables with similar names and found out I was picking the wrong ones! [emoji12][emoji35] Sent from my iPhone using Tapatalk

If coupling is good and confirmed via the 4 tap method. The remaining culprit is noise on the line whether it be noise makers, signal suckers. NOTE: Best practices state you should always hard reset your devices prior to enrolling them into the ISY. This will ensure the device is at a default state and any testing links and programs are deleted.

You can confirm if they are controllers by looking at the tree on the right when you select each device. It will tell you its association etc. If this proves to be correct and they are controllers you need to confirm proper coupling / bridging. Have you done this in your Insteon network outlined in the full users manual?

That isn't a solution to your problem. You either have noise on the line or poor coupling / bridging of the Insteon network. This also assumes you did in fact linked them (KPL's) correctly as a Controller in all of the scenes.

I can tell you from naming convention for variables make sure you identify them using (i) for Integer vs (s) for State. This will come into play when trouble shooting, debugging, and for at a glance selection. That is the first thing I did when this little (simple) nugget was told to me! When you break over 50 variables in your system having a good naming convention / schema is very important. Many people have been hood winked in trying to figure out why a program doesn't operate because they thought that variable they assumed they would recall was a state vs integer was indeed the opposite!

Oberkc, I swear you're such a poet!

For me its all KISS . . . Only if something needs more line of code to get the expected results do I even go down that path.

So very true. This is why we live by under promise, over deliver! Our primary goal is always up time and turn around time from call to resolution.

At this point I will take that over that massive *date program*! Kudos to those who took the crazy amount of time to craft and share it to the membership. But, the reality is it was a real hard sell to get even two people to get it going. I am a technician not a salesmen so don't have the time to lay down the fluff about how to make it work. When it should be a native feature by default.

Well, since we're asking might as well ask for the moon! My feed back is from the view of a new user which I had to deal with for ages. I am tired of being beat up because the ISY has no basic calendar / clock. This is considered basic 101 for almost all the software and platforms I have worked with in other systems. Its hard to show off all the power of the ISY when two days later the client rings you up and says *Where is the calendar* and I reference them to those two massive programs to do dates. You don't even want to know what comes out of their mouth . . .