sdynak

Yes please .. At least her Mobilinc was still working on 14.XX .. With Locative it did not work today when she left so I think something with Locative is still not perfect even on earlier versions. I can try reinstalling but knowing what is happening on 15.1 I'm thinking just to let hers go back to Mobilinc for now. I had hopes for Locative as Mobilinc has not been updated in years and figure it was just a matter of time. Fingers crossed :).

I too have been plagued with the Geofence breaking in IOS 15 starting with Mobilinc so I switched my phone to Locative and it seemed to work initially so I set up my wife's phone which she is still on 14.XX IOS and it worked initially as well. Today the first test for both phones on a Monday leaving the home failed on both not updating proper status & running my programs. Not sure if the best thing is to wait for IOS to get fixed or try to work with the devs. I sent a message to Mobilinc support and so far no response. Have already spent so much time just to figure out what was broken (geofence) so getting exhausting but it would be nice to keep my system running where I use it.

?

Try to right click on the link and do a save as

This is the first link if you have the PLM ISY 994i Series including Z-Wave support

1st post in the install section

Thank you.. I ended up opening a ticked with UDI.. for the moment I am still on 5.0.16c and added a z-wave repeater. I have things working about 80% of the time but still get intermittent issues. I guess it is as good as it will get for now. I may eventually move forward with the latest at some point and if I have issues will give these suggestions a go. The problem is my ISY is already in the same room in line of sight so if things are that sensitive it will never be 100%.

My pleasure..

Check this topic:

Can't argue with that.. Just might be at the point.

Well unfortunately even after rolling back to 5.0.16c I am still having status issues with my Schlage. I tried factory resetting, excluding & adding back. I did get an error when I first rolled back and it seems related to the Schlage lock. Possibly because I had to exclude & include and maybe it had old info. One of the few things I have that I really want to be consistent and it just is not happening. I know this is not the right thread but I had some posts about 5.3.2 with similar issues. The only thing I have not done yet is factory reset the new dongle. Any thoughts if that will make a difference? Really not a big deal with only 2 devices. Thanks..

Oh boy.. that went right over my head LOL.. Got it! Thank you!

Yes.. I did a restore ISY with a backup from 5.0.16c and it stayed on 5.3.2. I then read some posts saying that the backups don't actually contain the FW and only devices, programs, settings and the like. Have had ISY for over 5 years and never downgraded or thought about it until now. I only have 2 Z-wave devices and my lock is no longer working sufficiently since I sent to 5.3.2 and unusable. That is why I want to go back on top of errors I got after installing (can see in a previous post in this thread)

Ok.. I asked because I just tried and it did not downgrade to a good 5.0.16c backup and saw something about goin backwards on FW you have to start from scratch & build back to the one you want. Not sure why it didn't work for me then. Thanks..

Is it correct that the only way to downgrade FW is by factory resetting the ISY & installing an earlier version from backup? Could you go right to the last FW you want? This is the first upgrade I have had issues over many years and want to downgrade to get functionality back. Thanks!

Cool.. I just might go that route and hope things get resolved down the road. We'll see.. Thank you

Thanks again.. Not sure if you know but do you think with the new board and 5.0.16 there would be any compatibility? Just trying to see if it is worth downgrading only to 5.0.16 and leave the new board and try from there.

Thanks.. I might go that route and see if it helps my situation.

Got it.. good to know. I thought the upgrades and 500 board would have helped and be ready for moving forward. Thanks

Thanks for that.. I only have 2 zwave devices.. My Schlage Lock and my Dome water valve. The water valve is working fine and I never had to do anything to it. I have factory rest my Schlage a few times now with varied results where it looked good but still hit or miss on status updates. I have not factory reset the 500 board. I only did the upgrade path with backing up & restoring. Initially it looked ok but had the status issues with Schlage. I did have some random issues before but this is significantly worse it seems. Did you factory reset the 500 board?

Great.. do you know if there any locks that are working well? Back on 5.3.0 and Schlage is still struggling with proper status. I do not have the Yale yet. It is not a distance issue.. I am 20ft with a clear line of sight from my ISY to my lock.

I contemplated it.. my concern is how busy they are and don't want to bog them down with this. I'm going to try a Yale lock and I'll wait until 5.3.2 is refined. I'm thinking I won't be the only one with the error hopefully so it will get sorted out in the refinements. If the error is still there when it is official I'll open a ticket. Thanks..

I went ahead and tried to upgrade to 5.3.2 in hope of sorting my Schlage lock status issues and got this after I logged back in. Any thoughts what to check? EDIT: Schlage coming up with unknown status now so didn't seem to help there either. It was at least working somewhat in 5.3.0 after a lot of work. Going to drop back to 5.3.0 for now. Never had errors like this in my past upgrades up to 5.3.0.

Were you having status update issues before this with your Schlage locks?