InsteonNut

@Spencer Can you send me an email with your settings to support@mobilinc.com so I can help? Wes

Cert issue resolved. My apologies for the downtime yesterday and today for MobiLinc Connect Pro/HD users. Wes

Sorry folks. This is a cert issue impacting HD/Pro users. I’m working on it.

Hi @KHouse Yes! MobiLinc Pro and HD are still available and supported on iOS. Wes

Hi @jrainey MobiLinc Pro/HD on iOS is still supported. MobiLinc X is the newest app with multiple subscription and one-time purchase options available to suit your specific use-case and needs. The easiest way to see pricing and features that interest you is to download the free MobiLinc X app and open it. All pricing options are clearly listed in your currency. Feel free to email me at support@mobilinc.com if you have questions I can help answer. Wes

Hi @KHouse I'm still around! Answering questions, keeping servers running, and helping users. Wes

Hi @JSchumann FYI: I responded to your support email with additional information. Wes

Hi @theitprofessor I responded your to DM. Feel free to reach out to me directly at support@mobilinc.com if I can be of service. Wes

Hi @Geddy Yes, that Apple developer link is for a very narrow and specific use case where users on your app can request the location of another user on the app via a background push notification. This is presumably what the "Find My" app uses and Apple is opening this up for other 3rd party apps to use. Apple released iOS 15.2 beta 3 this week and so far, for me, geo-fencing seems to be much more reliable. It's not listed as a fix in the release notes aside from "bug fixes" so I can't say for certain that beta 3 fixes this, but it was a noticeable improvement over all other iOS 15 releases. Wes

Hi folks, Thanks @MrBill for that discussion link. Yes, Apple really has broken something with geo-fencing here that I have no visibility into. I'm running the latest iOS 15.2 beta and what I see now is iOS 15.2 telling MobiLinc that the phone has "left" the region, but iOS isn't telling MobiLinc when the phone returns to the region. It seemed more stable on iOS 15.1. At least there I got both Enter and Leave notifications to fire with MobiLinc. I'll keep testing their beta releases and update this thread should anything change. Wes

I received reports that iOS 15.0 broke geo-fencing but was fixed in the early beta of 15.1. Apple hasn't changed anything here with the developer API with regards to geo-fencing, so currently we're waiting for the release of 15.1 to the public to fix this issue Apple introduced. If you are able to run 15.1 and you still have trouble with geo-fencing, my best suggestion at this time is to delete your geo-fences and re-create these and turn on the geo-fence notification feature in MobiLinc. That way you'll know that iOS is telling MobiLinc when the boundary is crossed. If your ISY's variable isn't switching from/to 1/0 then you'll know it's a communication issue at that point and not a geo-fence issue. Wes

Thanks @lilyoyo1 The subscription fee is primarily there to cover my costs running the servers and support. Thanks for the pointer to the first post. IP Camera notifications I don't have any plans to bring to MobiLinc X. It's a surprisingly expensive feature to run and as such I had to price it separately in MobiLinc Pro/HD. I haven't seen the adoption or demand for camera notifications on Pro/HD in the years I've had it there to justify the cost, development, and other expenses in bringing it to MobiLinc X. I suspect that once the big camera players in this space like Ring, Nest, and others added similar functionally it somewhat took the wind out of the sails of this feature. Wes

Hi @marcinThanks for checking in! I don't have any announcements to share today. Is there something specific that's on your mind for MobiLinc X? Wes

Hi @jesusmr Yes! MobiLinc X is the current app and is still under development. I don't have any announcements to share at this time. If you have feature suggestions or any questions, please reach out at support@mobilinc.com Wes

Hi @palacekeeper The bundle is there for those that started with MobiLinc Pro and then want to "upgrade" to either Orchestrated MobiLinc or MobiLinc HD. The bundle allowed me to offer that upgrade path at a discount. Wes

