paulbates

Hi and welcome to the UDI Forums! FWIW, you mention "Link a Remote Linc 2" in your initial post. That's not the keypad. If that's what you been using, its better to: New Insteon Device Add the 3 octet Insteon ID xx.xx.xx - printed on the device's label Autodiscover Paul

I like them. Have to put the jumper for limiting the sensing on a couple because they trigger from too far away.. I want to sense the driveway, not every car the goes by down street. If you use them outside, it helps to put a small bead of super glue or silicone calk on the left, right and bottom were the bezel meets the housing, keeps the water out. I've had some outside for several years now, right out in the open. Paul

Its been a while, but I think there have been times I've had to launch locativ after a reboot to get it to work, even though its location based background app. After that its fine. Since its a firm provided phone with an mdm container, it does get forceably rebooted remotely, and I usually know when that happens when I am forced to use my passcode to login. I restart locative then. Yeh not an ios fan either, but I will not carry 2 phones, so I have just my firm's provided phone. They let me pick my provider/phone/os (from tangoe). But from an app perspective, ios is the really the only workable option for integration and collaboration. I said "uncle" on this a few years ago and carry an iphone. You've probably looked at your logs, but I've found that the portal always sends the message to the ISY, but sometimes the 'if' of my ISY program was doing what I told it to do.. vs what I meant. Paul

Ok. my log shows it catching everything, with 2 caveats on use: things worked predictably when the geofence radius was a ~200 yards or more away from my property. It easier to know that the fence has been crossed, and it gives the longer than expected chain of events time to complete. Might want to try it with only one location app an see how that works. Not sure how multiple location apps running in the background get prioritized. Its location services are set to "allow location access always" under Location Services. Paul

I saw V2 announced recently and the associated android app, but not ios so I have to believe its not available yet. The good news is that locativ is in the app store and continues to work fine with V1 of the occupancy node. Not sure how you've defined the zone, but I know it works better for me if its a few hundred yards away from the house. Paul

Its not 100% clear, but this is not the first case. Either some are supposed to be that way in kit form and this was an accident, or they were tested and not reset. Paul

If the admin console shows it one way, but they behave another, its likely that those 2 came linked together and there's a link between those 2 in #4 that the ISY can not see. I would factory reset #4, right click it in the AC and restore device Paul

Yep! Rather than excluding things, like days of old, they "adjusted" the pricing. I kind of get the business problem... if its already discounted because of buying bulk, and then blanket apply a 30% discount on top of it... they can't do that. To your point, you have to keep track on many items to know if its really worth it. In the end, I do more projects with the same money, so like the old x10.com, I put some projects on hold and "play the game". I did get a few items on this sale and it was a good deal. In fact I forgot about one, went back Monday morning and it still worked.

This can be done with scenes as you are working on: Take the motions sensors down, and one at a time, put one in linking mode by pressing the set button for few seconds set the options in the admin console for the motion sensor to "Send on commands only". repeat for the second motion sensor You probably have this, a program that checks for either ("or") motion sensor to be "switched on" , wait and send the off to the same scene, assuming there is more than one light switch involved

This is indicative of noise. Unlike turning devices directly on and off, which generates acknowledgements, scenes do not have acknoledgements on the ISY. You can imagine what would happen in a scene that controls 20+ devices. All would try to deal with acknowledgements at once. I have a couple with 20, and more devices. A clue is that things are not being turned off by one device in response to the scene. Is that a switch with a load? Sometimes, turning on the load will allow what ever is being controlled to create noise. You can prove this by removing the load (unscrew bulb, temporarily unwire a fixture)... and repeat your original test. Paul

That's great. I'd prefer $27 obviously, but either one of those prices is very good for good quality switch, and keeps the total cost of implementing projects down.

They've been having major holiday sales on Insteon as long as I can remember. If you can be patient setting up your home, it saves a lot. Most of my 50+ devices were bought this way. Sales in the past would sometimes exclude a number of items, so I'm liking this sale for being "everything". Things do run out of stock at the sales because people by them up. If you're in the market, start looking at smarthome's site before a major holiday.

That's where I'm at. I don't need a notification from locative. I use pushover and its "apps" (folders) to organize notifications. In this case I should know that I'm in or out of an area.. I want the ISY to act accordingly I use notifications for key events or errors. I'll sometimes have more when I'm writing new programs and need to debug.. so its easier to figure out what happened when. But when things are working, i get rid of them

Yes. You'll want to make sure that its specs. 2000 watts, match the fan. Probably ok but I don't know In related news, I just bought a dimmer version of it because Smarthome is having a 30% off insteon sale through today. MEM18 is the discount code Paul

