Yes, but I have seen at least one person note that their Tempest had v133 right out of the box. That is what I’m referring to.
I really doubt that but it might be. If you find that post please tag me.
Will do. I don’t remember if I saw it on FB or here.
The first is referring to the Hub being updated.
The second is referring to @ecommerce having v133 pushed to his Tempest to solve an issue that he reported.
I have not seen anyone on this forum report they were shipped hardware with the Tempest at v133. I will not say it hadn’t happened but I find it unlikely since shipping takes about 5 days and 133 hasn’t been public that long.
Got it. Just making sure.
I may be the source of the 133 question. A friend of mine here in central Washington just received his new Tempest last Friday. It is running v133. I asked about update procedures since my Tempest is v129
Thanks, @KJ.Davis, @jamie.stephens comment may be what I was remembering.
It is also referring to the Tempest being at v133 when it was received.
So the Tempest was not on v133? I don’t recall the hub ever being on v133, v134 yes.
It appears that a lot of folks (new to the Tempest WeatherSystem) kinda have the Hub
(HB-0000####) Firmware v143 confused with the actual Tempest (ST-0000####). . .latest Firmware v129.
Most all of us are awaiting the push of Firmware v133 for the actual device.
Just received my new unit today and set it up a few hours ago.
Firmware curently at:
Hub = 143
Tempest = 133
Except he is referring to the Hub.
Yeah I said 133 I thought the discussion was about the hub since it was titled as such

Firmware curently at:
Hub = 143
Tempest = 133
That’s interesting. ST v133 is being pushed out.
Maybe it was updated prior to shipping (it shipped last Friday). Or maybe the acceleration has begun.

Maybe it was updated prior to shipping (it shipped last Friday)
That’s entirely possible though I think it might have by accident.

That’s entirely possible though I think it might have by accident.
That’s OK, I’ll take it!

It is possible that WF figured that v133 is stable enough to put on the current Tempests before they ship out but are making sure that nothing gets messed up on any in the field before remotely updating them.
That is exactly what happened. We decided Friday that v133 was ready for “production” status and began applying that version to all new Tempests heading out the door. Meanwhile, we are slow-rolling v133 to Tempests in the field as this will be the first time we’ve updated a large number of sensor devices (as opposed to the more well-connected Hubs).

That’s interesting. ST v133 is being pushed out.
Indeed! Just posted an announcement here: New Tempest firmware: v133
As of this morning there were about 160 (mostly beta/field tester) Tempests on v133 and almost 4000 on v129. We are in the process of upgrading 100 or so over the next 24 hours. Assuming that goes well, we’ll bump that up to 500 for the next 24 hour period. By the end of the week, we should have everyone upgraded.

It appears that a lot of folks (new to the Tempest WeatherSystem) kinda have the Hub
(HB-0000####) Firmware v143 confused with the actual Tempest (ST-0000####). . .latest Firmware v129.
This is another source of confusion to be sure! I’m not that new to Tempest but I still get them confused. Who came up with these naming conventions???
I installed a new hub yesterday that had not been updated to the latest firmware. It very quickly got updated to 143. This morning I woke up and checked the Tempest firmware level, and, it was upgraded overnight to 133.