My PW2 updated to 1.40.2 today, so could be regional, could be staged rollout.
I was 1.38 -> 1.40.0 -> 1.40.2, it skipped the .1 update from this thread.
What I noticed was from when 1.40.0 came out, the PW2 last communication timezone changed from +10, to -7 and is still -7 in 1.40.2 and the customer info from the web portal is still saying it's aus utc+10. It also hasn't auto charged up from grid in tou cost saving even when it was 29% at midnight, and 12%(reserve set 2%) at 7am when the 18 hours of peak time started. 1.38 (reserve set to 20/24%) when needed would top up enough to get through 16 hours of peak. No idea if this is because the PW2 is now in no grid charge being US mountain time, or it's hoping the sun shines for the next 24 hours
I don't have the installer PW to double check/change the setup timezone, so i don't know if that would change anything. Does the password reset work for the installer password or just customer?
{"state":"/update_succeeded","info":{"status":["nonactionable"]},"current_time":1569281946730,"last_status_time":1569281516702,"version":"1.40.2","offline_updating":false,"offline_update_error":"","estimated_bytes_per_second":null}
i don't recall the estimated bytes per second being in the older update info either (from the h**ps://pw2/api/system/update/status page)