Risco Lightsys Alarm component

i dont know that model, just see if you can another second connection,… if not then use proxy, its as easy as that
with proxy , risco cloud is still possible, thats th purpose of the proxy, is a bridge between local and cloud

ok if i do so, i should disable risco cloud in the setting (json file) and restart the control panel or the IP module by deactivating it and then reactivating it in the configuration from the keyboard***
Not sure how to do that

So i just tried proxy first…
But i saved the config.json file in my config folder and started the addon… but nothing happens

the log of the addon says:

Risco local MQTT

Ophalen van het logboek van de add-on is mislukt: 502: Bad Gateway

So probably its not even starting?

1 Like

no idea, when you use proxy method, you need to change your risco panel, so it connects to your HA addon instead of www.riscocloud.com
read the readme
Socket Mode · TJForc/risco-lan-bridge Wiki · GitHub

I did, like 10 times already… all 3 pages lol
how do i change the risco panel then? i seem to miss that…

Where did you change that?
Had succes in running it locally?

you can change it with the risco software, if you are installer of your own panel, if not, you need to chage it on your inside lcd panel within the settings, just google a manual of your risco system

I dont have risco softwware (i didnt install the alarm)
I looked indeed at the manual https://www.ricor-security.nl/downloads/Gebruikers%20handleiding%20Risco%20Lightsys.pdf

But cant find any setting in there how to change the url it points to

google for the programmar manual, not that one
but you need to have the installer code, if you dont have it, then stop, its useless then

another way , if you have an advanced router, make an new route to forward outgoing traffic to another IP, its an iptable route on your gateway

i use this command below on my asus router, so dont have to change anything on my risco panel

iptables -t nat -I PREROUTING -s 192.168.0.26 -d www.riscocloud.com -p tcp --dport 33000 -j DNAT --to-destination 192.168.0.17:33000

.26 is the panel, .17 is my HA addon

ah! now we go a setp furher, i didnt know !
Found this https://www.alarmnu.nl/wp-content/uploads/2015/01/5IN1837LightSYSInstaller_Manual_NL.PDF

Thats the one then.
Perhaps the programmer code is still the default one
Phew what a manual to find it

Will see if i find it in there
If not, i can still try the direct way but then i wont be able to use the app anymore AND i will know how to restart my control panel or ip module

thats the one indeed, but you need the installer code
or use the iptables method
or dont use cloud anymore
or upgrade your TCP board to allow multiple connections

normally the person who installed the panel should give you the code, just ask

1 Like

I think i have the code (the manual speaks about the default code, so its probably the same)
But i cant find it in the manual lol
Will look a bit further

The iptables method , is a bit above my head (using unifi USG here)

Not using the cloud anymore might be an option, but then as i said, i will konw how to restart my control panel the or the ipmodule

Upgrade tcp board is not an option

So it narrows down :slight_smile:

Any idea why the addon isnt throwing a log?
You sure the json file is in the correct place right?

yes, my risco-mqtt.json file is in the root of the config folder

you need to change/find this setting on your panel , and point in to you addon

1 Like

i think indeed readme is wrong, you created config.json
needs to be :

ENV RISCO_MQTT_HA_CONFIG_FILE=“/config/risco-mqtt.json”

ah its not config.json but risco-mqtt.json
edit:

changed the json file to risco-mqtt.json, restarted addon, restarted HA but still nothing in the addon’s log :frowning:

Log from system:
Failed to to call /addons/c774f33c_risco-mqtt-local-addon/stats -

21:12:27 – (FOUT) Home Assistant Supervisor

Timeout on /addons/c774f33c_risco-mqtt-local-addon/stats request

21:12:27 – (FOUT) Home Assistant Supervisor

:frowning: this aint going smooth

  • Failed to to call /addons/c774f33c_risco-mqtt-local-addon/stats - 404 Client Error for http+docker://localhost/v1.41/containers/addon_c774f33c_risco-mqtt-local-addon/json: Not Found (“No such container: addon_c774f33c_risco-mqtt-local-addon”)

ok it seems that the addon doenst work yet for rpi
:frowning:
I will have to keep going the cloud route then for now

Then i come back to my original question:
For the integration i need an email, password and code

I made a new user but that one has no email and no password
Do i add a new user or new cp user? And what should the role be?
Both type of users dont have all 3 fields, so im not sure what to do
3 fields:
-email
-password
-code