tcp socket service interaction with virtual devices

[pos 22]

Hi

This is a question of how to best implement devices and interaction with a tcp socket service. I was going to buy DSC IT-100 to make a link between HC2 and my DSC alarm. But as I also needed an serial to ethernet unit and at the same time saw that Envisalink actually directly exposes the same low level API against the DSC alarm as the IT-100, I chose an Envisalink 4….

 

Now…
I am not going to use any Fibaro HC2 plugin for this. I am going to build a LUA TCP socket connection myself and implement the DSC low level API against my DSC PC1616 alarm.

 

QUESTION:
Lets assume I have this TCP socket service up and running in an autostarted LUA service that is always up and running and maintains the connection to the PC1616 alarm and receives data when stuff happens in the alarm. Now… When I receive a zone breach from one PIR in the PC1616 alarm to the tcp socket service written i Lua, how do I best make this “trap” available to other scenes. I mean, normally such a trap comes directly from a device where you could create a scene trigger from the devices “value” as a scene trigger.

Is there a way to use virtual devices for this? how?

What I really wonder is how to be able to threat all my 14 PIR:s and door sensors from my PC1616 alarm as different devices where I can just get its “value” to see if it’s breached or not.

Is there a way to send fake triggers? I mean.. Can I from my constantly run tcp socket service send out a trap and fake a source device ID as it would have come from from for example an fibaro motion sensor?

 

Any smart suggestions would be very appreciated

 

Thanks in advance

Peo

[pos 22]

One way is probably to let the tcp socket service auto update global variables that in turn is used as triggers for other scenes.

 

But ideally I want to if possible, handle a tripped PIR in the DSC alarm in the same way as a tripped PIR in a fibaro motion sensor. But the fibaro motion sensor is a device where you could trigger on its "value" or just read it from the device ID, whereas the info from the PIR in the DSC alarm comes to the TCP socket service and need to be handled there.

 

Peo