Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@semilimes/node-red-semilimes
Advanced tools
The new semilimes connector which integrates with the public API
This Node-RED package lets you extend your semilimes experience with automation and IoT capabilities, such as the implementation of auto replies, booking flows, control dashboards or message-based interfaces, all exposed through your semilimes app.
Official semilimes API Documentation
You can install the nodes by either
using node-red's "Manage palette" in the side bar and searching for node-red-semilimes
or
running the following command in the root directory of your Node-RED installation
npm install @semilimes/node-red-semilimes --save
Some of the use cases of this node work more reliably when saving the necessary variables in a persistent storage. To ease this behaviour without adding complexity to the built flows, it is recommended to enable multiple context stores in your NodeRED configuration, so that you can use in-memory flow/global variables (deleted upon restart), or file variables, surviving a restart.
To enable the default implementation of multiple context store, add this configuration chunk in node-red's settings.js file.
To use the multiple-context in your flow, you can select the storage whenever you are dealing with a flow or global variable, like the example below:
Note: The default implementation of the file context in NodeRED makes sure that values are cached in memory and flushed to disk every 30 seconds, to preserve SD cards health in systems that make use of them (e.g. RaspberryPI). You can tweak this value to your liking by setting the appropriate variable in the configuration itself.
Learn more on the multiple context stores section in NodeRED documentation.
Install the semilimes app through the Official semilimes Website or by using the following direct store links
Access the semilimes Services website and login using the on-screen instructions
Create a subaccount
Enter billing information for the created subaccount
Request an API Key for your new subaccount
Add a standard inject
node
Add and connect a Sender
node, select Channel - Create
and give it a title. This will be your new channel name. Make sure you give a value to the Save ChannelId
property, you will reuse this later.
In the same node, configure its Connector
property to create a connection configuration, and enter your API key.
Add and connect a Message
node and select the Text
message option, then enter a message in the Text field.
Add and connect another Sender
node, this time for actually sending the message. Select Channel - Send
and configure its ChannelId
property with the one you previously saved in step 2.
Make sure you select the previously created Connector
in this node as well.
Run the flow and access your semilimes app with the subaccount corresponding to your API key. You will find a new channel containing your first message!
For reference, your completed flow should look like this
You can find all the provided examples by importing them from this Node-RED package, or you can explore and import them manually at this GitHub link:
The nodes are tested on linux environments with Node.js v19.2.0
and Node-RED v3.0.2
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
FAQs
The new semilimes connector which integrates with the public API
We found that @semilimes/node-red-semilimes demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.