Hi @marcin MobiLinc X is where all my development effort is. If you find that Pro served your needs better, then by all means hop back to MobiLinc Pro! Pro is still a solid app that a lot of folks like to use for different reasons. Integrating Push directly inside of MobiLinc X is still very much on the roadmap. But I don't have any announcements to share today. If you haven't already, make sure to upvote the features you want to see in MobiLinc X under the Settings tab. If something you want isn't listed there, make sure to email me at support@mobilinc.com so I can track what folks are looking for in the new MobiLinc X app. Wes

Thanks @uffy! This is consistent with other reports we've seen with this behavior. It was due to the Hue Emulator. Wes

@uffyDo you by chance have the Polyisy connected to your ISY and/or have your ISY port-forwarded through your router? Wes

Hi @vspete Yes, this is by design. If you background MobiLinc, it will hold the subscription for up to 2 minutes. We found that users would frequently go in and out of MobiLinc in bursts and going through the reconnection logic and syncing with the ISY was added overhead and a slower user experience. Instead, by keeping the connection alive for for a few minutes when backgrounded, this gives a better user experience during these burst activities. Ok, this is good and what I would generally expect. It is possible that the Watch will open it's open subscription along with the iPhone. It's also possible that the watch will re-use the iPhone's connection. If you only ever see 2 connections and 8 are open then there's something else going on with the ISY as detailed in your original post. This also mirrors my testing on this issue. I've never seen a case in the lab where the iPhone/MobiLinc and Apple Watch MobiLinc ends up eating all 10 slots. Wes

Thanks @vspete I checked 4.8.0 and 5.3.0 FW for the ISY and both still report a total of 10 sockets for subscriptions. Note that this is different than issuing requests to the ISY. You can see what's in-use by going to: http://ISY-IP-ADDRESS/rest/subscriptions from a web browser and logging in with your Admin Console username/password. What I don't know is if Node Servers also use this pool or not. My guess is that between iOS/WatchOS and the ISY the network connection isn't getting closed out in a way where everyone is happy resulting in the ISY holding onto old (dead) subscriptions and locking out new connections until either: 1. Old subscriptions expire and are cleared. 2. The ISY is rebooted to force all to clear. If this started with the latest iOS 14.3, then it seems likely that Apple has changed a behavior somewhere. Wes

@vspete A 2048-bit cert will take the ISY sometime to setup that SSL handshake. It's not obvious to me if that's the issue at play here or not, but three things I would recommend: 1. For performance, our MobiLinc Connect portal will give you the best connection performance with current best-practice security. Understood that you have ISY Portal. In that case, I would back off the cert back down to 512 for the best connection performance. 2. As a test, configure MobiLinc (and by extension, the Apple Watch app) to only use HTTP to eliminate HTTPS as a possible vector and test. 3. Update the watch to the latest OS (If not already). I'm not aware of anything that changed in iOS 14.3. What I do know is that if the subscription channel is abruptly cut off from the ISY, the ISY (the last time I checked and recall) will keep that "slot" around for 10 minutes before timing out and clearing the slot for another connection. The ISY has 10 slots. Between Admin Console, MobiLinc, Watch, and Node servers, this may fill up quickly especially if the Watch isn't network disconnecting properly. Wes

@vspeteI'm just now getting caught up on this thread after the holidays. How are you connecting to the ISY in MobiLinc? Are you using a direct IP connection or our MobiLinc Connect service? Have you tried both? Are there different behaviors? Wes

Hi @JTejera Wes from MobiLinc here. I haven't seen any issues with MobiLinc Pro/HD/OML or MobiLinc X and the 5.3 firmware with our one-time purchase options (direct IP) or our MobiLinc Portal integration. One thing you _may_ run into is with programs. The 4.x to 5.x migration completely changed how programs are structured. If you notice anything odd in MobiLinc after the migration, you can create a new profile in your older MobiLinc Pro app and sync cleanly with your upgraded 5.3 ISY to get things back into alignment if you run into any issues. Wes

Hi @marcin I'm sorry, I don't have a timeline. Updates ship when they are ready. Wes

Hi @marcin I've got a number of features in development. If you are a current MobiLinc X subscriber, please upvote the features you want to see under Settings->Feature Request in MobiLinc X. If there's a feature you want, but don't see listed, send me an email to support@mobilinc.com with the request. Wes