Teken

I am the odd man out here I guess. I have folders based on devices and use. Insteon, Autelis, GEM, Dash Box, Mobilinc, Timers, Energy, Temperature, Water Sensing, HVAC, Security, Sent from my iPhone using Tapatalk

Exactly! Look at the *Resume Dim* feature I have never seen or heard of this before in any device. Its not listed in HL2 (not surprising since its EOL) but can assure you if it was updated it would offer the same feature. Has anyone played with the Resume Dim and seen how that operates in real life? Again, this is another *FEATURE* not documented yet its listed in the *Options* list so lets get off the whole its not in the e-doc shall we.

Stu, I don't follow what you mean by reverse engineering?? These features are NOT proprietary to the vendor they are made available so they can be used. Why would anyone sell a product to the masses and allow third party companies build a controller and in turn not allow them to develop the same feature set?? That makes no sense and that literally does not apply here at all. This is not like a Apple Lightning cable which is proprietary and requires a license to make, sell, and use said device. UDI already has NDA agreements and other cross license terms which they follow to support the Insteon product line. Lets not confuse the issue at hand shall we. Generalizing Here: These features are available, they work, and competing software / hardware devices make use of some or all of the features Smartlabs offers.

In the big picture does it really matter what is listed in a (e-doc) that has been historically out of date, inaccurate, or simply missing information? No, it doesn't . . . People make it sound like the wheel is being invented here, its not. These features are present, available, working, and proven. It comes down to UDI obtaining the required information so they can implement it to the ISY. When I read people saying its not documented, unknown, should we guess??? No . . . People should use the resources and contacts they have internally / externally to get the information. This is exactly the same (circle talk) that happen when I asked about having the remote wake up of a battery device. I was told this could not, would not, will not happen. Its not that this feature didn't exist, or didn't work, or available on other competing products, it did! Fast forward more than four years later the ISY now support remote wake up and updating of the programming. Its obvious to me its not a technical limitation or having the ability to do it. It comes down to the willingness to simply do it, period. I am tired of reading the endless replies that we should guess, don't know, has it ever, doesn't matter, who cares, etc. Bottom line, this isn't rocket science, its a dumb device which has specific technical specifications which must be made known to develop and provide the said features. Whether or not UDI wants to invest the time to support the features is entirely up to them. But, in my mind only makes sense from a business stand point. Why would anyone sell a product that advertises it only supports 2 things, when the actual products supports 7?? If its not apparent to the forum members these topics really get under my skin . . .

Correct, you must use s relay switch as a dinner will not present full voltage to the fan which will then damage it in the long run. In an extreme condition the fan can over heat and cause a fire. Sent from my iPhone using Tapatalk

Don't recall off the top of my head to be honest. Regardless, there are features that are present in these devices so they should be exposed and made available in the ISY. The Lamp Linc had options before and has since lost them which is clear they exist but something has been lost along the way. I am sure once UDI has a chance in the New Year to engage their internal Smartlabs contacts these issues will be resolved. i have faith in their ability to find out what is going on and resolve them.

+1 Agreed. What needs to happen is UDI needs to engage their Smartlabs internal engineer contacts and identify what aspects are required to ensure full feature support. It makes absolutely no sense to hide features from the 3rd party Dev's they are the one's helping promote and sell more products! So when I read we have no way to know what is available, how about someone ask the powers that be for the information.

I have to assume you didn't read the entire thread which clearly shows examples of what is being spoken about. Please review the screen captures for the devices listed. Specifically all of my KPL's no longer show an option box to change various settings. They were present before. The other screen captures show the differences in what HL2 can do vs ISY for various devices. Sent from my iPhone using Tapatalk

Stu, I believe LeeG is fixated on you showing him where in (ANY) manual does it state the program lock / LED Tx is available. I reviewed all KPL full users manuals and saw nothing mentioned about those two features. Having said this, means absolutely nothing to the public and the general populace as Smartlabs has never provided any insight about firmware updates and what features or removal of such until it was seen in the wild. I personally don't care in the big picture that they don't share this information to us. But, this critical information needs to be shared to the developers like UDI. Without clear, concise, and proper documentation how is one supposed to create and deploy software to support the Insteon hardware?? I have sat from afar for a few years and watched how various companies can provide support for the exact same devices. Yet have missing features, added features, or not even support a device at all. This is shocking and maddening at the same time. Its clear to me there is more than one way to deploy support for a hardware device for Insteon. What surprises me is why is this so hard to do? Isn't there like a e-doc that comes to the dev's that says this device has five features and this is what they do, and the dev should make it this way?? The disparity in HL2 vs ISY and conversely drives me insane at times.

