PB11

Hi All I've just realized my 2450 is no longer working since my migration from ISY994 to Polisy. I have looked through the forum and have not been able to find any comment regarding compatibility between Polisy and I/O Linc. Anyone have any experience with this? Thanks kindly

Well I took it as a chance to clean house. I used the alexa website to get the names of my previous devices and scenes and went through rebuilding them and cleaning Alexa up. I will test over the next few days to see how things are working. Now to Node server installation on the Polisy

Thanks @larryllix. I did do this step but the spoken have not transfered. When I now go back, my polisy is not the migrate from option and my old 994i is the migrate to option so I'm not able to run it again.

Hello All I've read through all i could find, but the migration (restoration of backup) of my 994 to Polisy has resulted in my Amazon spoken missing from the Portal Amazon Tools. The nodes are visible, just the spoken configuration is missing. My polisy seems to have all the nodes from my previous isy. Have updated preferred isy, updated ISY skill in alexa and still no luck. Polisy seems to be working otherwise. One thing i have not been able to configure is the IP of the 994. These settings are greyed out on Polisy Admin Console. If i need to rebuild I have exported the topo, but am uncertain which is the amazon spoken. Also, I failed to make note of my Node server slots. Any way to recover this info? Any suggestions would be much appreciated.

Fair enough. Hadn’t realized 15.1 had been released. I’ll make sure I don’t upgrade either of our phones until corrections are made The other variable is that I’m using poly cloud. I uninstall the Node server and reinstalled it re-creating my Geo nodes not certain this had anything to do with locative coming back online but at the time Michael did say some of the node servers were having issues sorry I couldn’t be of more help

I was having the same issue, but upgraded both my XR and my wife’s XS to the most Current version of iOS which is 15.0.2. In addition I completely uninstalled and reinstalled locative once the update was done. Based on a recommendations from another forum user I copied both the enter and exit URLs before deleting Locative Both seem to be working quite well now.

Wait, that wouldn't let me set conditions based on one person already home or me just arriving home. The "LakeHouse" status would be True when the "If" statement is assessed in either situation. Correct? I will keep the universal "home" status in mind though. I hadn't considered that.

Maybe its the way I'm utilizing it in the programs that needs to be adjusted. Rather then looking at it as an individual status, the "Home" dictates the status. Ok. I'll try a few tests.

Wait, I think this is what I already have set up. Or is this something different?

Really, that easy? And this would cover either of us home and one arriving home. Ok, before I go any further on this, I'll definitely check it out. Thanks very much.

Ok, clear on the (). Thanks for that. Regarding the "If", So PB geofence changing to false, and AP Geofence still at false, will execute "Else". So this would result in my light coming on when no one is home?

Hello All I'm hoping I can get someone's opinion on this little program. I've previously run this successfully without the else, but I found as my wife came home and I was in the kitchen it triggered the changing of my kitchen to coming home lighting. I've now created a second PB Arriving Home which will not change the kitchen lighting if one of us is home. What I'm not certain about is what triggers the assessment of the "else" statement. My assumption is that the "Else" will not be considered unless the "If" is triggered by the changing of our geofence status and the "If" criteria not being met . Is this correct, or will ISY run through it based on something else? When is it correct to group "if" statements in "( )" Thanks very much

@MrBillNice find. I'll give this a shot once my lovely gets home from work. Thanks!!

Ya, it actually seems like the XS may have a different touch capability compared to the XR. I wasn't able to see anything online.

Ya it’s all up to date. First notice wife’s IOS was out of date so uninstalled Locative, did IOS update to 15 then reinstalled and reconfigured Locative. when I long press it takes me Into location settings. have tried long press, short press, hard press. No joy.

Wondering if anyone knows if the long hold “trigger event” feature on Locative should be functional on all iPhones? it seems to be working on my XR but not working on my wife’s XS.

Ok, so I am using locative with Occupancy. Its all in the details. Completely overlooked this one. @MrBillOccupancy it is. I'm an IOS guy. Thanks for clarifying that . Also took the steps of running the long hold arrival as suggested above but did not see any status change. Yesterday I went for a drive with my UD app open to my geofence nodes and watched as both my neighbor hood and ios device node status changed. So its not locative, but MyQ that is having issues. Working on that from previous string here.

Hi @MrBill. I so leave it open at times, but would say that I reboot at least once a day. I'll keep an eye on it and see when and how often it happens. Thanks for the reply.

@MrBillThat is a good question. Here's a dumb one, how would i know? I have attempted a few ways until i got it working. I believe its Geofence as the (Mobile Device) which I assume refers to the app wasn't available for iphones when I originally set it up. Is there a benefit to either? Side note: Do I need to @ someone when quoting them or are they notified simply because they are quoted?

@larryllixplease let me know if you really don't want to head down this road, but I've just spent some time trying to understand the above. I'm a little dim over here. So what command would you give to trigger the StateVar change? It seems like you would need many programs to account for all the "Then's" that you might want. i.e levels of dim Then "Turns on an insteon scene to 50%, or 60%." Am I not grasping the logic here? and is the "Else" triggered with the same command. So if "Turn On Insteon scene" is already on, the "Then" is skipped and the "Else" is triggered which turns it off? For example. I'm with my approach I'm having a difficult time with the following. In my kitchen I have I have 16 pot lights which are split between 2 main powered switches. This obligates me to group them as a scene if I want to turn the entire kitchen lighting. By grouping I lose the ability to dim. I was trying to build a program such that if I turned on If kitchen light 1 main > off Then kitchen light 2 main = kitchen light 1 main. I was unable to find a setting that would allow me to have one device mimic another's state. I'm trying to understand how i could apply a statvar to this problem, but have only used Statvar on a vary basic level. This really seems like it might be the next level of what ISY is capable of. Maybe its that I just don't have the knowledge of programming logic.

