pos

https://marketplace.fibaro.com/items/dsc-power-series-alarm-integration Regards Peo

You have not read the documentation PDF ? You fix this as a part of the setup by changing the zones multi variable. Amount of zones and the names you want. There are more to adjust. User names for example... I suggest you go through the PDF PS And if you after the final configuration like it, please rate it at Fibaro marketplace Regards /Peo

You can try this and see if you like it. https://marketplace.fibaro.com/items/dsc-power-series-alarm-integration If you like it, it would be nice if you rated it And there is an update on the way. Probably before christmas. /Peo

B t w.... This is from the DSCengine docs regarding your setup. --snip-- DSC IT-100 with Global cache Right now this option is considered a beta as it is not yet very well tested and introduced in DSCengine 3.0. I have no indication though that it shouldn’t work ok. For this the following hardware is used: - Global Cache' iTach Flex with Flex Link RS232 Serial cable - DSC IT-100 serial card Install the Global cache per its instructions and make sure it can communicate on the network. Install Global Cache iHelp tool to find IP address of Global Cache. Log in to the Global Cache, change from IP to Serial, set baud= 9600, Flow Control= None, Duplex= Half, Parity= None, Databits= 8, stop bits= 1, Gender change = false Modify the DCFG_SETUP predefined variable and set: - DSC_INTERFACE to 1 - IP to the IP address of the global cache (port 4999 is hard coded in DSCengine) Note that there is no bind with user and password using this solution. So make sure it is just used internally! Many thanks to Chris Swan for making this IT-100 option possible by doing initial testing as the author has no such device.
 --snip-- /Peo

Hi I have this code also uploaded to Fibaro Market place https://marketplace.fibaro.com/items/dsc-power-series-alarm-integration. I think there is some info in the attached PDF documentation regarding IT-100 and global cache that maybe can help you. Also check the release notes text file. I use envisalink myself, but added support for your setup to DSCengine after some mail ping pong with another user that wanted to use DSCengine but did not have an envisalink. PS A new DSCengine release is coming out soon. If I have the spare time it will hopefully be within a couple of weeks. Regards Peo

@danveedan Did you update your question after my answer? Or did I miss the info of your model I *guess* (not 100% sure though) your alarm is not compatible as later DSC alarms has a closed API (open to a few integrators). Z-wave you say. It could be proprietary as some stuff from Danfoss. Do you have any more info?

What spec do you have of the DSC alarm? Is it a Power Series alarm? What model is it? Regarding connection options: Is it a TL260GS or similar? Or maybe an IT100 serial card with an serial to wifi or eth add-on.

When I started with Fibaro HC2 2017 I saw the DSC plugin. As I have a DSC alarm I tried to use the plugin. The person who made that does not even know the difference between a zone and a partition. Crappy plugin with no usable features. Therefor I asked Fibaro (after looking at the developer API docs) if and how to act to create a better one with more features. For free.... They gave me the very same answer as seen in this thread. I.e that it was no longer possible. Therefor I instead as a work around created a VD https://marketplace.fibaro.com/items/dsc-power-series-alarm-integration. I got good feedback on that. But still.... There are however features that want to add that is simply not possible to do with a VD, but can be done with a real plugin. And some features that I have added was tricky to accomplish as the lua docs about what is limited in the sandbox is non existent. Sharing with guys like sankotronic, tinman and petergebruers solved a few things. So I also want a good answer from Fibaro. I think of leaving the Fibaro platform as it is so locked. And if you have problems, you cannot even look at your own logs as the system is locked regarding access to the underlying OS (I guess it is maybe possible to open the box and boot in single user mode though). And Fibaro rarely answer questions.

# DSC Powerseries! - Works with The DSCengine virtual device from Fibaro marketplace (both with envisalink add-on card and with the DSC serial card) - Works with the Fibaro built in DSC plugin if using an envisalink add-on card # The Neo series has a closed API. - Does not work

Hi @nicopret I see what you are trying to achieve. It is doable. I think you have to use net.HTTPClient() in scenes. Try that and get back if you do not solve it. Regards peo

Hi The only relevant question on the FAQ is "I cannot log into the gateway. What should I do?". But as The HC2 is correctly configured and the old app is working as it should, all statements there are irrelevant. As I am a network guy since 1996, I have total control of firewalls, TCP/IP, and is classified by others as an expert of TCP/IP. In this case the local access when at home is on the same LAN and no FW is involved. And... the old legacy Fibaro APP is working. Of course I could test to enable remote access, event though I do not want it. But I thought I would as here first.... Regards Peo

Hi I just downloaded the new Fibaro app in IOS. It does not work to login. Is enabled remote access a requirement now? If so, I will simply skip the new app. Today I use the legacy app over local LAN and over VPN to home from outside. I.e remote access is not enabled from internet. So I just try to login the same way in the new app as in the old one. And it does not work. Any clues appreciated... Tnx Peo

Enable debug and restart. Then check the logs so you see the issue

If you use Linux or UNIX, you have a syslog service build in. If you use windows you can install *any* syslog software service running on windows. I suggest you install a free syslog service. If you install it on your computer, make sure the local firewall accept incoming syslog traffic and that the syslog service autostart at boot. Then... In DSCengine:s config variable DCFG_SETUP, set the syslog IP variable to the IP of your windows computer running the syslog service. Also enable syslog (this is another DCFG_SETUP variable) See quick guide.... Then restart DSCengine so it pick up the changes and it works... This is what it could look like with basic debug level... /Peo

The question mark is explained in the quick quide. I *really* suggest you read the quick guide..... --snip-- --snip-- /Peo Regards Peo