I’ve received and installed a new Home Hub 2 and migrated from the 10 year old v2. And it’s very disappointing and overall a waste given the age difference in the hardware.
1). Lack of Z Wave support wasn’t a showstopper for me, But still it was an option with the old v2. And I have 2 choices for my few Zwaves. Bin them or keep a hub just for them. Which is what I did.
I’m already reaching the DriverSoft limit. I didn’t hit this on the older v2. I would had expected this to me increased over the old model. It’s full of drivers not required, as was the older model. These shouldn’t be forced down if they had to limit the available driver limits.
when connected to the router directly via LAN cable it’s rebooting hourly and is very unstable as it the thread network. Strangely when connected via WiFi it’s great. No idea why by it seems to be overloaded when connected via LAN.
Given the 10 year gap in the hardware the 300 device limit needs to be revised in line with the hardware capacity.
5). Hard to know for sure, But the range of the ZigBee connection seems to be less. Of course this can be easily extended, But I would have expected it to be at least on par with the older hardware, and given the lack of Z Wave support. I would have expected more.
6). Should be able to communicate locally with other ST hubs (the one running Z wave). But can’t.
And on a good note, the unify option for the Thread network should mae it more stable.
Being able to Grouo the Hubs and TVs again should help extend the network. And I assume (hope). The network will fail over to the secondary hubs if required. Like Aqara ?
I thought it was mentioned that while they are installed, they are not running and thus don’t affect any limits or something to that effect, @nayelyz had commented about it in another thread so she can follow up here if she wants.
Not my experience, However it seems that the limits are hard coded by the platform so I suspect the limits for the new Home Hub 2 are less or very similar to the older v2. But if the limits are based solely on used drivers the soft limit is tiny. I’m
Not using the vast majority of listed drivers
How recently have you installed it? Has the latest firmware version hit it yet (000.059.00008), it’s only this version that has the driver memory optimisation
I installed it 2 weekend last back and it has the
59.8 now. I also deleted a few drivers to get below the soft limit warning. It would be nice if SmartThings published the limits per hub/device. Or somehow manage the resources based on use. I’m sure not all drivers are created equally
I was on soft limit on the v3 and moved to “ok” on v4. I’m kinda hoping the increased memory vs v3 plus the firmware memory optimisation will give me plenty of headroom for expansion
Yes, if a driver doesn’t have any devices connected to it, it isn’t active, thus isn’t considered for the driver memory limit.
Also, Hub groups can be used to make them collaborate (see this article) but it is suggested that you use the hub with the most amount of features you want as the primary.
I’ve set the main hub to be the home hub 2, However the behaviour is erratic. After the firmware update I reconnected the device directly to the Router again. And all seemed okay for a few hours. But overnight when the network rebooted the v3 was listed as primary, And the HH 2 as secondary and all devices reporting as offline.
The HH2 is back online now as just says it will be the Primary in a few minutes.
Can you clarify what you mean by ‘In the meantime nothing is working even locally’?
Do you mean local routines are not executing?
Do you mean that buttons, dimmers, motion sensors, etc. no longer work locally?
What do you mean ‘overnight when the network rebooted”?
Do you mean your LAN rebooted or did both of your hubs reboot?
I have had the very occasional glitch when my hub updated (e.g. a time duration operation that never ended). I can only imagine that multiple hubs in a hub group updating at different times could also cause glitches. If your HH 2 hub updated overnight, that might explain your V3 hub becoming primary (at least temporarily). Did either of your hubs update overnight?
Hi no devices connected to the v3 hub when it took control so nothing worked, Either in the app or with local routines. I was like having the hub unplugged although all hubs reported as being online.
I rebooted my Router on a schedule at 3am.
All the hubs are on 000.059.00008 except the TV which is on 000.058.00013 and yes I think one or both hubs updated overnight which probably made it fail over to the secondary.
When all devices were back online it just said the HH 2 would become the primary soon. But never did. I also tried forcing it to be the primary at it said it couldn’t try again later.
In the end I powered down all Hubs and router for 15 mins and forced the HH 2 as primary. Everything returned to normal I around 5 mins when it reconfigured the ZigBee network
@nayelyz what is the limit on the new HH 2. I have approx 35 drivers in use at the moment. So if I add more but I don’t use them it doesn’t count towards the limits ? Interesting. I’ll test that later today
Note : Post testing @nayelyz I’ve attempted to install all of the drivers from the Aeotec Group. None of them are in use. However I cannot add any more. Looks like it’s a hard coded limit based on installed drivers and not drivers in use.
Thankfully it does seem to be a bigger limit that it was previously. But it is a limit on installed drivers
Thanks so pretty much the same memory but a faster processor in the newer hub. Given that the newer hub has a thread and ZigBee 2.4ghz radio in a smaller box. I can see why I’m experiencing smaller range. (Resolved by moving around a few outlets)
Not seeing and benefit from the CPU. Perhaps its milliseconds quicker response times.
One of the reasons I stopped using hub groups was that when a failover happened it was as often as not unclean in some way. In particular Matter devices would take a long time to come back, if they came back at all, and sometimes I lost Zigbee. I usually had to mess around rebooting the hub. The failover was often unnecessary as the original primary was usually working normally,
I used to get the message that my primary was going to revert to the original in a few minutes. Only once did it actually happen.
Okay so about the only advantage in moving to a new HH 2 isn’t quite working properly and doesn’t fail over.
I’ve a lot of bridged matter devices, none of them connected. Not even the virtual devices reconnected.
I think I’ll take the backup v3 and put it in a drawer.
‘I think I’ll take the backup v3 and put it in a drawer.’
My spare V3 hub is online, but not part of a group, so that it gets the latest firmware.
Actually hub groups are not an option for me because my (main) hub is a 2015 V2 that doesn’t miss a beat.
If you are going to reboot your LAN router nightly, I would use it’s DHCP feature to fix the IP address of both your SmartThings hubs.
The only issue I ever had with my V2 hub was that it used to go offline for short periods on a regular basis (several times a week). During one of the offline events I used my router to find that the V2 hub had a spurious IP address (no relation to my LAN IP range; it wasn’t even in a private use IP range).
I fixed it’s IP address and the problem never recurred.
5 or 6 times I have advised people with similar offline/online symptoms to fix IP addresses but nobody ever came back on the thread to say this did/didn’t solve the problem. Ho hum.
