Hey @mlchelp recently came across the kasa matter smart plug. Just wanted to confirm that your type of pairing to SmartThings would not give you energy monitoring correct?
Is there any edge devices available for this device to provide energy monitoring feature?
I got a Smartthings v2 starter kit a long time ago and experimented with it and also added various 3rd party devices - mainly before Smartthings completely changed their software. Partly due to that change but mainly due to being very disappointed about general incompatibilty between brands and the terrible UK options for smart wired dimmers I gave up for a while on all smart home solutions.
Now that Matter is around and has recently been updated to version 1.2 I am starting to look in to this again. My v2 hub is updated and seems to have Matter support but obviously not Thread support. I also have a Philips Hue Bridge also updated with Matter support and also an Apple TV 4K with both Matter and Thread support.
I can see that with the Philips Hue Bridge it is possible to add Zigbee devices to it and these are exposed as Matter accessible devices. I get the impression from this thread and other sources that at least on a Smartthings v3 hub if a Thread Matter compatible device is added this can be shared via Ethernet to other Matter systems i.e. it acts as a border router.
What I am not clear on is if a v2 and/or v3 hub can share non-matter devices to Matter. Remember the Philips Hue bridge can do this!
As an example of a goal I cannot see possible to do any other way, if this works I would like to get and share a Samsung AC unit via the Smartthings hub to Matter. If this cannot be done due to Samsungās preferring to lock you in then they will lose the sale of the AC unit and ASHP unit I am planning as they appear to have no plans to add native Matter support to their other devices.
I want to make all my planned devices either native Matter or expose them to Matter via hubs/bridges. Apart from this being the whole point of Matter to provide interoperability, it will I feel also help protect against some brands in the past having killed of their products when they discontinued them or when they went bust. There have been many cases of e.g. entire home smart lighting solutions going dead when the cloud service was turned off when companies went bust.
So what is the situation about exposing devices to Matter via a Smartthings hub?
As of the time of this posting, it canāt, because those are actually two different device classes.
A āmatter controllerā Can bring matter compatible devices in to its own app. Again, at the time of this writing, the smartthings V2 hub, V3 hub, smartthings station, and the Aeotec hub are all matter controllers. (The Philips hue hub is not.)
A āmatter bridgeā can join the app for a matter controller, and bring with it some of the devices attached to it, which would not otherwise be able to be used with matter. Thatās what the Philips hue hub is: a Matter bridge. But smartthings does not yet offer any matter bridge.
So, at present, smartthings supports matter one way in.
Philips hue supports matter one way out.
This is just a decision that each manufacturer has made.
If youād like to read more about how matter works with SmartThings, see the following community FAQ.
Some of the Samsung Refrigerators and TVs are Matter controllers and can support Matter over Wi-Fi devices. If you add the TV/Fridge dongle that has a Zigbee radio, that will add Matter over Thread support as well as making the device a Thread Border Router.
Deciding to try a Thread device now that my Aeotec Smartthings hub supports it, I got a discounted Thread Eve Motion sensor on Amazon. During pairing, the pair would fail, telling me a thread border router was required, which is how I ended up here on the forum. After reading the above, I unplugged the hub and the border router error went away when the hub restarted.
Unfortunately I think I got a device that was returned defective, because even though the reference to the thread border router error went away after the Smartthings hub reboot, the Connecting to Sensor phase produces an error and fails even after a device reset.
Is your fridge using the dongle? Iām seeing lots of problems with my Dongle randomly disconnecting from my smart monitor and requiring a power cycle.
Yes, my fridge has the dongle. Iām seeing two behaviors that routinely occur. First, the Family Hub itself goes offline randomly for a period of time. This has been confirmed to be a bug in 46.8 that was supposed to be fixed when 47.x was pushed to the fridge. Iāve been waiting for months for that to happen. The second thing that happens regularly is that the Thread stack stops responding and shows as Unavailable as I described in my previous post. Have to restart the Family Hub for Thread to come back.
I just wanted to add myself in here as I too am having my Family Hub w/Dongle as well as my S95C TV (2023) with built in Hub drop its Thread Border Router. Iāve got one other Bulit in Hub a HW-Q990C (2023) as well, but this one never seems to drop itās Thread capabilities unless it goes offline completely, but when it reboots itās back. To me Thread is dropping when SmartThings sees the device itself go āOfflineā even though itās still connected via Wi-Fi. Not sure if the is the cause, but itās what Iāve observed. Iām able to get the Refridgeratorās Thread capabilities back by restarting the Family Hub like you and the TVās Thread capabilities by turning the TV on then doing a Hard Reset by holding the power button until I see the OLED logo. I hope this is just a firmware bug and will soon be patched.
P.S. all 3 of my Hubs are running firmware version 000.047.00011
Well, I finally got my ST Hub on the fridge to update to 47.11. Turns out that it needed a software update of the Family Hub software (Tizen) to move the ST Hub to the new firmware. However, I was never prompted to install the updated Family Hub software because it never automatically downloaded. Finally was able to force it and once upgraded, the ST Hub immediately updated as well.
Will keep you up to date on whether my ST Hub going offline and the Thread stack being unresponsive issues are fixed or not.
Coming back to the ThirdReality Matter Nightlight and STās lack of ability to change colors, I did some testing using the Edge Device Builder which allows you to change the profiles for devices rather than the driver selecting it for you. So, I played around with different profiles for the nightlight such as switch-color-level, light-color-level, light-color-level-2000K-7000K, etc. Some of the profiles would cause the light to simply not respond and the device card wouldnāt load. Others would change the device card to show some color preset names and a color selector. The presets would change the light level, but not the color and the selector would never come up to allow changing colors. Other profiles, I would get the dreaded āDevice hasnāt load all attributes yetā. So, my conclusion was that there is something more than just having the correct device profile for the nightlight.
After some reading, I found there is an app from ThirdReality called 3R-Installer (sometimes referred to as 3R-Matter) that can be used to upgrade the firmware. Figured Iād give that a try since I knew the version of the light I have was a beta/development model. I factory reset the light and paired it with this app and noticed that its firmware version was 0.1Alpha and it said there was no firmware upgrade available. I thought that was odd since Iāve read about other people upgrading their lights using the app. Wrote to support about it and they said I have an alpha version of the product and if I showed them proof of purchase from Amazon, they would send me a new light with production release firmware.
It arrived today and I paired it to the 3R-Installer and it has the latest firmware. In the 3R-Installer app, I went to the device panel and selected āLink with Matter Enabled Servicesā, selected SmartThings and it proceeded to commission the light with ST. I also got notified from Alexa that a new Matter device had been added from ST. So, lo and behold, I can now control the color for the light with the production firmware. Funny thing is that the alpha light and the production light are both using the matter-switch driver and both have the light-color-level profile.
So, in summary, the alpha light didnāt identify itself in a way that ST thought it should be a light-color-level device and there was something about the firmware that didnāt allow the color to be changed even when that profile was selected. Now, with the production firmware, it works as advertised on their website with the exception of being able to use the light sensor value and occupancy sensor in Routines. Those capabilities are not defined in the light-color-level profile so there needs to be a specific profile created for the nightlight that would include those attributes.
As for Alexa, I can control the color, dim level, and on/off through the ST integration and those can also be changed in an Alexa routine. The production nightlight is not available as a trigger in an Alexa routine.
Well, bad news for firmware 47.11 for the ST Hub on the fridge Family Hub. Thread stack became unresponsive again and my Thread devices went offline Also, no Thread info comes up in the AWA for the hub when in this state, just a spinning icon.
Coming back to this topic of composite devices, now that I have one (the same THIRDREALITY nightlight as above) and have been digging into how Matter devices are assigned a driver and profile, it would appear to me that there needs to be either 1) a device specific fingerprint to specify what profile should be assigned to the device or; 2) a generic fingerprint based on Matter device type that includes all the device types for this device, namely 0x010D Extended Color Light, 0x0106 Light Sensor, and 0x0107 Presence Sensor.
In the absence of either of the above, the profile assigned to the device is based on the first endpoint which, in this case, is the 0x010D Extended Color Light which receives profile light-color-level and doesnāt include the necessary components for the sensors to be exposed.
I donāt know if the architecture doesnāt support it or just that no-one has bothered to create a fingerprint and profile for this specific device. I have created both but I donāt think I have any ability to contribute to the code base so Iām not sure how I could get them added to the matter-switch driver.
In my quest to get the sensors working on the THIRDREALITY SmartColor nightlight, Iāve dived into the world of building my own drivers. I created a version of the matter-switch driver that includes the fingerprint for the device that matches on the vendorID and productID and a corresponding profile that includes the sensor components. Once I installed the modified driver to the hub and commissioned the device, I can report that it displays all the components on the device card and in the Routine triggers. This at least answers the question regarding support for composite devices. Now, I need to update this version of the matter-switch driver to include the capability-handlers for the sensors so that the values get populated.
Bonus is that Alexa can now see the device for triggering in routines using motion detection.