I did some additional testing. It seems that the discovery is challenged by the double switches. I have several of them and typically not both are recognized but only one of them. This is a consistent pattern. Could it be that you import only the ones with endPointId:0? This seems to me the only pattern I see currently without knowing the inner workings of the tool
Virtual devices will have to be added manually because the app doesn’t have any pre built templates for them. You can add a Fibaro Virtual Device manually by copying & pasting an existing device & updating the Id. Then just add any properties you wish to monitor to the “Attributes”.
For “Double Switches”, I would like to see why they aren’t syncing. Can you send me the latest devices.json file from your hub so I can inspect it? So the device with “id” 779 named “LichtBrüoKarin” is a double switch?
Here you go.devices.txt (635.8 KB) . It is a json again.
195, 197 is a double with 194 as the master.
778, 779 is a double with 419 as the master
595, 598 is a double with 595 as the master
I think these are the three (there is another one which is connected but not in use currently). The behavior seems consistent
I just finished making the updates on my dev machine so that the next version will create 2 devices for your double switches. For the time being, you can just copy & paste an existing device & manually set the ids.
Before I publish the change I’d like to get this Scene control figured out. Thanks a bunch for posting the error in their forum too! I went ahead & added to that discussion the error that @hrannar is seeing.
Could have had this idea myself. Thank you 
On your Virtual Device proposal: I tried to do that and then realized that I do not want to monitor properties but actually call actions. So, what was a call for “PressButton” and a parameter with the number of the button in HC2 is now a call to a method of the VD. So, what I would need to do is generate a call like method or an own action. Can I configure a device and then a button on a UI to generate the equivalent to this?
curl -X POST “http://10.10.0.100/api/devices/784/action/test” -H “accept: /” -H “Content-Type: application/json” -H “X-Fibaro-Version: 2” -H “Accept-language: en” -H “Authorization: Basic xxxxxxxxxx” -d “{“args”:[”{}","{}"],“delay”:0}"
That way I can even solve the scene problem (as an intermediate patch) by writing a QA
Whenever you try to write to a property on a virtual device, the app will call an action named “set[property]”. So for your virtual device, just add a property called “scene” & an action called “setScene”.
Your other option would be to just create a virtual binary switch like this user has done. Then from the Home Remote’s perspective, it is just an ordinary switch.