So i’ve extended my ST Wifi with additional Wifi/Hub pucks to enable meshing features. Do the additional pucks contribute to the Zwave and Zigbee mesh nework? Or is that feature only enabled only when setting them up as a new Home.
In the ST app, I only see a single device for Hubs and viewing my network in the ST API I don’t see the additional pucks as a device registered anywhere.
And if they are only enabled as a wifi mesh, can I enable the hub part of the puck as separate Home for let’s say an outhouse and yet use the wifi feature as part of my Mesh?
I may be wrong, but I’m pretty sure that if the primary hub and subhubs are all on the same Wi-Fi mesh net work then it is all treated as one home automation network as well. You can’t assign different subs to different locations in your account. But I’m not 100% sure.
As far as Zigbee and zwave, I am sure that each of the individual subhubs Will act as a Z wave or zigbee repeater in exactly the same way that any other repeating device, like a light switch, would if placed in that same physical location. So the sub hub still Has to be within Zigbee or zwave range of other devices to get messages back to the primary hub.
In other words, the answer to one of the most frequently asked questions about these models is do you get effectively longer range from zigbee or Z wave Because you have the longer range for the Wi-Fi mesh. And the answer to that question is no. Each protocol is still limited by its own specific range.
thanks for the response, yes that is what I am assuming as well but taking for example ZWave, if this is registered as part of the ZWave network, it should show up with a deviceID somewhere in the newtork. This is the reason I am doubting this assumption.
They are supposed to have a device ID, but multiple forum users in the past have reported that they just show up as unknown device. This was then identified as a known bug, and was supposed to be fixed eventually, I don’t know if it ever was.
(TPManley, Who responds in the following thread, is one of the senior engineers at smartthings.)
I need to do some troubleshooting then as I didn’t see any new or unknown devices show up. If it has though, I would think that removing them should go through the process of zwave removal process.
Anyway thanks for the reference above, I will go through the discussion and learn a bit more.
There is one other aspect: originally, the subhubs did not act as Z wave and zwave repeaters. This was changed in a later firmware update. So you should make sure that both the firmware on each subhub and the plume software is up-to-date.
Also, what model number are the hubs? There have been two generations. The first, “Samsung smartthings connect home“ did not use plume and the subhubs were not zigbee or Z wave repeaters. That version was discontinued for the US about three years ago, but might still be available in some other countries. Model WV520.
The current generation is “Samsung smartthings Wi-Fi with Plume”. Model WV 525. As long as the firmware is up-to-date on that one, the subhubs should act as repeaters for the other protocols.
I wonder if this is where the culprit is, both devices are WV525 but the one I added must have had an old firmware when i joined the network. I can see the firmware is updated now but may not have on boarded the Zwave before then with the lder firmware from the box.
I will try to pair it again, not sure how to remove it from the network now… haha
