Samsung Connect Home/SmartThings WiFi Hub Firmware Hotfix Notes - 0.47.12

Yeah, my bad. I’m not sure what that version represents. You need to be in the ST hub dialog as I described above before going to the 3 dot menu->Information.

that’s similar to what mine looks like as well except shows Version 1.6.04.45036

I wonder if this is due to having the Connect Home and using it for both Wifi and the ST hub? I can only seem to find the firmware number in the web portal (not in my ST app)

2 Likes

When I tap the hub on my devices screen, I get this:

If I tap the 3dot on that screen, and then Information, I get the screen I showed earlier…

With all these conflicting screen paths, why would anyone get frustrated at just how hard it is to get the right information using the primary tool (the app) Smartthings has provided? :person_shrugging::person_gesturing_no::person_facepalming:

Hardware and firmware versions should be easily accessible, in the app, for everything. And which kind of ‘version’ is shown should be clearly labeled. Telling people to go use a tool other than the app shows a consistency problem in the design of the app.

Guessing you have the Connect Home WiFi hub and I have the ST WiFi hub (Plume) which would account for the difference in the UI view. Is the “Devices on network” bubble clickable?

Thank you for the good news, I now was able to successfully use a community made driver for the Harmony Hub, but sadly none of the others LAN base drivers that I need work yet (Hue, TP Link, Lifx and Tuya). Do you know if is there something to be updated in this community made LAN base drivers to work?

SmartThings is working on their own Hue edge driver that you will be migrated to or you can use this one

Here’s tp-link and lifx

2 Likes

None of those two drivers work for me yet

Won’t install or don’t work properly?

which hue bridge do you have? If Philips Hue V1 Bridge - This device will no longer be supported in the SmartThings app.

Won’t properly work. The hue driver discovered the hue hub after many tries and reinstalls of the driver and reboots of the ST wifi hub, but it shows the hub offline and don’t let me do the linking process. The TP link and lifx driver doesn’t discover any device during the scan nearby process.

I have the V2 (the square one)

Restart your ST hub.

… Awesome, I think I just factory reseted my wifi hub…

I still have 3 devices that keep dropping; iris motion sensors and door sensors. They will stay connected to the main Wi-Fi hub but won’t stan connected thought the satellite Wi-Fi hubs… even though they are just a couple feet away from it. What gives? Never had this problem before. This stated about 3/4 weeks ago.

I decided to readd manually all the offline devices diring the weekend. Hopefully they remain that way.

Sorry if I’m duplicating at all here … I just now read all the posts in this thread. So when my Zigbee devices went offline with prior firmware update, 13 devices went offline. I re-paired all of them to the hub per a recommendation in a different thread and they worked again. Then the latest hotfix got pushed out a few days ago and now I have 16 devices offline. So … based on what I’m reading, do I just need to re-pair all 16 devices in order to get everything working again? And then I should be good to go going forward?

Nothing yet about Matter for these models?
Expected update? Or they never will be updated for Matter?

1 Like

Matter, doesn’t seem to matter :rofl:
Yup they don’t seem to care.
My Matter device stopped working of course it was a zigbee based device , not thread.
Most of the issues seem to involve zigbee devices. Sometimes thisnis hard to figure out for less super techy users.

What was your device?

There are three major types zigbee and thread (works with Matter) and Zwave.

1 Like

Matter needs an IP transport medium and neither Z-Wave or Zigbee support that. Matter runs over Wi-Fi and Thread (and in theory any physical media or radio protocol that supports IP). So I’m confused by your statement about your Matter device that stopped working but it was Zigbee, not Thread.

3 Likes

The question about Matter support coming to these hubs has been asked multiple times in multiple topics. There has never been a definitive yeah or nay on whether it will happen. It seems like it would be a slam dunk to add Matter over Wi-Fi since 1) these are Wi-Fi devices; and 2) the Matter stack already runs on the ST Family Hub on the fridge (I know cause I have one) over Wi-Fi (and Thread if you have the dongle). I can sorta understand not getting Matter over Thread as they probably need to write/port a Thread stack to these hubs (which is feasible since there is a Zigbee radio in the hub).

Now, all that being said. I’m a bit pessimistic because of this:

{
  "zwaveStaticDsk": "17190-53446-57653-19148-39064-09804-17750-45437",
  "zwaveS2": true,
  "hardwareType": "CELL_HUB",
  "hardwareId": "0024",
  "zigbeeFirmware": "5.4.7",
  "zigbee3": true,
  "zigbeeOta": "2",
  "otaEnable": "false",
  "zigbeeUnsecureRejoin": false,
  "zigbeeAvailability": "Available",
  "zwaveAvailability": "Available",
  "lanAvailability": "Available",
  "matterAvailability": "Unsupported",
  "localVirtualDeviceAvailability": "Available",
  "childDeviceAvailability": "Unsupported",
  "edgeDriversAvailability": "Available",
  "zigbeeChannel": "20",
  "zigbeePanId": "48CB",
  "zigbeeEui": "000B57FFFEF6A65E",
  "zigbeeNodeID": "0000",
  "zwaveNodeID": "01",
  "zwaveHomeID": "D72CE6D6",
  "zwaveSucID": "01",
  "zwaveVersion": "6.04",
  "zwaveRegion": "US",
  "macAddress": "F4:C2:48:2E:6E:3E",
  "localIP": "192.168.1.217",
  "zigbeeRadioFunctional": true,
  "zwaveRadioFunctional": true
}

It doesn’t say that Matter is “Unavailable”, it says that it’s “Unsupported”. That’s the same thing that my Family Hub says about Z-Wave:

{
  "zwaveStaticDsk": "00000-00000-00000-00000-00000-00000-00000-00000",
  "zwaveS2": false,
  "hardwareType": "SAMSUNG_DA_REFRIGERATOR_HUB",
  "hardwareId": "0045",
  "zigbeeFirmware": "5.4.7",
  "zigbee3": true,
  "zigbeeOta": "0",
  "otaEnable": "false",
  "zigbeeUnsecureRejoin": false,
  "zigbeeAvailability": "Available",
  "zwaveAvailability": "Unsupported",
  "threadAvailability": "Available",
  "lanAvailability": "Available",
  "matterAvailability": "Available",
  "localVirtualDeviceAvailability": "Available",
  "childDeviceAvailability": "Unsupported",
  "edgeDriversAvailability": "Available",
  "zigbeeChannel": "24",
  "zigbeePanId": "5B71",
  "zigbeeEui": "84B4DBFFFE144E15",
  "zigbeeNodeID": "0000",
  "zwaveNodeID": "00",
  "zwaveHomeID": "00000000",
  "zwaveSucID": "00",
  "zwaveVersion": "0000",
  "zwaveRegion": "0",
  "macAddress": "CC:6E:A4:E2:14:94",
  "localIP": "192.168.1.148",
  "zigbeeRadioFunctional": true,
  "zwaveRadioFunctional": false
}

Because there is no Z-Wave radio in the dongle or in the fridge. Could be jumping to the wrong conclusion, but…

1 Like