My Access just showed up in todays mail. Here is what I did to transfer WU (sensors can remain on your old one)(assumes you have spare network ports available)Plug the cables as outlined in the quick start guide. Wait (many minutes) for the blue light to be steady.Open My Acurite, Add the discovered Access.Add sensors (this is the PITA part if you have a bunch.) Naming them. (edit sensor)Once that is done and things look good on the DASHBOARDWunderground partSelect SHARE WEATHER under settings. REMOVE the tick next to the smarthub and TICK the AccessEDIT the Wunderground sharing Fill in your password and then select the Access (was the smarthub)

Exit That is it. Your old WU settings (under the smarthub) do not need to be removed because you are not sharing your smarthub, so they get ignored.

FWIW: I had to edit the "Sharing to Wunderground" dialogue and specifically remove the smartHUB ﻿﻿﻿﻿before the change worked when I added the Access. Without the change, I was told the Station ID was already being used (by the smartHUB)

I especially like that the access has MUCH better reception than the smartHUB. My 4 sensors all report a signal strength of 4 vs 1. I get this information by pointing my web browser to the IP address that has been assigned to the Access by my local router using DHCP. Getting this IP address is not easy since you have to understand the ARP protocol and how to read the information.

It does appear that wunderground does not notice the change in source.

When you go to add your smartHUB are you getting an error message? What are the lights doing on the smartHUB? Make sure you have DHCP enabled, and Mac address filtering disabled. Make sure you have TCP Port 80 open as this is the port the smartHUB sends information through.

FWIW: if you have an Access, I cannot imagine any reason you would want the smartHub to still be sending data. I did do this for a period of time, but because the smartHub has a poor wireless performance with the system it collects data from, I continued to get warnings from both Acurite and wunderground that those systems were dropping off-line, and if the power to my cable company went down (can you imagine that?) warnings of lost data. So, I discontinued the smartHub. (In case it isn't clear, "MyAccurite" did show both the Access and smartHub as options but only one was reported to wunderground. The information displayed was more or less the same so it isn't like there is any advantage to having both -- unless you allocate a different set of sensors, but I cannot imagine any advantage in doing that.)

Given that....

I have found that the Smart Hub does not respond to ARP requests all the time. In fact, it seems to send out broadcast ARPs that may claim an IP address that is already allocated via DHCP to a different host on your network. My router ignored those ARPs which meant that the smartHub could not talk on my network at all. If you have a sniffer application that you can use, and if you have a "smart bridge" (TP-Link makes one that is really cheap) that can be configured to send all packets that traverse the bridge to a listening port, then you can monitor this same thing. NOTE: it has to be a bridge and not a router. The apple airport, for example, will not allow you to "snoop" all the packets, only the packets that are routed through the port a given device is connected to.

What you might do is try to discover the IP address that the router has provided to your smartHub. Unfortunately, the Apple Airport no longer shows you the MAC addresses it hands out to systems connected to the ethernet port. If you have a "terminal" application that can directly access the ARP table then with a little detective work you can figure it out.

I use Emacs but that is because I've had years of experience with it as an extremely powerful text editor, mail application, shell application and so many other functions. I rarely use it now though.

Here's what the arp table looks like on my Mac. (being a newer mac it no longer has an ethernet port only the wireless port). Note the 10.0.1.39 address has a MAC address that starts 24;c8:6e: this is assigned to Accurite. Given that information, I can use my browser to go to 10.0.1.39 which returns a page that provides some raw data about my Access.

The problem everyone is seeing is that ARP entries can take a very, very long time to be removed. You might think that rebooting your DHCP router would solve the problem, and sometimes it does, but some routers remember who it had assigned IP addresses to through the reboot, and if your smartHub or Access didn't have one before the reboot, it may not get a new one after.

DHCP is a complicated protocol and sometimes it just doesn't work. When you have an ARP implementation (ala the smartHub) on top of that that doesn't follow -all- of the rules then things get really messed up. All you can do is wait. Sadly, sometimes trying to take active steps just messes things up more because it restarts the ARP timeout.