Notifications issues on Android Phone - GNS and Gmail

I used to use GNS with my Android phone on the local network and had no issues. For the last 6 months or so I have not been able to get it to talk to my phone (coms error). This is with a new imaging PC and new phone - Pixel XL.

I have made sure GNS is passed thru the windows firewall (public and private) and set my router to forward that port. Still did not communicate. My Imaging PC is set up with a static IP as well…

SOLVED: It appears that either there was a bad install or a bad version of GNS (paid version) installed on my Android phone. I uninstalled and reinstalled it and now it is working fine. That is odd since I had tried the same thing a few days ago and it did not work.

Also of interest for those with Gmail accounts: I tried email and text but I have a gmail account with 2-step verification and there seems to be no way to get it to work with that. It will not allow access from less secure applications when 2-step is active (even following the steps suggested in help). I suspect there is no way to fix this issue w/o disabling 2 step verification, which I do not want to do.

Tagging @jaime to see if he has any thoughts on GNS.

As for email, I recommend creating a non-secure gmail account that you use ONLY for SGPro notifications.

I may do that! I would then guess one can whitelist the SGP address only?

Not so much an explicit white list, but with it, you can turn 2 factor authentication off and allow the account o be accessed by less secure applications without affecting your personal information. Keep in mind that you only need to use this account for the sender. You can have it send to any address you want without worrying about security. You can toggle the security level here:

https://myaccount.google.com/lesssecureapps?pli=1

Hello,

thanks for heads up, but really no clue, and no point to try anything now. Should work :slight_smile:

Hm, now that I think of it, the latest beta version won’t work with the older one, probably some kind of mix up?

This should be more clear in the next version, which I intend to publish before the end of the year.

This is only due to the firmware that you use and if any new update is rolled out the error will resolve. For more information go to https://errorcode0x.com/error-code-0x80070002/