Hello Davonavo, I would await for UDI to review this and a related thread. I believe there was a mistake / bug introduced in this last beta release. I also believe if the options you see are available in the console the reason it doesn't work is because UDI still needs to figure out how to code for these new options for the Open / Close sensor.

Based on a very limited sample of what I have seen and read here and with other people. I believe we are on the cuspid of seeing early options and functions of the ICS3 protocol in the wild. This comes across to me that some aspects are not being deployed correctly by UDI per the Insteon developer docs. While there appears to be a (early testing) of firmware that support some of these new features. I believe once UDI is able to engage their Smartlabs contact lots of these things should be resolved and working as expected. Sent from my iPhone using Tapatalk

LeeG, No worries, how do you envision this feature to operate if you had to take a wild guess? Because it comes across like the repeat hop feature but isn't??

OK, I just went through all of my KPL's dimmers and relays. There is a serious bug as the option list is missing in all of these units. I gather this is a over sight and bug opposed to not being supported. Lets wait for UDI to chime in as to a ETA for a fix for the missing *Option* features.

Did HL2's battery status ever work correctly in indicating actual battery levels as seen below?

Given Smartlabs inability to communicate effectively with their customers this is not surprising. In seven years I have never seen one firmware update / deprecation ever covered as to when, why, or what has been introduced. You and I are on another thread about a Open / Close sensor which appears to have a heart beat, variable low battery selection option. There is no mention of those *new* features anywhere in the 1.9 / 1.9+ manual either. I just loaded HL2 and can confirm the ISY is not configured properly to show all the options for the Lamp Linc & Micro Dimmer. The Lamp Linc has no options in the ISY at all and they are the most basic in nature: Enable LED, Beep, Blink on traffic, Program lock, Variable LED brightness, X10 codes. What is strange is that the e-doc indicates X10 has been removed and deprecated yet its present? The Micro Dimmer is a little different and off the top of my head its missing: LED brightness, Error blink. But the ISY does have a resume dim option which is not listed in HL2.

I am going to fire up the HL2 and see if the lamp linc have more options to set. If it does, that really surprises me that UDI is not offering the same feature sets. I have to believe this is an oversight or a bug. Then again HL2 found my Insteon enabled flood stop controller but UDI decided not to support it. Sent from my iPhone using Tapatalk

I think there is a bug somewhere because the new lamp lincs also do not have any options listed. The manual clearly indicates several software only options like beep, load sense, etc. But none of them are present. I am seeing this on both 4.2.21 & 4.2.25 Sent from my iPhone using Tapatalk

It's lucky this is a hobby! Otherwise this gets really expensive, fast! [emoji4][emoji5]️ Then again, it's almost like an addiction once part of the home is automated. I truly believe Insteon has brought HA to the masses where it's affordable for all. Even though HA systems like Control 4 are present they cost are 3-5 times the cost of Insteon and requires a pay as you go installer to add and make adjustments. Sent from my iPhone using Tapatalk

Should you have any further questions please do come back. I am sure lots of forum members will be able to help should the need arise. Sent from my iPhone using Tapatalk

I have never heard of anyone accomplishing this so you might be the first! [emoji4] I would suggest you purchase a brand new 2413S from SH and be happy it will operate as expected. Sent from my iPhone using Tapatalk

I took you literally that it was a (N) and not a 2412S PLM. The older Smartlinc was a 24XXN. Sent from my iPhone using Tapatalk

You must use a 2413S PLM Sent from my iPhone using Tapatalk

I don't really think you missed anything at all. I do believe having more is always better for the collective as a whole. Sometimes keeping things simple is much better than using all the high tech gizmos abound. I am a firm believer in unplugging all electrical devices during a commission of a site then trial by fire. It simply does not work and adds more time than it really saves by sitting and waiting to see if all is well. Even when using the breaker method its sometimes impractical to identify what is all on a circuit with out spending lots of time documenting each room, floor, zone, etc. Adding back a single item while watching either HL2 software or the level 3 event log is one of the best methods to see bad COM's when they are present.

Hello Gary, Sound like you are off to the races and will enjoy your Insteon network well into the future. NOTE: Once you have confirmed proper coupling / bridging via the 4 tap beacon test outlined in the full users manual for the various dual band products you own. It doesn't really matter where you place the other devices so long as coupling is present. From a practical stand point I have always deployed a dual band plugin device in all four corners of the home, floors, zones. This ensures any RF only devices such as hidden door sensors, open / close, motion sensor, leak sensors are always with in 25-50 feet of any of the plugin devices. I have not seen an Insteon device falter using this method besides bad COM's where signal suckers / noise makers are present. As you're probably very aware all the coupling in the world will not resolve persistent noise / signal sucking issues.

Just my luck! Well, here is a global plea to those who may have a copy and can fire it over to me.