Interesting results. Created a local device using the IP address. That does allow me to save the alarm push message selection. I went out and walked in front of the cameras a bunch of times, had a long list of alarms on my phone lock screen. That was good. Once I selected one of those and it took me into the app, that is the only alarm trip I can see.
There is a message when configuring a local IP that the alarm messages aren't saved and will be lost when you close the app. That's not completely true in my case either. I have the one message in my alarm message list. I can close the app, lock the phone, come back in and that message remains. But the other dozen that were on my lock screen as alerts (and are in my message box in the "account") are not visible at all.
P2P connection - when I try to enable the alarms channel by channel, the settings are not saved and no error messages are shown. But, I found the Multi-channel alarm subscription page. If I go there and enable the alarms, when I touch "save" it comes back with a "Failed to Subscribe" message. Is this normal, or am I doing something wrong?
Ultimately, I think the local IP connection will work for my wife's iPad. It only has wifi and never leaves the house. She wants it to alert her, which it will do. But she will have to go to the Live camera view to see what is going on outside. I'm not sure that for her, for this application, she needs any more than this? As long as it makes some noise, flashes the banner on the screen, she knows to go look at the live screen.
I think for my phone, since I travel for work, I'll need the "account" configuration. If I'm with a client I can't be checking my phone. So I come out of the meeting and I can see the list of alarm messages and video clips. But I could be looking at this hours later, so the live view isn't going to help me at that point in time. (Unless I get the P2P to work without the "account" login?)