Device Profile in SmartThings Advanced

Devices & Integrations
, , ,
1

Recently, I had to re-setup from scratch my whole home automation due to the recent crash.

I have multiple Philips Hue lights (panels, bulbs, spotlights).

When I was setting up the routines/automations, I noticed some are not perfectly running.

After some troubleshooting, what I noticed is that some of those devices are in different Device Profile.

Device Profile of those working: rgbw-bulb, color-temp-bulb

Device Profile of those not working: switch-level

All those Philips Hue devices are dimmable devices, but for unknown reason, the dimming routine does not seem to work for those with Device Profile: switch-level

I have tried to reset & re-connect the devices but to no avail.

Is there anyway for me to change the Device Profile & see if it works?

2

There are multiple ways to integrate Philips Hue. How are your devices connected?

3

All using Zigbee protocol.

4

Post some screenshots from the AWA of the affected devices. Most importantly: vendor/manufacturer and model IDs.

5

This is 1 of the devices that appears not to have proper integration:

image
image1920×911 89.9 KB

& this is one of those working properly:

image
image1920×911 89.6 KB

I just noticed that the Manufacturers are different although they are all Philips devices.

Thank you for looking into this.

Note: Please ignore the OFFLINE status; hub was rebooting when I took the screenshots.

6

What do you mean?

Can you control the device in the app?

7

Yes, simple control (off / on) is working.

Manually dimming the lights also work via the ST app.

But automated routines like below (gradual dimming) does not work for those Philips devices with “switch-level” Device Profile.

image
image1612×212 12.2 KB

8

You should have mentioned that in your post…

Is there a colorTemperature in the arguments?

Screenshot_20260807_125240_Samsung Browser
Screenshot_20260807_125240_Samsung Browser1200×575 32 KB

9

my bad… i should have been more clear in describing the problem. well noted.

As for the arguments, there is no colorTemperature for those devices with the reported issue as they are not RGB lights… for those properly working (with the gradual dimming routine) yes there is as those are RGB lights.

10

I know. Just wanted to make sure that the arguments were built correctly for your device.

Now take a screenshot from the attributes section of the device.

By the way: your model has no entry in the fingerprints of the driver, so a generic fingerprint is selected which points to the switch-level profile. You haven’t mentioned if your device supports color temperature.

Edit: looked it up:

Typical input (server) clusters on endpoint 11 (from similar Hue white/Bluetooth bulbs in the same series and community reports):

  • 0x0000 — Basic
  • 0x0003 — Identify
  • 0x0004 — Groups
  • 0x0005 — Scenes
  • 0x0006 — On/Off
  • 0x0008 — Level Control (brightness)
  • 0x1000 — Touchlink / ZLL Commissioning

Manufacturer-specific clusters (commonly around 0xFC00 / 64514–64516 range) for Philips proprietary features (effects, power-on behavior, etc.)
Typical output (client) clusters:

  • 0x0019 — OTA Upgrade

Device type / profile: Usually under the Home Automation profile (0x0104) as a dimmable light (device ID typically 0x0101 or equivalent). It follows Zigbee standards closely enough for broad compatibility but uses Philips proprietary commands for advanced effects and some configuration when “native control” is enabled.

11

Kindly refer below (taken from those devices which gradual dimming routine does not work as expected). Color temperature is not supported by those devices, only dimming.

image
image1920×911 80.7 KB

image
image1920×911 80 KB

12

Complete screenshot from the commands, please.

And a screenshot from the routine in the SmartThings app.

13

Thank you for your patience with me @Andreas_Roedl … I am still learning from this advanced stuff…

Here is the commands:

image
image1920×911 77 KB

duration: 7, effects: {“operands”:[{“map”:{“capability”:{“string”:“switchLevel”,“type”:“string”},“start”:{“integer”:100,“type”:“integer”},“end”:{“integer”:30,“type”:“integer”}},“type”:“map”}]}, fadeType: “WindDown”, state: “Run”, afterAction: timeZoneId: “Europe/Brussels”, afterActionType: “KeepCurrent”

& here is the routine:

Screenshot_20260807-134026
Screenshot_20260807-1340261080×2400 192 KB

14

The synthetic.lightingEffectFade capability - and therefore the command - is missing. Maybe it’s only supported by certain devices - certified, with an entry in the fingerprints.

Strange that you were able to create the routine in the app.

15

Is there a way or workaround to modify this in the driver/app?..

Indeed strange that the app lets me create the routine without throwing any warning or error.

More strange as these devices are from Philips, same as the others, so I expected it to be recognized by the hub with similar profile, if not exactly the same.

16

These synthetic capabilities are added by the cloud. I don’t know exactly how it’s decided which lights get them. Everything points to the fact that they have to be devices with adjustable color temperature. So: get different bulbs.

To add: a custom driver won’t help here. There’s nothing we can do, because all of that is happening in the cloud.

17

Thank you @Andreas_Roedl for the inputs. It is a pity that we lost such flexibility in the app/driver.

Meanwhile, to keep my routine, I just set a hard transition of the dimmer instead of the fade (gradual) for those devices recognized as “switch-level”. The rest remains with gradual fade & is working as expected.