bcdavis75

Granted I've been a little out of the loop. But we can't run ISY on the Polisy yet correct? And if we could, I'm not sure how the extra ethernet ports help. You still need an interface to plug into the wall right?

I emailed Smarthome.com to see if they had an info and when it would be in stock and this was the answer: "Thank you for contacting Smarthome Support. Our apologies for the inconvenience caused. We understand that you would like to know about the availability of our products, we would be happy to assist you further! We had escalated the issue to our resources, and we got an update stating that the Insteon PLM (Item # 2413S) is a discontinued product and we do not have any immediate plans to bring the Insteon PLM back in due to limited sales." Given the propensity of failure with these PLM's, what are ISY owners supposed to do if this is true?

Chill.

Hi all. I'm thinking of embarking on a small project to get my Pella Shades working with the ISY again. Long story short, I used to be able to control them By going ISY>IFTTT>WINK HUB>Pella Bridge. Believe it or not, that all worked great until WINK decided to make their hub subscription based. The Pella Bridge itself is a Zwave device but from what I can tell, connecting directly to it doesn't work very well. Sooo... I'm thinking of an alternative approach that I once used to to control my Garage Doors (before V5 and the MYQ nodeserver). I took apart one of the shade remotes (pictured) and I'm thinking about soldering the buttons to an I/O Linc. BUt here's the rub, unlike my garage door openner where 1 button toggled both open and close; on these remotes, open and close are distinc buttons. Moreover, I'll need to hack 2 remotes becasue some of the blinds are bottom up and some are top down and those sets are linked to their own remotes because it's impossible to mix them on a single remote (Pella sucks by the way). So if I understand IOLinc correctly, I'd need 4 of them???. Also to be clear, remotes (pictures) are linked directly to the shades I want them to control. The Pella Bridge device is a separate unit pella sells to connect shade to a VERY select set of home automation systems of which WINK used to be included. So the Bridge is not part of the equation for this project because I have no way to communicate with it. I'm wondering if there's a different device out there (maybe a a ZWAVE device) that has multiple relay's on the same device and would be a cheaper route? Also, I was assuming I'd be using the Normally open and Common connectors but if I'm wrong, any advice appreciated.

So glad you posted this. I noticed I'm having the exact same issue with some of my insteon dimmers. I haven't had time to dig into it but same deal; When controlling the device from the admin console, "ON" actually turns things off. Fast on seems to work fine. I will go back and check the "On Levels".

I have two of those. They work well.

I use a Kasa switches Powerstrip and the KASA nodeserver. Not as nice a real PDU but cheeper and it works.

Hi all. I wanted to chime in from the perspective of a pure consumer -- I'm not a developer; I have no interest in leaning Linux and building my own Polygot server; I regularly use this forum for help on things and give virtually nothing in return I took the plunge on Polisy becasue of all the awesome possibilities it represents. At the moment, they are still just possibilities becasue I've run into some serious issues. Fortunately @Michel and team have been extraordinarily responsive. As a consumer dipping my toe into this new model, it's both exciting and scary. I've already had to reach out directly to several node developers for help getting some things to run. Some have been very responsive (props @simplextech) and some not so much. But I can't blame the the unresponsive too harshly... I haven't paid a dime for your work. It is a little intimidating however to consider the possibility of deeply integrating my home via node servers, having something break, and having no clear channel to get help. Of course these forums continue to be a great resource but but the breadth of integrations might make it more and more difficult to get answers. Official UDI tech support is always great too... but is that the support channel for 3rd party nodes going forward? The things that I'd love to see happen as a dummy (user): The pay model that Michel referenced. Hope it happens soon. It's hard for me to quantify exactly what I'm WILLING to pay. $30 bucks for Sonos??? No brainier. $5 for tesla? yeah. And a subscription would not be ideal. I'd rather pay on an irregular schedule as upgrades are needed due changes in the API's or whatever. OR, I would be happy to an annual subscription to UDI for unlimited node access in perpetuity to be divided up among the developers based on some black box algorithm that the forum will reverse engineer over the course of years and 1000s of posts Some channel for bespoke node development. I don't know if anyone care about Carrier Infinity or insynctive shades but I'd pay someone to make a node. The nodestore interface. There's a lot to do but some low hanging fruit: Add fields for "Date Added", "Update Available", and links to the underlying product it controls. Also, all the instructions and custom parameters need to be directly integrated. I never want to go to Git hub for anything. The relationship between Cloudpoly, Polisy Poly, my portal and related Alexa connections is all getting very convoluted. It feels like this could all be unified. But users like me oversimplify things Clear support channels Anyway, a lot of that is a knee-jerk. Overall (even though everything is broken at the moment), I'm very excited and happy for Michel UDI because I think this will all really take UDI to the next level. Keep it up guys.

