Im in a pickle. We lost power last week (Bellevue/Issaquah) everything
is back up and glorious. My Wyze ecosystem ROCKS <3 it!
But I dont know my new public IP I need to remote in take care of
some things.
The ISP is no help and I cant think of another way to learn the public
IPv4 address.
I know its not a Wyze problem or support issue (all Wyze stuff is
working just fine) BUT if Wyze could help me learn my public IP I
would really really appreciate it!
Can you please help me out here? I can/will (over) verify I am who I am if some kind of privacy issue.
I’ll continue to use and <3 your products and services either way! But please let me know if you can help here.
Go to https://www.whatsmyip.org it will display on the top of the page. Make sure to disable any VPN. You have to access the site from the location that you want to remote though.
I think the ask is for the public-facing (ISP-assigned) IP address for a location that is remote from the user’s current location. This seems like something that would be handled by having DDNS set up before a power-blip/IP-reassignment issue if consistent remote access is truly necessary.
Yes absolutely ddns would solve this in the future, but right now I’m without. Unless you have a time machine… And if you do DM me I wanna test drive it
Since I don’t have ddns setup, and no easy way of knowing at the moment though… If some internal support persons could help me out I would love it!
It’s not really a wyze issue and I know there are ways to avoid this (ddns, phone home scripts) but right now I’m just kinda begging and hoping.
None of us here are Wyze employees and can’t help you with that. Not sure what router you have but I have an Eero and I can access it from anywhere via the app. I usually remote in on my home computer and I always check the public address via Eero app, so never needed a DDNS.
Oh I was wondering if any Wyze employees look around in the forum.
I run my own custom Linux router so no app… and I just dont have DDNS setup at the moment. I was just reaching out in hopes that someone from Wyze might be able to help.
But yeah if its community folks w/o access there isnt likely a solution.
Its funny, I’ve been on a few IoT websites for devices I own (wyze, ring, tuya etc)… and if I take a look at network traffic the sites send physical location info back, my address, and my Lat/Lon even.
But none send public IP address along… when talking to the browser
Its probably a “security” thing… but dang physical Lat/Lon undoes that argument.
Yeah I did reach out with them… I have my modem in pass-through mode and they gave me the IPv6 address that goes to the modem. But my router gets a different IPv6 and ipv4 address. And the modem’s address is kind of useless I think.
I’m not sure if the tech person is able to give me my routers IP address. Kind of sucks because they definitely hand out the leases so they have to know somewhere, but I imagine that the support tech might not have that information.
I may call back and press them more but I don’t want them give anyone a hard time over it you know.
Does not help you currently, but if you have remote access software set up on one of your computer (TeamViewer, AnyDesk, etc), you can remote into that computer and use any number of websites that will give you your public IP. It’s a stupid name, but I always remember https://ipchicken.com/
I also have a couple of domain names that point to my public IP, so I can just ping one of them to get my IP:
C:\Windows\system32>ping newburghlights.org
Pinging newburghlights.org [47.156.109.11] with 32 bytes of data:
Reply from 47.156.109.11: bytes=32 time=4ms TTL=64
Reply from 47.156.109.11: bytes=32 time=74ms TTL=64
Reply from 47.156.109.11: bytes=32 time=72ms TTL=64
Reply from 47.156.109.11: bytes=32 time=2ms TTL=64
Ping statistics for 47.156.109.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 74ms, Average = 38ms
They might not be able to tell the IP if they can’t remote in to the modem/router. I was on DSL not long ago and called support to remotely reboot the router and they told me that they weren’t able to do that.
Asking the ISP for looking up your IP may be beyond the scope of 1st and 2nd level support.
Somewhere in the ISP infrastructure there is a DHCP server. In the DHCP server admin there will be a lease table. This will have the info that would show your IP. I doubt seriously that this is included in the scripts that 1st and 2nd level support has access to.
To future proof your issue do what @K6CCC suggested for remote access.
No no I mean so much metadata is able to be had from the Wyze APIs. But not the public IP. ie the Camera talks to Wyze servers and the Wyze servers know the IP that the request originated from. But they dont include that in the metadata that is sent to clients (browsers or phone) they do send back the lat/lon, mailing address, even local IP, etc… just not the public IP of the origin/cam.
Asus routers make this process very simple. They allow you tag along their domain, like yourowndoamin.asuscomm.com and is always active no matter how often your IP changes, as long as your router is connected. Then you can ping yourowndoamin.asuscomm.com and even set up your own servers.
I need to remote in take care of
