Teken

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 . . .

Here's a novel idea on a related matter. How about a real drop down calendar widget so people can select days, weeks, months, holidays, with out having to craft some giant program which is just a massive kludge. Having a calendar would save people lots of time, frustration, and provide a much better user experience. This isn't 1930, its 2015 and this should be on the *To Do* list for 5.XX

Extra bonuses are having the ability to turn RF / Power Line on or off. Along with Smarthops and other various feature enhancements which you can read here: http://forum.universal-devices.com/topic/14735-insteon-onoff-outlet-2663-222-review/

To be fair to Smartlabs this was their first go at the outlet linc. As you're aware you can not query a battery device either (not yet that is).

Correct, this is why the new dual band, dual outlet was such a God send. It is a controller / responder and works like a champ!

SOAP BOX COMMENTS: I guess my views are quite different from many others who are mostly consumers. Based on your reply, I can see you fully understand why I hold this view. In the big picture its really personal choice and having faith in your systems to operate and react to your will. After working in many commercial environments and seeing how others cope, or endure system issues. I have gleaned all of the *Don't Do* opposed to the *Must Do*. I love my toys just like all the rest but my personal experience keeps me grounded in the fact. Reliance on too much high tech will leave you stranded when its needed the most. I believe if people plan and deploy their systems on a base level to operate independently. This resolves about 90% of the possible issues that could arise. The biggest No, No, in my mind is mixing security with HA. Lots of people do it and have great experience with it. But, from a security and safety stand point this is counter to what the goal is. If people had your personal experience in a power generation plant they too would understand why things are done in pairs or in three's. The military always chirped on and on about the power of three. Sometimes it was really a PITA for us in the field but you know what? After going through a few disasters with them and watching how their systems operated even with two things down. It didn't take much for me to emulate that same view and philosophy in all that I do. Sorry for the off topic reply . . .

I wanted to know where this device is on the 2015 road map. Along with builderb's question answered.

Hello Don, Speaking for myself only from a personal point of view. I always create my system(s) so that it can operate as a stand alone Insteon network. A controller is simply used to accomplish more complicated events / scenes. Or where another device is interacting with the Insteon network like say main water shut off valve, power management, temperature, etc. I have seen lots of million dollar homes literally remove every physical switch from a wall and rely on a HA controller. This offers a clean look in the home, but is truly stupid in ever possible way you could think of. As you're probably aware the PLM is the most important part of the Insteon integration to a controller. You have no doubt read countless threads where it has failed or where the HA controller was off line and not operating correctly. Imagine you couldn't turn on a simple fan, light, door because it relied on a controller?? I have supported many Military, Financial, Federal, EMS, Fire, Hospital environments. There isn't one of these agency's or business's that would allow a controller to operate and have full control of their systems, none. My key point is that if you grow your system and linked them natively in the worst case scenario even with out a PLM / Controller your home would still operate. NOTE: Outside of scenes nothing beats the ISY Controller in integrating fire, weather, energy, network, HVAC related data to the Insteon network.