I think that the phone rep will have to create a special update file for those devices to properly update, which will likely require some back and forth , but the current software version should be 11.2.4, and not 14.5. 

I also have to wonder if you may be running some sort of firewall on the router/modem, which could be blocking the device from reaching Sonos’ own servers, where both the software updates and diagnostics are located, while allowing the speakers to reach non Sonos endpoints such as various music streams. 

Unless the cable modem has a DHCP server built in, I’m not sure how a direct connection would work, as the ZP requires an IP address to work, normally handed out by a DHCP device. But then i could be wrong, and one of the more knowledgeable networking folks may be along to correct me. 

There has to be a router. Maybe it's a modem / router not a pure modem.  In fact it must be if ZP is connected directly to it. Do you mean it's connected by Ethernet?

Where has the 1970 date come from?  Something needs the date and time setting, although may not make a difference.

Like Bruce, I am baffled by the reference to v14.5.

Error 11 is because the firmware is too old to self-update.

The lead digits (14.5) on the build number are an internal version number. 

The 1970 timestamp on the anacapa log (still accessible back in those days) is normal. There was always an offset. 

@royhicks

To get the ZPs updated will possibly require a telnet session, via remote access through your computer. Alternatively it may be possible to flag your account for an intermediate version that the ZPs can update to, then reflag it for the current S1 version.

It could well require attention from someone higher up than front line support, but I guess you’ll have to start there. Tip: resist all entreaties to “troubleshoot”...

After looking again, the SW version is indeed 11.2.4 and the 14.5 is the build.  The “modem” from the ISP is also a modem/router, which DHCP, FW, etc, although the FW does seem wide open.

It is hard to resist the urge to troubleshoot , but I’ll try to wait until I call them on on Monday.  Will post outcome afterwards.

Thanks for all the advice.

Roy

The controller is at version 11.2.4.

The firmware build is 14.5-xxxxx, which is years out of date and is therefore unable to update itself.

No troubleshooting required. The ZPs need external assistance.

After troubleshooting with 2nd level support on Monday, and with an engineer tonight, everything is now updated to the latest SW  

Also found out that sending the diagnostics was never going to work based on the particular SW version that these devices were running and that it had nothing do do with my router/network.  

Engineer essentially unlocked the devices and then manually connected to the CLI of each device and initiated the upgrades, to get the devices to a point where they were able to finish the remaining upgrades on their own.

Time to start playing around with these and see what they can do :)