Fabio, one last question: did you manage to upgrade your panel to version 5? Mine is stuck at 3.25.
No, I have older lightsys, I am stuck at 2.71 firmware
Probably I have a little more recent one but also not upgradable to the latest version. I assume you have RW132IP, not RP512IP?
Apparently I cannot use RP512IP with my panel and RW132IP is not available anymore, so sadly I guess Iâm stuck with GSM/GPRSâŠ
No idea about model, but I have a really old TCP module, only allows 1 connection⊠So I use the cloud proxy option
Then it must be RW132IP.
I hoped I could use IP as primary and GPRS as backup, but it seems to be possible only with the newer IP module and firmware version 5.
Wondering if itâs possible to make it connect to the cloud via GPRS only and still have the IP module around for direct connection.
I donât use direct connection, I use cloud proxy
So I took my chances and purchased RP512IP. For anyone that may face the same dilemma in the future:
Turns out the module works fine in LightSYS2 (installed in 2016, stuck and firmware version 3.25).
I can connect to it with risco-mqtt-local and at the same time the cloud still works over GPRS.
In one word: nice 
What is not supported with this old panel revision is using LAN as the primary cloud connection method and GPRS as a backup. But thatâs a minor thing.
Is it possible to activate the numeric dialer? My alarm does not show it, with the official Risco integration if it is available.
a greeting
you dont need dialer, because its using a service account already, so you can arm/disarm without a code
if you want one, that look for a custom card config
1 Like
You can turn on the use of code for arming or disarming (or both) in the integration options. Once you do, the UI will also display the numeric key pad.
If you use the local version, then there is no integeration, itâs based on mqtt
thanks to both of you for responding, but as the colleague says, local risco is for mqtt and does not give the option to enable the keyboard (at least for now) 
it would be great to have that option without having to resort to third parties
You can configure the MQTT Alarm control panel to request a code. See the options code, code_arm_required, and code_disarm_required:
The reason I canât use the local version is that I rely on group arming, which the local version doesnât yet support.
Hi,
Iâm trying to get this working - The connection to the panel seems fine, but the proxy doesnât seem to fire up and connect to www.riscocloud.com. Perhaps I am missing something - Any advice will be appreciated.
This is my config:
{
"log": "info",
"panel": {
"panelIp": "192.168.1.4",
"panelPort": 1000,
"panelPassword": 5678,
"panelId": "0001",
"SocketMode": "proxy",
"watchDogInterval": 10000,
"DiscoverCode": true,
"ListeningPort": 33000,
"CloudUrl": "www.riscocloud.com",
"CloudPort": 33000
},
"mqtt": {
"url": "mqtt://192.168.1.2:1883",
"username": "<redacted>",
"password": "<redacted>"
},
"zones": {
"default": {
"off_delay": 0,
"name_prefix": "Motion - "
}
}
}Thank you for the reply. Yes, I changed the cloud address under communication â Cloud to 192.168.1.2 (Docker Host) from www.riscocloud.com.
In the logs of the add-on I can only see a connection to the panel, I donât see any attempts from the container to connect to www.riscocloud.com.
i see it like below:
Loading config from: /config/risco-mqtt.json
6/27/2022, 2:04:38 PM [info] autoConnect enabled, starting communication
6/27/2022, 2:04:38 PM [info] Connecting to mqtt server: mqtt://homeassistant:1883
6/27/2022, 2:04:38 PM [info] Listening on IP :: and Port 33000
6/27/2022, 2:04:38 PM [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
6/27/2022, 2:04:38 PM [info] Connected on mqtt server: mqtt://homeassistant:1883
6/27/2022, 2:04:38 PM [info] Panel is not connected, waiting
6/27/2022, 2:04:46 PM [info] Incoming connection from panel received
6/27/2022, 2:04:46 PM [info] RiscoCloud Socket: ready
6/27/2022, 2:04:46 PM [info] Setting a timer for panel connection in 30000 ms
6/27/2022, 2:05:16 PM [info] Panel info: LightSys/RP432, FW 2.70
6/27/2022, 2:05:16 PM [info] Panel options: 4 parts, 32 zones, 14 outputs, Pir Cam support: false
6/27/2022, 2:05:16 PM [info] Starting devices discovery
6/27/2022, 2:05:16 PM [info] Retrieving System Information
6/27/2022, 2:05:17 PM [info] Retrieving zones configuration
6/27/2022, 2:05:36 PM [info] Retrieving outputs configuration
6/27/2022, 2:05:38 PM [warn] Command[5] Receipt of an error code: Device Doesn't Exists
6/27/2022, 2:05:38 PM [warn] Got error while fetching output 5 data: N19
6/27/2022, 2:05:38 PM [info] Output 5 does not exists, stopping outputs discovery
6/27/2022, 2:05:38 PM [info] Retrieving partitions configuration
6/27/2022, 2:05:38 PM [info] Panel and MQTT communications are ready
6/27/2022, 2:05:38 PM [info] Publishing Home Assistant discovery info
6/27/2022, 2:05:38 PM [info] [Panel => MQTT][Discovery] Published alarm_control_panel to HA on partition 1
here is my config, the ip 1.150 doesnt mather, that one isnt used
{
"log": "info",
"logColorize": true,
"panel": {
"panelIp": "192.168.1.150",
"panelPort": 1000,
"panelPassword": xxxx,
"panelId": "0001",
"watchDogInterval": 10000,
"guessPasswordAndPanelId": false,
"Disable_RiscoCloud": true,
"Enable_RiscoCloud": true,
"autoDiscover": false,
"socketMode": "proxy",
"listeningPort": 33000,
"cloudPort": 33000,
"cloudUrl": "www.riscocloud.com"
},
"mqtt": {
"url": "mqtt://homeassistant:1883",
"username": "xxxx",
"password": "xxxx"
},
"zones": {
"default": {
"off_delay": 0,
"name_prefix": ""
},
"GARAGE": {
"off_delay": 0,
"device_class": "garage_door",
"name": "Garage Door",
"name_prefix": ""
}
}
}
This part does not feature in my logs. Will adapt to as close as possible to yours and restart.