
Product
Introducing Repository Access Permissions and Custom Roles
Socket now supports Custom Roles and Repository Access Permissions so organizations can control who can access specific repositories and actions.
iobroker.openwrt
Advanced tools
This Adapter interacts with the OpenWrt RPC API of a OpenWrt-Device (Router, Switch, AccessPoint, RaspberryPI, etc.).
Reading data from ubus to ioBroker-Objects: At the moment only the "ubus call" results are fetched. With that commands you should get the most data out of the router. The json-results are parsed and written to the objects database, see here [ubus]
Setting data with ubus from ioBroker to OpenWrt:
You can send Commands to the router over the API with the State-Object "sendCommand".
Put in the command you want to send to the router, the result will be written as JSON-Object to the "sendCommandLastResult" Object and the "sendCommand"-Object will be cleared.
To enable the API, install the following package and restart uhttpd:
opkg install luci-mod-rpc
/etc/init.d/uhttpd restart
Source: HowTo at the official OpenWrt-Github-Repo
To check that the API ist working fine, just navigate to this url with your webbrowser:
http://[TargetDeviceIPorHostname]/cgi-bin/luci/rpc/auth
If you get something like this, the API is successfully installed:
{"id":null,"error":{"message":"Parse error.","code":-32700},"jsonrpc":"2.0"}
Side-Note: The URL-Check on the "admin"-Page checks for "jsonrpc" text in response
Type the URL, Username and Password (same as the SSH/Webinterface) in the admin page
If everything works fine, you will see the new Objects:
If there is something wrong, you can check the communication at the admin-panel.
First the URL should be "OK", test it with the "Check URL"-Button.
Second the Authentication with user/pass can be tested with the "Check Auth"-Button.
If there are some error's the button will get red, look at the ioBroker-Logs for more informations .
MIT License
Copyright (c) 2022 Schnup89 tobias_tsafi@gmx.de
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Interact with the openwrt RPC API
We found that iobroker.openwrt demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.

Product
Socket now supports Custom Roles and Repository Access Permissions so organizations can control who can access specific repositories and actions.

Product
Socket MCP now lets AI assistants review org alerts, investigate threats using the Socket threat feed, and inspect package files in addition to dependency scoring.

Product
Socket Firewall blocks malicious VS Code and Open VSX extensions before install, protecting developers from compromised editor marketplaces.