Virtual Devices Tutorial

[ahmad89 0]

Hello,

Anyone has documentation to learn how to handle virtual devices in general so that I can work on adding any specific wants I have (projector...etc) ?

Regards

[ Added: 2014-06-09, 16:24 ]

Any help with this ???

[ Added: 2014-06-09, 16:24 ]

Any help with this ???

[MalvinYNJ 4]

No documentation but Google has vast knowledge for you.

[ahmad89 0]

The issue is I do not know what to google to be honest.... Is it a general knowledge thing or specific per device?

[j.nowacki 5]

Could you please specify your problem? Maybe give us example of device you want to create? Or search for ready examples of devices posted by users of this forum.

[ahmad89 0]

There is no specific device, i am just speaking in general, i have seen some examples of controlling other devices on the network.via virtual devices like the example of a lock on a vera controller... i just wanted to know what i can study on my own to know more about the concept of virtual devices...

[j.nowacki 5]

I think the best way to do this is to study exiting cases, importing devices from forum and looking at the code. Feel free to ask questions here if you don't get the way something works.

[monions 1]

We're working on a new application note about Virtual Devices, how to use them and what the different settings are.

They're quite easy - once you understand how they work

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

We already have some examples available for controlling iTach devices and the Sprinkler panel - these show how to create the virtual device and how it does what it needs to for that example. But we're going to have a more generic introduction. Same as we've done for the Block Editor Scenes.

We plan to have this available by the end of next week.

[evanbeem 2]

We're working on a new application note about Virtual Devices, how to use them and what the different settings are.

They're quite easy - once you understand how they work

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

We already have some examples available for controlling iTach devices and the Sprinkler panel - these show how to create the virtual device and how it does what it needs to for that example. But we're going to have a more generic introduction. Same as we've done for the Block Editor Scenes.

We plan to have this available by the end of next week.

 

Hi Mark,

 

I looked at Vesternet, but that particular APP note is not on the site. It would plug an enormous hole in the available knowledge about this Fibaro feature.

Is it still planned to have it available for the world?

 

Regards,

Erwin

[KIMSHA 0]

I think the best way to do this is to study exiting cases, importing devices from forum and looking at the code. Feel free to ask questions here if you don't get the way something works.

Can you please explain the following as I have a Yale lock that will not work with Fibaro and want to get it to work as per this method:

I am having real trouble understanding how to write the following into a virtual device, can you please assist?

 

 

I.e., add your locks to Vera3 / Lite and control them via virtual devices in HC2.

Code is very basic (note DeviceNum=6 - it means sixth device on Vera3):

Open button:

HC2 = Net.FHttp("172.16.1.111",3480)

response,status,errorCode = HC2:GET("/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=1")

fibaro:log("Night Latch Lock command sent")

Close button:

HC2 = Net.FHttp("172.16.1.111",3480)

response,status,errorCode = HC2:GET("/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=0")

fibaro:log("Night Latch Unlock command sent")

Request status and change icon:

local selfId = fibaro:getSelfId();

HC2 = Net.FHttp("172.16.1.33",3480)

response,status,errorCode = HC2:GET("/data_request?id=variableget&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=Status")

fibaro:log(response)

if response == "0" then

fibaro:log(status)

fibaro:call(selfId, "setProperty", "currentIcon", "1004")

--fibaro:log("lock opened" )

else

fibaro:call(selfId, "setProperty", "currentIcon", "1003")

-- fibaro:log("lock closed")

end

fibaro:sleep(60*1000);