Total Connect 2.0 users may have recently noticed some Push Notifications showing that certain events originated from "[External] ApiGee". This is the result of an integration that Resideo is configuring. These alerts usually originate from a third-party integration.
Resideo, also known as Honeywell Home, is constantly working to improve the user's Total Connect 2.0 experience. They're working in the background to implement suggested improvements provided by both customers and alarm dealers. ApiGee appears to be one of those integrations. We don't have any details about what expanded features this may include, but the work they are doing in the backend has caused a few odd Push Notifications to be generated.
In most cases, we've seen these push notifications associated with using Alexa in conjunction with the Total Connect 2.0 skill. You probably noticed if you are using Alexa to access and control your system that when you enabled the TC2 Skill you had to provide your Total Connect 2.0 Login and Password. This creates what's called a server-to-server integration. Once the skill is enabled and proper login credentials have been entered, you'll see an option to enable the skill for the alarm panel and automation devices and then the skill is ready to go. If you have multiple locations being used with a single TC2 login you'll only be able to select one location to access using this particular Alexa account.
When you ask Alexa, for example, "Alexa, ask Total Connect 2 what the status of my alarm system is." The server at Amazon uses the credentials you provided at the time you set up the skill to actually log into Total Connect 2.0 and query the system status. This, of course, happens very quickly. Currently, this log-in appears to sometimes be viewed as a user logging in and is therefore triggering a push notification. This will only happen if you have Administration type notifications enabled. Administration notifications include Login, Logout, Login Instlr-Read Only, and so on. However, rather than Alexa's access being logged as the person whose credentials were used for the integration, it is instead being logged as [External] ApiGee.
At the time of this writing, March 3, 2021 at around 6:00 pm, it appears the issue with push notifications may have been resolved. We attempted to cause one of these notifications so that we could obtain a screenshot, but we were unable to do so. It appears that in the Activity screen if you select the icon to Show Admin Logs at the top, you will still be able to see these events being logged. The Admin Logs is the screenshot shown at the top of this post. It's probable that these events are meant to show up here, but were never meant to produce a push notification. Hopefully, this relatively minor issue has been resolved, and whatever this new feature may be, it will be available soon.