Sorry if this has been covered but is there a fix for the buttons not being fully visible/scaling properly on a KPL . See below how the "On" button is running off the edge? This is on a MBP 16" Running Catalina.

Sorry if I missed it... but is this now the final version people are using? I just bought 2 new leak sensors. want to try it out...

Quick update. This was a no go: https://www.amazon.com/Cooper-RF9537-NDW-Electronic-Voltage-Fluorescent/dp/B00S9KMF0Q Humming, flickering, general weirdness. On to the next one. The insteon dimmer continues to at least behave predictably. But them is ah hummin'

Good suggestion. I can try it. I didn't search too hard.. I'm sure there are ELV Z wave dimmers that cost less too. But a dumb dimmer test s worth a shot. I COULD live with hum (not sure about the wife)... but I'm worried about damaging the load... which is not easily reachable. I'm guessing there's no verified news about Insteon coming out with an ELV wall dimmer?

Hey Teken. How would a mico dimmer change the dynamic? Also, just curious would another option be to get something like this: https://www.homecontrols.com/Leviton-Vizia-RF-600W-Electronic-Low-Voltage-Scene-Capable-Dimmer-LVVRE061L I'd need to upgrde my ISY for Zwave... but I've been starting to feel like going down that road anyway.

I should mention... this is the light: https://www.lumens.com/silo-x20-led-monopoint-by-wac-lighting-WAC662502.html?utm_source=google&utm_medium=PLA&utm_term=&scid=scplpWAC662502&sc_intid=WAC662502 There are 5 on the track. The bulbs cannot be replaced (integrated into the fixture). Also, the track is 30 feet up and was installed with scaffold... which is now gone. Good times. I can confirm that a dumb on/off does not hum. I don't have an insteon relay handy but I could order one.

I just installed a new LED track light. Looks great but has a very audible hum when connected to an insteon dimmer. The electrician also tried a Lutron dimmer. Same hum. With no dimmer... no hum. The lights are rated to be dimmable with an "electronic dimmer". He even called insteon to ask but couldn't seem to get an answer regarding insteon dimmers. So are the compatible with "electronic dimming" load? If not... so I have any options? I'm guessing a relay would work but it's not ideal. These lights need to be dimmed at night.

So has anyone successfully added this to V4.62? I'm trying it now and it shows up as a node but I'm not see it show and status and no change when motion detected.

I'm curious. A few of you have mentioned that the Insteon dual band protocol is a flawed concept becasue line noise compromises both "bands". I don't want to get too far off my own topic but is that known fact or a strong suspicion? For me, I'm not contemplating a rip and replace. I have no experience with Zwave devices and I'm generally happy with Insteon despite the occasional failure and/or communication problem. However, I don't want to be caught flatfooted if Insteon starts to disappear or keep buying their stuff if the writing is on the wall and I've just been missing it. Thanks for all of you views on this. It's an interesting discussion. I should mention that more then anything, I hope UDI keeps chugging along! Even as a novice DIY'er, I find the ISY an amazing device compared to all the other nonsense out there.

As one of the first owners of the Commodore Amiga... I know what you mean Anyway... is fair to sum up you opinion by saying there's a lack of clear options at the moment and therefore, sticking with Insteon is not an inherently more risky option? @paulbates The HUB was the other thing I forgot to mention. Obviously that causes a long-term misalignment.

