pv-power-control adapter for ioBroker
Adpater to control the pv power to manage devices like wallbox
This section is intended for the developer. It can be deleted later
You are almost done, only a few steps left:
Create a new repository on GitHub with the name
Initialize the current folder as a new git repository:
git init -b main git add . git commit -m "Initial commit"
Link your local repository with the one on GitHub:
git remote add origin https://github.com/Newan/ioBroker.pv-power-control
Push all files to the GitHub repo:
git push origin main
Head over to src/main.ts and start programming!
We've collected some best practices regarding ioBroker development and coding in general. If you're new to ioBroker or Node.js, you should check them out. If you're already experienced, you should also take a look at them - you might learn something new :)
Several npm scripts are predefined for your convenience. You can run them using
npm run <scriptname>
||Compile the TypeScript sources.|
||Compile the TypeScript sources and watch for changes.|
||Executes the tests you defined in
||Tests the adapter startup with unit tests (fast, but might require module mocks to work).|
||Tests the adapter startup with an actual instance of ioBroker.|
||Performs a minimal test run on package files and your tests.|
||Performs a type-check on your code (without compiling anything).|
||Translates texts in your adapter to all required languages, see
||Creates a new release, see
Configuring the compilation
The adapter template uses esbuild to compile TypeScript and/or React code. You can configure many compilation settings
tsconfig.json or by changing options for the build tasks. These options are described in detail in the
When done right, testing code is invaluable, because it gives you the confidence to change your code while knowing exactly if and when something breaks. A good read on the topic of test-driven development is https://hackernoon.com/introduction-to-test-driven-development-tdd-61a13bc92d92. Although writing tests before the code might seem strange at first, but it has very clear upsides.
The template provides you with basic tests for the adapter startup and package files. It is recommended that you add your own tests into the mix.
Publishing the adapter
Using GitHub Actions, you can enable automatic releases on npm whenever you push a new git tag that matches the form
v<major>.<minor>.<patch>. We strongly recommend that you do. The necessary steps are described in
Since you installed the release script, you can create a new release simply by calling:
npm run release
Additional command line options for the release script are explained in the release-script documentation.
To get your adapter released in ioBroker, please refer to the documentation of ioBroker.repositories.
Test the adapter manually with dev-server
Since you set up
dev-server, you can use it to run, test and debug your adapter.
You may start
dev-server by calling from your dev directory:
The ioBroker.admin interface will then be available at http://localhost:8081/
Please refer to the
dev-server documentation for more details.
- (Newan) initial release
Copyright (c) 2022 Newan email@example.com
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.