Yes, it should fire relatively quickly. GPS is declared to be accurate within 5 meters. I use my last iphone as a trail GPS frequently, and pictures of the same thing can have a location that fluctuates 30 feet. I think vertical angle to the satellite matters. It should easily detect and send its message within 10 seconds I would guess, worst case. The point is when testing, be sure to go 50 yards past the boundary you set up before turning around to come back. The app continues to work for me... and I'm using the latest version available on ios. Its like using an older copy of MS office.. it wont get better in any way, but it will continue to function the same for some time. The only risk I see is that its not being updated, and at some future point (years?) an ios upgrade will include/change something that requires developer changes. This app uses simple GPS and webservice calls, I think that will be a while. Edit: I went back and looked at locative settings. I was sure I had notifications turned off; I don't want them and I don't see them. However, they are turned back on in the app settings, but I don't ever see them. Web services call to the ISY Portal are definitely working every time. It makes sense that the notification and its success or failure would be based on a service... the locative web service that has since been shut down. Notifications can't be provided by the app any longer. That doesn't matter, the app can still detect where it is, and send web services call to the ISY Portal. I use mine to turn on my back driveway lights when I drive in and its continued to work. How big is the radius set? I set the radius at a few hundred yards so the message can make it from att through the ISY portal to our home network. Here is my event log for my phone for the last few days using locative. (The last one is 0/away as a I tested the locative link with safari, and had to set it as away to see it change in the ISY) I do know that to test it initially, I had to walk/drive out past the boundary and then come back. Others are using this (including rcolman, post above). If rebooting the ISY didn't help, I'd turn in a ticket.

My safari copy/paste of the link comes back blank too. Its a web service so that's normal. I never see anything on locative when its working. I may have shut notifications off. I'm wondering if the ISY needs to be rebooted as technically a nodeserver was added? I don't remember having to reboot, but don't remember for sure. I don't see how mobilinc would matter here, its strictly an ISY portal to to ISY relationship. I my radius @ several hundred yards, give the cell service etc, time to get the message. It was really good to get off of IFTTT Paul

You can copy the text out of locative and paste it in safari to test too. I just tried that and could flip it back and forth manually

Its been a while since I set this up, had to look at my phone. Also, I never did the Global http server so I guess I never did test, I just started using it. Not sure how big the radius is for yours, you may want walk / drive well out of the area and come back to get the app to respond to the GPS.

If you use V5 firmware, you can skip the 3rd parties like IFTTT and Stringify and use UDI's occupancy node. Even though they discontinued their dedicated web service, the Locative app remains available and works well for me. You can match that with the ISY Portal's Occupancy Node Server that is hosted in the portal itself. I'm still using version 1 of the ISY Portal's Occupancy Node. For that, when you set up a named zone in the portal, you can click the little blue arrow next to it and that will show you the https link needed to past into locative. You do need to be on V5 of ISY to use this, I think. It adds the node to the ISY. See screen shots below. Version 2 of the ISY Portal Occupancy Node Server came out recently but I haven't set it up yet. UDI recently created a specific app for this for android for V2 Occupancy node and I think I saw a post that said there would an ios one, but I don't know about either one or when ios would be coming. Locative is a little clunky to set up first time as you have to get those links on to your phone to paste them into locative. I opened the portal in safari. Paul

Yes, and to be honest, I migrated off of x10 a few years back so I've never tried it through the portal.. A node is a node I would think. @bmercier thoughts? Paul

Hi Bill and welcome to the UDI forums. Its not mentioned in your writeup-- you need to subscribe to the ISY Portal, use the portal to connect your amazon account, echo and ISY, and you need to add the devices you want to control individually to the portal interface, after adding them to the ISY as you have. Were those additional things done? Paul

Both event and error logs are available through the portal and can be cleared through the portal. You might find an answer there, either by using or logging into it with scripted automation. Paul

Scott, that would be great, or one of the wireless tag solutions. Given the history of this tread I assumed Insteon only. I have the Venstar remote sensors for my thermostats and they solve this problem perfectly use averaging. Paul

Brian I'd not want to "operate" on one of these electronically. Another option is to get another wired version of the thermostat, provide it power to run it so it reports temperature frequently to the ISY like a sesnor. Don't connect it to the HVAC system (since the wires aren't there anyway). Your programs would have to do the averaging between this new "remote" and the others, and adjust setpoints accordingly or whatever method you'd like. Paul

Sounds good. If you simply pull the wall plate and and un-wire the 3 way... then go look at the log to see if its stopped the storm. If there's no change, you've eliminated the switch as the problem and can wire it up. Buy a new 3 way only if its the culprit Paul