Yea, that’s the one I used. I guess the addon install itself went fine as I even got an update yesterday. But getting it to start is a no-no…
So just installing the addon via custom repository, putting the json in the config folder should work (at least to get the addon running)?
Strange, works for me , indeed config file is enough…
Otherwise create a ticket there , the owner is quite active
I’ve the same issue, ticket has been opened on github but no response…
I’ve seen someone which seems to have locally copied the addon but I ve no idea about how to do it
I have it running for a long while now… No issues for me
The docker image is not built for every architectures, so no support for raspberry for now. Honestly I don’t know how to build the image for all architectures and I have no time to have a look at it currently.
Open to contributions : GitHub - vanackej/risco-mqtt-local: Provide Risco alarm system integration to Home assistant using local TCP communication (no cloud required) and MQTT
It can be used without docker / HA addon easily in the meantime : GitHub - vanackej/risco-mqtt-local: Provide Risco alarm system integration to Home assistant using local TCP communication (no cloud required) and MQTT
I have this running on HOAS rpi4 (arm64/v8) after a few hours tinkering.
if running Hoas you’ll need ssh access to the host.
grab a copy of the source from GitHub. HOAS rpi image doesn’t come with git, so grabbing a tar.gz via cURL is the easiest option here. I put the source files in /mnt/data, which is where Docker working files live.
once you’ve got the source, create a config.json file from the provided template
edit the Dockerfile - needed to include npm and typescript dependencies.
rebuild the docker image for target architecture. I used -t so the references to the original repo points to my newly built Docker image:
> docker build -t vanackej/risco-mqtt-local:v0.4.2 ./risco-mqtt-local-0.4.2 --platform linux/arm64/v8
>docker run -v $(pwd)/config.json:/data/config.json <YOUR_DOCKER_IMAGE>
If successful, you should see the docker container startup instead of ’[FATAL tini error]’
So far, so good. Now I just have to get it talking to my alarm panel.
Caveat: I have just enough Docker knowledge to be considered dangerous. I’m unsure whether above is the correct approach and pretty certain I’m breaking more than a few ‘good practice’ rules here. Dealing with updates is going to be a pain but just testing the concept for now.
Update to my previous comment: it looks like @vanackej and the project team have just released multi arch support! (Thank you!)
Yes indeed, I just published 0.5.0-beta.1 version, with arm64 arch support.
Anyone experiance settting up an TCP Proxy ?
A PR is coming to the HA core intergration to add local support, so not only cloud
But the new local integration doesnt support a proxy (for people with older TCP boards)
Who can help setting this up? Then we can create an seperate TCP proxy addon for that
thnx
Are you saying that risco will have an official integration for running local?
Yes, it’s coming very soon, code is converted to python
Hallo Ignacio. I have the same problem, have you solved it?
Hi Paul
Yes it is solved. In the Configuration menu i found a way to map buttons with actions. I don’t remember exactly how but i fixed using configuration mapping
Ok, enter configuration for risco component, once you set initial parameters and press OK, there is a Second step that allows you to configure mappings
Hi,
Any news??
Is same??
thats the addon, but not based on Python, but same local connection yes, also supports a proxy
the integration thats coming tomorrown is based on python and its an official one, but lacks a proxy
thank you very much for the clarification.
If it’s tomorrow, maybe I’ll wait for the official one, almost better.
One doubt:
I don’t quite understand the use of the proxy here.
Could you give me some more details for the use of the proxy?
thankssss
proxy is only requiered if yout have al old TCP board, does boards only allow connection
so if you still want to use risco cloud AND loca intergation, then you need
a) a proxy (listener between cloud and local)
b) disable the cloud
c) but a new board that allows multiple connections (cloud and local)
oki thank you.
The new version with the official local functionality has been released.
I have tried to configure it.
I add IP Host of my PBX, default port 1000 and my PIN.
I get “Unknow Error” after a few minutes.
And the following appears in the HA log:
Maybe your board doesnt allow multiple connections? What Risco system do you have? Do you have a multi tcp socket board?
Also you don’t need to provide the pin to connect, you need the fill in the code to allow connection, it’s not the same as the pin (it’s called the “access code”, default it’s 5678)
