# Node-red-contrib-threema

**URL:** https://discourse.nodered.org/t/node-red-contrib-threema/80960
**Category:** General
**Tags:** docker, iobroker
**Created:** [31 August 2023 18:57 UTC](https://discourse.nodered.org/t/node-red-contrib-threema/80960 "2023-08-31T18:57:03Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![My\_Millenium](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@My\_Millenium](https://discourse.nodered.org/u/My_Millenium)
#### Post date: [31 August 2023 18:57 UTC](https://discourse.nodered.org/t/node-red-contrib-threema/80960/1 "2023-08-31T18:57:03Z")

</div>

Is here anyone who uses node-red-contrib-threema in node-red successfully?  
I have installed the Python SDK as described [here](https://gateway.threema.ch/en/developer/sdk-python) and due to some error-messages in the terminal I also installed libsodium-dev.  
Via command line I am now able to e.g. retrieve my credits or to retrieve the public key of any Threema ID (since this works I suppose that the SDK is properly installed and configured).  
But these nodes do not work (msg.error is "Error: spawn /opt/ioBroker/threema-gateway-venv/bin/threema-gateway ENOENT"

Node-red is running as an adapter in IOBroker which is running in a Docker-container on a Synology.  
The path to the Threema gateway files is /opt/ioBroker/threema-gateway-venv/bin/threema-gateway.  
The path to the private key is /opt/ioBroker/threema-gateway-venv/bin/privatekey.txt

I am stuck. I Hope that anyone can help....

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [30 October 2023 18:57 UTC](https://discourse.nodered.org/t/node-red-contrib-threema/80960/2 "2023-10-30T18:57:54Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
