Thoughts after one night: doesn’t seem quite stable 
Never had these disconnects with official integration.
Is that the state of your alarm panel? I dont have that issue
What addonn version are you using? How did you configure the proxy ?
try using my config, we are working/testing on the new addon to have a stable connection between panel <=> proxy <=> cloud , there are a few new config options in the json, copy paste mine, disregared the IP, its not used
"panelIp": "192.168.1.150",
"panelPort": 1000,
"panelPassword": XXXXX,
"panelId": "0001",
"watchDogInterval": 10000,
"cloudConnectionDelay": 10000,
"guessPasswordAndPanelId": false,
"Disable_RiscoCloud": true,
"Enable_RiscoCloud": true,
"autoDiscover": false,
"socketMode": "proxy",
"listeningPort": 33000,
"cloudPort": 33000,
"cloudUrl": "www.riscocloud.com"
Yes, that’s the state of the alarm panel. But all the other sensors show the disconnect as well.
Installed the forked add-on you referred to. Will check my json tonight or tomorrow.
Apart from the disconnects:
- Clock seems in sync on the physical panel.
- Official integration has ‘armed’ and ‘alarmed’ sensors, this one only has ‘alarm’. That’s the same as alarmed I guess? Fine for me though, I have no need for the individual armed sensors, only want to know which sensor triggered the alarm.
- I noticed some extra entities that are not in the official integration. Still have to look at what they all do.
- Speed looks ok.
Ok, check your config indeed, also just post your issue on this thread, i’m working together with the developer on this “new” addon
In the official addon, once there was an internet/tcp interrupt, it didnt reconnect to the panel/cloud anymore, thats now fixed, he improved reconnections
as you can see its a very big issue thread, just copy/paste your info/issue on it, its an addon in progress to make it better
Json was pretty much the same as yours, except “cloudConnectionDelay”: 10000 and “autoDiscover”: false
What do these settings do?
Changed them and restarted the add-on, let’s see if that’s any better. If not, I’ll grab some logs and put them on Github.
Auto discover, not related I think, the reconnect is for when Interner or network is down on local, the addon listen for new incoming connection from your panel…
Unfortunately, after 35 minutes another disconnect. I’ll take it to Github 
1 Like
I’m waiting how u guys are doing…
If its a succes i’ll change too
@skank fyi, still playing around with it. Keep getting the disconnects, @pergola.fabio doesn’t. So system dependent I guess… Puzzling issue for the code owner as well.
So for the moment for me:
- either stable integration without auto clock sync and no follow-me
- or the proxy addon with a few disconnects daily
Starting to think to just buy a new IP module that accepts multiple connections
1 Like
For me it was not possible to change only the IP board, my main board was not compatible… I’m stuck on 2.71 firmware…
How can you check it? Is it the FW version that HA detects?
EDIT - answer to my own question: yes
HA said “LightSys/RP432 Firmware: 5.28”, updated the firmware on the panel and now HA says “LightSys/RP432 Firmware: 6.07”
Wondering if the major firmware upgrade changes anything in my issues 
No idea about rls notes, but dont think it wil fix NTP issues
But i guess you can buy a multi socket TCP board, i cant, i have the older lightsys 2
I was hoping it would fix the disconnects towards the addon. Unfortunately not
Damn
Still following this here
Waht about the clock?
He is testing a.new addon version to see if the disconnect issues are resolved… If it works, then you have a solution using the addon
1 Like
hi guy’s
I have just started getting this erro when trying to arm any ideas Risco error: N12??
EDIT:
never mind guy’s it was just a Low Batt
I gave up and bought a new IP module that allows multi socket. Everything works like a charm now.
1 Like
Can you explain me where? how much it costs… can i see if i have the same module?
Risco RP512IP - IP Module multi-socket or Transmetteur IP RISCO RP512IP multi-socket pour Agility & LightSYS for example
If you have Lightsys 2 firmware v 5 or higher it should work.
Installation is pretty easy: turn off power, open cabinet, unplug battery connector (ignore siren or unplug it before ), remove old module, plug in new module, connect battery, close cabinet, turn on power.