Teken

Stu, LOL . . . Yes, we are surrounded by risks all the time and most of us balance those potential risks all the time. But, in this case the OP needs to know if one day the cord for what ever reason over heats and melts causing a fire. If the insurance company identifies the root cause they will be more than happy to decline insurance coverage. These are things people do all the time but rarely take into consideration or plan for.

The odds your closet solution poses a risk is highly unlikely. But, wanted to call out an extension cord is intended only for temporary use and not meant for a permanent installation which is against the CEC / NEC. Extension cords are also not in wall rated due to the fact the insulation must *breath* as part of their design to dissipate heat. Placing a ULc / UL cord into a confined area is against code and voids the ULc / UL intended heat rating. In the big picture and (reality check) this will probably never be an issue. But, you should understand the risk and the understanding that your home insurance is void in this case. You will not be covered by any sort of insurance due to the unapproved *Risk*

I always find it strange and interesting at the same time that Smartlabs will introduce some features but not mention it at all. Your device would probably fall in the 1.9 manual iteration vs the 1.9+ manual. Which neither mention these new features. Based on a quick review it appears firmware v.43 in various devices brings these features on line for different aspects. But, since not all devices track with the same firmware this is not a true method to determine capabilities. Keep us all in the loop as to what UDI finds or resolves for you.

That is so weird you can see the node added yet do not see the options button?? Where as the other member can see the options list but does not have the ability to interact with it?? I believe if the OP deletes the device and adds it back in he may see the same thing you do now. I hope he see's the options tab though because then some basic tests could be performed. Much thanks for taking the time to craft the program and to see the heart beat works. I am going to sit this one out for a a few months so (existing) supplies of the Open / Close sensor clears inventory and perhaps newer firmware may be loaded down the road.

Brian, When you have some time could you please review this thread and perhaps offer some insight about a possible fix and solution: http://forum.universal-devices.com/topic/14895-insteon-leak-sensor-2852-222-review/?p=127122

Not to go on a tangent but wish the iPhone App was at feature parity to the iPad version. It needs some serious upgrades in that department!

Jimbo, That is most excellent to hear these features work. Can you provide a screen capture of the options list for this sensor for those who don't have this latest release.

Apologies, I should have stated Apples Home Kit. Smartlabs is working on a Home Kit version of the HUB which may finally offer all of us a nice UI interface and multi 3rd party support. Sent from my iPhone using Tapatalk

Agreed the front end needs more polish and a wife friendly UI. I was really hoping the HUB II would have been more capable because my goal was to use that device as the front end. But after a third attempt it continues to lack even in the most basic / advanced ways. Perhaps the Home Link version will surprise us all in the next 11 months. Sent from my iPhone using Tapatalk

At 100% it's still not at full output. If your fan has been running fine for three years don't worry about it. Note besides electrically being unsafe it's against code. This is like putting a dimmer on a outlet. Sent from my iPhone using Tapatalk

I think most of us are OK that Smartlabs isn't really pushing the controller area too hard. Since the ISY is more capable in almost all areas. I would rather they focus on releasing new products or upgrading existing devices to do more. Sent from my iPhone using Tapatalk

You do this because you have limited space and room? Or is there another reason for stacking devices? I have never understood why this is done in a home when a power strip would be a much better option. [emoji47] I know a few people have stacked AP units to devices not dual band in hopes of getting better COM's. But that is really a band aid to a noise issue or signal sucker. [emoji51] Sent from my iPhone using Tapatalk

It does depend on the electronics and how dumb the fan is. If you try to use a dimmer on a VFD type motor some interesting things will happen. You won't see very many smart bathroom fans in a home very often outside of those which have a built in humidity / timer function. In a commercial environment where money isn't an issue I have seen two businesses like IKEA / Costco use smart fans which are digitally controlled and managed by a HVAC management system. These can not use a dimmer regardless if it's a triac / thrysistor. If a device actually reduces the line voltage which many don't this is where current increases thus causing a burn up / fire condition. Sent from my iPhone using Tapatalk

If you have confirmed proper coupling / bridging I would be looking at noise makers / signal suckers instead. As you're aware the I/O Linc is not a dual band device but future releases will be. You can replicate one by adding a AP / Range Extender on to the face of the I/O Linc.

If your PLM is a 2413S its a dual band unit. If its a 2412S its a single band unit and should be updated to DB. The latest hardware is 2.XX, which addresses the early two year failures due to dried capacitors. This release also removes the ALL ON / ALL OFF command lines from the device table. As some people have reported insteon devices turning all on by themselves with no ISY awareness of these events. To date there have been a few people reporting back even with this removal of the ALL ON / ALL OFF command line this problem persists. I am unsure how that can be since the actual command line no longer exists. So, have to gather there are other factors at play here. This also does not address the fact no other controller has ever seen this problem before.

I believe it's a embedded windows OS. Sent from my iPhone using Tapatalk

Use it as a ISY UI controller? [emoji53] Sent from my iPhone using Tapatalk

So here is a completely shot in the dark. How about one of you use the new remote update feature and make a program and see if it works that way? I have my doubts but it's free to try! [emoji4] Report success / failure to the group. Sent from my iPhone using Tapatalk

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.