Disable cloud on it, that will open the 1001 port
Or don’t use the official integration, and stick with the addon , scroll up a few posts
Thanks. Disabled it and ports 1000 or 1001 are closed… I have tried also a portscan, no success.
maybe a reboot of panel is needed? i never tried it, i still have ckoud enabled and i use the addon with proxy, not the official integration
i also have old TCP board, where the ports are closed
I’ll try… there is abolutely no documentation on this. I may also test the SIM card elsewhere to confirm there is no NAT issues.
It’s indeed difficult, remember, this integration is reverse engineering, that’s why it’s indeed difficult
I confirm that after a reboot ports 1000 or 1001 remain closed.
How did you disable cloud? On the panel itself?
I never tested it, but normally if you disable cloud, it should open the port, because it’s used for the CS software…
Yes, on the panel itself. I have also checked if the problem could be in the NAT but all seams fine…
Hmm, not sure why it’s closed for you…
I don’t use the integration, I still use the addon , because I don’t want to disable cloud… So I use the proxy
dont see anything usefull there?
Does anyone know if there’s a way to speed up the “polling” interval? I’ve connected the alarm directly but 1 sec goes by between motion detection and actual mqtt topic being populated.
Hmm, for me it’s instant, no delay
What alarm panel (model) and what sensors (models) are you using?
Using lightsys panel, with BDM sensors
Has anyone tested the latest local integration that @onfreud has created? I can’t seem to connect using the latest integration, however I can connect using the vancko nodejs container with MQTT connect to it.
Same issue here. Couldn’t get the local integration to work so went back to the add-on.
Please report it to GitHub with logs, so Onfreund can have a look
Hi there. I have a Risco light sys home alarm and the app works fine on my phone. However, when adding the integration to home assistant i get the error in the attached image. The error text in the log is the same.
this was previously working for me before i created a brand new VM.
all help appreciated
thanks
paul
report an issue to github, the project owner doesnt visit this forum