>>> Join Us in the Fight Against Air Pollution

AirGradient Forum

Cannot connect to device via local network

#1

Trying to follow Local Server Documentation

I’ve got the indoor monitor connected to my LAN and sending data over to the AirGradient dashboard, but when I try to connect to the device locally (in order to ping the API endpoint to store data in prometheus), I can’t get any connection to the device.

I’m operating on 10.25.x.x rather than 192.168.x.x - could this cause an issue? I can see the device on my router (with IP 10.25.0.187) but as other posters have mentioned, I should use a static IP for prometheus rather than mDNS.

Any pointers here to be able to connect to the local device would be much appreciated.

#2 
➜  ~ ping 10.25.0.187
PING 10.25.0.187 (10.25.0.187) 56(84) bytes of data.
From 10.25.0.9 icmp_seq=1 Destination Host Unreachable
From 10.25.0.9 icmp_seq=2 Destination Host Unreachable
From 10.25.0.9 icmp_seq=3 Destination Host Unreachable
^C
--- 10.25.0.187 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3077ms
#3

for reference, other devices respond (e.g. NAS server), so I’m wondering if i’m missing a port number, but then if a ping doesn’t work then it’s like the device isn’t responding on that IP address.

#4 
➜  ~ nmap 10.25.0.187
Starting Nmap 7.80 ( https://nmap.org ) at 2024-05-04 10:42 WEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.05 seconds

this indicates the device is not responding on that IP at all - could this be an issue with the device?

#5

Which firmware are you on?

#6

This is what’s reported via the AirGradient dashboard

Monitor Maker: AirGradient
Linked Location: Indoor
Firmware Version: 1.1.2
Model: I-9PSL-DE
Monitor Commissioning Date: May 3, 2024

#7

fixed - after upgrading the firmware to 3.0.10-beta2 everything is working and i’ve now got this hooked up to prometheus/grafana!