KE7FNS wrote: ↑Sat Mar 06, 2021 9:47 pm
The Nextion gets its information by what the OS reports.
I would be curious to see what the MMDVMHost log reports for your IP address.
I don't know how to get those logs.
n3jf wrote: ↑Sat Mar 06, 2021 8:35 pm
I don't need to do that. I can see that it's connected. It's on my router. It's passing DMR and DSTAR traffic. I can access the pi-star dashboard. The dashboard shows it's connected.
If you took a few minutes to do what I suggested, you would see exactly what the OS reports, and could compare that with what the MMDVMHost log reports. They should be exactly the same. That would at least narrow down where the problem is at. OS, MMDVMHost, Nextion programming etc.
Well, I can SSH into it, but I don't know what to do once I'm there. Like I said, this is my first pi-star system.
n3jf wrote: ↑Sat Mar 06, 2021 8:35 pm
There is no Ethernet port on the ZUMspot.
If you have no ethernet port then you must have a RPi Zero W and you can still use a microUSB to ethernet adapter plugged into the inner microUSB port on a RPi Zero W.
...if I had one...
n3jf wrote: ↑Sat Mar 06, 2021 8:35 pm
Right, I agree. That's why I said "apparently". It apparently ignored it, because it didn't connect to the router, and it didn't start beaconing its SSID after it couldn't connect to the router. As you correctly said, it *should* have beaconed the SSID after it couldn't connect to the one and only router to which it could possibly have connected. But it didn't.
That is also impossible, it doesn't just randomly decide to ignore it if it wants, computers don't work that way. If there is a file named "wpa_supplicant.conf" on the boot volume it always moves those settings to the proper OS location, and deletes the file on the boot volume. It completely overwrites your old settings on the OS.
Yes. Unless, maybe, there's an obscure bug in the code..
You also keep contradicting yourself, at the first part of your last post you state it WAS connected to your router because you could see it in its settings. If it was connected, it CAN'T beacon a wifi access point.
Nope, I'm really not contradicting myself at all. I've given a lot of information in my posts, so it's quite possible that you've missed some salient points. All of this I've said before:
It wasn't connected at all, in any way, but the ZUMspot display showed it was connected as 192.168.1.111.
It wasn't connected in any way and the router showed it was not connected in any way (no matching IP or MAC addresses).
It was not connected in any way and my wifi sniffer was unable to find it beaconing its SSID, ever.
It was not connected in any way and neither my computer or any other 2.4GHz wifi-enabled device could see it beaconing, ever.
I was unable to use a browser to connect to the IP address displayed on the ZUMspot, or SSH to that IP address.
My new router is defective. I've said that. It's going back. A new one will arrive later today. This current router does one of three things:
1) I allows 2.4GHz connections WITH internet (very infrequently).
2) It allows 2.4GHz connections WITHOUT internet (very frequently).
3) It refuses 2.4GHz connections completely (very frequently).
After leaving the router on overnight and firing up the ZUMspot this morning to do more troubleshooting, the ZUMspot successfully connected to the router. I now see an IP address on the router for the ZUMspot (192.168.1.223) and it has the matching MAC address of the ZUMspot. Consequently, I am now able to open a web browser and connect directly to the ZUMspot using the IP address on the router (192.168.1.223), but NOT at the address shown on the ZUMspot's screen (192.168.1.111). The existing browser shortcut also works - it didn't yesterday. Every method of connecting to the dashboard that failed yesterday, works today. The ZUMspot's display still shows the wrong IP address.
All of the above I have already said.
n3jf wrote: ↑Sat Mar 06, 2021 8:35 pm
But that's the point. It did NOT connect to a wifi signal. There are no open wifi access points for it to connect to. None. The only way it could connect would be for it to provide a WPA pre-shared key, which it would not have... with one exception, the pre-shared key for MY router. It did NOT connect to my router (see above). It did not beacon its SSID. I know what you're say... I should have done all the things you say, and I agree, it should have. But it didn't.
It was not connected! I'm not sure how much more clear I can be. The router did not show it in its list of connected devices. A network sniffer could not find it. There was no way to connect to the pi-star interface. But it still showed an incorrect IP address on the screen.
Again, I agree, it *should* see it. But it never beaconed its SSID.
Since there are no open access points, it would require a WPA PSK to connect to any of the available routers. It does not have any PSKs, only the one I gave it to my router, which requires it. It was not connected to my router.
Again, you say it wasn't connected, but yet you said you see it in your router...... Both of those cannot be true at the same time, it is a mutually exclusive condition if one is true the other MUST be FALSE.
I AGREE, that would be impossible! If that was what I said. But it isn't. You seem to have missed a lot of the information in my posts, which is why I have continually had to repeat it in subsequent replies.
n3jf wrote: ↑Sat Mar 06, 2021 8:35 pm
Again, that could be. But since I have a bookmark for the pi-star interface, which has worked successfully since day one, something would have to have changed on the pi to suddenly make it incompatible with the bookmark. Also, there's no evidence at all to suggest that the browser (actually, 2 browsers - Chrome and Firefox - and an iPad running Opera, and an Android phone running who knows what browser) had suddenly decided to force an https connection! The fact that the very same bookmark is now working again with zero changes (and it's working in the other browsers on this computer, the iPad and the Android phone) suggests that nothing at all changed.
What changed was your router. You stated you installed a completely different router. That different router might not have of been able to correctly convert a URL/hostname to an IP address on your local network. That is a pretty common issue where people try pistar or pistar.local and it doesn't connect,
but it does connect when they enter the correct IP address.
...And then magically, the router started being able to do exactly that? Suddenly able to correctly convert a URL/hostname to an IP address on my local network where it couldn't the night before (same day, actually, I only got 4 hours sleep)? Remember, the router was left on overnight and then the ZUMspot was started again from fresh in the morning. Nothing changed on the router or the Pi or the web browser(s) on multiple platforms. It's clearly not a browser issue. The pi is still at version 4.1.4/20210224, just as it was yesterday. And you're forgetting that yesterday
I *did* enter the correct IP address shown on the ZUMspot in the URL of the web browser and it wouldn't connect (because it hadn't made a connection to the router... which brings us back to the very start of this thread).
Again, what does the OS report? What does MMDVMHost report?
No idea!
I answered each of your questions as best as I could, if that isn't good enough for you then I don't know what to tell you. You are the first person I've ever heard of that has reported a Nextion displaying an incorrect IP address.
It's not a question of your answers not being good enough for me, but you haven't really followed the facts that I've outlined. Your answers have all been great, but in many cases you've made assumptions about things that I've explicitly said are not the case. As for being the only person to report a Nextion displaying an incorrect IP address... lucky me! FML! It's sitting here beside me, still showing 192.168.1.111, when the router shows it on 192.168.1.223! I'm sure that if I were to reboot the ZUMspot it would display the correct IP address... assuming it could connect to the router again, which I highly doubt.
I"m sure I could assign that exact IP address in my test setup, and my Nextion would display the correct information.
Yep, again, I agree. But *something* happened to make it confused, because it *is* confused.
Maybe you should reimage the SD card, and reprogram the Nextion with a different screen and see if it also reports an invalid IP Address. Maybe whoever created your screen has a bug where it can't handle IP addresses that high. That is a pretty high IP address, most routers start assigning at 2, or 100.
Could be that too. Apparently not this router. For some reason it chose 223. I'm not gonna do anything with the image at this time. The new router should be here later today. The 2.4GHz wifi on this one is definitely screwy, as I've said many times before. It's quite possible that is why the ZUMspot is displaying the wrong IP. But even if it is the router's fault, the ZUMspot should not be giving a false IP address.
Thanks again for your input.