TexMike

I checked the teenagers iPhones when they finally got out of bed. They are using GET and I copy the URL's from the portal and text it to their phones and past into Locative. Have you considered using UDMobile instead of Locative? I don't use iPhone, but I've seen good feedback from iPhone users on the forums. Locative works fine on the kids iPhones, so I've never pursued it.

If your seeing the PIN request, I think you are using the old nodeserver that required a depreciated app. Make sure you're using Occupancy 2.0.

To debug, use the occupancy portal URL's in a browser to manually report in/out if that works you know the issue is with Locative, if it does not then you know it's the portal/nodeserver configuration. My occupancy 2.0 nodes show in the AC with a motion sensor icon. P.S. I just rebooted after the disabled programs update and wanted to highlight another feature of using the Occupancy 2.0 nodeserver. Geofence status is held on the portal, so my run on reboot program queries the nodes and gets correct geofence status for all phones. So, in addition to handling the logic for anyone home and all away, it gets accurate current status on reboots.

On is inside geofence, Off is outside. Using UDmobile configure the Occupancy 2.0 nodes to on for entering geofence and off for exit. For Locative click on the blue box/arrow for each device in the portal to get the URL's for report in/out and use those to configure Locative. Wife and I use Android and kids iPhones and it all plays well together.

@Chris Jahn also posted an interesting technique for keeping track of disabled programs, run at startup, etc. My Polisy did perform the OS update, I updated early after the release because I was having an Admin Console issue and support suggested the update. I had to use my text backup file of programs to determine enabled/disabled status and it was very time consuming. I'm going to adopt one of the techniques so I never have to go through that again.

I had the opposite problem on Polisy, all my programs were enabled. Fortunately, I had a text copy of programs to reference. I will use naming nomenclature for disabled programs to avoid this mess in the future.

OK, now I see how to add phones to V2.0 w/o using the old app and pin. Now I can set it up like before with UDMobile directly setting the node status and Locative for the iPhones. Thanks, Mike

If I understand correctly the version 2 only works via an obsolete app. I'm using the Occupancy server which allows updates via https://my.isy.io/api/location/key/report/in or out. However, after the new installation on IoX the nodes seem to be read only even from AC. See below.

Hi @Javi, I just finished migrating from ISY to IOP and need to reconfigure occupancy. I was using UDMobile to directly set the occupancy nodeserver node status based on geofence. I'm not sure what changed, but now occupancy nodes seem to be read only from IoX and UDMobile. I would like to continue to use the occupancy nodeserver for multiple reasons. It handles "all away" and "anyone home" logic, all my programming is set up to use it and the kids iPhones are using locative and it works. My wife and I are on Android using UDMobile and I know I could set the kids up on UDMobile with restrictions, but locative just works and I'd prefer to just leave it as is. I thought of setting up a network resource for UDMobile to trigger https://my.isy.io/api/location/key/report/in or out based on geofence, but I can't seem to get the network resource to work. I tried to follow your notification Wiki example, without success. Could you please show me the proper network resource configuration? I know this adds another network operation, but can't think of another way using the occupancy nodeserver. If you have a more elegant solution, I'm all ears. PS: Excited to try the notification nodeserver now that my configuration supports it. Thanks, Mike

Any update? I was ready to migrate from ISY to IOP, but decided to hold off because I'm mostly Z-Wave.

@JaviI've been running on two Pixel phones for a few days now and it's working great. I did not enable UD Mobile Location Services or change polling. Both phones do have a car insurance app running that may help to keep location services updated and both phones were previously using Google assistant geofences. I turned off the integration with UD, but did not disable the Google assistant geofence. Two kids are using iPhones with Locative, so I just set occupancy node status from UD Mobile on the Pixel's and let the node server handle the logic. I'll probably leave it that way since it's working. In the future if UD Mobile gets the ability to restrict access, I may put UD Mobile on their iPhones. I could just tell them never to mess with UD Mobile and they wouldn't, but I'm hesitant to set them up with full access just for general security reasons. Thanks for the great work on UD Mobile, Mike

Agree, I don't use my downstairs stat temp in any of of my comfort settings. Like many houses it's in a bad location, in a hallway under a return air intake, I only use remote sensor temps to get a more accurate reading and prevent short cycling. However, it doesn't seem to address the original subject of eco+. The temp displayed on the ecobee is based on sensors participating in the comfort setting, not the reading on just that stat.

Is the eco+ icon showing up on the stat? Anytime a setting is overridden by eco+ the icon will show on the stat. Are you sure it's not because temp is not above cooling differential? I have cooling differential set to 1 and it's not uncommon to see +1 on the stat for a while before A/C kicks in.

I got eco+ pushed to my two stats over a month ago. While I also don't like "features" being pushed on me w/o my control, you can effectively disable it by turning off all the functions one by one. Personally, I kept the "feels like" function on and turned all others off. With wild swings in humidity here in Texas, adjusting temp based on humidity is a nice function to have.