Chevelle

Thanks for the replies. I am dealing with fan controllers so they are installed in the walls. I can't move them around. The first fan controller is located in the same room as the EISY and Z-Wave dongle, about 18 feet away. This is the controller that IoX can see and it all works fine. An Aeotec Extender 6 is in the next room about 10 feet away from the first controller. The second fan controller is 12 feet way from that extender. Another extender is 12 feet way from the second fan controller. The third fan controller is 10 feet away from the second extender. These distances don't seem all that long. Leaving out the extenders, there is 18 feet between the dongle and first controller, 22 feet between the first and second controller and 22 feet between the second and third controller. I would think the controllers are close enough to talk to eachother, even without the extenders. Interesting observation... When I am at the second controller (living room ceiling fan), when I press the switch to turn the fan on or off, the green light on both extenders go on for about a second. That would seem that the extenders see the controller. (I cannot see the extenders if I am in the room with the first fan controller.) Any ideas?

I recently moved to a new house and am starting from scratch with a new installation of EISY. I have left over Aeotec Range Extender 6 devices as well as several GE Smart Fan controls. After adding the USB Z-Wave dongle, I was able add one fan to the system. It happens to be in the same room as the EISY. I have not been able to add the two additional fan controllers to the system. They are farther away but I would still think they would be close enough. I have not been able to add the Aeotech Range Extender 6 units either. Any thoughts? As a bonus help question, When the fan controller was added, the list includes the dimmer, scene responder, switch all, basic assoc 2, and basic assoc 3. I get the dimmer. That is the fan and it works fine. What are the others? Thanks.

So how is one to know all of this? If a feature is not available, one convention is to have the option grayed out. "Pro"?? That's a new one for me. I guess I'll have to look into what that is.

Oh geeze. Poor execution but let's go with that for now. So then why doesn't the ACTUAL buttons labeled "Write Changes" and "Write Updates to Device" NOT work?

I recently moved and am setting up a whole new system now that I have moved from the ISY994 to the EISY box. As personal preference, I like most of my lights to have a 2 second turn on and turn off rate. When a new device is added, it defaults to .5 seconds. When I use IoX and try to set the ramp rate, writing the change to the device doesn't work. I have tried using the "Write Changes" option at the bottom of the screen as well as the "Write Updates to the Device" when right clicking on the device in the device tree. However, it all works if I use the app on my phone. Any thoughts before I open a ticket? Thanks.

I have several different lights in the livingroom. Grandfather Clock - An Insteon on/off module that turns on and off the light in the clock Floor Light1 - One floor "up light" Floor Light2 - Another floor "up light" Table Lamp - a Hue color bulb in a table lamp Fan Light - The lights in the ceiling fan All of these respond OK with Alexa. I will group the two floor lights so that they both do the same thing when commanded instead of having to command them separately. I am not sure why, but things are working better now after fiddling with things. I am not sure if Alexa has "learned" anything or that I am now doing things slightly differently. I have an IoX program called DoSunset. It affects most of the lights on my system, not just the livingroom. It automatically runs 30 minutes before sunset. If it is cloudy, sometimes I want it to run earlier and so I have it setup to run by Alexa when I ask. If found that if I set the spoken word in the portal to "It's Sunset" and also set the voice command in Alexa to "It's Sunset", it runs. I have a "TV Time" scene for when I want to watch television. It doesn't work if I have the Alexa voice command set to "It's TV Time" but it does work if the voice command is just "TV Time." I had the same problem in my last house when I had scenes for watching television in the family room and for the home theater. "It's TV Time" and "It's Movie Time" did not work but if they were just "TV Time" and "Movie Time", they worked. Just quirks of Alexa.

I recently moved and am setting up my home automation from scratch. (I moved from the old ISY box to EISY.) After a few initial hiccups, I am adding more devices and integrating more with Alexa. One of my programs is called DoSunset. When it is 30 minutes before sunset, several of the lights in the house go on. It all works great. That program is also added to Alexa. The spoken word is "It's Sunset." Here is the issue. When I tell Alexa, "It's Sunset" it goes to the Big Sky skill and starts telling me about when sunset will be. My other programs are working fine with Alexa but this one gets fouled up. I realize this is an Alexa thing but has anyone else run across this and how did you get around it?

With all these meetings, I won't have any time to be addicted any more!

There is a saying in the radio controlled model airplane community.. "I'm not addicted to flying RC. I can stop any time I want to.... I just don't want to." I think it applies to home automation as well.

Talk about fast paced learning! It had only been a few days and I am into this big time. It is like some kind of addiction. A soon as I implement one capability it's, "OK. What's next!" All that is missing is a sinister laugh along with the wringing of hands. Anyway, I moved away from UDI Mobile and now do it with IFTTT and Webhooks. It took a while for things to settle down as I tweaked but it looks like everything is working as it should. I found that it was important to have a relatively large GeoFence to have everything work reliably. (In my case, the radius is about 1/4 mile.) Now, my garage doors close after I have left the area if I forget to close them before I leave (although with all this effort, I will probably never forget again) and the floodlights come on in the driveway when I enter the area if it is between sunset and sunrise. Cool stuff. Gotta go now. The Raspberry Pi just arrived to be used for PolyGlot (MmuuuuAhhhhaaaa)

Well then, this is really bizarre. I spent a good part of the afternoon setting up a program that was supposed to detect when I crossed into the GeoFence. When that happened, it was supposed to enable and run a program to turn on the driveway flood lights for 5 minutes and then turn them off but only between sunset and sunrise. I got it all set up and only tested it by manually setting the state of my occupancy on and off. I never tested it by actually crossing the GeoFence. I had to run an errand and when I while I was gone, sunset occurred. As I drove up to the driveway, lo and behold, the lights when on! So for an ap that doesn't work, it worked pretty well. Better than I thought it would especially because of the settings issues I mentioned above. I checked the links you attached. No clear solution. I can't imagine that there isn't something being used that is reliable. What about the location service in IFTTT. (I haven't done any IFTTT stuff yet.)

I am very new to all of this (just two days) but have gotten very far along after ditching the Insteon hub. I am thrilled with all the options I know have. Probably more by accident than by skill, I managed to install UDI Mobile on my phone and set up a GeoFence for my home. I also manged to connect it to ISY via the portal node server and Occupancy v2.0 (with UDI mobile). My presence (Android phone) shows up in ISY and have written a few simple programs that use this information. My questions are: Do I understand the settings in the app correctly? The phone pushes my status (in or out of the GeoFence) at intervals set in the app, like 15 minutes and that it will not report distance changes less than 100m? And reducing these settings reduces battery life? I guess I figured this app would work differently. The phone always know where it is and since it also know where the GeoFence is, why doesn't it just report when the GeoFence is crossed, once in and once out? Or am I thinking about this all wrong. Should I be using a different app to setup my GeoFence and report to ISY when I have crossed into or out of it? Thanks.

Thanks for the quick answer. I guess that means I don't even have to relist it in the portal.

After plenty of frustrating hours with the Insteon hub, it is now gone and replaced with ISY. What a world that has now opened up! After a day, I am surprisingly far along. All of my devices (Insteon, Philips, Amazon) are in the new system. Scenes have been created in ISY and routines have been created in Alexa to where everything works as it used to (except for the quirkiness from the Insteon hub.) Here is my question... I understand that scenes created in ISY have to go through the portal to be found by Alexa. No problem but what do I need to do when I just want to change a scene. The name of the scene stays the same as does the spoken phrase. Do I have to delete the scene in Alexa and from the portal and reload the new version? Thanks.