We have a newer V3 SensorStation we installed in the last few months. But since installing it, we haven’t been able to connect to it, whether to configure WiFi, download files, or even to check status.
Typically, after connecting with an Ethernet cable, the SS will be available at sensorstation.local, and if that fails, you can usually find the IP by going to Network > IP Address.
In this case, there is nothing reported under IP address in the SS menu. And the device doesn’t appear to be showing up at all on my computer (via arp -a).
I’ve tried rebooting multiple times but haven’t gotten anywhere. I’m not sure if it’s relevant, but this is the first of the newer SS I’ve used – since CTT started using the larger enclosure and putting the power inverter inside the case (great improvement, by the way). Though maybe I’m just not having good luck with this one.
@user80 or @user1023 (or anyone else), do you have any suggestions on what I should try next?
I have had one or two SensorStations do this before, and what I concluded were inoperable USB ports. Depending on which USB-ethernet connector you use, they typically have a light that turns on when a USB port is successfully connected, so I would find that my connectors would not register a connection no matter what USB port I tried. If you have tried using different USB-ethernet connectors, ethernet cables, and USB ports on the SS, then that is likely the problem, and should be sent back to be fixed. David may have other thoughts on this.
I ran into this issue recently, where no ip address was showing and I couldn’t connect to/find the V3 SensorStation with my computer. We re-flashed the pi with the latest ctt software and it fixed the issue.
Hi Josh. Sorry about the issue. Meelyn is looking into it. I haven’t had a chance to bang on the new 3.3 boards too much yet so I admit I can’t offer any solutions yet. What I have done it the past that has worked, is switch the USB→Ethernet around- so take computer end and plug into SS, and vice versa. For some unknown reason this mostly seems to work (akin to old school cmd-alt-del when nothing else works, I guess). But the disk image is new, so who knows. We did just update the disk image after finding a bit of code missing from it two days ago- so a quick and easy fix might be to flash the pi and run the over the air updater and see if that gets the ghost out of your machine. Part of the QA here is to connect them to our network via Ethernet and Wifi, so the issue does seem odd…but again, with the new disk image, we’re sure to find some new bugs once it’s out in the wild and away from our more controlled environment.
Ok so I tried all the USB ports, swapping the ends (and USB-Ethernet adapter), rebooting, and I haven’t had any luck.
I then tried to enter the WiFi credentials via USB but ran into an issue with that as well. I’ll comment about that separately since I suspect it’s a different issue.
I haven’t yet. I’m worried about data loss if I can’t connect and download to the computer, or connect to the internet, prior to flashing the new image. I’ll try to get it connected to the internet Monday when I’m back on site. (Meelyn has been in touch)
Yeah, don’t reflash until you’ve downloaded data! When you go back to the site, if you have an extra SensorStation to bring with you, you can swap out the rpi’s and try downloading old data on the other SS. Also, swapping out reflashed rpi’s is quicker than waiting the 20+ minutes of reflashing in the field