I've been having this weird little overlay windows popping up on my Admin Console the last several days. It seems like its the tail end of my device list, but is in a separate window. When I click on it, the underlying fields come forward and this window seems to disappear, but the Devices in its list are still missing.

Wow. I have a hard time conceptualizing it. I need to spend more time gaining a deeper understanding about the guts of ISY programming. I like the sound of this. Again, beyond my comprehension at the moment, but I'll keep plugging away at it. @MrBill You are absolutely right about the mindset and that I was using Alexa as the controller. In parallel I was also trying to thoroughly configure my ISY, which was just causing conflict between the two controllers. I had originally started out with an Insteon controller, which was limited at best, but relied on Stringify for the heavy lifting. Sadly, once Stringify was shut down I lost most of my automation functionality. I decided to revisit the ISY I had been using on a very limited bases at another property. I had no understanding of its capacity at this time. Because of what seemed like ISY's complexity I embraced Alexa for its simplicity and similarity to stringify. My reasoning for the diatribe above was to maybe prevent any newcomer from going down the path I did and wasting all the learning hours on utilizing Alexa when I could have been focusing on ISY. This is not to take away from what Alexa has added to home automation. Honestly, if it weren't for this forum, and the power players on this forum, @MrBill @larryllixand several other contributors I can't currently think of, I wouldn't be utilizing ISY the way I currently am. ISY is powerful, but the real power is in the people who share their experience and knowledge. Guess I was just trying to contribute and payback all the assistance I've been given.

Hi All Let me preface this by saying, I am happy to delete this topic if is proves to be more confusing then helpful. I'm just brain dumping so I'm not certain how clear this will be to anyone but me, and the entire topic may not even be an issue for others. If anyone thinks there should be more clarity please let me know and I'm happy to edit. There are others on the forum with much more knowledge then what I have to share regarding this topic, and much of what I'm writing down has been gained from much help and input from others over the past year, but I thought I would put this into text for anyone who might be playing with a similar setup. My take on ISY Scenes, Alexa Groupings, and Alexa Routines is as follows. My initial setup was to create scenes on the ISY Admin Console, as well as Groups and routines in Alexa. The biggest hurdle was with my multiple 3 way switches By grouping any 3 way switches as a scene in ISY i.e. Kitchen Lights removed any ability to control switches on an incremental level, i.e. dimming room lights. I initially thought I could name all 3 switches "kitchen Lights" and that Alexa would send the command to all 3. This was not the case and in fact caused Alexa to see multiple devices of the same name and therefore return the error "There are multiple devices with this name, which one would you like". To get around this, I named the switches after the room followed my a number and the scene after the room light i.e Scene Name = Kitchen Lights Light Name = Kitchen Light 1. This adds difficulty when attempting to control any single switch via voice command. "Alexa, set kitchen light 3 to 50%". Functions, but not ideal. If I also created groupings in Alexa with the same room name to gain control over things like Sonos Room Grouping, it created another naming conflict which was difficult to trouble shoot and locate when trying to solve the "There are multiple devices with this name" or " The command is not possible with this device" (wording approximate)" I then thought that Alexa Routines would be the best work around, and found that creating multiple scene routines for each Room with the different settings I wanted was the way forward. i.e. Dinner Kitchen, Night Kitchen, but this quickly became too numerous to remember, and difficult to manage when returning months post creating routines. It was hard to remember my logic as well as commands for each scene. I'm sure there are several other approaches I tried, but its all a big mess in my head now. In the end. In the end I found that keeping most of my configuration within ISY and being more selective on scenes and the naming of scenes in my isy, gave me a more accurate and incremental control on lights via Alexa. In ISY Using the main power switch in all my 3 ways, I named it after the specific room i.e. "Kitchen lights", then the remaining 3 way switches, Kitchen Lights 2, Kitchen Lights 3. I also created a Scene named after the room i.e. Kitchen. This setup lets me dim lights by using logical light name i.e. "Alexa, set kitchen lights to 30%", but also control the entire room as a whole i.e. Alexa, turn off kitchen, without any further setup required in Alexa other then syncing devices and scenes via the portal. With this said, it is nice to have a few additional scenes for specific moments. i.e. Alexa, turn on Cooking, Alexa, Dim house. Approaching things in this manner, has significantly reduced the number of routines or groupings needed On the Alexa side as Alexa will interact with the ISY scenes as rooms/groups anyway. I also only introduce the switch with main power to the Alexa list of devices to reduce number of devices to manage and to simplify and increase accuracy of voice commands. In Alexa Minimizing configuration in Alexa, ie. very few groups if any, only primary light switches, and no granular routines made for the cleanest and most accurate functionality. It also really simplifies making changes or adding functionality which are primarily done on the ISY. I've also noticed a significant uptake and understanding of commands throughout my family with this cleaner setup. My motto now is, Less is More. Not sure if this offers any clarity, and again am happy to delete should this only make things more cloudy for some. PB

@Geddy Just an update, things seem to be syncing on their own at this point. Thanks for helping me out on this one. All the best.

Greetings All I've had Occupancy setup for a year or so(can't remember which version i.e. Occupancy, Occupancy 2(Mobile Device), Occupancy 2(Geofence) and uncertain how to confirm this), and on the most part has been pretty solid. Once in a while, today being one of those times, the status of our 2 iphones is not accurate. What I'm wondering is if there is a way to force a status check? I've attempted to run the "If" component of my geofence program but I think its really only checking on the existing status not actually confirming the status I've used the "Query" button on the Admin Console Main Page for the iphone Geofence node, but nothing seems to happen with status or in the Event Viewer. Would anyone be able to shed some light on this one? Thanks very much Peter