meteohub.de

My Nano SD webpage started to get real slow, so I decided to reboot it. That was a mistake. It is now fast blinking which I believe indicates that it can't access the 'internet'. Internet is working as you're reading this message. Looking at my weather stations reports on Findu.com it shows several dropouts in data so something is going on with the device.

I can access the local webpage which says:
Currently it is hard-coded to a static IP. It was previously DHCP but now does not get to the internet with either. It does get an address from DHCP though.
My internet connection has been stable. I don't see anything being blocked by my local DNS (PiHole). Everything has been whitelisted at the DNS.
I've also tried reserving the IP at the router.

It doesn't look to be a local network issue, it appears to beyond my local network.
What logs should I be looking at on the Meteobridge (OpenWRT console)?
If I let it sit overnight will it re-attempt to connect to the 'internet'?

Looking at other posts I will try a factory reset tomorrow to see if that fixes it.

How did you first reboot it?

If you haven't done a full re-power (not a system re-boot as such) then then try repowering before doing a factory reset.

I tried full power reboot and switch reboots. I found this post viewtopic.php?f=56&t=13795&p=28714&hili ... ies#p28714 that mentions the original 300mA power supply can be anemic. I've ordered the power supply on Amazon that is 3A.

It is powering up but it's not making the connection to the internet so I wonder if the onboard WIFI is straining the power supply. I won't know until tomorrow when a new power supply arrives.

Mattk wrote: Tue Nov 10, 2020 4:26 am How did you first reboot it?

If you haven't done a full re-power (not a system re-boot as such) then then try repowering before doing a factory reset.

New Power supply didn't help. Going to do a factory reset.

OK after many tries (10x++) and reboots it finally decided to work. I'm setting everything back up now. This time I'll make a backup.


edit (1 hour later): Alright this is ridiculous. This thing cost over $300 and when you reboot it it loses it's mind. I just started getting things configured and needed to reboot and now it's back at a fast blink. I had less issues with my old Windows 7 laptop and a serial cable.

At this point I've got fast blink the webpage says:
However it does NOT respond to ping and does not show in my WAP controller's IP list

Going to keep trying.

Can't find a set of settings that work. Tired local DNS, OpenDNS 208.67.222.222 nothing is working.

It sounds more like a hardware issue than anything else. I don’t know if a problem with your SLC micro SD card would cause the problems you’re having, if so, you can get a replacement on eBay for a reasonable cost.
The ATP AF2GUDI is available on eBay for about $20 with shipping ( item # 193697994136 ),
or an even better deal. Five ( 5 ) ATP AF2GUDI microSD cards for $25 including shipping on eBay ( item # 184512207900 ).

BigAlT wrote: Thu Nov 12, 2020 1:45 am It sounds more like a hardware issue than anything else. I don’t know if a problem with your SLC micro SD card would cause the problems you’re having, if so, you can get a replacement on eBay for a reasonable cost.
The ATP AF2GUDI is available on eBay for about $20 with shipping ( item # 193697994136 ),
or an even better deal. Five ( 5 ) ATP AF2GUDI microSD cards for $25 including shipping on eBay ( item # 184512207900 ).

I bought this October 9 for $409. I'm going to proceed with a RMA with Ambient Weather.

Sounds like a good idea. The slowdown you experienced without any changes made by you to your NANO SD seems like a component starting to fail.

I got the new unit in and after about 3 days of runtime the webpage is non-responsive again. I've had to reboot it twice now. I'm able to reboot it by cycling power. I haven't been able to determine what is causing the slow down.

SSH was also very slow to respond.
After reboot everything is good again.

I do see on that my packet rate to CWOP drops when things get slow:
https://aprs.fi/info/graphs/a/AT994



System
Platform: Meteobridge NANO SD (ambientweather Version)
RAM: 125 MB total, 54 MB free (56% used)
Storage: swissbit SLC, 1826 MB total, 1779 MB free (3% used)
SW Version: Meteobridge 4.4 (Oct 17 2020, build 3501), FW 1.4
Uptime: 0 hours, 17 minutes Buffer: 6 items (1%)

Network
MAC: B8:D8:12:60:xx:xx
LAN IP: -- WLAN IP: 192.168.200.122
LAN Mask: -- WLAN Mask: 255.255.255.0
Gateway: 192.168.200.1 TX Traffic: --
DNS: 192.168.200.11 RX Traffic: --
WAN IP: x.x.x.x Provider: Time Warner Cable

Localization
Location by IP: United States / New York / Rochester
UTC: 2020-12-04 14:57
Local Time: 2020-12-04 09:57
Timezone: America/New York
Latitude: 43.253329
Longitude: -77.734063

If you’re having trouble with a 2nd unit it sounds like the problem is not with the NanoSD itself. Possibly an issue with your Davis Console or router.

I updated the firmware to the latest on it. Never had issues with the Davis serial adapter. I’m open to suggestions to try and troubleshooting ideas.

ac2ev wrote: Fri Dec 04, 2020 5:03 pm Network
MAC: B8:D8:12:60:xx:xx
LAN IP: -- WLAN IP: 192.168.200.122
LAN Mask: -- WLAN Mask: 255.255.255.0
Gateway: 192.168.200.1 TX Traffic: --
DNS: 192.168.200.11 RX Traffic: --
WAN IP: x.x.x.x Provider: Time Warner Cable

DNS looks bad to me. I doubt you have a dedicated DNS at .11 in your LAN. Please use 8.8.8.8 if your router does not provide it properly.

Actually I do. It’s a Pi-Hole DNS filter. I can bypass it by setting the DNS manually. I don’t have issues with the Nano SD unit getting out. The internal pages slow down along with SSH. I have not experienced this with any other devices on my network. There’s a half dozen Raspberry PIs, 4 laptops, 3 chrome books, half dozen cameras, etc,

Network is all Ubiquiti equipment.

I set the meteobridge to manually with Google’s DNS.

Since you are using Pi-hole you need to assure yourself that you have not inadvertently created a cyclical DNS mess.

This is important if your DHCP server is still your router. Meaning that you are not using Pi-hole as a DHCP server....

You need to make sure that you have not configured Pi-hole to do Conditional forwarding to your router for DNS. You can check this in the Pi-hole web portal by going to Settings / DNS and then scrolling all the way down to the bottom and make sure that "Conditional Forwarding" is off.

Conditional forwarding only works if your router is doing DHCP and the router isn't also doing forwarding to the Pi-hole. They can't both be doing forwarding to each other is what I'm saying. You have to pick what is the upstream ...they can't both be upstream to each other. One of them needs to point to 8.8.8.8 or equivalent Internet DNS service.