How to identify the device profile name being used?

w35l3y · January 15, 2023, 5:47pm

Sometimes, I use try_update_metadata({profile = "..."}) to update the profile at certain circumstances.

I tried using device.profile.name and device.profile.NAME to get the current device profile name, but it didn’t work.

Currently, I had to create an enumeration preference that contains profile device names in the options.
And I use device.preferences.presentation to identify it.

It works satisfactorily when I have a device with multiple profiles, but creating a preference with single option just to identify the device profile name doesn’t make much sense to me.

github.com

w35l3y/EdgeDrivers/blob/main/personal-tuya-devices/profiles/normal-presenceSensor-v1.yaml#L30


      
                - name: Presence Sensor
          preferences:
            - name: presentation
              title: Presentation
              required: true
              preferenceType: enumeration
              definition:
                options:
                  normal_presenceSensor_v1: Normal
                  generic_ef00_v1: Generic
                default: normal_presenceSensor_v1
            - name: prefSensitivity
              title: Sensitivity
              description: An integer between 0 and 9
              required: true
              preferenceType: integer
              definition:
                minimum: 0
                maximum: 9
                default: 7
            - name: prefNearDetection

So, my question is: Is there any way to programmatically detect what is the current device profile name being used?

nayelyz · January 16, 2023, 10:11pm

No, the name isn’t included device object, using the following you can get the capabilities configured in the profile and its ID:

log.info(st_utils.stringify_table(device.profile, "Device Profile", true))

That was previously asked and someone shared his workaround here:

Query profile name from a device Writing Edge Drivers

I had this problem too I have a generic custom log capability I use on all my drivers, to aid in debug and to allow users to see what’s going on without logcat. This capability is invisible in all views and can only be seen in the history tab. I then give that log a meaningful Id in the profile of each device. - id: activitylogger label: activitylogger capabilities: - id: universevoice35900.log version: 1 This then allows me then do the following in code to figure out my device type, as each device type has an instance of universevoice35900.log, with a different Id, of course you could do this with any capability. can_handle = function(opts, driver, device, ...) return device:component_exists("activitylogger") end, I hope this helps

w35l3y · January 16, 2023, 11:40pm

So, instead of having profile name, the ideia is to have custom capabilities to act as tag ?
Then we would check existence of that capability instead of profile name… yeah, it might work.

I still think that sometimes is useful to compare the current profile with the one that were chosen or the available options.
As we update profile by its name using try_update_metadata({profile = "..."}), then the way to compare is by name.

Thanks @nayelyz

blueyetisoftware · February 24, 2023, 2:14am

Normally, you can do what you need using the capabilities, but if you absolutely need to know, you can use the profile.id. You would need to add a table of your profile ids into your driver somewhere.

How to identify the device profile name being used?

Customers

Developers

Download the SmartThings App