Hi @Ward_321 I sent you a DM
The 60.10 update has brought my “original” V3 back online. It periodically goes offline (the app to be clear, while routines and rules continue to run) as I posted
here.
What I don’t understand is why my “new” V3, which only runs as a TBR, with no devices, no hub group here, does not update but is still on 59.8 if on the AWA is shown as Beta?
Hi, @Johnnybegoode
Did you enroll that hub before the Beta firmware started rolling out? If you enroll after the release date, it won’t be considered automatically until the next one.
We can ask the team to include you in the current one, we just need your Hub’s EUI.
Ok, this is the new hub EUI
D052A807F232000D
Many thanks
I’m curious as to why internal appliance hubs can’t recieve these beta updates. Will the release firmware eventually come to them, and will it enable Thread 1.4?
The Station and appliance hubs typically lag the other standalone hubs by a month or two. Sometimes even more.
And that being said, my fridge hub is currently on 58.13 and my Station is on 58.10. Station has Thread 1.4, but the fridge still has Thread 1.3.
Would you know if the next firmware update would even enable 1.4, also is there a reason that the internal hubs lag behind the standalone ones?
I’ve always assumed it is because the V1/V2/V3/V4 are SmartThings in-house hubs, albeit no longer with an in-house sales channel, and all the others are third-party products, albeit with that third-party being Samsung.
so … again … it would be REALLY useful if we could have a changelist from one beta version to the next. What’s new in 60.11 over 60.10? Anything got resolved that we need to try again? Anything new? Anyting reverted?
Tried asking for this with the beta app as well, they just ignore the requests. It honestly seems like they don’t even keep track of what the changes are.