Oh no disagreement there. I think what I was trying to get at is is there a valid concern that UDI and Insteon's interest may diverge and/or that Insteon will simply not be able to compete other ubiquitous platforms that, for whatever reason, have more name recognition and acceptance. My preference (I think) would be to stick with Insteon products for exactly the reason you mentioned.

Apologies if this topic has been hashed out elsewhere. I'd love to get some opinions (or pointed to other relevant discussions) regarding peoples thoughts on Insteon v. converting to zwave devices on the ISY. The impetus for me is two-fold. First, I have a lot of old dimmers/keypads 8-10years--some of these are beginning to fail. It's not the failure itself that concerns me. It's more the question of whether or not I should just replace them with Insteon dimmers or reconsider the options. The second impetus was a discussion I stumbled onto in this forum regarding the new version of the Insteon Motion detector. The discussion alarmed me becasue it dispelled some pre-conceived notions I've had about the relationship between Insteon/UDI/Smarthome. The truth is, I've never fully understood the relationship but I'd assumed it was one of mutual proactive co-operation at the very least--maybe that's still the case. But That particular topic didn't make it seem that way. Also, I haven't spent a lot of time in the V5 forum but I gather that a lot of the upgrades have to do with more fully implementing Zwave? So it's entirely possible that these accumulated impressions causing me to question if I should be gradually, moving away from Insteon are totally misplaced. I'm not nearly as informed as most of the folks in this forum. So let me know your thoughts. They are appreciated.

Ah. Got. Thanks!

Hi all. Hoping to get some help on a program issue. The purpose of the program is to use the network resource module to announce a warning through my sonos system when motion is detected in my basement. However, despite the fact that I have a wait command after triggering the network resource, each time motion is detected, the announcement gets interrupted and starts over again. Screen shot of the program is attached. Thanks in advance for your help.

Hey stu. Well that's part of what's happening but the program flow has a lot of other elements. What I found way back when I first tried to set this up was that my LED controller Scene was also affecting my lighting scenes if the ose Lighting scenes were linked directly to the KPL buttons. Thus I unlinked them and used programs to initiate the lighting scenes creating that annoying lag. Perhaps there was something else going on but by limiting my LED controller Scenes to 1 button and 1 KPL, everything is working much better (lighting scenes are now directly linked to those KPL buttons.).

STU! Don't take this wrong way but I may be deeply in love with you. That did it! I realize what I was doing wrong in past attempts. The Scene I used to control the LED had more then 1 Keypad Link link button in it. I was trying to use 1 scene to control the LED on/state of the buttons on Both KPLs in the room that had the same function. I'm curious... how did you know that? Is there something fundamental that changes in a scene if it only has 1 member? Anyway... thanks to everyone who responded. I greatly appreciate it.

Hey guy. Perhaps I should have posted this first... but it wasn't really prepared with public consumption in mind. This link will show the program flow of what's happening in this room. https://docs.google.com/drawings/d/1e8B6I_0kkW5pUjdej1KJXiFBK2uG4YezmbCwz-ALHfU/edit?usp=sharing In essence. There are 2 KPLs that contral 2 main scenes; "All On" and "Dim". As several of you mentioned, the actual KPL buttons are controls their own scenes for that pupose alone--they don't control the lighting scenes directly. The program flow changes a variable as various conditions are met as a person switches between the 2 scenes. The only thing that makes it a little complex is that I have a "Day/Night" variable that, when changed to night, moves the room into the DIM scene--simultaneously turning off the "ALL ON" Buttons on both KPLs and on the "DIM" buttons. The program flow then also accounts for the scenario when my wife decides she doesn't want the room dimmer despite the fact it's dark outside.... SO if someone manually hits the ALL ON button again, it will stay there. What other details of the room would be helpful? Stu... that's very interesting that you have no lag... If I could simply solve that issue, I'd be set. Perhaps the issue is signal related as Lee alluded to, I'm going to try his test this evening.