Consider the following situation…
- ST app is limited to show the state of one single capability in the dashboard view (without custom presentation)
- The device contains sensors for the capabilities listed below
- Carbon Dioxide
- Dust (PM10)
- Fine Dust (PM2.5)
- Relative Humidity
- Very Fine Dust (PM1.0)
- Volatile Organic Compound (TVOC)
The last one is “Total Volatile Organic Compound”, I can’t modify it anymore.
As a default, I would use a capability which is NOT Available for other types of sensors, probably fine dust, 2.5 PM, which is one of the most common for an air quality detector. Or TVOC, which might be considered the most serious.
But that said, I think it’s inevitable that different people will have different preferences for this. I don’t think there is a “best,” because I think it just depends on the use case for which a particular detector was purchased.
I’d create them as separate child devices…
I thought about it, but I am trying to keep different profiles as much compatible as possible.
I use a generic way to create child devices.
It works well only when each child is in a separate component.
To make different profiles compatible, I try to concentrate most capabilities in the main component.
So I would need to think another generic way to create child devices from capabilities of the same component.
And it probably would require a complete rewrite of profiles, which would demand a different driver because the old profiles wouldn’t be compatible with new ones.
For my case, the parent/main is usually a switch, light, or similar. It is possible to attach multiple sensors, and sensors of the same type (e.g. multiple temperature sensors). So it’s not possible to use multi-components.
A parent with multiple child devices (1 for each connected sensors) is probably the easier way.
I’ve been puzzling over this recently…since I added an Air Quality sensor to my mix, and along getting relevant info to get displayed somehow… have it control my air purifier (especially at night, it goes to sleep in auto mode when all the lights get turned off. But, I could manually control the fan speed, etc. But, trying to figure out how that should get done… Plus there are issues with SmartLife scenes, they report as incomplete so its hit and miss on whether they’ll respond from SmartThings. And, going through IFTTT is also hit and miss… but that’s what my IR remote device is connected to.
When I initially set up the Air Quality sensor, it was showing CO2 on the tile, which was reasonable…but as things updated, it has switched to showing temperature on it…which is the least useful thing, since its near my Aquara temp/humidity sensor which is one of two sensors that control a fan and a humidifier.
There is one problem with the sensor though…it periodically maxes the pm2.5 (~8743)…hmm, wait, now its showing pm2.5 on the tile. Though probably need to find a proper edge driver for it. It’s using the 0xEF00 Tuya Cluster driver. (oh I see, the driver recently updated on Saturday.)
That’s right. Since last saturday.
Now if smart things would open up the air care app to devices other than Samsung’s overpriced air purifiers this integration would be perfect
Any thoughts why the Air Care Service is not shown/available in my service list? I’ve seen this service at a local retailer store, but the guys there could not help.
We got “HomeCare”, “Energy” (not working with ST Plugs/Outlets though?), “Cooking”, “PetCare”, “Clothing Care” and “Music Sync”. No Air Care. Localization is Germany, is that the problem? Android App(1.8.00.22) and Hub (000.047.00011) are updated. And I even have a properly working Samsung Airpurifier and a brand new “frient Air Quality Sensor” working with an EDGE driver, showing VOC (ppb) on the tile.
Update: And the service is even promoted in the “discover” section of the app! (in german, sorry, but you may see: “Alltag/AirCare…” at the bottom of the screenshot. clicking on it just brings me back to the previous menu after a few seconds.
Officially, that service is only currently available in South Korea and the US. It is based on the location of the account.
Available in South Korea and US.
See the “Support” section of the following page:
Thanks, but that’s a bit outdated, cause all the other Samsung services presented there are available here despite that “support- info” from around 2020/2021. but, yeah, maybe there are still some certification issues with that one; which is a curios regarding those indoor-air quality issues the last few pandemic-years…
IF I change the localization of my account or hub, which I am not sure may or may not be possible without generating a new account - do you think that would interfer with other existing devices or anything in the account? hm, quite a gamble for a small service dashboard…
by the way and -sorry again- completely offtopic: any idea why the samsung owned outlets do not show up in the energy service? they are applicable within the app and in automations, they show stats within their tiles, but do NOT appear in the energy-dashboard-device list.
I re-installed them several times and even tried different drivers: they wont show. the aqara plug on the other hand immediately shows and delivers current and cumulative consumption.
Air Care only works with drivers with WWST certification which at this moment only Samsung devices are the only ones that have this.
thanks troy, I do not have the Air Care service at this moment, which is my “problem”. Although I do have a working Samsun- own AirPurifier AX47R9080 (which I found cheaply on a re-selling platform). this purifier should have that WWST certificate for sure and works within the ST App properly.
I understand what you’re saying now. Yes, your location is the limitationof not having the app , otherwise the service would work with your device
The energy app is pretty pointless, most of us have smart plugs that report energy inc ST branded plugs but they get no inclusion into the energy app which is a mystery
The only reason i can think off is that where the ST app is developed there is no energy issues, or there is but they really dont care so it is not priority or even thought about
I think it’s mostly that Samsung has a big business selling HVAC and kitchen appliances to multi unit buildings, including a whole bunch of apartment complexes in Asia. So the energy tracking dashboard was originally part of a building manager dashboard and was provided for Samsung appliances.
Later, they moved it into the smartthings app, but it’s a completely different CodeBase than the rest of smartthings and I just don’t think anybody has ever gotten around to looking at it from a residential customer point of view.
Partly JD i agree but there was a time the info panels on the energy app/plugin most definitely mentioned outlets and there inclusion into the energy app
The text got changed fairly recently and now there is no sign of outlet inclusion so perhaps at one time they were due for inclusion
Thats what I thought, being disappointed as well, BUT then I bought some Aqara Smart Outlets (SP - EUC01) recently to use them in our cellar/ maintenance area. And, hello, they appear within the EnergyDashboard next to (some of my) Samsung appliances ((Dryer=shows, oven=doesnot, vacuum=shows, airpurifier=doesnot → mystery!)) showing stats and are part of a “Energyadministration Routine in Away-Mode”
My working theorie now is, that they only provide information for the energyservice dashboard with a device running “in the cloud”, not locally.
Aqara SmartOutlet uses the Zigbee Switch Edge Driver, shows in IDE as “placeholder”.
Samsung SmartOutlet uses the Zigbee Switch Edge Driver as well, shows as placeholder as well.
Trying an Edge-Driver from Mariaona for this Samsung Outlet /(Zigbee Switch Power MC) did not change anything.
Oh, and, by the way: I was able to also integrate a (german located and only in Germany operating) energy measurement device for my entire home called Poweropti by Powerfox into Smartthings AND their EnergyService Dashboard as “main measurement method” (including rate/tariff and billing interval). Works flaweless and via Wi-Fi.
So the ST EnergyService DOES work in the right direction, but only with too few devices yet, which needed specifications no one knows exactly.