I’ve just tried to repair a couple of devices that are still using the old cloud-based drivers. I was under the impression, that newly connected devices would automatically use Edge drivers going forward.
However, when I reset and repair some of my device (like a Zigbee 3.0 AduroSmart Eria dimmer plug or z-wave Technisat switch) it still seem to defaults to the old DTH drivers. Is there a way to force them you use a basic Edge driver instead?
Yes, but it’s a lot of work. And many steps. See the following post. The only thing that’s different with a stock edge driver is that you don’t have to subscribe to the channel (step 5 in the list). But the other steps are the same.
Also note that not all stock edge drivers have been released to production yet, so you still have to check the fingerprints.
Interesting, going the scan nearby method did indeed install an Edge driver for my AduroSmart Eria plug. Unfortunately, the device seems to be detected as a regular on/off switch (listed as “Zigbee switch”) and is missing the dimmer functionality of the old DTH driver. The Edge driver also tries to display power consumption values in the ST app, which the device doesn’t support.
How do I get the dimmer functionally to work again? Maybe the fingerprint for the device is missing the proper feature values?
EDIT: There a three different version of the AduroSmart Eria (all of which are ST certified):
Once it’s joined with an Edge driver, you should be able to choose another driver from the menu option on the device page. You may have trouble if the desired driver doesn’t have a matching fingerprint though. If it’s a community-developed driver, you can find the thread for it on here and request to have your device’s fingerprint added.
The driver menu doesn’t present me with any alternative drivers, unfortunately.
Is there a way to contact the ST-team regarding this issue? My guess is, the three different product versions are all lumped together. Or do I have to go through the manufacture to get this fixed? Seeing, how the have a ST-certified product that doesn’t work properly anymore.
You can get it from the CLI, a programmers tool for the new architecture, but if you don’t already have that setup, it’s probably easier to get it from API Browser plus, which is a browser page that a community member created that gives you a lot of the same information that the IDE did. It has become very popular. The following thread tells you how to get access to it.
My dimmer converted to edge by smart things a while back. It is listed as a zwave device and has the dimmer function as well as a timer. My best guess is that your device needs a more specialized driver not currently available from smart things. You might go to the manufacturer page and see if they offer a specific driver for your device. I have two devices that are still on groovy.
Going by your description, it may be the BDP3001 as that was in the zigbee-dimmer DTH yet has been given the switch-power profile.
Unfortunately, the deviceModel field which is handy for the fingerprint isn’t exposed in the public version of the API, though it can be seen via the CLI or any other app using the Core SDK (or any other one that uses the same internal version number for the devices endpoint).
@TOMillr, as JD mentioned, you can get them from the CLI but also, a Community developer created a driver to get those values shown in the device’s detail view, you can access it in the link below, its name is Zigbee Thing Mc, it accepts all Zigbee devices:
ok, thank you for helping us to confirm what Graham mentioned above. (thanks BTW, @orangebucket)
I’ll create a report about this, to see why it has the wrong profile.
In the meantime, you can make it work if you download the driver, modify the profile assigned and upload it, for this you also need the CLI
Or, you can kindly ask someone that shares drivers for Zigbee devices to correct it on their side. I know @Mariano_Colmenarejo based on the functionality of the standard drivers to add more features.