Hi @sulisenator
To be honest, I have no idea if that would fix the app’s slider.
The slider is a way of displaying in the app a value of a command.
If that command works by sending it numerically from a routine or scene, I’m leaning toward a problem with the App, like most of the ones we’ve been seeing in recent days.
In my driver too, but it does not provide anything different from the stock driver, it is a copy to avoid having 2 drivers if you need a device that is not in stock and it is in mine
I’d like to know if somebody else has a similar issue: while my Fibaro Roller Shutter 2 work flawlessly with the driver (i have 5 of them) , my two Fibaro Roller Shutter 3 work if I send open, close and pause, but if I set a % I hear a “click” like when you send a close command and it’s already closed, and the device doesn’t do anything else.
Any advice to fix it?
I don’t think is the polarity, because open and close work properly, but I accept any advice.
Maybe some z-wave setting I am not aware of?
I have had that problem with my Fibaro Roller Shutter 2, when I changed from DTH to Driver.
To fix it, I just recalibrate the shutter. And since then, works great.
Good evening, Mariano Could you implement a drive for the aeotec smart meter (HEM GEN 5) with three clamps? The one provided in beta only works on a clamp
I’ve had a quick look at the device manual and driver.
It seems that the driver has been configured to report total power and total energy of the 3 probes on endpoint 1.
Parameter 101 value 3.
To make it measure the 3 phases independently, would need to add a multicomponent profile and a subdriver that manages the reports of the 3 enpoints independently.
I don’t know if I’m about to do aeotec work for a device that is in production and being aeotec a smartthings hardware partner
Update:
If I’m bored this winter, I’ll think about it for you.
Aeotec is little or not at all visible in the forum and I see that its integrations leave users quite dissatisfied, with very, very basic configuration parameters.
If users knew how little it costs to put all or almost all the configuration parameters in the drivers, they would not buy another device from them.
And to them as manufacturers, they should be ashamed to say that some of their integration works with smartthings.
Hi Mariano.
I need a little help. How do I differentiate a driver in fingerprint.yml based on the number of endpoints?
I mean,
I have 2 devices, one with a plug and the other with 2 plugs with the same Raw Description, the only difference is that in one ep = 1 the other ep = 2.
If I have understood you correctly, you have to create 2 profiles.
1 profile for the simple plug and another different profile for the device with 2 plugs.
Then in the fingerprints.yml you assign a profile to each of the devices.
You can see it on the zigbee multi switch on GitHub