Risco alarm system

Hardware
,
263

Change everything and using daytime now, but without luck to sync :frowning:

Its getting worse lol, it was working before, now it says theres something wrong my json, although i didnt change a thing.
I even recopied everything to be sure, but still error

Loading config from: /config/risco-mqtt.json
Startup error SyntaxError: /config/risco-mqtt.json: Unexpected token } in JSON at position 358
at parse ()
at Object.Module._extensions…json (node:internal/modules/cjs/loader:1266:39)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object. (/app/dist/main.js:23:24)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)

image
image452×521 9.51 KB

264

You are not using the proxy anymore?

265

What do you mean? Yes i am…
In the risco panel, i didnt change the ip adress from the cloud, its still pointing to my HA device

266

Your json needs the proxy setting, otherwise it won’t work.

“socketMode”: “proxy”,

267

Also there is an extra comma that shouldn’t be there on the line with the off delay, that’s causing the json error.

268

Yeah , but you don’t configure the addon to use the proxy, it was still a direct connection…

Earlier you posted my config and now you post a total different config?

269

Ohhh no i never used that

270

yup that fixed it.
Im gonna stop it again and add the socketmode line
Anything else?

271

RiscoCloud Socket: ready

Aha!
So maybe now the clock will adjust too?

272

If you start the addon with the proxymodz enabled, do you see the panel connecting now? You should see it in the log, it can take up to 2 minutes…

Make sure that you have cloud enabled on your panel, because it’s probably not… Otherwise you the addon in non-proxy mode should never work, and in your case it did…

273

Use these settings…

    "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"
274

If everything is OK, it should look like this:

Screenshot_20231230-055700
Screenshot_20231230-0557001080×2340 181 KB

275

No need to i think.
Everything is back up, and the clock on the panel synced now!

However i do see errors in the addon log

image
image1260×802 27.8 KB

276

Ignore those warnings, they are normal! I have them too

277

Ok so all working well now, thanks a lot !

278

Finally :slight_smile:

279

Yeah sorry :slight_smile:

280

Hi, this add-on is compatible with lightsys+? thanks

281

Did you try it?

282

Hey there!
I’m trying to use the risco-mqtt-local addon for my risco panel using it locally (so no cloud!). I am however unable to connect to my panel with the following showing in the logs:

1/25/2024, 12:03:11 AM [error] Command[1] error: Error: write ECONNRESET
1/25/2024, 12:03:11 AM [error] Socket Closed.
1/25/2024, 12:03:11 AM [error] Risco command error: TIMEOUT. Command: {"panelId":1,"commandId":1,"attempts":1,"crcOk":false,"commandStr":"RMT=XXXX","sentBuffer":{"type":"Buffer","data":[...]}}

where data is an array of random looking numbers. I know for a fact the access code and IP address are correct. What am I missing? Thanks!