theemanofsteele
So, I got the TSS (not the pi version) a few days ago and got it all hooked up according to the documentation. I configured my stations and schedules and everything has been great. Until today... I noticed I could no longer access the TSS (from the mobile app, web interface, etc) and it doesn't make much sense. In the device, I check the IP and it shows 0.0.0.0.:80 osip. So, I figured 'ok, it's not getting assigned an IP for some reason'. So I tried rebooting it and my router that it is connected to via Ethernet. After a full reboot (even disconnected the power), still showing 0's for the IP. So, i figure it's time to try giving it a static IP and Default gateway. I turn it off and power it on while holding B3 to get into the settings. I set DHCP to off and then the IP to an open IP i have on my network and set the correct Default Gateway. Saved and rebooted, still showing 0's for the IP. So now I figure it's time to try a factory reset. I factory reset, still the same issue. Tried setting the static IP and default gateway, still the same issue. With all the options I tried above I have also tried setting the DNS on the device to the DNS on my network and using the default of 8.8.8.8 but to no avail. I also tried reserving the IP address in my router and telling it that the MAC address of the TSS goes with that IP. Still nothing. I have Googled and searched in these forums for any possible solution but I feel like my options are starting to become limited. I fear the device is borked somehow. I would have thought a firmware upgrade may have caused the issue but, the first thing I did when I got it was flash the firmware to 2.1.7 and everything was working just fine. Just as part of the trouble shooting I have tried flashing firmwares 2.1.5 and 2.1.6 as well and tried all the options I mentioned above on each of those with the same results. To my knowledge, it went rogue sometime later this morning because my sprinklers ran at their scheduled time of 4:00am today but I haven't been able to access the device since the afternoon.
*The weirdest part about this whole thing, when I set the static IP address, it still shows 0.0.0.0 when looking at the IP by pressing B1...
Any help will be much appreciated! Thanks!
theemanofsteele
Update:
So, I have discovered some interesting things during this troubleshooting/debugging process. In short, I have resolved the issue by flashing firmware 2.1.6 and removing the SD card. If you want to know the details of the solution, read on.
I noticed that when I cleared off the SD card and restarted the device (running 2.1.7) it no longer exhibited the 0's IP address. I was able to use the device for all of about 10 minutes and then lost connection again. The device had reverted itself back to a 0's IP address. So, I took out the card, erased the files off of it, and put the SD card back in. Booted it up and it registered a valid IP right away. Was able to use it for a few minutes and then it crashed again. So, to further test this theory, I wiped the SD card again and put it back in the device and then booted it up. It registered with a valid IP and appeared to be out of the bad state and in a good state again. In the short window that I had, I flashed 2.1.6 firmware back on the device. After that was done I shut it down and removed the SD. Once I booted it back up, I no longer was seeing the 0's IP address. It has been running all evening now and have not had any issues with it. I am nervous I am not out of the woods yet but this is the only solution I have found thus far. Now, I tested my theory even more. While I had files still on the SD card, I tested it on a 2.1.6 version and I saw the same 0's IP Address behavior. It seems there are some files that are generated that are interfering with the device when it tries to register an IP address. As soon as I wiped the SD card, it would get itself out of a bad state. The reason I am staying on 2.1.6 until further notice is because 2.1.7 requires you to have an SD card in the device. I don't mind that personally except it is causing the device to crash. So, my solution, flash the device at 2.1.6 and remove the SD card. I will be more than happy to discuss this further or send any data I might have to the developers. Any further testing you would like me to do I would be happy to do as well.
I hope this helps anyone else who may come across this same or similar issue.
FYI my device hardware version is v2.3.