upstatemike

I am thinking of pre-ordering a Polisys but have never used Polyglot so I want to be sure it will address my need. I'm looking to use Insteon KeypadLincs to control Hue or Lifx lighting in a given room such that each Keypad Link button directly sets a specific scene (color, brightness, etc.) for the room without any reliance on Internet connectivity. Am I correct in my understanding that a Polisys will let me set that up in simple ISY programs (no complex scripting or programming)?

Yes the firmware and UI match.

I enrolled it by selecting the New Insteon Device icon and entering the address with "Remove existing links" checked. It created 2 devices, Closed and Opened. No Heartbeat. Have not updated from 4.5.4 because I haven't seen anything in the change log that really applies to me. I'll try a hard reset to see if that affects anything.

Sorry if this is already answered someplace but I couldn't find it. I just installed an On/Off sensor REV 1.6 into my 4.5.4 system but I can't get it to work. Both Closed and Opened devices always show as on and do not change status. I can see in the event viewer that ISY is getting the signal for each on and off but no status change on the devices. Do I have something configured wrong? (There is nothing on the external sensor terminals and the little jumper inside is in place.) If I hit the reset button the status of the Opened device will go to off until the next time I cycle it with the magnet then it stays locked on again after that.

I had to first enable it and then disable it again... don't know why it was working if it wasn't enabled but in any case everything went smoothly after that.

I just tried to follow the update instructions for V3 and am stuck on the first step. I cannot disable any older version of the ISY skill because none are included in my list of skills. The devices exist, and they respond fine when I ask Alexa to control them but the skill is nowhere to be found. The Alexa App (PC version) says I have 20 active skills and that matches the count in the list presented. None of them are ISY yet the ISY commands function fine. What do I do now?

I understand what you are saying but sometimes I'm not trying to force a particular state... I just want to know what is going on (or what ISY thinks is going on if I suspect the answer will be different from reality). Is the reason there is no way to check due to a limitation of the Amazon API?

I am also looking for the ability to query status via Alexa. (Alexa, what is the status of the basement lights?). I am not having any comms issues, I just want to verify if a light has been left on in a given area. Is the lack of status due to a limitation in the Amazon API? If not, is this a feature that could be added?

Working great but I wish I could ask the current setting of a thermostat before deciding what to change it to. At least if you say "raise the kitchen furnace 1 degree" Alexa will respond with the new set point so you know where you are.

I don't like the tone. If I talk to a voice interface I expect it to talk back.

Due to power line interference I ended up placing my PLM on a dedicated outlet about 75 feet from my ISY. I used Cat5e from Home Depot to do the run. It has been working fine with absolutely no issues at all... probably because I didn't know it wasn't supposed to.

I couldn't find a way to retrigger the timer to keep the light on as long as there is motion when the logic was in the Elk so I did it all in ISY. Response time was the same in both configurations when I was testing which way to go.

Sorry I have to disagree with you on that. My family is tired of general purpose devices that do a little of everything but none of them well and are especially tired of app based interfaces that require them to wake up a device and launch an app to do something that should only require a simple button push or voice command. The Nucleus hardware is a lot cheaper than iPads so you can afford to put them throughout the house and is also powered by POE which makes better sense for an intercom devices than iPad style chargers. Also an iPad is really designed to be carried around to different locations which is kind of the opposite of how you use a whole-house intercom system.

I've asked Emily to see if she can get some clarification from the Nucleus CTO.

FYI I got the following reply from Emily at Nucleus: "...I conferred with our CTO about your Universal Devices question: we are integrating with Amazon Alexa AVS and will be able to support the Universal Devices integration via that compatibility. There is a caveat: the current Alexa AVS does yet include the Universal Devices capability but should at some point in the very near future. So Nucleus will be able to be a dashboard for your Universal Devices hub perhaps not in the first iteration of our software but hopefully in the second or third."

Maybe the recent Echo Connected Home integration will help highlight the value of a collaboration with UD.

Now that Echo integration is working so well how about an integration with the Nucleus Smart Home Intercom system? They claim they already work with Insteon (I assume via Smarthome hub) so an ISY integration would make good sense. http://nucleuslife.com/

Solved it. Your point about wireless motion sensors only sending on helped me find the problem. Since alarm motion sensors will transition back to off or secure before the wait statement completes the second program was switching to False before the off command for the lights was executed. Switching the trigger on the second program solved it: If Status '1stMid / FrontHall:Sensor' is ON And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- (motion on/off logic is still reversed when using IOLincs) It also works fine now with Elk inputs: If Elk Zone 'Front Hall Mot' is Violated Then Set Scene '1stMid / Scene:FHallMotion' On Else -No Actions- If Elk Zone 'Front Hall Mot' is Normal And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- I don't know why it worked before but I probably had it right and then changed it at some point.

I have a pair of simple programs I use to control the lights in my front hall and this has worked great for years but now suddenly they won't time out and shut off. The programs are very simple where the first one turns the light on when motion is detected: If Status '1stMid / FrontHall:Sensor' is Off Then Set Scene '1stMid / Scene:FHallMotion' On Else -No Actions- And the second one waits for the timeout period and shuts the light off unless I have turned on a keypad button that I use to lock the lights on: If Status '1stMid / FrontHall:Sensor' is Off And Status '1stMid / LivRm:KpdD' is Off Then Wait 30 seconds Set Scene '1stMid / Scene:FHallMotion' Off Else -No Actions- Suddenly the off command never executes and I can't figure out why. I verified that all of the links are right in each device and the communications is good because the status is accurate in the admin console. I have two different locations with the exact same problem but I also have several locations using the same program with wireless motion sensors instead of IOLincs and they are still working fine. I did just update to 4.3.26 but I haven't seen any report of a bug that would account for this behavior so I'm not just blaming the firmware. I also tried connecting the motion sensors to Elk zones instead of IOLincs to trigger the programs but I got the exact same issue... the lights go on but never go off. Sometimes I can shut the lights off from the admin console and the programs will cycle correctly exactly one time on and off but the second time the motion is triggered they just stay on. Can anybody see a problem in the programs or something else obvious that I'm just overlooking?

I have 3 Nest thermostats and like the look but otherwise am not entirely thrilled with them so have been researching Lyric and Ecobee3. At the end of the day it seems all of the nice looking designer thermostats rely too heavily on external Internet connections to provide core features like operating them from secondary locations in the house. (I have some trouble negotiating stairs and it is a big deal for me if I have to go to a different floor to adjust the thermostat because the Internet connection is down.) I used to use RCS serial thermostats connected to a Stargate controller which worked reliably but were not very attractive. In the end I suspect I'll end up going back to serial stats.. maybe HAI thermostats with remote display controllers on each floor. At least these can be connected to an Elk M1 and will not have any dependency on Google or the Internet.

Will the UDI PLM have a larger link capacity than the Smarthome one? Will it have a faster processor so it can find matches in the table faster?

Thanks but this is a controlinc not remotelinc. Ended up manually linking it to an appliance moduel then reading the link table to discover the new address.

Once again am having a Controlinc challenge... This time I pulled a spare off the shelf to replace a failing unit and discovered there is no address label on it. How do I "discover" the address on a Controlinc?

I'll give that a try eventually but for now I just dug out an older version ApplianceLinc and used it from the same location with no issues at all.