I get this every day. You just have to back out and then re-enter the app and it will reconnect. Unfortunately, the fact that the app won't stay connected means that grid outage notifications do not come through on my phone. The outage event is logged, but there is no notification unless you happened to be looking at the app recently and it is still connected to its server.
@jlankford Interesting (frustrating though). My app stays connected all the time and gives me push notification for events. I wonder if it is a phone "brand" issue or some other setting.
Sometimes the easiest solution is the best solution.
Sometimes not.
Neighbor 1 - Pixel 7 on T-Mobile, auto login enabled does get push notifications - Seen the error intermittently and the back out and re log in fixed
Neighbor 2 - Samsung Galaxy A-11, auto login NOT enabled, gets all push notifications - Has never seen the error to his recollection.
Me - Samsung Galaxy S23, auto login enables, get all push notifications - I have seen the error with the above-mentioned resolutions, have not tried your solution but if I see it happen again, I try it out.
That's what I found out anyway. Only semi common item so far would be the Pixel, but he continues to get notifications.
JB
Sometimes the easiest solution is the best solution.
Sometimes not.
Thanks for this info. I had assumed that auto login was necessary to get the push notifications, so it's interesting to see a confirmation that's not true. I have only ever seen one notification on my phone. As it happens, it was for a true grid outage. All of my backup testing so far, where I throw my main disconnect switch to simulate a grid outage, I have never received a push notification. The logged event history looks the same for all, whether it's a real or simulated outage - "No AC Connection" with a start time and a recovery time.
I receive a text notification from my utility when we have a real outage, so I haven't been too concerned about the lack of push notifications, but it would be nice to have it working properly.
@jlankford Grasping at straws here.... Maybe permissions? I know when I set up my phone app and it was asking for permissions, I am pretty sure I gave it access to my phone and to notifications. My phone also usually asks if I want to give permission always or just when the app is running. I am sure I would has said always but I cannot seem to find that particular setting on my phone.
The other thing I have played around with but only recently was the "App Notify" Button in the Web Monitor.
Configuration - Users - Action column - App Notify. This is supposedly another way to set the push notifications.
Might see if there is a difference between what it says for notifications and what you eg4 app on the phone says?
Like I said, really just grasping at straws though.
JB
Sometimes the easiest solution is the best solution.
Sometimes not.
@jlankford I have a couple of neighbors that also use the app. I will try to reach out to them and see if they have the issue as well. Might be a bit but I will post an update here.
JB
Sometimes the easiest solution is the best solution.
Sometimes not.
One time my Wi-Fi had decided to connect to the dongle instead of my house Wi-Fi. Still had cell service so it would allow me to connect to the web monitor fine for some reason. I set my Wi-Fi to the correct network, and all was good.
Also had the inverse issue happen, was connected to house Wi-Fi and was trying to local connect. Set the correct network and all was good.
The last time it happened it was weird though. Correct network, good signal, everything appeared fine. Had internet access could make wi-fi calls but would not connect with the app.
At that time, I rebooted my phone, turned on airplane mode to eliminate cell coverage, turned on Wi-Fi leaving airplane mode on as well, and all was happy again.
Once I eliminated the cellular network from the equation all was good. The next day it was working on cellular as well as local Wi-Fi.
I had assumed that my cell provider was having some issues. Read the following day that sure enough they were having some issues with some updates, and it was affecting DNS.
Hope this helps some,
JB
Sometimes the easiest solution is the best solution.
Sometimes not.
