SmartHUB has "fallen and can't get up"

  • 1
  • Problem
  • Updated 5 months ago
I've been quite familiar with 09150TRX problems since acquiring one, but this one is a new one on me.  I'm wondering if the device has just gone bad or something.
It was rocking along just fine, reporting both to WU and to My-Ac until yesterday when I got the dreaded alert message that it had stopped reporting.  I went through the usual steps to recover it, but none of them worked.   Next I disconnected it from power and from the network and let it sit - for at least two (2) hours, thinking I was going to have to go through the setup process again.   After letting it sit, I first reconnected the ethernet cable, then applied power.  Both the sensor status and network status lights came on as expected when the device first boots up.  After bootup though, it goes into a state where the sensor light stays on, but the network status light starts a cycle where it's on for 45 seconds, off for 45 seconds.  I've now attempted the process at least 3 or 4 times since the problems started but each time the result is the same.  Most recently it's been sitting in this status for at least five (5) hours.  Still the network light is blinking at 45 second intervals (timed).  I've power-cycled the router, tried more than one ethernet cable (known to be good - tested to work with computers), always with the same result.  Checking with my network tools I can see that the device never registers with DHCP and never gets assigned an IP address, and that my router never "sees" it -- even though there is obviously some sort of network traffic going on as indicated by flashing lights at the RJ45 connections on both the router and the device. I can connect a laptop to the same router port using the same ethernet cable, and it runs perfectly.   No matter what I try, the result is the same:  the bridge boots up, then enters a state where the network status light turns off for 45 seconds, on for 45 seconds... lather, rinse, repeat --- for as long as I'll let it sit there.
I've not seen this behavior documented anywhere, so what's this telling me?
Photo of Robert Garrett

Robert Garrett

  • 9 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 1
Photo of oneblackcloud .

oneblackcloud .

  • 25 Posts
  • 19 Reply Likes
Too bad the lemon laws don't apply to Acurite.
Photo of Robert Garrett

Robert Garrett

  • 9 Posts
  • 0 Reply Likes
I'm not upset about it - yet.  I've been a software guy and a network guy for 40+ years.  There's a saying, "All hardware eventually breaks, all software eventually works."  What bugs me a little about working with this device is the lack of detailed information about it for someone like me who knows their way around both networks and software.  The status light pattern I'm getting now probably means something, but it's not documented anywhere that I've been able to find.  There's also no documented procedure for performing a "factory reset" on the device so either it's not possible (which points to a design flaw) or the vendor isn't willing to share it (which is a little insulting).  Given the state it's in now, that would have been my next step -- "wipe" it and start over from the beginning.
Photo of sparkie951

sparkie951

  • 50 Posts
  • 11 Reply Likes
It sounds like it is not pulling an IP address from your router... I would try reseting your router and Cable, DSL, or what ever connection device that connects you to the Internet.
Photo of Robert Garrett

Robert Garrett

  • 9 Posts
  • 0 Reply Likes
No, it's not - and it's not trying to either. I run my own DHCP server here on-premises and can see exactly what it's doing, or not doing. I can also run network packet traces "on the wire" here to see everything that's happening (or not happening).
Photo of Robert Garrett

Robert Garrett

  • 9 Posts
  • 0 Reply Likes
Found it!  After my previous comment I decided to fire up Wireshark and see what I could see.  Looking over Wireshark traces of all the traffic on my network, I could see that there were other devices that were sending DHCP/Bootp requests and not getting responses from my DHCP server.  That was odd because I was able to use a test laptop to gain an address via DHCP just fine.  Everything else on the network seemed to be working, even the one device that kept sending in the Discover broadcasts packets and not getting a response (one of the boxes on our TV system), so I started digging around for an explanation sort of half-heartedly while working on other things.  I found something online that made me suspicious of my DHCP server so I checked all the settings.  What I found was that sometime in the past I had evidently configured it to respond to DHCP traffic but not Bootp traffic - why I don't recall - it certainly wasn't intentional.   So on a lark I enabled Bootp and saw that the TV box immediately was assigned an address.  That made me curious.  Sure enough, when I went in to check on it the SmartHub had likewise come back up and was on the air again.   So I guess now we know what that 45-second on/off cycle means: it means the device is waiting for an IP address in response to DHCP/Bootp.  Testing with the laptop and having that work threw me off.  I guess it uses DHCP and the SmartHub (and apparently at least my TV box) use Bootp and not DHCP.  Who knew?
Photo of sparkie951

sparkie951

  • 50 Posts
  • 11 Reply Likes
I run the same system that you do as well with a dedicated DHCP server as I also do outside hosting... Just by your description, the DHCP sounded like the culprit.. Glad you found and fixed it.
Photo of AcuRite Rachell

AcuRite Rachell, Employee

  • 6236 Posts
  • 198 Reply Likes
Hello Robert,
We are happy to hear you were able to resolve this issue. The left light on the smartHUB(antenna in back) is the network light. If you see this light cycling on and off in 45 second intervals this tells us the smartHUB does not have a network connection. I do apologize for any inconvenience experienced. Please let us know if you have any other questions. Thank you.