Zone name and type not working on a multi-alarm deployment

[stezak77]

I'm using this node red integration to control two different alarm systems connected to the same network, each one with its own ip address, port and credentials.
All zone properties are correct except for zone name and type.
Names and types of the second alarm system zones are evaluated from the first alarm system zones.
The issue should be due to zone caching implemented at global level instead at alarm instance level.

[maxill1]

You are right. I will remove the cache from global context in next release. Thank you.

[stezak77]

Thank you :)

[maxill1]

0.1.3 is out with cache on server node. I can't test it directly since I don't own two alarms. Please let me know if the fix is working.

[stezak77]

Thank you for the prompt fix. I tested it and works great now.

[stezak77]

Hi @maxill1 I think this issue can be closed