Anybody can test Fibaro Walli Double Switch?

I have a dual switch, I have added it in the edge driver
And it can be showed correctly in the ST app on the Galaxy A10(with Android 11)
But when I test it on the phone Apple X, the device is show as a normal(only one)switch.

I read the edgedriver, and find that there is only the product “Fibaro Walli Double Switch” has the same driver, anybody can test Fibaro Walli Double Switch on the phone Apple X?
Fibaro Walli Double Switch tihe info “mfr = 0x010F, prod = 0x1B01, model = 0x1000”.

I’m sure that the device load the same driver when it was connnected with the two difference phones.

Can you provide more details, please?
Do you mean on Android you see two devices (tiles) and only one on iOS?
Or, do you mean the number of components exposed in one device instance?

You can share screen captures for us to have a better reference on what you mean.

Yes, I’m sure the above effects. And alos this is the first time for me , for which we repeatedly tested and verified more than 6 times. I mentioned Fibaro Walli Double Switch for there only it has the most similar edgedrive except with difference fingerprint.
I’ll test the edgedriver today and take a screenshot for you when it happen again.

Tips:I guess it may be that the ST APP on Apple’s mobile phone did not receive the fingerprint of the device in time.In the past, this kind of phenomenon happened occasionally when the network was bad.

Hi @chenjun

To use the fibaro walli with other double switch with different fingerprints it is not enough to add the fingerprints to the fingerprints.yml.
You have to add the fingerprints to subdriver as well.
In the subdriver, the components are assigned to the enpoints and if you do not run the subdriver, the 2 switches will not work.

Also, Lately it has happened to me that some device does not execute its subdriver, as if the can_handle does not execute.

After repackaging the driver it worked. A Little bit weird

Thank you!
I added the fingerprint in the file “zwave-switch\src\zwave-dual-switch\init.lua”;
And I did not add info in the file “zwave-switch\src\zwave-dual-switch\dual_switch_configurations.lua” for the child with the default profile “switch-binary”;

There are the screenshot on the iPhone X for my dual switch:

On the Galaxy A10(with Android 11):

When I test the device, I remove all other drivers.
You can review the driver code here.

Ok, is this post related to the issue you sent me over DM? The device name is the same (“Switch”) and shows “checking” or “connected” because the capability “Switch” has no value as seen in this image:

You should see in the driver’s logs what’s going on (you need to use the logcat command of the ST CLI).
If there’s an error, you should be able to see it there, it shows the message exchange between the device and the driver and how they are being handled (Eg. converted to capability events)

Note: Also, per your description, you’re developing the Edge driver based on the parent/child scheme. Just as a reference, this should be used at your own risk. See my comment here

The “New One Switch” is a dual switch, I just add the fingerprint in the correct position–You can find that it work correctly on the Android phone.
In fact, just because I am not familiar with edge drivers, I can only add a small amount of code on the official basis to achieve basic functions.
Why do it can not work correctly on the iPhoneX?

Ok, I will trace the log with logcat command of the ST CLI.