How to trigger a function in an edge driver from another device?

[georgeh (George)]

Thank you for the update.

By “name”, did you mean “key” or something different? (Was my choice for the key parameter correct.)

Any comment on my “generic-sensor” name question at the end of my last post?

[nayelyz (Developer Support Team)]

@georgeh

By “name”, did you mean “key” or something different?

Sorry, this comment was about your question of the devices name that appears in the CLI:

@nayelyz

About the devices, there are two properties each of them has, “name” and “label”…

@georgeh

Was my choice for the key parameter correct.

In this case, knowing the exact format is pending because this capability has only one command. That’s what I asked the team.
But, if it had an attribute called momentary as well, it would be correct.

[georgeh (George)]

@nayelyz

this comment was about your question of the devices name that appears in the CLI:

My confusion, sorry… I grabbed all the device info for the 3 meters using this driver, shown below. What is odd is that the last one (name=generic-sensor) has that name instead of “base-electric-meter”. The latter was the name in my edge driver’s device profile, since that same driver is used by all 3 devices as confirmed by the driverID’s. I did notice that the vids for all 3 are not the custom one I attempted to create, confirming there was some problem in that attempt.

device info (snipped for brevity)…

- deviceId: 5fc34a44-72a1-4234-964a-ea0b8b42c81d
  name: base-electric-meter
  label: MR Energy Meter
  deviceManufacturerCode: 0086-0002-0009
  manufacturerName: SmartThingsCommunity
  deviceModel: 0002-0009
  presentationId: 55d63670-00f1-3c33-94b0-f57023d6f492
[...snip...]
    driverId: 51bbdf78-fdfc-4f84-8e7f-ead931741a5b
[...snip...]
  type: ZWAVE
  vid: 55d63670-00f1-3c33-94b0-f57023d6f492
  mnmn: SmartThingsCommunity
  ocfDeviceType: x.com.st.d.energymeter
  restrictionTier: 0
  allowed: []

- deviceId: f7ce5f1d-1e0b-44e0-86c5-4d77f7602e01
  name: base-electric-meter
  label: Net (-MR) Energy Meter
  deviceManufacturerCode: 0086-0002-001C
  manufacturerName: SmartThingsCommunity
  deviceModel: 0002-001C
  presentationId: 55d63670-00f1-3c33-94b0-f57023d6f492
[...snip...]
    driverId: 51bbdf78-fdfc-4f84-8e7f-ead931741a5b
[...snip...]
  type: ZWAVE
  vid: 55d63670-00f1-3c33-94b0-f57023d6f492
  mnmn: SmartThingsCommunity
  ocfDeviceType: x.com.st.d.energymeter
  restrictionTier: 0
  allowed: []

- deviceId: c65654e3-701e-433d-997e-6da9b8b0a194
  name: generic-sensor
  label: Solar Energy Meter
  deviceManufacturerCode: 0086-0002-0009
  manufacturerName: SmartThingsCommunity
  deviceModel: 0002-0009
  presentationId: 55d63670-00f1-3c33-94b0-f57023d6f492
[...snip...]
    driverId: 51bbdf78-fdfc-4f84-8e7f-ead931741a5b
[...snip...]
  type: ZWAVE
  vid: 55d63670-00f1-3c33-94b0-f57023d6f492
  mnmn: SmartThingsCommunity
  ocfDeviceType: x.com.st.d.energymeter
  restrictionTier: 0
  allowed: []

[nayelyz (Developer Support Team)]

@georgeh

What is odd is that the last one (name=generic-sensor) has that name instead of “base-electric-meter”.

Check the fingerprints.yml file and look for the device’s fingerprint. There, we specify which profile must be used by the device. For example:

In your case, are all devices using the same device profile?
Also, if it’s not taking the new VID assigned, you need to make sure the configuration in the profile is correct (the indentation is also important). For example:

name: temp-humidity-press-illu
components:
- id: main
  capabilities:
  ...
  categories:
  - name: Thermostat 
metadata:
  mnmn: SmartThingsCommunity
  vid: 1b807861-a243-3df4-99fa-f815f562278a

Note: Please consider that even if you assign the VID you created, the label won’t be modified because the reference isn’t correct and the answer from the team is pending.

[georgeh (George)]

@nayelyz

In your case, are all devices using the same device profile?

AFAIK. All devices are using the same driver, with the same device profile. Also, two of the devices
have identical fingerprints – one being the oddball “generic-sensor” and the other having the expected “based-electric-meter” name. Its almost like there’s stale data somewhere. I have updated the devices several times, and its possible that other name was in a much older version of the driver, but not in the currently installed one.

[philh30]

The device name for z-wave/zigbee is the name of the profile the device used when it was first included. It never gets updated, and I haven’t found a way to change it (except through the Groovy IDE, which is a problematic way to do it).

[nayelyz (Developer Support Team)]

@georgeh

I have updated the devices several times, and its possible that other name was in a much older version of the driver, but not in the currently installed one.

Have you checked the profile’s ID? In the device’s details (response of the API), there’s a property called “profile” (“id” inside), you would know if they’re using the same one.
If you made changes without deleting the driver’s package or reinstalling the device, it makes sense both have different names because of what @philh30 mentioned.

[georgeh (George)]

All profileID’s are identical.

@philh30’s explanation must be correct in this case, although I swear I had to reinstall the device (after excluding) to get it to pair with the new edge driver. It doesn’t seem to impact the behavior any, just provides another opportunity for confusion. Hopefully its a reported problem already.

On the label re-attempt, I’ll wait to hear about the correct reference to use.

Thanks for the efforts!

[nayelyz (Developer Support Team)]

@georgeh

It doesn’t seem to impact the behavior any, just provides another opportunity for confusion

No, it shouldn’t impact the behavior, users don’t see this text in the app either, only the label, which they can change as required.
Just to understand the situation to see if I can replicate it:

1. You had the profile “generic-sensor”, then changed it to “based-electric-meter”.
   a. If you have a single profile, you cannot change the name and package it again because it would seem you deleted the original one. Instead, you need to delete the package completely (uninstall, unpublish, remove).
   b. If you had another profile called “generic-sensor”, you would be able to package the driver again and that could have cause the mismatch.

2. From the previous points which one is your case, a or b?

[philh30]

@nayelyz I believe what most likely happened (and what I’ve had happen on my own devices) is:

1. The device initially matched to a driver that has a profile generic-sensor and the name of the device was assigned to match.
2. @georgeh reassigned the device to a different driver, which has a profile base-electric-meter but does NOT have a profile generic-sensor. The name of the device was not updated, because the names never update after initial install.

[georgeh (George)]

Honestly not sure whether it was case a or b. After initial unpairing it paired with the stock beta ST edge driver. I then made several incremental tweaks to that driver, each time packaging as a new driver rev I selected via the app. I don’t think I changed the profile in any of them though. Eventually I cleaned up and deleted old revs using the full delete process you described.

[georgeh (George)]

@nayelyz

I didn’t notice you were trying to change the label of the momentary capability. This is a special case because it only has one command (push) and no attributes. So, the key momentary.value doesn’t seem effective.
I already asked the team about this. I’ll let you know their comments.

Hello, just thought I’d check in whether you have any update on what the correct format for changing the momentary label use might be?

[nayelyz (Developer Support Team)]

Hi, not yet. I already pinged the team again to get this info, sorry for the delay.