That’s exactly our use case: what you see in the previous messages are a couple of ways of filtering entities to have a list of the currently open windows or doors; this is a starting point to build an automation that triggers when the alarm is armed, using the template in the text of the message.
Since you have different integrations for opernings, you’ll have to make 2 lists and join them (this can be done in template).
As an alternative you could use a python script like a I did, but you’ll have to enter your openings manually and maintain the list when something changes.
how to disable the risco cloud so you can connect with an older system?
edit:
ok i did find it somewhere above:
anyone an idea why i get this error (i think i cant connect):
- i disabled the risco cloud
- i checked the panel access code
- i checked the ip of the alarm system
i also activated logging on the integration page of Home Assistant and i added following to configration.yaml:
logger:
default: info
logs:
homeassistant.components.risco: debug
i can’t see anything with “risco” in the system logs (home assistant core).
only this in the home-assistant.log file:
2025-05-07 17:12:34.090 DEBUG (MainThread) [homeassistant.components.risco.coordinator] Finished fetching risco data in 0.412 seconds (success: False)
do i have to look somewhere else to get more information whats failing when i try to set it up?
Hi all
I got a problem
My risco integration is working for months/years now.
I went away on vacation… for 2 weeks
Since i got back, its not working anymore.
The addon says it cant connect to panel
When i look into my unifi settings
it shows its unconnected.
With now and then short connected.
However when i ping it, it says its connected (although unifi says its not)
Even ipscanner finds it.
Any idea?
There has been a power down period too if that would have caused it?
I dunno
Tried rebooting too.
Hello! Has anyone figured out how to control programmable outputs from the control panel with the HA? That would be a fantastic option.
Hi guys, I recently discovered the possibility of disconnecting from the Risco cloud and activating everything locally.
Sorry to ask so many questions, but 345 pages are hard to read.
On the Lightsys keypad, the version information shows 5.64 (does this correspond to the firmware version?)
If I understand, from version 5 onwards, it’s possible to install the multisocket IP module to allow cloud and local coexistence. Where can I find the software and manual to configure it?
Is there only an Ethernet port, so do I need to run a LAN cable close to the control panel, or is it also possible to establish a wireless connection?
After installing and correctly configuring the module, is it possible to use the original version of the integration on HA? Is it possible to turn the alarm on and off, or just control the sensors?
@pergola.fabio I’m tagging you because you seem to be the most informed 
Thanks, and sorry for the so many questions.
I have the old board, it runs on 2.76, you have 5.x, so I think you already have the multisocket, so no need to disconnect cloud…
@pergola.fabio thanks
Regarding the installation of the card, where can I find the software and the manual?
Does the Home Assistant integration also allow you to activate and deactivate the alarm or just control the sensors?
Thanks in advance.
You can use the alarm panel, its all in the integration manual
Hi guys,
How can i re configure the integration? I just change routers and the IP of the panel changed…
Edit: Just delete and add again. All entity given the same name so my automations are solid.
Hello,
LightSYS+ is compatible with home assistant? Can I set a specific zone via HA?
Sensors are also availbele with HA?
Thanks
I have an old ass Prosys 128 system. Is it compatible with the integration?
I can add a ACM (TCP/IP module) but since it’s almost 2 decades old, wondering if it’ll work with HA
Hi
I’m getting this warning
The configuration for entity binary_sensor.risco_alarm_panel_panel_connection_status_2 uses the deprecated option object_id to set the default entity id. Replace the "object_id": "risco-alarm-panel-panel-connection-status" option with "default_entity_id": "binary_sensor.risco-alarm-panel-panel-connection-status" in your published discovery configuration to fix this issue, or contact the maintainer of the integration that published this config to fix this. This will stop working in Home Assistant Core 2026.4
Any chance to fix this?
Create an issue on GitHub for that, make it with the correct integration you are using… Devs are not watching here…
Made it
make sure to run : 2025.10.3, it was already fixed before
I am running Huidige versie: 2025.10.3
try to stop the addon, delete the mqtt device so all entities are gone, restart the addon
They will have new names then?